Book a demo
Book a demo
Login

Solution WordPress + Umami

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.

Technical review: · Source reviewed; no production deployment test claimed

Published · Updated · xCloud editorial

Read this guide as Markdown

Requirements and responsibilities

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

Dashboard and application procedure

Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.

Step 1 of 5

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.

Sources: Umami collect website data · Umami track events

Step 2 of 5

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.

Sources: Umami collect website data · Umami track events

Step 3 of 5

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.

Sources: Umami collect website data · Umami track events

Step 4 of 5

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.

Sources: Umami collect website data · Umami track events

Step 5 of 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.

Sources: Umami collect website data · Umami track events

Maintenance

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.

    Umami collect website data · Umami 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 and scopes to discover

    teams.index, servers.show, sites.show

    Scopes: read:servers, read:sites

    xCloud MCP documentation and connection profiles · xCloud agent capability boundaries

  • 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.

    Umami collect website data · Umami track events

Copyable agent brief

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

Sources

Continue

Explore the next WordPress workflow