- To see Claude referral traffic in GA4, open Reports, Traffic acquisition, switch the dimension to Session source/medium, and search for
claude.ai / referral. - On 13 May 2026 Google added a native AI Assistant channel to GA4 that groups Claude, ChatGPT and Gemini sessions automatically. Use it for the headline number, but it lumps the assistants together.
- GA4 undercounts Claude, because the desktop app drops the referrer, so reconcile it against Microsoft Clarity, Bing and your server logs before you trust the figure.
To track claude.ai referral traffic in GA4, go to Reports, Traffic acquisition, change the primary dimension to Session source/medium, and search for claude. Any rows showing claude.ai / referral are people who clicked a link to your site from inside Claude. That is the 30-second answer. The rest of this guide is about getting the number right, because GA4 makes Claude traffic look smaller than it is.
This matters because AI assistants now send real, high-intent visitors, and you cannot grow a channel you cannot measure. If you want the upstream half of the job, getting Claude to cite you in the first place, that is what our free Claude SEO skills are for. This guide is the downstream half: proving it is working in your analytics. It pairs with our wider guide on the GA4 SEO metrics that actually matter.
See Claude Traffic in 30 Seconds
The fastest check needs no setup. In GA4, open Reports → Acquisition → Traffic acquisition, then set the primary dimension to Session source/medium and type claude into the search box.
You are looking for claude.ai / referral. That is GA4 telling you a session arrived from a clicked link inside Claude's web app. Add Sessions, Engaged sessions and your key event as columns and you have a usable Claude report in under a minute. For anything you want to keep, save it as an exploration so you are not rebuilding it each week.
The New AI Assistant Channel
On 13 May 2026, Google added a native AI Assistant channel to GA4's Default Channel Group. When a session arrives from a recognised assistant, GA4 now tags it with the medium ai-assistant and files it under that channel automatically. Google's own announcement names ChatGPT, Gemini and Claude.
This is genuinely useful: you get an AI referral number in your standard reports without building anything. But it has one limit that trips people up, it groups every assistant together. The channel total answers "how much AI traffic do I get", not "how much Claude traffic do I get". Here is how the two approaches compare.
| Approach | What it shows | Best for |
|---|---|---|
| AI Assistant channel | All recognised assistants (Claude, ChatGPT, Gemini) grouped as one channel, tagged ai-assistant | The headline "how big is AI traffic" number, tracked over time |
Manual source/medium (claude.ai / referral) | Claude on its own, separated from the other assistants | Measuring Claude specifically and tying it to conversions |
| AI traffic dashboard (Looker Studio) | Every AI source in one live view, pulled from your GA4 | Ongoing reporting and spotting where the numbers disagree |
Do not trust any single one. GA4 has known gaps (the next section is the big one), so the approach we take at StudioHawk is to blend them: the channel for the trend, the manual filter for Claude on its own, and a dashboard to pull it together. If you want a ready-made one, our free AI Traffic Looker Report does exactly that from your GA4. Belt and braces beats one number you only half-trust.
Why GA4 Undercounts Claude
Here is the part most guides skip: the number you just pulled is almost certainly too low. The Claude desktop app does not pass a referrer, so when someone clicks your link from the app rather than the browser, GA4 has nothing to attribute it to and dumps the session into Direct.
You cannot fully fix this inside GA4, but you can size it. If Claude clearly cites you a lot yet GA4 shows almost nothing, desktop usage is the likeliest explanation, and a chunk of your "Direct" traffic is really Claude. Reconcile it against sources that see what GA4 misses:
- Microsoft Clarity for AI-referred sessions and on-page behaviour, set up with our Microsoft Clarity for AI search guide.
- Bing Webmaster Tools for the citation side, covered in our Bing Citation Share guide.
- Server logs, where a Claude user-agent hitting your pages is hard evidence the bot has read you, even when the click never showed up.
Isolate Claude From the Rest
Once the AI Assistant channel is live, "AI traffic" and "Claude traffic" stop being the same thing. To report on Claude on its own, do not lean on the channel total. Build an exploration in GA4 with a filter where Session source contains claude.ai, and add a matching comparison for chatgpt.com and gemini.google.com if you want them side by side.
Save that as a segment and you can drop Claude into any report: landing pages, conversions, geography. That is how you answer the question a channel total never will, which of my pages is Claude actually sending people to, and what do they do next.
What to Do With Claude Traffic
Measuring Claude is the start, not the finish. The mistake is treating Claude traffic as a new game that needs new tricks. When a client sees Claude traffic, the one thing we tell them to do is the same thing that earned it: get the SEO fundamentals right, and use Claude to do that work faster.
Claude cites pages that answer a question clearly, are cleanly structured, and come from a source it trusts. That is just good SEO. So the move is not an AI-specific hack. Take the pages Claude already sends traffic to, sharpen the fundamentals (clear answers, clean structure, real authority), then widen the same pattern to your priority pages. The shortcut is to let Claude do the grind: our free Claude SEO skills turn each fundamental into a skill you run in seconds, from an AI Visibility Check to content, technical and citation audits like the AI Citation Monitor. Same fundamentals, a fraction of the time.
FAQ
How do I see Claude traffic in GA4?
Go to Reports, then Traffic acquisition, set the dimension to Session source/medium, and search for claude. Rows like claude.ai / referral are visitors who clicked a link inside Claude and landed on your site.
What is the GA4 AI Assistant channel?
A default channel Google added to GA4 on 13 May 2026. It groups sessions from recognised AI assistants (Google names ChatGPT, Gemini and Claude) under one AI Assistant channel and tags them with the medium ai-assistant, so you can see AI referral traffic without building a custom report.
Why is my Claude traffic so low in GA4?
The Claude desktop app does not pass a referrer, so those visits usually land in Direct instead of claude.ai / referral. If Claude cites you often but GA4 shows little Claude traffic, desktop app usage is the most likely reason. Cross-check Microsoft Clarity, Bing and your server logs.
How do I separate Claude from ChatGPT and Gemini?
The AI Assistant channel groups all recognised assistants together. To see Claude on its own, filter or build an exploration on Session source containing claude.ai, rather than relying on the channel total.
Does Claude referral traffic convert?
Claude visitors tend to arrive with specific, researched intent, so they often engage more per session than generic referral traffic. Track Claude as its own segment in GA4 and tie it to your conversion events to measure it properly for your own site.