How to Track AI Traffic in Google Analytics

It is already in your analytics. It is just filed under Referral with everything else.

Why You Cannot See It By Default

Visits from AI assistants arrive as ordinary referral traffic. Google Analytics does not have an AI channel, so those sessions sit in the Referral bucket mixed in with directories, partner sites and forums.

The result is that most businesses assume they get no AI traffic, when in fact they get some and it is filed under a hostname they have never looked at.

Separating it out takes about fifteen minutes and it is worth doing before you spend any money on this channel, because it turns the question from a guess into a number.

The Sources To Look For

The session source values you want to catch are the hostnames these assistants send from. The main ones at present are chatgpt.com and chat.openai.com for ChatGPT, perplexity.ai for Perplexity, gemini.google.com for Gemini, copilot.microsoft.com for Microsoft Copilot, and claude.ai.

New ones appear regularly and hostnames change, so treat this as a list to revisit rather than a one time setup. The safest approach is to match on a pattern rather than an exact list, catching anything whose source contains chatgpt, perplexity, gemini, copilot or claude.

One thing this will not catch is Google AI Overviews. Clicks from an overview are attributed to ordinary Google organic search, so there is no way to separate them in GA4. Anyone claiming to report on your AI Overview traffic specifically is estimating.

Building The Segment

In GA4, go to Explore and create a blank exploration. Under Segments, add a new session segment.

Set the condition to Session source, choose the matches regex option, and enter a pattern matching the hostnames above, separated by pipes. Name it AI Assistants and save.

Drag that segment into your exploration, then add Session source as a dimension and Sessions, Engaged sessions and your key conversion event as metrics. You now have a table showing which assistants send traffic and what it does.

Add Landing page as a second dimension. This is the interesting one, because it tells you which of your pages the assistants are citing, which is otherwise very hard to find out.

Making It Permanent

An exploration is fine for a look, but you will not remember to open it. Two ways to make it stick.

Create a comparison on your standard reports using the same condition, so you can toggle AI traffic on any report you already look at.

Or create a custom channel group in Admin, under Data display, with a new channel called AI Assistants defined by the same source pattern, placed above Referral in the ordering so it captures those sessions first. This is the cleaner option because the traffic then appears as its own channel in every acquisition report from that point forward.

Custom channel groups apply from the date you create them and do not backfill, so make one now even if you are not ready to act on it.

Reading The Numbers Honestly

Expect the volume to be small. For a typical local business this is tens of sessions a month at most. Anyone telling you otherwise is either working with a national brand or counting something else.

What is usually more interesting is the quality. AI referred sessions frequently show higher engagement and conversion rates than average, because the visitor arrived after being told by name that you were the right choice, rather than by scanning ten links.

So read it as a share of conversions rather than a share of traffic. A channel producing two percent of sessions and eight percent of inquiries is telling you something worth acting on.

One caveat specific to this site and worth stating generally. If you gate analytics behind cookie consent, and you should, then everything in GA4 undercounts, because sessions from visitors who decline are never recorded. Use Search Console for anything where completeness matters, and treat GA4 as a directional picture of behavior rather than a headcount.

What To Do With It

The landing page dimension is the actionable part. The pages appearing there are the pages assistants find quotable, and they usually have something in common: a direct answer near the top, real specifics, a clear structure.

Apply whatever those pages are doing to your commercial pages. That is a cheaper and more reliable route to more of this traffic than anything sold as a GEO service.

Then watch for the pages you expected to see and do not. A service page absent from that list, on a topic customers definitely ask about, is usually a page that never answers the question directly.

This kind of reading is what askotter automates once a site is live. The site is connected to Analytics and Search Console from day one, watches which pages earn citations and inquiries and which quietly stop, and writes the proposed fix with the data attached for a person to approve before it ships.