How to see in Google Analytics whether ChatGPT sends you visitors

In GA4 you build a segment or an exploration on the known AI referrers: chatgpt.com, perplexity.ai, gemini.google.com and copilot.microsoft.com. That gives you a minimum. Part of AI traffic arrives without a recognizable source and ends up in Direct, and part of AI’s influence never leads to a click at all.

That last point is not a theoretical caveat. Below are numbers from our own sister site, and they illustrate the problem more sharply than any general percentage.

Which AI referrals GA4 does see

When someone comes to your site from an AI platform and the referrer is passed along, you simply see it. The domains you will find in your reports:

• chatgpt.com (and historically chat.openai.com)
• perplexity.ai
• gemini.google.com
• copilot.microsoft.com (and bing.com for Copilot answers in Bing)
• claude.ai

GA4 now also has its own channel group for this traffic. It catches part of it, not all, and that gap is exactly what this article is about.

Building an exploration in GA4, step by step

The menu paths in GA4 change regularly, so we describe what you build rather than where you click.

1. Create a new free-form exploration. This is the report type where you combine dimensions and metrics yourself.
2. Choose the referring source as dimension. In GA4 that is session source or session source/medium, depending on whether you want to see the medium too.
3. Add as metrics: sessions, engaged sessions, average engagement time and conversions.
4. Add a filter that matches the session source to the domains above. Use “contains” per domain instead of an exact match, so subdomains and variants are included.
5. Save it as a segment if you want to use it more often. Then you can put the same AI traffic next to your other channels in other reports.

Want to go beyond counting sessions? Add the landing page as a second dimension. Then you see which pages AI actually uses as a source, which is more useful than the total.

Why this is always a minimum

Four reasons your measurement by definition comes out too low:

• No referrer. Part of the referrals arrive without a source. That traffic ends up in Direct.
• Apps instead of browsers. Clicks from a mobile app more often produce no usable referrer than clicks from a browser.
• Copied links. Someone gets an answer with your name in it and later looks you up or types your address. That is AI influence that comes in as Direct or as a branded search.
• Answers without a click. If you are mentioned without anyone clicking through, there is no session to measure. This is probably the largest part, and it is fundamentally invisible in GA4.

Our own numbers, as an illustration

Briljant.nl, the Dutch edition of our platform, publishes about AI visibility every day. If there is a site where you would expect AI traffic, it is that one. In GA4, from August 8 through September 4, 2026, it looked like this:

Channel	Sessions	Share
Direct	370	59.7 percent
Organic Search	155	25.0 percent
Other channels	88	14.2 percent
AI Assistant	7	1.1 percent
Total	620	100 percent

Source: the Google Analytics 4 property of briljant.nl, August 8 through September 4, 2026, 620 sessions. Retrieved September 5, 2026.

Seven sessions in the AI Assistant channel group, against 370 sessions coming in as Direct. What that does mean: Direct is traffic whose source does not come through, and part of AI referrals end up there. What it does not mean: that those 370 sessions come from AI. We do not know that, and nobody who tells you otherwise does either.

The lesson is more modest and more useful: the number GA4 hands you as AI traffic is not a number you can base your AI strategy on.

What to do with the result

Three things, in order of usefulness:

1. Look at the landing pages, not the total. Which pages does AI send traffic to? Those are the pages used as a source, and so the pages to improve first.
2. Follow the trend, not the absolute number. The number is a minimum and stays one. The direction it moves in does say something.
3. Put it next to your branded search volume in Search Console. If that rises while you changed nothing else, you are probably seeing the part of AI influence that does not come in as a referral. See connecting Search Console to your AI visibility.

When GA4 is not enough

GA4 measures visitors. Your AI visibility consists of two things that are not in it: which AI systems fetch your pages, and whether you are mentioned in answers.

The first you see in your server logs and your robots configuration; see how AI crawlers read your site. The second you measure by asking the platforms the same customer questions repeatedly and noting whether you are mentioned; that is what the prompt tracker does every day. The traffic that follows is measured by GEO Analytics.

Together, plus your GA4 numbers, they give a complete picture. See also how to measure AI visibility and AI agents and the end of the website visit.

Also advertising in ChatGPT? Then you measure that paid part separately with the pixel and the Conversions API. See conversion tracking for ChatGPT ads.

Conclusion

GA4 can show you that there is AI traffic, and which pages it touches. It cannot show you how much there is. So treat the number as a minimum and a trend line, not a measurement.

Want to know whether you are mentioned at all? Asking the AI itself is the only direct method.