# Add an analytics service to WordPress Compare measurement needs and privacy constraints, then validate the chosen data path. A consenting test visitor produces one page view and one form event. Canonical: https://xcloud.host/use-cases/solutions/add-an-analytics-service-to-wordpress/ Published: 2026-09-30 · Updated: 2026-09-30 · Technical review: 2026-09-30 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Compare measurement needs and privacy constraints, then validate the chosen data path. For: business-owner, operator ## Requirements and responsibilities - Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A WordPress business site needs traffic data linked to a specific lead form. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) - Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Duplicate scripts can inflate conversions. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## Illustrative situation Illustrative scenario, not a customer case study: A WordPress business site needs traffic data linked to a specific lead form. A consenting test visitor produces one page view and one form event. ## Choose the approach - Choose an analytics provider and privacy-aware event plan. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) ## Dashboard and application procedure ### 1. Define target decisions, events and data policy **Where:** Umami administrator and WordPress tracking integration **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Define target decisions, events and data policy; exact site identity, named approver and controlled sample data. **Action:** Choose one lead form and define page view, successful submission and consent behavior with the business owner. **Expected result:** Tracking measures a business decision. **Verify:** Tracking measures a business decision. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If an event fires on button click before form success, redefine it. Capability: Configure and validate Umami tracking Sources: [Umami collect website data](https://docs.umami.is/docs/collect-data); [Umami track events](https://docs.umami.is/docs/track-events) ### 2. Create the analytics property with correct domain **Where:** Umami administrator and WordPress tracking integration **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Create the analytics property with correct domain; exact site identity, named approver and controlled sample data. **Action:** Create an Umami website for the exact domain as one documented analytics option; record its website ID and account owner. **Expected result:** Events will belong to the right site. **Verify:** Events will belong to the right site. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If the property ID belongs elsewhere, correct it before tagging. Capability: Configure and validate Umami tracking Sources: [Umami collect website data](https://docs.umami.is/docs/collect-data); [Umami track events](https://docs.umami.is/docs/track-events) ### 3. Add integration in WordPress or approved tag tool **Where:** Umami administrator and WordPress tracking integration **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Add integration in wordpress or approved tag tool; exact site identity, named approver and controlled sample data. **Action:** Install Umami's tracking script once in WordPress through an approved method; add a custom event only on confirmed form success using documented tracker behavior. **Expected result:** One technical path emits page and conversion data. **Verify:** One technical path emits page and conversion data. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If multiple scripts fire, remove duplicates before launch. Capability: Configure and validate Umami tracking Sources: [Umami collect website data](https://docs.umami.is/docs/collect-data); [Umami track events](https://docs.umami.is/docs/track-events) ### 4. Test consent, event count and referral attribution **Where:** Umami administrator and WordPress tracking integration **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Test consent, event count and referral attribution; exact site identity, named approver and controlled sample data. **Action:** With consent where required, complete a marked test submission and inspect Umami events plus the form's real destination. **Expected result:** One correct event corresponds to an actual lead. **Verify:** One correct event corresponds to an actual lead. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If the form fails but event appears, move the trigger to success state. Capability: Configure and validate Umami tracking Sources: [Umami collect website data](https://docs.umami.is/docs/collect-data); [Umami track events](https://docs.umami.is/docs/track-events) ### 5. Assign owner for tag updates and access review **Where:** Umami administrator and WordPress tracking integration **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Assign owner for tag updates and access review; exact site identity, named approver and controlled sample data. **Action:** Document data access, retention and retest after form/theme updates; do not infer historical conversions when tracking breaks. **Expected result:** Analytics has a named operator. **Verify:** Analytics has a named operator. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a browser blocker or consent prevents collection, report that limit rather than promise full counts. Capability: Configure and validate Umami tracking Sources: [Umami collect website data](https://docs.umami.is/docs/collect-data); [Umami track events](https://docs.umami.is/docs/track-events) ## Maintenance - Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: A consenting test visitor produces one page view and one form event. A chat prompt is not a scheduled task. Sources: [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/); [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) - Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## Recovery decisions - If analytics disappear, inspect Umami website ID, tracking script, consent and browser requests. Restore the approved tracking configuration and retest; do not infer missing history. Sources: [Umami collect website data](https://docs.umami.is/docs/collect-data); [Umami track events](https://docs.umami.is/docs/track-events) ## AI handoff Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only. ### Supported scope - **Confirm requirements and inspect resources** (mcp; read): Discover the connected profile and operation schema first; only teams granted to the connection are visible. Checkpoint: Confirm exact team, server and site identity. Use dashboard\_url returned by the resource; do not invent a dashboard link. Operation identifiers to discover: teams.index, servers.show, sites.show. Scopes: read:servers, read:sites. Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - **Configure and validate Umami tracking** (app; manual): A named Umami and WordPress administrator sets the website ID, tracking script, events and data policy. xCloud MCP hosting reads cannot prove browser events. Checkpoint: Observe a consent-appropriate page view and event in Umami; inspect duplicate scripts and failures. Sources: [Umami collect website data](https://docs.umami.is/docs/collect-data); [Umami track events](https://docs.umami.is/docs/track-events) ### Copyable agent brief ```text Help with add an analytics service to wordpress for the exact xCloud team and site I name. Read available hosting identity and state first, then ask the named WordPress, app, provider or dashboard owner for operations and records outside this connection. Prepare these authored tasks: Define target decisions, events and data policy; Create the analytics property with correct domain; Add integration in WordPress or approved tag tool; Test consent, event count and referral attribution; Assign owner for tag updates and access review. The acceptance check is: One correct event corresponds to an actual lead. Do not infer application transactions or completed dashboard jobs from hosting resource reads. WordPress staging push/pull, backup schedule, restore and cache-setting changes require the authorized dashboard owner; the packaged REST wrapper is GET-only. ``` ### Manual checkpoints - The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Install Umami's tracking script once in WordPress through an approved method; add a custom event only on confirmed form success using documented tracker behavior. - The business owner compares the controlled sample with this observable result: One correct event corresponds to an actual lead. - Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only. ## Feature coverage - **business-acceptance** (covered): A consenting test visitor produces one page view and one form event. Steps: phase-4 - **recovery** (covered): Duplicate scripts can inflate conversions. Steps: phase-5 ## Sources - [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) — reviewed 2026-09-30; v4.4.2 package; xCloud v2.8.8 capability review - [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) — reviewed 2026-09-30 - [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) — reviewed 2026-09-30 - [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) — reviewed 2026-09-30 - [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) — reviewed 2026-09-30 - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/) — reviewed 2026-09-30 - [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) — reviewed 2026-09-30 - [Umami collect website data](https://docs.umami.is/docs/collect-data) — reviewed 2026-09-30 - [Umami track events](https://docs.umami.is/docs/track-events) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/add-an-external-booking-service-to-a-wordpress-site/) - [Deploy a private analytics service beside WordPress](https://xcloud.host/use-cases/workflows/deploy-a-private-analytics-service-beside-wordpress/) - [Deploy Metabase for internal reporting](https://xcloud.host/use-cases/workflows/deploy-metabase-for-internal-reporting/) - [Operate a self-hosted analytics service](https://xcloud.host/use-cases/operations/operate-a-self-hosted-analytics-service/)