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 local business wants to understand which page produces inquiries without collecting excess data.
xCloud agent capability boundaries · WordPress 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.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Duplicate tags or blocked consent can make reports misleading.
Illustrative situation
Illustrative scenario, not a customer case study: A local business wants to understand which page produces inquiries without collecting excess data. A consenting test visit and form event appear once with the right site identifier.
Choose the approach
Choose an analytics service and measurement plan before adding scripts. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress 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.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Define events with purpose
- Where
- Umami website settings and WordPress tracking integration
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Define events with purpose.
- Action
- Write one business question, such as which service page produces inquiries, and choose only the page view and form event needed to answer it. Define consent, retention and access.
- Expected result
- The measurement plan has a clear use.
- Verify
- The owner explains what decision the two events will change.
- If it fails
- Remove events with no clear decision from the initial plan.
Sources: Umami collect website data · Umami track events
Step 2 of 5
Choose service and property
- Where
- Umami website settings and WordPress tracking integration
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Choose service and property.
- Action
- Use Umami as one documented example: create a website property for the exact hostname, give a named administrator access and document the tracking ID.
- Expected result
- Property and site identity agree.
- Verify
- Compare website ID, hostname and owner before installing its script.
- If it fails
- If the property belongs to another site, select or create the correct one.
Sources: Umami collect website data · Umami track events
Step 3 of 5
Install one tracking path
- Where
- Umami website settings and WordPress tracking integration
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Install one tracking path.
- Action
- Add Umami's documented tracking script once through an approved WordPress method. Configure a form-success event only after checking how the chosen form reports completion; a button click is not proof of a saved lead.
- Expected result
- One tag path records intended events.
- Verify
- Inspect source and network requests for duplicate scripts.
- If it fails
- If theme and plugin both inject tracking, remove one path before interpreting metrics.
Sources: Umami collect website data · Umami track events
Step 4 of 5
Test consent and events
- Where
- Umami website settings and WordPress tracking integration
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Test consent and events.
- Action
- With appropriate consent, open a marked test session, view a service page and complete one form. Compare Umami's page and event view with the form's actual destination; local storage exists only if the plugin provides it.
- Expected result
- One page view and one conversion event appear for the correct site.
- Verify
- Match event time and hostname to the actual form outcome; repeat with consent declined according to policy.
- If it fails
- If counts differ, debug consent or event firing before using reports.
Sources: Umami collect website data · Umami track events
Step 5 of 5
Maintain reliable reporting
- Where
- Umami website settings and WordPress tracking integration
- Permissions
- Named WordPress or app administrator; business owner signs results.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Maintain reliable reporting.
- Action
- Record who checks event health after theme or form changes and who can export or delete collected data.
- Expected result
- Reports remain interpretable after releases.
- Verify
- Another maintainer finds the event definition and test procedure.
- If it fails
- If tags break, mark the affected reporting period rather than filling it with estimates.
Sources: Umami collect website data · Umami 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 visit and form event appear once with the right site identifier. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · 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.
Recovery decisions
If analytics disappear after a WordPress change, inspect the Umami website ID, tracking script, consent handling and network requests, then restore the last approved tag configuration. Do not fill missing event history with inferred counts or restore the WordPress database as a first-line analytics fix.
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.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Add Umami's documented tracking script once through an approved WordPress method. Configure a form-success event only after checking how the chosen form reports completion; a button click is not proof of a saved lead.
- The business owner compares the controlled sample with this observable result: One page view and one conversion event appear for the correct site.
- 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 visit and form event appear once with the right site identifier. Test consent and events
- recovery (covered): Duplicate tags or blocked consent can make reports misleading. Maintain reliable reporting
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Umami collect website data
- Umami track events