Premium Analytics: call the preview the new Stats in its dialogs

[dognose24]

Part of the Stats v2 soft launch, alongside #52720.

Proposed changes

The preview's welcome modal, feedback modal and banner, and switch-off dialog name "the new Traffic and Insights tabs" (#52525), which was right while those were the only tabs in the preview. #52720 adds Subscribers and Ads, so every classic Stats tab is in it and the copy goes back to the new Stats instead of growing a list:

• Welcome: Welcome to the new Stats, and the body reads "It's built from widgets…" again.
• Feedback: Is the new Stats ready to replace the old one?, the banner's "what you miss about the new Stats", and the [Ready to replace the old Stats? …] prefix on the feedback text.
• Switch-off: Switch off the new Stats?, and the failure and "switch on again" lines to match.

Tests follow the strings. The Calypso side of the invitation (banner, modules menu entry and dialog) is Automattic/wp-calypso#114594.

Merge order: after #52720. Merged before it, the copy would call a two-tab preview "the new Stats".

Related product discussion/links

• Agreed in #premium-analytics when #114482 landed: name the tabs until the remaining ones ship, then drop the list.

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

No.

Testing instructions

On a site running the preview:

• Reset the onboarding (wp user meta delete <id> wp_persisted_preferences) and open Stats. The welcome modal is titled Welcome to the new Stats.
• Page options → Send feedback: the question reads Is the new Stats ready to replace the old one?
• Page options → Switch off: the dialog is titled Switch off the new Stats?
• jp test js packages/premium-analytics passes.

🤖 Generated with Claude Code

[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 WoA dev 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 (Jetpack or WordPress.com Site Helper), and enable the update/premium-analytics-preview-copy-new-stats branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/premium-analytics-preview-copy-new-stats

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/premium-analytics-preview-copy-new-stats

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

---

Jetpack plugin:

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

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: October 6, 2026

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

---

Wpcomsh plugin:

• Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

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

---

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

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[chihsuan]

LGTM!

Merge order: after #52720 ships. Merged before it, the invitation would call a two-tab preview "the new Stats".

I think we just need to deploy them together — the merge order itself shouldn’t matter as long as both changes ship at the same time.