[WooCommerce Analytics] Add woocomerceanalytics_session

[puntope]

Fixes and issue with the way we set the cookie for storing woocomerceanalytics_session that created cache issues.

In this PR we do set the cookie using JS to avoid those cache misses.

Proposed changes:

• Set the woocomerceanalytics_session using JS

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?

Testing instructions:

• Set up a Jurassic Ninja site using the code in this PR for WooCommerce Analytics
• Verify the cache by hitting different pages with curl -I
• When running it the second time you should see something like:

See how it was before when the set cookie was set in PHP headers

• Close all the incognito windows and open a new one, navigate to a Product (or perform any other event like going to checkout or cart)
• See session_started event is triggered and also the event contains session_id
• Create more events, see they have session_id and landfing_page in the props.
• Tests edge cases, like Empty carts or going to checkout when cart is empty.

Note:

Mybe you want to quickly push the plugin to a live JN site without waiting for the builds. This rsync wrapper knows which files to send and not send.

Rsync the Jetpack plugin to server destination:

jetpack rsync jetpack [email protected]:/home/path/to/wp-content/plugins

Find the command in your JN site

Notice also that for track to happen USage TRcking should be enabled in WoCommerce -> Settings -> Advanced -> WooCommerce.com -> "Allow usage tracking"

Also JP (or WPCOM) should be connected

[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]

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 tweak/analytics_session_id branch.

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

  bin/jetpack-downloader test jetpack tweak/analytics_session_id
  

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