Alerts, exports and AI
Route useful alerts, export lists and tracking plans, review tracking in pull requests and investigate with your agent.
Trace keeps issue investigation, team notifications and agent access tied to the selected Project environment. Configure each deliberately; publishing a rule does not automatically enable notifications.
Set up notifications
Open Trace → Notifications, also linked from Settings. Routes start disabled. Turn on Enable tracking notifications, choose an email, Slack or Telegram destination available through your Organization’s Integrations, choose Critical issues or Warnings and critical issues under Notify about, decide whether to Include verified recovery, then save. Owners and admins can configure Organization routes or their own Personal route.
Trace groups repeated findings. New incidents, escalation and verified recovery are distinct transitions, and each message uses the issue’s plain-language sentence. Snoozed issues do not generate new alerts, and brief incidents that recover before dispatch may be suppressed.
Turn on Weekly digest for a summary sent to the same destination on Mondays at 09:00 in the route’s time zone, set from your browser when you turn it on. It lists new, resolved and verified-recovered issues, active issues, key event delivery for the week and the number of Tag Manager and collection changes. The digest is independent of issue alerts. The week you turn it on is recorded without a message, so the first digest arrives the following Monday.
Inspect Recent deliveries before assuming a message reached the team. A pending or failed provider receipt is different from a sent notification. If a retry needs attention, review the recorded delivery state first.
Investigate with your agent
The SiteOS plugin provides MCP + Trace skills. MCP can read saved coverage, reports, events, issues, observations, the service map, GTM summaries, GA4 evidence and notification state. Your agent can connect this evidence with the website’s source code and suggest focused fixes.
Use Investigate with AI on an issue: it copies a prompt with the selected website context and issue reference. Missing Google access or failed imports should remain visible gaps; they are not evidence that nothing changed. To hand an issue to a person instead, Copy for ticket copies its plain-language summary, dates, next step and link.
MCP is read-only. The supported CLI handles reviewed installation, rule and notification changes. Google tag publication is a separate authorized workflow. An explanation alone does not fix or resolve an issue.
The CLI can also record your decision on an issue after reading it in the selected environment:
--until takes 24h, 7d or an ISO date. Like the same actions in the issue sheet, these record a workflow decision; they do not verify recovery.
Review tracking in pull requests
When Pulse GitHub PR checks and Trace are set up for the same Project environment, browser Checks on a pull request also note which tracking events the preview sends, by name only. Trace compares them with your published tracking plan, with what production sent in the last 7 days and with what the same Checks sent on the last merged pull request. The GitHub Check adds an advisory Tracking section only when something changed, such as a planned property that is missing or has another type, an event that stopped or a new event.
When Trace uses the SiteOS Cookie banner as its consent source, passing browser Checks also run a consent pass: up to three pages open again in a fresh browser, once with Accept all and once with Reject all. A Google Analytics, Google Ads, Meta Pixel or HubSpot tag that still sends after Reject all is flagged, and consent receipts are never recorded in your Cookie reports.
The section is advisory. It never changes the Check's result, and values never leave the test browser.
Export lists and tracking plans
Export CSV on Events and Properties in Explorer and on Issues saves the list as you filtered it, up to 5,000 rows. Cells hold names, counts and dates: observation counts are sampled and cover the selected period, and the issue list ignores the period.
In Tracking rules, Import or export saves the draft as a CSV spreadsheet, JSON Schema or SiteOS JSON, and imports any of the three after showing what would change. Imports only change the draft; publishing stays a separate review. See Issues and rules. The CLI has the same commands:
--format also accepts json-schema and siteos. Run the import again without --dry-run after reviewing its preview.
For JSON, the CLI provides machine-readable reports and bounded evidence lists, and MCP reads the same saved evidence:
To save a report locally:
Select the correct Project first and replace the environment when needed. Lists return one page; follow the returned cursor with the same filters for a larger export. For an issue, use siteos trace issue show --id ISSUE_ID --environment production --json with its exact returned ID.
Stored evidence omits raw event payloads and property values, so no export can reconstruct them.
Verify the outcome
After an implementation fix, perform the relevant action, inspect fresh evidence and wait for the check’s required analysis or Google reporting window. Review verified recovery separately from manual resolution.
Do not relax a valid rule merely to clear an issue. If the expected behavior intentionally changed, review and publish the new expectation and record that decision.