Connect Google Analytics

Connect an existing GA4 property to read its reports inside your Project. You can use this without native SiteOS collection, or switch between the two sources. Connecting Google does not install another website script or combine Google and SiteOS totals. To compare GA4 with native SiteOS measurement, see SiteOS vs Google Analytics.

Connect the intended property

1. Open Analytics in the intended Project and environment and choose Connect Google Analytics.
2. Authorize the requested read access with a Google account that can read the property. The connection is shared with your Organization; see Share Google resources.
3. Choose the GA4 Property and web stream, then Connect stream. Later, Settings offers Change stream and Disconnect stream.
4. Select the Google source and check the report's date range, time zone and freshness.

SiteOS may suggest an existing connection used by Trace GA4 monitoring. Review and select it explicitly; matching names do not establish the binding. Google Search Console uses a separate property connection. Its tab appears when that integration is available.

Explore traffic and events

Overview covers acquisition, sources and mediums, campaigns, pages, countries and devices. Choose a period and, where available, compare it with the previous period or previous year. Realtime is a separate recent-activity view.

Events lets you inspect recorded Google events and supported dimensions. Custom event parameters need the corresponding registered GA4 custom dimensions before they can be used in those reports. A parameter existing in your website code does not automatically make it available through Google's reporting API.

Keep the source visible when comparing reports. Google attribution, users, sessions and time-zone boundaries can differ from native SiteOS definitions.

Build funnels

Open Funnels to create or open a saved journey. Define two to ten named event steps, choose an open or closed funnel, and configure direct or indirect progression and an optional time limit where supported. Google computes these results; they are not reconstructed from native SiteOS events.

In a closed funnel, visitors must start at the first step, so overall completion can compare the final step with the first. An open funnel allows entry at later steps; that same percentage would be misleading. Inspect the step-level results instead.

The saved funnel opens as a report. Edit its definition when you need to change the journey; changing the global date range does not replace the saved steps.

Read retention cohorts

Retention groups users by their first-session period and follows their return over daily or weekly intervals. Choose the first-visit period and follow-up window for that question.

The first interval includes the initial visit. Future or incomplete intervals are unavailable rather than zero. A cohort needs time to mature before its later cells can be compared fairly with older cohorts.

Save reports and export CSV

Use Reports for named, shared report definitions. Organization owners and admins can save, change or remove definitions; authorized readers can open reports and export their displayed data. Save changes updates the existing definition, while Save as new creates another.

A saved definition stores the reporting question, not a permanent data snapshot. Results can change as Google processes data. Definitions tied to a previous property or stream may become incompatible after changing the connection.

CSV export uses the displayed report snapshot, including its period, time zone, freshness and relevant limitations. Exporting does not run a new Google query, so refresh the report first when you need newer data.

Check freshness and quality

Read the report's notices before drawing conclusions. Cached results, Google processing delays, sampling, privacy thresholds, grouped rows and restricted dimensions can affect availability or detail. A previously successful report may stay visible while refreshing; its timestamp still matters.

When a report is empty or unavailable, check access to the selected property, the web stream, dates, registered dimensions and any provider error. An incomplete retention window or thresholded result is not evidence that nobody visited.

Work with your agent

The SiteOS agent integration can read connected Google aggregate reports, realtime activity, events, funnels and cohorts in the selected environment. Use the CLI for supported setup and saved-report management. Read-only MCP reporting does not edit report definitions or send notifications.

Give the agent a concrete question with a source and period, such as: “Using the connected GA4 property, compare signup-funnel drop-off with the previous period and include any data-quality limitations.” Review the evidence before changing your website.