GA4 over MCP

One connection, two sources

GA4 is paired per Search Console property rather than configured globally, so an assistant asking about a site gets that site's analytics without ever handling a numeric GA4 property id.

What is reachable

The same reports the dashboard renders, each with a period-over-period comparison.

• Channels and sources, with an organic-only filter
• Pages and landing pages with engagement rate and bounce rate
• Error pages, so a 404 that still receives traffic surfaces immediately
• Countries, e-commerce and key events
• LLM traffic: sessions arriving from assistants rather than from search

Permissions

Granting the read-only analytics.readonly scope happens once per Google account; choosing which GA4 property belongs to a site happens once per Search Console property. Nothing is ever written back to Analytics and no user-level identifiers are stored.

Freshness and shape

GA4 responses are cached for six hours and capped at 25,000 rows per report, so a broad question comes back quickly and a very wide one comes back truncated rather than slow. Ask the assistant to state its date range, because GA4 and Search Console settle on different schedules.

Same key, same limits

One key covers Search Console and GA4. Rate limiting is per key at 60 requests per minute, with 1,000 per hour per account, and a 429 carries a Retry-After header.