WooCommerce Analytics: require package in the Jetpack plugin

[jeherve]

Fixes #35631

Proposed changes:

Important

Do not merge this PR until #35754, #35756, and #35857 get merged.

Let's require the WooCommerce Analytics package in the Jetpack plugin, and mark the existing codebase in the Jetpack plugin as deprecated.

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

• Epic: WooCommerce Analytics: refactor feature and move to WooCommerce #35511

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

• No

Testing instructions:

• This will require using the WooCommerce plugin on your site, and having created some test products.
• Connect the site to your WordPress.com account.
• Go to Jetpack > Settings > Modules and confirm that the WooCommerce Analytics module is enabled.
• Go to the frontend of the site, and confirm that https://stats.wp.com/s-xxxx.js is enabled, xxxx being the year and week number.
• Load Chrome, and install https://github.com/Automattic/tracks-chrome-extension
• Try checking Tracks events generated on Woo pages. You can follow the instructions in Update how Cart/Checkout is tracked to be realtime. #35139 or Update check for classic vs. block theme in the WooCommerce Analytics module #34065 for some examples.

[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 require-wooanalytics-jetpack branch.

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

  bin/jetpack-downloader test jetpack require-wooanalytics-jetpack
  

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 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.

---

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.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen daily.
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for April 2, 2024 (scheduled code freeze on April 1, 2024).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jeherve]

@senadir @opr Do you think you could give this PR a try, and see that existing WooCommerce Analytics functionality still works? It does seem to work on my end, but I think you're a lot more familiar with the feature than I am.

Thank you!

[opr]

Hi @jeherve - seems like the package is loading ok, but the stats file loaded for me is s-202409.js which does not fit the year/month (but it does fit year/week, is that what it's using?).

Also, this one is for @senadir not you but it seems that when using the cart block, the values below are incorrectly reported on all events:

cart_page_contains_cart_block: 0
cart_page_contains_cart_shortcode: 1

Nadir can you replicate/see the cause?

Requesting changes so we can update the PR description or look into the stats JS file, thanks!

[jeherve]

it does fit year/week, is that what it's using?

Yes sorry, that's what I should have written.

jetpack/projects/packages/woocommerce-analytics/src/class-woocommerce-analytics.php

Line 98 in fa0dba9

gmdate( 'YW' )

I've updated the PR description accordingly.

[chrisbliss18]

The changes look good. I ran the tests using both trunk and this branch. Track events generated as expected throughout the browsing, adding to cart, and checking out flow on each branch.

I approve. Thanks for the work on this Jeremy.

Changes were addressed in the PR description