-
Notifications
You must be signed in to change notification settings - Fork 800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jetpack Manage Banner: Add tracking info to the CTA and update event names in Jetpack #35378
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
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. Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Backup plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Boost plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Search plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Social plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Starter Plugin plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Protect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Videopress plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Migration plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a couple of failing tests as well. One of them is just to merge trunk, so no worries about it, but I tried to rerun the E2E test earlier today and it didn't fix anything.
The E2E test is something about not being able to fetch credentials, so it seems very unrelated to this PR; so maybe merging trunk will fix it? 😄
projects/packages/my-jetpack/_inc/components/jetpack-manage-banner/index.jsx
Outdated
Show resolved
Hide resolved
projects/packages/my-jetpack/_inc/components/jetpack-manage-banner/index.jsx
Outdated
Show resolved
Hide resolved
projects/packages/my-jetpack/_inc/components/jetpack-manage-banner/index.jsx
Outdated
Show resolved
Hide resolved
Yep, it's unrelated; I saw the same error in other PRs. I already recalled where I borrowed that code from the previous existing banner: https://github.com/Automattic/jetpack/pull/35283/files#diff-30fa007f36904a42a4886e3ce92058f8c3d9b155fe46f13246ca382c83eb76e1 The thing is that we cannot use arrow functions in props, and probably that is the reason why they all are wrapped into a In the end, I updated the code, but the click handling is almost the same, only minor tweaks. |
524e656
to
2e79ab4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and manual testing is working as expected (verified via Tracks live view)
…names in Jetpack (#35378) * Add tracking info to the JP Manage banner clicks * Update the trackEvent target in Jetpack dashboard * changelog * Update My Jetpack package version * Add changelogs after my-jetpack package update * Add the view event to Manage Banner in My Jetpack * Add the view event to Manage Banner in Jetpack dashboard * Code tweaks. Removing unnecessary useCallback hook.
Fixes https://github.com/Automattic/jetpack-manage/issues/271
Add better tracking to the two Jetpack Manage banners (they exist in the My Jetpack package and the Jetpack plugin).
Proposed changes:
We aim to improve tracking by listening for all button/link clicks and when the banners are viewed.
We're adding in a "viewed" track as well since the banner is conditionally loaded, so just using page visits would not give an accurate enough representation of usage.
This PR adds tracking info to the CTAs in the Jetpack Manage Banner in My Jetpack:
Tracked events - My Jetpack
jetpack_myjetpack_manage_banner_view
jetpack_myjetpack_manage_banner_click
manage
target: jp-manage-learn-more
target: jp-manage-dashboard-sites
target: jp-manage-sign-up
Tracked events - Jetpack dashboard
jetpack_manage_banner_view
manage
/dashboard
jetpack_wpa_click
manage
/dashboard
target: jp-manage-learn-more
target: jp-manage-dashboard-sites
target: jp-manage-sign-up
Other information:
Jetpack product discussion
https://github.com/Automattic/jetpack-manage/issues/238
Does this pull request change what data or activity we track or use?
Yes. It adds 4 new tracking event as described in the "Proposed changes" section.
Testing instructions:
/wp-admin/admin.php?page=my-jetpack
(with and without a Jetpack Manage user, with 2 or more sites attached to them)jetpack_myjetpack_manage_banner_click
events are triggered with expected targets:-
target: jp-manage-learn-more
-
target: jp-manage-dashboard-sites
-
target: jp-manage-sign-up
/wp-admin/admin.php?page=jetpack#/dashboard
(with and without a Jetpack Manage user, with 2 or more sites attached to them)jetpack_manage_banner_view
event is triggeredjetpack_wpa_click
events are triggered with expected targets:jp-manage-learn-more
jp-manage-dashboard-sites
jp-manage-sign-up