Countnest

AI referral traffic in GA4: the sources assistants send, and a regex that catches them

By Adrian Ababei · Published · Facts checked 15 November 2026

Want these numbers for your own site? Start a 30-day free trial of Countnest, no card required, or see pricing.

How an AI visit gets its source

An assistant can only tell your analytics where a visit came from in two ways:

  1. The referrer. When someone clicks a link in a web-based assistant, the browser usually passes the assistant's hostname, for example chatgpt.com or perplexity.ai. GA4 stores it as the session source.
  2. A campaign tag on the link. OpenAI says ChatGPT automatically includes utm_source=chatgpt.com in referral URLs. The tag is part of the link, so it still works when the referrer is dropped, and it stays on the link if someone copies and shares it.

If a visit carries neither, for example a link opened from an app that sends no referrer, it is counted as Direct. No tool can recover it reliably.

Where GA4 puts these visits

GA4's default channel group has an AI Assistant channel. Google describes it as visits "from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok". The rule behind it: the medium exactly matches ai-assistant, and GA4 sets that medium, with the campaign (ai-assistant), when the referrer matches Google's list of AI assistants.

Two things to know:

For what the built-in channel shows and misses, see GA4's AI Assistant channel.

The sources AI assistants send

This is the list Countnest uses to recognise 17 assistants (checked 15 November 2026). The hostname is what GA4 shows as the source.

AssistantReferrer hostnamesTag documented by the vendorSafe in a GA4 regex?
ChatGPTchatgpt.com, chat.openai.comutm_source=chatgpt.com (OpenAI)Yes
Perplexityperplexity.aiNone documentedYes
Geminigemini.google.comNone documentedYes
Claudeclaude.aiNone documentedYes
Microsoft Copilotcopilot.microsoft.com, copilot.cloud.microsoftNone documentedYes
DeepSeekchat.deepseek.com, deepseek.comNone documentedYes
Grokgrok.comNone documentedYes
Meta AImeta.aiNone documentedYes
Mistral (Le Chat)chat.mistral.aiNone documentedYes
You.comyou.comNone documentedYes
Poepoe.comNone documentedYes
Phindphind.comNone documentedYes
Duck.aiduck.aiNone documentedYes
Qwenchat.qwen.aiNone documentedYes
Kagi Assistantkagi.com (assistant pages only)None documentedNo: the same host carries Kagi search
Brave Leosearch.brave.com (assistant pages only)None documentedNo: the same host carries Brave Search
HuggingChathuggingface.co (chat pages only)None documentedNo: the same host carries the rest of Hugging Face

Countnest can tell the last three apart because it reads the referrer path as well as the host. GA4's source holds only the hostname, so leave them out of a GA4 pattern.

A regex that catches them, and nothing else

This pattern matches the 16 safe hostnames above, with or without a subdomain such as www.:

^(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|claude\.ai|copilot\.microsoft\.com|copilot\.cloud\.microsoft|deepseek\.com|grok\.com|meta\.ai|chat\.mistral\.ai|you\.com|poe\.com|phind\.com|duck\.ai|chat\.qwen\.ai)$

We tested it against real hostnames. It matches chatgpt.com, chat.openai.com, www.perplexity.ai and chat.deepseek.com. It does not match bayou.com, notyou.com, mail.google.com, duckduckgo.com, gptzero.me or mistral.ai (the company site, not the chat).

The anchors ^ and $ and the escaped dots are what make it safe. Google's help page offers an example pattern for an AI channel, but it is built from broad pieces such as .*gpt.* and .*copilot.*. Those also match any source that merely contains the letters, for example gptzero.me. Use Google's example as a starting point, not as your final rule.

Where AI traffic still hides

  • Direct: app links that send no referrer and no tag.
  • Organic Search: clicks from Google AI Overviews and AI Mode, by Google's definition.
  • Referral: any assistant you haven't added to your pattern yet. Check your source list every month or two. Google's help page also says to update the regex when the assistants change.
  • Inflated ChatGPT counts: utm_source=chatgpt.com travels with a copied link, so a link pasted into a chat or an email still counts as ChatGPT.

For how big ChatGPT traffic is in published studies, and how its share compares with Google, see How much traffic does ChatGPT really send?.

Doing it without a regex

Countnest recognises all 17 assistants from the referrer and from tags such as utm_source=chatgpt.com, with no setup. The AI traffic tab shows each assistant on its own row, the pages it sends people to, a trend per engine, AI revenue, and AI visit quality next to search. Click an engine to filter the whole dashboard to it. See AI traffic analytics or start a 30-day free trial, no card required.

Questions and answers

What source does ChatGPT traffic have in GA4?

Usually chatgpt.com. OpenAI says ChatGPT adds utm_source=chatgpt.com to referral URLs, so tagged clicks show that source even when the browser sends no referrer. GA4 then files recognised assistants in its AI Assistant channel.

Is Google AI Overviews traffic in GA4's AI Assistant channel?

No. Google says the AI Assistant channel excludes AI Overviews and AI Mode, and that Organic Search includes them.

Can I use Google's example regex for AI assistants?

As a starting point. It uses broad pieces such as .*gpt.*, which also match unrelated sources such as gptzero.me. An anchored list of exact hostnames is safer.

Why leave Kagi, Brave and HuggingChat out of the GA4 pattern?

Their hostnames also carry search or other traffic, and GA4's source shows only the hostname. Countnest separates them by also reading the referrer path.

Do AI assistants send the prompt?

No. Assistants don't pass the question the person typed. You see the source and the landing page only.

See your own numbers in minutes

30-day free trial, no card required. Then from $14 a month. Cancel anytime.

Start free for 30 days

Sources

Facts checked on 15 November 2026.