Skip to content
SiteOS

Documentation

Set up Trace

Choose Google connections, browser observation or both for the selected website environment.

Last updated

Select your Organization, Project and environment, then open Trace. Production and preview environments keep separate connections and observation settings. Review the target website before continuing.

Connect Google

Choose the Google path when you want GA4 reports or Tag Manager configuration history without changing the website.

  1. Use an authorized Organization Google connection, or connect an account with access to the required resource.
  2. For GA4, select the exact property and web stream. For GTM, select the intended account and container.
  3. Wait for the first successful import. Queued or waiting means the report is not ready; a failed import needs attention.
  4. Review the saved report and synchronization time in Services.

Google sign-in alone does not connect a property. A selected resource and successful import are separate steps. See Google Analytics and Tag Manager.

Install the observer

Choose this path for browser evidence about supported services, requests, consent or data-layer events.

  1. Prepare an installation for the selected environment.
  2. Review allowed website hosts, sampling, collection policy and excluded destinations.
  3. Save and publish the reviewed configuration.
  4. Install the exact snippet returned by Installation, once on the website.
  5. Perform a representative action and verify fresh observations and the current runtime/configuration in coverage.

Preparing a draft does not install a script. A published configuration does not prove the website loaded it. Keep the existing tracking tags and optional CMP working as intended.

The Set up Trace with AI action provides a prompt containing the website and selected SiteOS context. Your agent can inspect the implementation, use the supported CLI and verify actual signals. See Observer and coverage.

Review the first findings

Open Overview and check what evidence is available. An installation can be learning, partially covered or waiting for traffic. New event discoveries are informational; they do not all need incident alerts.

Follow an issue into its evidence. Add rules for confirmed business expectations, then configure notifications if you want the team to receive alerts. Notification routes start disabled.

Keep each connection independent

The observer works without Google or SiteOS Cookie. Google imports work without the observer. SiteOS Analytics is also a separate service attachment; enabling Trace does not create Analytics events or make its observations count as visits.