We ran into this on our own site before we ever wrote about it. The analytics said a big chunk of recent visitors came from "Direct," the bucket that normally means someone typed your URL or used a bookmark. Except these were landing on deep pages nobody bookmarks, at odd hours, after we had started showing up in AI answers. The traffic was real. It was coming from assistants. And GA4 was filing almost all of it under the wrong label.
If you are trying to prove that AI referral traffic is worth your time, this is the wall you hit first. The visits exist, they convert, and your reports hide them. Here is why it happens and the exact fix.
Why AI Referral Traffic Lands in "Direct"
GA4 decides where a visit came from by reading the referrer, the little note a browser passes saying which page sent you. When that note is missing, GA4 has nothing to attribute, so it defaults to Direct. And a lot of assistant traffic arrives with no referrer at all.
Bot visits distort the same reports from the other side. If you have ever been offered cheap visitor packages, read why traffic generator software sends bots, not buyers.
The biggest cause is apps, and it plays out differently across clients:
- Mobile apps and in-app browsers. When someone taps a link inside the ChatGPT mobile app, the Perplexity app, or an in-app browser, the referrer is usually stripped before it reaches you.
- Desktop is more generous but inconsistent. A browser-based ChatGPT click often carries chatgpt.com as the referrer, and sometimes a utm_source=chatgpt.com tag, but that tagging is not applied to every click.
- Perplexity is mixed. Its web interface tends to pass a referrer reliably, while its app strips it like the others.
So a meaningful share of genuine AI referral traffic will always be invisible as referral, no matter what you do. The goal is to recover the share that is recoverable, which is most of it.
GA4 comparisons can mislead in other ways too. Our $1.9M e-commerce case study shows how a tracking gap in an earlier period can inflate a year-over-year growth figure.
The native GA4 channel helps, but only partly
Google added an "AI Assistant" channel to GA4 on May 13, 2026, and if you have seen it appear in your reports, that is why. It is a real improvement. It is also narrower than people assume. By most accounts it recognizes a short list, essentially ChatGPT, Gemini, and Claude, and leaves others out. Perplexity, Copilot, Grok, DeepSeek, and anything without a clean referrer stay buried in Referral or Direct.
So the native channel is a floor, not a ceiling. If your customers lean on Perplexity or Copilot, and plenty of B2B buyers do, the default channel will undercount you. The fix is to build your own channel that catches the full field of assistants.
Build a custom channel group that catches every assistant
This is a 10-minute setup in GA4, and it does not touch your tracking code.
- In the admin, under Data display, open Channel groups, and create a new custom channel group based on the default.
- Add a new channel, put it at the very top so it is evaluated before Referral and Organic, and name it something like AI Assistants.
Give that channel one condition: Session source matches a regex covering the assistant hosts. A practical pattern looks like this:
chatgpt\.com|chat\.openai\.com|openai\.com|gemini\.google\.com|bard\.google\.com|claude\.ai|perplexity\.ai|copilot\.microsoft\.com|bing\.com/chat|grok\.com|x\.ai|deepseek\.com|you\.com
Placing the channel above Referral matters, because GA4 assigns each session to the first channel it matches. If AI Assistants sits below Referral, perplexity.ai gets claimed as a referral before your rule ever runs. Put it first and it wins. Once saved, the group applies going forward and to historical data in most standard reports, so you can look back as well as ahead.
Also Read :- how to measure AI search ROI when the clicks disappear
Catch the UTM-tagged clicks too
Some assistant links arrive with a utm_source value, most commonly utm_source=chatgpt.com. Those are already clean, but it is worth making sure your regex matches the source value whether it comes from the referrer or a UTM tag, since GA4 populates session source from both. If you run your own campaigns, you can also tag any links you control, for example in a newsletter that an assistant might summarize, so those are never ambiguous. For anything you do not control, the channel group is your catch-all.
If you use a CRM or a lead form, pass the detected source through as a hidden field at submission. That way a lead that started in an assistant answer is labeled all the way through to the deal, not just in web analytics. We learned this the useful way while tracking where applications and enquiries actually originated, and it changes which channels look worthwhile.
The traffic you will never see in GA4 at all
One important boundary. There are two kinds of AI activity, and GA4 can only ever show you one.
- When a human clicks a link in an answer and lands on your site, GA4 can capture it, and the fix above recovers it.
- But when a crawler like GPTBot or OAI-SearchBot fetches your pages to build or ground an answer, GA4 never sees it, because the bot does not run your tracking tag.
That activity shows up only in your server logs or your CDN, never in analytics.
This matters because being read by those crawlers is how you become eligible to be cited in the first place, and you cannot manage it from GA4. If you want to know whether assistants are even allowed to read you, that is a server-log and robots question, and we cover the decision in should you block or allow AI crawlers. Getting cited once they can read you is a separate job, covered in how to get your brand cited by ChatGPT and Perplexity.
What to do with the numbers once you can see them
Recovering AI referral traffic from Direct is the start, not the point. Once the channel is clean, look at what those visitors do. In our experience assistant referrals often arrive further down the funnel than a cold search click, because the user already read a summary and is clicking to verify or to buy. If that holds for you, the right response is to treat AI referral traffic as a quality channel and resource it accordingly. Pair the GA4 view with a visibility check across the assistants themselves so you see both the clicks you get and the citations you earn, which we lay out in measuring your visibility in AI search.
Clean attribution also protects your budget. If AI traffic is hidden in Direct, it looks like it costs nothing and produces nothing, which is exactly how good channels get defunded by accident. Make it visible and let it earn its place.
If you would rather have this set up correctly once, with the channel group, CRM pass-through, and a reporting view that holds up, our team does this as part of our SEO services, and a free audit will show you how much of your Direct traffic is actually coming from assistants.
Frequently Asked Questions
Why does my ChatGPT and Perplexity traffic show up as Direct in GA4?
Because many assistant links, especially from mobile apps and in-app browsers, strip the referrer before it reaches your site. With no referrer, GA4 has nothing to attribute and defaults the session to Direct. A custom channel group recovers the visits that do carry a source.
Does GA4's built-in AI Assistant channel track all assistants?
No. The native channel added on May 13, 2026 recognizes a short list, essentially ChatGPT, Gemini, and Claude, and leaves out Perplexity, Copilot, Grok, DeepSeek, and referrer-less sessions. Build a custom channel group with a broader regex to capture the full set.
What regex should I use for an AI Assistants channel in GA4?
Match session source against the assistant hosts, for example chatgpt.com, chat.openai.com, gemini.google.com, claude.ai, perplexity.ai, copilot.microsoft.com, grok.com, deepseek.com, and you.com. Place the channel above Referral so it is matched first, since GA4 assigns each session to the first channel it fits.
Can I see GPTBot or AI crawler visits in GA4?
No. Crawlers like GPTBot and OAI-SearchBot fetch pages without running your tracking tag, so they never appear in GA4. That activity is visible only in server logs or your CDN. GA4 shows human clicks from AI answers, not the crawling that feeds those answers.
Will a custom channel group change my historical data?
Custom channel groups apply to past and future data in most standard GA4 reports, so you can analyze earlier periods once it is created. It does not alter your raw tracking or require code changes, it only reclassifies how existing sessions are grouped into channels.
Want this handled for you? Our AI SEO services can help you rank on Google and get cited by ChatGPT, Gemini, Claude and Perplexity.
Aashirvad Kumar
Writes about SEO, digital marketing and growth at Optimize For SEO.