Implement Simple Analytics

[iamdharmesh]

Description of the Change

Merged PRs:

• Fetaure: Add Analytics Admin Page, Navigation & Controls #203
• [Simple Analytics] Add Data Layer & Form Event Tracking #213 ([Simple Analytics] Add Data Layer & Form Event Tracking #204)
• [Simple Analytics] Subscriber Change Over Time Chart & Mailchimp API Integration #206
• [Simple Analytics] Audience Overview KPI block #209
• Feature/form performance chart #207
• [Simple Analytics] Accessibility #214
• Feature/216 UI fixes #218

Closes #189

How to test the Change

N/A

Changelog Entry

Added -

Credits

Props @username, @username2, ...

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests pass.

[ankitguptaindia]

QA Status: Needs feedback ⚠️

Hi @iamdharmesh I tested this PR via feature/simple-analytics by creating a build zip from GH action https://github.com/mailchimp/wordpress/actions/runs/26459085882 (zip attached) and noticed that the graphs are not loading in the Analytics page.

I tested on three different fresh new sites and faced the same result.

Details

Site:1

Site:2

Site:3

---

Here are the steps I am following:

Recording.1849.mp4

---

• Zip file created via GH action:
  wordpress.zip

cc: @vikrampm1

[iamdharmesh]

Hi @ankitguptaindia, Thanks for the comment.

Hi @iamdharmesh I tested this PR via feature/simple-analytics by creating a build zip from GH action https://github.com/mailchimp/wordpress/actions/runs/26459085882 (zip attached) and noticed that the graphs are not loading in the Analytics page.

It seems you created zip based of feature/data-layer-and-form-event-tracking branch. Could you please check once? Thanks.

[ankitguptaindia]

@iamdharmesh Thanks for the quick reply, I just checked, and yes, I accidentally copied wrong branch name while creating the build.

Graphs loads correctly with correct branch:

[builtbytay]

@iamdharmesh @alaca

UAT Feedback — Mailchimp SAP Integration

---

1. Error Handling QA

Video reference: Internal Slack File

Issue: Error state is unclear to the user and the CTA button has no action.

Action required: Audit all possible error states end-to-end. For each, confirm:

• Error message is human-readable and explains the cause
• CTA button is present only when there is a user-actionable resolution
• CTA correctly resolves or routes to resolution

Known error states to test (expand if additional states exist):

Error	User-Resolvable?	Expected Behavior
API not connected	Yes	Clear message + "Reconnect Mailchimp Account" CTA
Database error	No	Clear message explaining issue is internal; no CTA button should render

⚠️ If additional error states exist beyond these two, document them and apply the same resolution logic.

---

2. Copy Changes — List Performance Over Time

Location	Current	Updated
Section label	Form Activity	List Activity
Subtitle/description	Views, submissions, and conversion rate over time	All form views, submissions, and conversion rate over time

---

3. Issue Prevention — Plugin Version / DB Upgrade Edge Case

Context: During UAT setup, installing a previous plugin version followed by replacing it with the UAT build caused the database upgrade script not to run, resulting in a broken/unusable analytics state. This was triggered by an accidental install sequence (wrong version first, then deleted and replaced) — not a standard user flow.

Confirmed: Normal users won't hit this through typical installation. However, the DB table creation script is currently gated behind a version check, which makes it fragile in non-standard install sequences.

Action required: Move the DB create/upgrade script out of the version check so it runs reliably regardless of install order. Dharmesh to confirm approach with Ante.