Most guides that promise to "connect Google Analytics to ChatGPT" don't actually connect anything. They tell you to export a GA4 report to CSV, paste it into ChatGPT, and ask questions about the numbers in the file. That works for a one-off, but it isn't a connection — it's a copy-paste, frozen at the moment you exported it, blind to everything you didn't think to include.
There is a real way to connect the two, where ChatGPT pulls live data from your GA4 property on demand, runs the comparison you asked for, and answers — no export, no CSV, no stale snapshot. It runs over MCP (Model Context Protocol), the open standard that lets an AI assistant call external tools safely. The catch nobody mentions: in ChatGPT, custom MCP connectors live behind a setting called Developer Mode, and most articles written before late 2025 don't know it exists. This guide is the current, accurate version — no code, about five minutes, and it ends with ChatGPT querying your real analytics.
Two ways to "connect" GA4 to ChatGPT — only one is live
It's worth being precise about what you're setting up, because the two approaches feel similar and behave nothing alike.
The manual way (not a real connection). You open GA4, build a report, export it, and paste the rows into ChatGPT. ChatGPT reasons over a static file. The moment you want a different date range, a new segment, or a metric you forgot to export, you're back in the GA4 UI rebuilding the report. ChatGPT never sees your property — only the slice you handed it.
The MCP way (a live connection). You connect GA4 once through an MCP server. From then on, in any new chat, ChatGPT can call that server's tools to pull whatever it needs — funnels, traffic breakdowns, device splits, anomalies — without you touching GA4. Ask "why did mobile checkout drop last week?" and ChatGPT fetches the funnel, splits it by device and source, and tells you where the loss concentrates. That's the setup this guide covers.
The old ChatGPT plugin store, by the way, is gone — plugins were deprecated in favour of connectors and the Apps/MCP model. If a tutorial tells you to install a "Google Analytics plugin," it's out of date.
What you need before you start
- A GA4 property you have access to (Editor or read access to the data).
- A ChatGPT Plus or Pro account. Custom MCP connectors run inside ChatGPT's Developer Mode, which is a beta feature available on paid tiers (Plus, Pro, and Business/Enterprise/Edu via workspace settings). The free tier can't add custom connectors yet.
- A hosted GA4 MCP server so you don't have to build or run one. This guide uses ConvRadar, which is a hosted GA4 MCP server with a browser-only, no-code setup. If you'd rather see the full landscape first — Google's official server, community forks, BigQuery — the GA4 MCP server overview compares every option.
- About five minutes. No terminal, no API keys, no
pip, no JSON config files.
Step 1 — Connect your GA4 property to a hosted MCP server
ChatGPT can't speak to GA4 directly; it speaks MCP. So first you need an MCP endpoint that wraps your GA4 data. With a hosted server this is browser-only.
Go to convradar.com and sign up — during the current open beta it's free, with no card and email signup only. Once you're in, connect GA4: authorize read-only access with the Google account that owns the property (the connector can never write to or change your analytics), then pick the property you want exposed.
One thing that matters more than it sounds: on connect, ConvRadar backfills the last 90 days of your GA4 data. Most analytics integrations only see data from the moment they're installed, so "compare this week to two months ago" doesn't work until two months pass. With the backfill, real historical comparisons work in your very first ChatGPT message.
The endpoint you'll use in the next step is the same for everyone — there's no per-user URL and no API key to paste:
https://mcp.convradar.com/mcp
Authentication is handled by OAuth when you connect, not by a secret in the URL.
Step 2 — Turn on Developer Mode in ChatGPT
This is the step the outdated guides skip. ChatGPT's standard connector flow expects a server to expose two specific tools (search and fetch) used for deep-research-style retrieval. A GA4 MCP server exposes its own diagnostic tools instead — funnels, anomalies, traffic quality — so it needs the full-tool path, which is Developer Mode.
In ChatGPT:
- Open Settings.
- Go to the Connectors tab.
- Open Advanced settings.
- Toggle Developer mode on.
Developer Mode unlocks full MCP connectors — any tool a server exposes becomes callable, not just search/fetch. OpenAI flags it as a beta power-user feature and asks you to only connect servers you trust, because a connector with write access could take real actions. A read-only GA4 connector is about as low-risk as it gets, but the warning is worth understanding before you flip the switch.
Step 3 — Add the GA4 connector
Still in Settings → Connectors, click Create (this option appears once Developer Mode is on). Fill in:
- Name — anything you'll recognise, e.g.
ConvRadar GA4. - Description (optional) — "Live GA4 analytics and conversion diagnostics."
- MCP server URL —
https://mcp.convradar.com/mcp - Authentication — choose OAuth.
- Trust checkbox — confirm you trust the connector.
Click create. The first time the connector is used, ChatGPT opens an OAuth window: sign in with the Google account that owns your GA4 property, click Allow, and you're returned to ChatGPT. The token is stored and refreshed automatically — you don't repeat this. The connector now persists across every conversation.
Step 4 — Use it in a chat
Open a new chat. From the + (tools) menu, select Developer mode and enable your GA4 connector for the conversation. Then ask a real question.
A strong opener: "Run a full audit of my GA4 property and surface the three biggest issues." ChatGPT will call the connector's tools, pull live data, run the diagnostics, and answer — the first audit takes 30–60 seconds because it's making several calls back to back; follow-ups are near-instant.
Other first prompts that exercise the connection:
- "Compare last week to the previous week — where did I lose conversions and where did I gain?"
- "Diagnose why my mobile checkout completion is below 1%."
- "Which landing pages have the highest drop-off relative to their traffic volume?"
- "Is my paid traffic quality declining? Look at engagement, not sessions."
Once you're comfortable, the GA4 prompts library is the shortest path to knowing what to type, and the conversion rate drop diagnostic walks through the use case most people hit first. If you're curious which of your visitors ChatGPT itself is sending — and whether they convert — how to track AI traffic in GA4 is the companion piece. The prompts are identical whether you're in ChatGPT or Claude.
What actually changes once it's live
A GA4 dashboard is passive — it shows what you asked to see, and you still have to interpret it. A ChatGPT chat with GA4 connected inverts that. You ask in plain English; it does the lookups, runs the comparison, and hands back a diagnosis you can act on.
You also start asking better questions. When you have to build a report, you only ask what fits a report. When you can ask anything, the messy, valuable questions come out — "is something off this week?", "did the pricing change help?", "which channel is buying users versus just sessions?". And because the connection is live, anomaly detection can run across every dimension at once, so the third-best landing page that quietly lost 40% of conversions gets surfaced even when you weren't looking for it.
The full tool surface — 22 conversion-diagnostic tools, the OAuth scopes, the endpoint details — is documented at convradar.com/docs/mcp.
ChatGPT vs Claude: the setup difference
The same ConvRadar connector works in both ChatGPT and Claude — MCP is an open standard, so you're not betting on an AI vendor. The only real difference is the setup path.
| ChatGPT | Claude | |
|---|---|---|
| Where connectors live | Settings → Connectors (Developer Mode required) | Settings → Connectors → Add custom connector |
| Plan needed | Plus or Pro (Developer Mode is beta) | Pro or Team/Enterprise |
| Same connector URL | https://mcp.convradar.com/mcp | https://mcp.convradar.com/mcp |
| Auth | OAuth (Google sign-in on first use) | OAuth (Google sign-in on first use) |
| Setup friction | One extra toggle (Developer Mode) | Slightly more polished today |
Claude's custom-connector flow is a touch smoother right now because Anthropic shipped it first, which is why a lot of people start there — the no-code Claude setup guide covers that path step by step. If you're deciding which assistant to put your analytics work in, the honest Claude vs ChatGPT for analytics comparison breaks down where each is stronger. Most serious users end up running both with the same connector installed in each — Claude for deep diagnosis, ChatGPT for quick checks and Python-on-CSV crunching.
Troubleshooting
"Developer mode" isn't in my settings. It's a paid-tier beta. Confirm you're on Plus or Pro, and that you're in the web app or desktop app rather than an older mobile build. On Business/Enterprise/Edu workspaces, an admin may need to allow custom connectors under workspace permissions first.
The connector is added but ChatGPT won't use it. Make sure you enabled it for the specific conversation from the + → Developer mode menu — connectors are per-chat. Then phrase the question as a data ask ("pull my funnel for the last 7 days") so the model knows to call a tool.
OAuth signed me into the wrong property. The connector authorizes whichever Google account you log in with. If it's pulling the wrong data, disconnect and re-authorize with the account that owns the right GA4 property.
It says the data only goes back a few days. That happens with connectors that start collecting from install. ConvRadar's 90-day backfill avoids it — if you're seeing a short window, the property may have just been connected and the initial sync is still running.
FAQ
Can ChatGPT connect to Google Analytics? Yes. Through MCP, ChatGPT can connect to a GA4 MCP server and query your property live. You enable Developer Mode in Settings → Connectors, add the server's URL, authorize with OAuth, and ChatGPT can then pull funnels, traffic, devices, geos, and anomalies on demand. Pasting a CSV export into ChatGPT also "works," but it's a static snapshot, not a live connection.
Do I need ChatGPT Plus or Pro? For a live MCP connection, yes. Custom MCP connectors run inside ChatGPT's Developer Mode, which is a beta feature on the paid tiers. The free tier can analyze a file you upload, but it can't add a custom connector to your GA4.
Is Developer Mode safe? It's safe for a read-only connector like a GA4 analytics server, which can only read your data and never write to it. The reason OpenAI gates it behind a warning is that full MCP access also allows connectors that can take actions (send email, edit records), where a malicious server could do harm. Only connect servers you trust, prefer read-only ones, and you're fine.
Do I need code or API keys?
No. With a hosted GA4 MCP server the entire setup is browser-only — sign in, authorize GA4, paste one URL into ChatGPT. There's no API key (OAuth handles auth), no pip, and no config file. If you'd rather self-host Google's official server, that route does require Python and a terminal; the GA4 MCP server overview compares the tradeoffs.
Can I use the same connection with Claude? Yes. MCP is an open standard, so the same connector URL works in Claude, ChatGPT, Cursor, and any other MCP-aware client. Install it once in each — your GA4 setup, history, and prompts carry over. Many users keep it in both.
Is my GA4 data safe? The connection uses read-only OAuth scopes and never writes back to GA4, and you can revoke access from your Google account in one click. ConvRadar's full security details are at convradar.com/security.
What happened to the ChatGPT Google Analytics plugin? ChatGPT plugins were deprecated and replaced by connectors and the MCP/Apps model. There's no GA4 plugin to install anymore — the current, supported path is a custom MCP connector, which is what this guide sets up.
Try it on your own numbers
Point ChatGPT at your real GA4 property and ask the question that's been bugging you for the past month. The setup is five minutes, it's free during the open beta with no card required, and the same connector drops straight into Claude if you want it there too.