Google Analytics MCP: GA4 reporting as a conversation

Written by Uptimal, the team that builds and operates Upbuild and runs marketing analytics for multinational clients across the globe. Everything below reflects how the connector actually behaves in production.

GA4’s Data API is powerful and famously unloved: dimensions and metrics that must be compatible, quotas that bite, and an Explorations UI that hides more than it shows. An MCP server puts an assistant in front of it. You ask for “sessions and key events by default channel group, last 28 days, compared with the previous period”; a tool like ga4_run_report executes exactly that against the Data API, and the assistant formats, compares and explains.

What marketers actually ask

• “Which channels drove key events this week, and how does that compare with last week?”
• “Landing pages with falling engagement rate month over month.”
• “Purchase funnel by device: where is mobile leaking?”
• “Is anything anomalous in yesterday’s traffic versus the trailing 28 days?”

The quota reality nobody mentions

The GA4 Data API meters properties with token budgets per hour and per day, and concurrent-request caps; standard properties get materially less than 360. This is a genuine design constraint for conversational access: ten rapid-fire questions can spend real quota. Upbuild’s server caches identical requests briefly and keeps queries tight, which in practice keeps a normal analysis session well inside standard-property limits. We wrote up the numbers separately in GA4 API quotas explained.

GA4-specific quirks the connector absorbs

Dimension and metric compatibility is validated before the call rather than after a cryptic error; property selection is explicit when your Google login can see many properties; and sampled or thresholded responses are flagged as such, because an assistant confidently quoting thresholded data is worse than no answer. Pair GA4 with GTM when the question is “why did tracking change” rather than “what happened”.

Connecting is the usual flow in the setup guide: one OAuth with the Google account that has property access; no service accounts, no JSON keys, nothing to install.

Frequently asked questions