Add premium-analytics plugin

[retrofox]

What?

Adds an internal WordPress plugin (projects/plugins/premium-analytics/) that activates the automattic/jetpack-premium-analytics package. Thin wrapper — loads the autoloader and calls Analytics::init().

⚠️ Depends on #48085.

Relates to WOOA7S-1344.

Why?

The premium-analytics package needs a consumer to verify it loads correctly in wp-admin. This plugin exists as a development and testing harness — not intended for publication (autotagger and autorelease set to false).

How?

• jetpack-premium-analytics.php: defines constants, loads Jetpack autoloader, adds settings link
• class-jetpack-premium-analytics.php: calls PremiumAnalytics\Analytics::init()
• composer.json: requires automattic/jetpack-premium-analytics from monorepo path
• .phpcs.dir.xml: text domain configuration for linting

Testing instructions

1. Pull the branch and run pnpm install
2. Run jetpack install plugins/premium-analytics to resolve Composer dependencies
3. Run jetpack build packages/premium-analytics to build the package
4. Run jetpack docker up and activate the Premium Analytics plugin
5. Verify the Analytics menu appears in wp-admin and the SPA loads

Screen.Recording.2026-04-14.at.6.55.45.PM.mov

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

No. This plugin is a thin wrapper that loads the premium-analytics package. No new data collection or tracking is introduced.

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

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Premium Analytics plugin:

No scheduled milestone found for this plugin.

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

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/premium-analytics/src/class-analytics.php	0/26 (0.00%)	0.00%	2 ❤️‍🩹

Full summary · PHP report

[anomiex]

Gave it a quick overview. Seems ok for its stated purpose; some suggestions inline.

[anomiex]

No need for this file if it's going to be empty.

[anomiex]

I wonder whether a mirror repo is even necessary. If this is only going to be used within the monorepo (e.g. with jetpack docker, jetpack playground, or maybe jetpack rsync), you could probably skip it.

On the other hand, if you're wanting to use the plugin with Jetpack Beta Tester (including on Jurassic Ninja), that'll need a beta-plugin-slug key here and it'll need us to do some setup on betadownload.jetpack.me.

[retrofox]

For now, the plugin is just a dev harness to test the package locally (Jetpack Docker, Playground, Rsync).

No need for a mirror repo at this stage. If we need Beta Tester / Jurassic Ninja support later, we can set up the mirror and beta-plugin-slug in a follow-up.

[kangzj]

Nice one! Works as described 👍

[kangzj]

One thing though - if WooCommerce is installed, Analytics would already be registered as a menu item, so we should probably use a different name like 'Premium Analytics' dunno..

The base branch was changed.

[retrofox]

One thing though - if WooCommerce is installed, Analytics would already be registered as a menu item, so we should probably use a different name like 'Premium Analytics' dunno..

Good call. The menu title is now configurable via Analytics::init() options, so each consumer can set its own label:

Analytics::init( array( 'menu_title' => 'Premium Analytics' ) );

The plugin already passes 'Premium Analytics' as the title. The package default remains 'Analytics' for standalone use.