Skip to content

Docs: clarify WP Cloud Client GA4 behavior (407941)#421

Draft
cursor[bot] wants to merge 1 commit intomasterfrom
cursordocumentation-agent-workflow-25bf
Draft

Docs: clarify WP Cloud Client GA4 behavior (407941)#421
cursor[bot] wants to merge 1 commit intomasterfrom
cursordocumentation-agent-workflow-25bf

Conversation

@cursor
Copy link
Copy Markdown

@cursor cursor Bot commented Apr 1, 2026

JIRA

Change classification

  • Feature behavior change
  • Configuration / system behavior

Summary of documentation updates

  • Updated existing documentation at:
    • docusaurus/docs/business-app/administration/business-profile-analytics-connections.mdx
  • Added a new subsection under Google Analytics setup:
    • Use GA4 tracking on a WordPress site with WP Cloud Client
  • Documented current behavior from the completed story notes:
    • GA4 can come from the connected property in Business App → Settings → Connections
    • GA4 can also come from a Custom GA4 Tracking ID in WordPress Admin → Settings → WP Cloud Client
    • Both IDs can run at the same time when configured
    • Custom ID format is G-XXXXXXXXXX

Existing docs updated or new docs created

  • ✅ Updated existing documentation
  • ❌ No new documentation pages created

Placement reasoning

  • The change extends existing GA4 connection behavior already documented in the Business Profile & Analytics Connections page.
  • Adding this as a subsection in that page keeps setup and behavior details in one place and avoids duplicating analytics instructions in unrelated sections.

Acceptance criteria coverage

Acceptance criterion Doc impact Coverage
GA4 tracking code injected into site <head> when analytics is connected Yes Covered in new WP Cloud Client subsection (GA4 injected in wp_head)
GA4 property ID configurable through Websites Microservice Maybe (internal detail) Not explicitly documented; no stable partner-facing UI detail in payload
Toggle to enable/disable GA tracking without removing the connection Yes, if implemented Not documented; no explicit implementation evidence in linked notes
Business profile data (name/address/phone/hours) rendered via shortcode/widget Yes, if implemented Not documented; no explicit implementation evidence in linked notes
Profile data syncs periodically or on-demand Yes, if implemented Not documented; no explicit implementation evidence in linked notes
Plugin performance impact minimal Typically internal/non-doc No user-facing documentation change made

Visual inputs (Figma/images)

  • Jira attachments were referenced in the story, but direct image content was not accessible from this environment.
  • Documentation update used verified textual implementation notes from Jira comments.

Skills used

  • Repository skill used: sprint-review (release-safe and evergreen doc update guidance)
  • Discovery/edit support tools: ripgrep search, file globbing, and targeted file updates

Assumptions and limitations

  • Linked engineering PR https://github.com/vplugins/wp-cloud-client/pull/1 is not accessible from this environment (404/repository not resolvable), so author handle(s) could not be safely resolved for additional tagging.
  • Only behavior explicitly supported by the available Jira notes was documented to avoid assumptions.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi

Open in Web View Automation 

Co-authored-by: Haley <haleyserrano@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant