Google Analytics as a connected source: human outcomes next to your logs, and the measurement gap between them
Connect a GA4 property to see sessions, engagement, key events and revenue beside the requests your server actually served, find out which AI assistants convert, and measure how much of your real human traffic Google Analytics never records.
Google Analytics is now a connected source. Under Settings → Integrations you can connect a Google Analytics 4 property to a site, the same way you connect Search Console. Authorise with Google, pick the property, and the first sync starts. This is not an ingest path: nothing about how your logs reach us changes, and GA data never mixes into the request stream. It sits beside the logs as a second, independent view of the same visitors, synced nightly and about a day behind, as GA4 aggregates only, with no visitor identifiers and no bots.
A Google Analytics page under Traffic. Sessions, active users, engagement rate, key events (GA4's name for conversions) and revenue for the selected period against the previous one. A sources table. And an AI assistants table: the logs have always shown you which assistants send people to your site; GA now shows what those people did once they arrived, per assistant, so you can see whether ChatGPT referrals engage and convert or just bounce. A landing pages table with a search filter links every path to its URL detail page.
The measurement gap. Your logs record every request. Google Analytics records only what its tag was allowed to run for. The new Measured vs actual chart plots GA pageviews against human page requests in your logs, day by day, and one number summarises it: the share of real human page requests GA never recorded. Ad and tracker blockers, declined consent banners, browsers that block third-party scripts and pages that never finished loading all take visits out of GA while they remain in your logs. Somewhere between 15% and 40% is typical. A sudden jump is a tag or consent problem, and you will now see it the next morning instead of at the quarterly review.
Everywhere else it belongs. URL detail gains a Human behaviour (Google Analytics) block next to the Search Console one, with the page's sessions, engagement, key events, revenue, its own unmeasured share and its top AI and search sources. AI Landing Pages gains outcome columns per assistant and a key-events column per page when GA is connected.
API, CLI and MCP. GET /public/v1/websites/{id}/ga/overview and /ga/pages, loglens ga overview and loglens ga pages in the CLI, and the MCP tools get_ga_overview and get_ga_pages. Responses say ga_connected: false when nothing is connected, so an agent can tell the difference between "no data" and "not set up". Connecting needs Viewer access on the GA4 property; we read data only and cannot change anything in your property.