Google Analytics
Read GA4 reports, monitor sustained drops and compare eligible browser evidence.
Connect a Google Analytics property and web stream to the exact Project environment. Trace imports saved reports and configuration; it does not install a GA4 collection tag or change the property. To explore GA4 traffic, funnels and retention instead, use Google Analytics in SiteOS Analytics.
Connect and verify the first import
Open the Google Analytics connection in Trace and choose an authorized Google account, property and web stream. Google resources are shared through Integrations. Google browser sign-in alone does not authorize Analytics reporting. If the expected resource is missing, check the account’s access instead of selecting a different stream.
Confirm the saved binding and successful synchronization time. Trace refreshes imports about every six hours, and Sync now queues an earlier import. Queued means waiting; an import error means the current data could not be refreshed. Existing saved reports remain historical when a refresh fails.
The Google connection works without the Trace observer. Services provides GA4 reports and investigation views. The Overview supports 7 or 28 completed property-local days, compared with the preceding equivalent period.
Monitor report changes without a script
Eligible GA4 report checks can detect sustained drops in event frequency and overall traffic. They use completed, mature dates with stable same-weekday history and enough traffic. A new, small or unstable event can remain insufficient for evaluation.
These checks require two consecutive mature days. Dates must be at least 72 hours past their property-local end, so this is delayed report monitoring, not an instant outage detector. Event checks compare events per session; overall traffic checks examine both sessions and events.
A decline can reflect campaigns, real visitor behavior, consent or availability. Inspect those possibilities before concluding a tag broke. Limited, stale or failed imports cannot establish a problem or recovery.
Compare browser sending with reported data
Add the observer when you need to investigate supported requests sent to the selected GA4 Measurement ID. Eligible comparisons preserve the stream, dates, sampling, consent and parser coverage.
Reports marked processing, limited, mixed-policy, insufficient-evidence or reported-only are inconclusive. Resource loads, old observations without the matching ID, custom proxies and unsupported request bodies cannot establish comparable counts.
Even an eligible discrepancy is an aggregate signal. It does not identify a particular missing visitor or prove an exact percentage of lost events. A successful browser response and Google’s final event processing remain different facts.
Review configuration and recovery
Trace retains selected configuration history, such as changes to key-event designation. Removing a key-event designation does not necessarily stop the underlying event from being collected.
Find report, configuration and synchronization issues in Issues. Verified report recovery needs later eligible data; manual closure or changing streams does not prove a fix. A same-resource credential replacement can preserve history, while selecting a different property or stream changes the evidence context.
Read saved evidence with your agent
These commands read the selected environment. MCP also exposes saved GA4 and issue evidence. Deeper arbitrary Google reporting needs a separately authorized Google tool; SiteOS MCP does not grant Google configuration writes.