Launchpad: verifying email sends appropriate launchpad track event

[p-jackson]

Fixes Automattic/wp-calypso#99456

Proposed changes:

Other tasks record a wpcom_launchpad_mark_task_complete event when
a task is detected as completed. Nothing is recording this for email
verification though. We should record an event for this just like
every other task.

WPCOM fires a wpcom_email_verification_complete action when the
user verifies. We hook into that action here in Jetpack.

Email verification links send users to signup.wordpress.com not
public-api.wordpress.com. So it must use a different authentication
mechanism which is why I'm not trusting the wp_get_current_user()
function call like the other tracks events do. Using the user ID
from the action parameter is how other action handlers in WPCOM do
it too. See this example 36e9b-pb

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Tracking email verification task is the same sort of data we already track for other tasks. No changes
to our existing data usage.

Testing instructions:

• Apply this PR to your sandbox
• Sandbox signup.wordpress.com
• Create a new user
• Copy the verification link sent to your inbox
• Use this JavaScript snippet to extract the redirect_to URL out of the link
  • new URLSearchParams(new URL(' ... ').search).get('redirect_to') (substituting the link for the ...)
• Use your Tracks Live View and wait 10m for your event to appear. Filter by your new user's id and the wpcom_launchpad_mark_task_complete event
  • Alternatively you can add some logging to the line which records the track event

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the update/send-wpcom_launchpad_mark_task_complete-when-email-verified branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/send-wpcom_launchpad_mark_task_complete-when-email-verified
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[github-actions]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/jetpack-mu-wpcom/src/features/launchpad/launchpad-task-definitions.php	654/1506 (43.43%)	-0.14%	5 💔

Full summary · PHP report · JS report

[vykes-mac]

Event recorded great!!