September 18, 2026 · 6 min read
How to Connect GA4 to Claude or ChatGPT
Connect Google Analytics 4 to Claude or ChatGPT through an MCP connector, ask questions in plain English, and know why GA4 and Google Ads still report different numbers.

Yes, you can point Claude or ChatGPT at your Google Analytics 4 data and ask it questions in plain English. It works through a connector that holds your own Google authorization, so the assistant reads the same property you would open yourself, under the same permissions your account already has. The part most people get wrong is what happens next: the numbers an assistant reads out of GA4 will not match the numbers in Google Ads, and that is correct behaviour rather than a broken setup.
Can an AI assistant read my GA4 data?
It can, through a connector you authorize, and it reads rather than guesses. The assistant is not scraping a dashboard or working from a screenshot. It calls the same Google Analytics Data API that any reporting tool uses, so a question about last month's traffic returns the property's own numbers for last month.
What it cannot do is see anything your Google account cannot see. Authorization is the ceiling. If you have read access to one property and not to another, the assistant has exactly the same reach, and a property nobody granted it stays invisible.
How do you connect GA4 to Claude or ChatGPT?
You add the connector in the assistant, sign in with Google once, and choose which property it may read. There are no API keys to copy and nothing to paste into a settings file. Claude and ChatGPT are separate surfaces with separate endpoint URLs, so the address you add in one is not the address you add in the other; the current pair is listed on the MCP clients page.
Connect Google Ads at the same time if you have it. Most of the questions worth asking are cross-account questions, and an assistant holding analytics without the ad account can tell you what happened but not what it cost.
Why do GA4 and Google Ads conversion numbers disagree?
Because they count different events, on different clocks, and credit them to different clicks. Google Ads counts a conversion against the date of the ad click, while GA4 counts a key event against the date the person actually converted. A sale on Friday from a Monday click lands on different days in the two reports before anything else is considered.
Attribution then moves the number again. The two products do not have to share a model, and Google Ads also counts conversions it attributes across devices that GA4 may not join up. The full breakdown is in how GA4 key events differ from Google Ads conversions, and the counting rules on the ads side are in how Google Ads counts a conversion.
Asking an assistant to reconcile the two is a reasonable request, and a good answer names the reason for the gap rather than picking whichever number looks better. If the gap is far larger than the reporting differences explain, the problem is usually tracking rather than attribution, which is its own investigation in why Google Ads conversions stop tracking.
What can you actually ask once GA4 is connected?
The useful questions are the ones that would otherwise need three reports open at once. A few that answer well:
- Which landing pages took paid traffic last month and converted worst, ranked by spend rather than by sessions.
- Whether the drop in conversions last week shows up in GA4 as well, or only in the ad account.
- Which channels the people who converted actually arrived through the first time, not just the last.
- Whether a consent banner change moved the share of traffic being modelled rather than measured, which is covered in what Consent Mode v2 does to your numbers.
What you should not expect is a forecast dressed as a fact. An assistant reading GA4 can tell you what the property recorded. Anything beyond that is an opinion, and it should be labelled as one.
Does connecting GA4 let the AI change anything?
Reading analytics and changing an ad account are separate permissions, and reporting alone changes nothing. Analytics is a read surface. Where an assistant can also write, to pause a keyword or move a budget, that is a different authorization on a different account, and it should ask before every write rather than after.
That boundary is worth checking before you connect anything, whoever you connect it to. Our own position on it is set out in why every change waits for your approval, and the wider question of what an AI manager should and should not be trusted with is in AI managers compared with agencies.
What to do first
Connect GA4 and the ad account together, then ask one question you already know the answer to. A month of sessions, or last week's spend. If the assistant returns the number you can see in the interface, the connection is sound and the harder questions are worth asking. If it does not, fix that before trusting anything it says about which conversions to count.
GA4 and Google Ads are expected to disagree. Before treating a gap as a bug, check whether the dates, the attribution model and the conversion windows explain it.