To track AI referral traffic, set up GA4 to recognize the hostnames AI tools send visitors from: chatgpt.com, perplexity.ai, gemini.google.com, and copilot.microsoft.com. Build a custom channel group (or an exploration) that buckets those referrers into one "AI Assistants" channel, add a first-party event that fires when the referrer matches a known AI host, and watch the trend over time. A chunk of AI traffic arrives with no referrer and lands as direct, so measure the direction of travel, not a perfect absolute number.
Why can't I already see my AI referral traffic?
You probably can, in tiny fragments, scattered under "Referral" where you would never think to look. The reason AI traffic feels invisible is that GA4's default reports do not have a channel for it. A visit from ChatGPT shows up as a referral from chatgpt.com, a Perplexity visit shows up as perplexity.ai, a Gemini visit as gemini.google.com, and Copilot as copilot.microsoft.com. None of them roll up into a single category, so the volume looks trivial even when it is growing fast.
The fix is to stop hunting for AI traffic one hostname at a time and instead teach your analytics to recognize the whole category. Once you do, AI referral sessions stop hiding and start showing up as a named channel you can chart, segment, and tie to conversions. This is the downstream proof that the citation work is paying off, the visible counterpart to your share-of-voice measurement.
How do I see ChatGPT traffic in Google Analytics today?
Start with what GA4 gives you out of the box. Open Reports → Acquisition → Traffic acquisition, then add Session source / medium as a secondary dimension. Scroll for the AI hostnames. You will likely find chatgpt.com / referral, perplexity.ai / referral, and on mobile sometimes com.openai.chat as a referrer string from the iOS app.
This is enough to confirm AI traffic exists, but it is a terrible way to monitor it. You are reading a list, not a metric. The next two steps turn that scattered list into one number that moves.
How do I bucket every AI tool into one channel?
This is the single highest-leverage step. In GA4, go to Admin → Data settings → Channel groups, create a custom channel group, and add a new channel called AI Assistants. Define it with a rule that matches when the session source contains any of your AI hosts:
- chatgpt.com and chat.openai.com (ChatGPT)
- perplexity.ai (Perplexity)
- gemini.google.com (Gemini)
- copilot.microsoft.com and bing.com chat (Copilot)
- claude.ai (Claude)
Order the AI Assistants channel above Organic Search and Referral so AI sessions get claimed first. Now every report that uses the default channel grouping can be switched to yours, and AI traffic appears as one line. This is the same instinct as your citation audit: you cannot improve what you have not named.
If you would rather not touch the global channel grouping, build the same logic as an Exploration. Add a free-form report, set the dimension to Session source, add a filter that matches your AI host regex, and save it. It is faster to set up and easy to share, though it will not retro-label your standard reports.
Why does so much AI traffic show up as "direct"?
Because some AI surfaces strip the referrer before the visitor lands on you. App-based ChatGPT sessions, certain in-answer link behaviors, and privacy-conscious mobile contexts frequently send the click with no document.referrer, so GA4 files it under Direct or (none). You will never recover all of it, and any tool that claims a perfect count is overselling.
You can recover a meaningful slice, though, with two moves. First, tag the links you control. Wherever you can place a link inside content that AI tends to lift (your own docs, syndicated posts, partner pages), add UTM parameters like ?utm_source=chatgpt&utm_medium=ai_referral so the visit is labeled even when the referrer is missing. Second, fire a first-party event on page load when the referrer matches a known AI host. The reference template on this very page already does it, sending an ai_referral event with the ai_source:
var m = document.referrer.match(/chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai/i); if(m){ gtag('event','ai_referral',{ai_source:m[0]}); }
That event becomes a clean, queryable signal in GA4 that does not depend on channel grouping at all. Mark it as a key event if AI traffic is a priority and you want it surfaced in conversion paths.
How do I connect AI visits to conversions, not just sessions?
Session counts are vanity until they tie to something that matters. In GA4, build a comparison or segment where the channel equals AI Assistants (or where the ai_referral event fired), then layer your key events on top: form fills, demo requests, signups, purchases. Now you can answer the real question: not "how many AI visits did I get," but "what did AI visitors do, and were they worth more or less than organic visitors?"
In our experience running one visibility engine across more than 10 brands, AI-referred visitors often arrive further down the funnel, because the AI already pre-qualified them inside the answer. That makes the conversion rate the metric to watch, not raw volume. A small AI channel that converts at twice your site average is a louder buy signal than a big channel that bounces.
How often should I check, and what counts as progress?
Weekly is plenty for the trend; monthly is plenty for the report. Set up a saved exploration or a Looker Studio tile with three lines on it: AI sessions, AI conversions, and your citation rate from the answers themselves. Together they tell the whole story. Citation rate is the input, sessions are the proof the citation got clicked, and conversions are the proof the click mattered.
Be patient with the absolute numbers. AI referral traffic is small for almost everyone right now and grows in steps, not a smooth curve, because it spikes when you newly earn a citation for a high-volume question. Watch the direction of travel over months. If your AI sessions and conversions are both trending up while your citation rate climbs, the engine is working, even when the raw counts still look modest.
Where should I start if I have none of this yet?
Start with a baseline, not a build-out. Run your priority buyer questions through the AI tools, log which ones cite you, then check GA4 for any existing AI hostnames so you know where you stand today. Set up the AI Assistants channel and the ai_referral event the same afternoon. From there, the measurement runs itself and you spend your energy on earning more citations, which is the part that actually moves the line. If you want a clear read on where you stand and what to fix first, our free AI visibility audit and the full audit walkthrough are built to give you exactly that starting picture.
Questions people ask
In GA4, open Reports, then Acquisition, then Traffic acquisition, and add Session source as a secondary dimension. Visits from ChatGPT show up as chatgpt.com or chat.openai.com under referral. Because each AI tool reports a different hostname, the reliable approach is to build a custom channel group or an exploration that buckets chatgpt.com, perplexity.ai, gemini.google.com, and copilot.microsoft.com into one AI Assistants channel so you can see the whole category at once.
Some AI tools strip the referrer when sending you a visitor, especially in app contexts and on mobile, so the click lands in GA4 as direct or (none). The fix is to add UTM-tagged links wherever you control them, combine referrer detection with a first-party event that fires when document.referrer matches a known AI host, and accept that a portion of AI traffic will always be undercounted. Measuring the trend over time matters more than a perfect absolute number.
Track three things together: the volume of AI referral sessions in GA4 over time, the conversions those sessions produce, and your citation rate inside the AI answers themselves. Referral traffic is the downstream proof that a citation turned into a real visit. Pair it with a share-of-voice measurement so you can connect the visit back to the specific question and engine that sent it.
Want this done for you?
Want to know if AI is already sending you traffic, and how to grow it? Start with an AI visibility audit.
Get a free AI Visibility Audit →