-
Notifications
You must be signed in to change notification settings - Fork 798
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
IDC: Event tracking for the new screen #21900
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
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 (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
Backup plugin:
|
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.
Nice cleanup, still tests well for me 👍
The localStorage.debug = "dops:analytics";
did work for me this time around. Chrome dev tool's default logging level doesn't include "verbose" which the events show up under.
Go to Jetpack Dashboard, confirm that you see the IDC screen, and do not see the dashboard itself.
This is a little bit different from #21822 since we aren't showing the new IDC screen on the JP Dashboard in this PR, but was able to see the jetpack_idc_start_fresh
event fire okay from the Connection Manager screen.
Good call, I missed that while copying the testing instructions. |
Great news! One last step: head over to your WordPress.com diff, D70779-code, and commit it. Thank you! |
r235862-wpcom |
* master: Added a custom composer installer to use a separate vendor folder. (#21877) Masterbar: rewrite tracks-events.js without jQuery (#21907) pre-commit: Run `eslint --fix` like we do `phpcbf` (#21923) Hide licenses activation route when user account not linked. (#21919) Beta: Handle exception when no Internet connection (#21915) Update wordpress monorepo (#21918) Pin dependency automattic/wordbless to 0.3.1 (#21920) Use new GitHub secret to manage pushing to Project Boards (#21838) Backup: provide additional disconnect info in backup plugin (#21421) IDC: Event tracking for the new screen (#21900) Releases: add testing list for Jetpack 10.4 (#21909) Jetpack 10.5-a.0 Cycle Start (#21912) Jetpack 10.4: Changelog (#21908) Add/contextualized jetpack connection (#21815) Fix masterbar not being displayed entirely for resolutions of under 660px. (#21871) Handle the intermittent occurrence of null in `columnWidths[ rowIndex ]` array in TiledGallery (#21892) Add to My Plan's header section a small licensing-related piece of copy (#21899) Sharing: ask search engines to not index pages with query string. (#21843) PR Template: Indicate use of milestone (#21898) Likes: add some extra checks to queuehandler.js (#21896)
Extracted from #21822
Changes proposed in this Pull Request:
Jetpack product discussion
p9dueE-3Mn-p2
Does this pull request change what data or activity we track or use?
New tracking events were not introduced, only migrated existing ones to the new IDC package.
Testing instructions:
jetpack build packages/connection-ui
.Main screen
localStorage.debug = "dops:analytics";
to see the tracking events. Keep the console open, and activate the "Persist Log" feature.jetpack_idc_notice_view
and"notice-view" in group "jetpack-idc"
Stay in safe mode
jetpack_idc_confirm_safe_mode
andconfirm-safe-mode
.Move your settings
jetpack_idc_migrate
and"migrate" in group "jetpack-idc"
.Fresh connection
jetpack_idc_start_fresh
and"start-fresh" in group "jetpack-idc"
.