Stop guessing who to call. See who's ready to buy.Stop guessing who to callGet early access
Stop guessing who to call. See who's ready to buy.Stop guessing who to callGet early access
Stop guessing who to call. See who's ready to buy.Stop guessing who to callGet early access

›

›

›

›

How to track AI search traffic in GA4 in 2026

How to track AI search traffic in GA4 in 2026

How to track AI search traffic in GA4 in 2026

How to track AI search traffic in GA4 in 2026

How to track AI search traffic in GA4 in 2026

How to track AI search traffic in GA4 in 2026

Author

Aljaz Peklaj

Track AI search traffic in GA4 2026 hero, AI assistant referrals from ChatGPT, Perplexity, Gemini and Claude in GA4
Share this article
Table of content
0 min read

How to track AI search traffic in GA4 in 2026

TL;DR

  • Since 13 May 2026, GA4's default channel group has an AI Assistant channel for visits from chatbots like ChatGPT, Gemini and Claude. Clicks from Google's AI Overviews and AI Mode still count as Organic Search.

  • Google does not publish the list of assistants behind that channel, so build a custom channel group with your own regex. Custom groups apply to past data, and you control which domains count.

  • ChatGPT adds utm_source=chatgpt.com to its links. Visits that arrive with no referrer and no UTM tag land in Direct, so GA4 will always undercount AI traffic.

  • Fill the gaps with Search Console's generative AI report (impressions in AI Overviews and AI Mode, live for all sites since 31 August 2026), Bing's AI Performance report and your server logs for AI crawlers.

To track AI search traffic in GA4, use two things: the AI Assistant channel Google added to the default channel group in May 2026, and a custom channel group with a regex that matches the referrer domains of the assistants you care about. That gives you sessions, landing pages and key events from ChatGPT, Perplexity, Gemini, Copilot, Claude and others. This guide gives the exact regex, the setup steps, the reports to build and what GA4 cannot see, with the Search Console, Bing and server log checks that fill the gap.

Which AI assistants send traffic, and how they show up in GA4

When someone clicks a link inside an AI answer, the visit reaches your site like any other referral. GA4 reads the referrer (or the UTM tag, if there is one) and records the domain as the session source. So the first job is to know which domains the assistants run on.

Track AI search traffic in GA4 2026, referrer domains for ChatGPT, Perplexity, Gemini, Copilot, Claude and 5 more

Figure: the domains each AI assistant runs on, checked 15 October 2026. Google's AI Overviews and AI Mode have no separate domain.

Three details matter before you build anything:

  • ChatGPT tags its links. OpenAI's publishers and developers FAQ says "ChatGPT automatically includes the UTM parameter utm_source=chatgpt.com in referral URLs." That makes ChatGPT the easiest assistant to track, because the source survives even when the browser drops the referrer.

  • chat.openai.com is legacy. It now redirects to chatgpt.com, but keep it in your regex so older links and bookmarks are counted.

  • Google's own AI features are not separate. GA4's default channel group definitions say Organic Search includes "Google's AI Overviews and AI Mode." There is no referrer that tells a click from an AI Overview apart from a normal blue link.

ChatGPT is still the biggest assistant, but not by as much as a year ago. Similarweb's 2026 generative AI data shows ChatGPT's share of visits to generative AI websites fell from about 76% in June 2025 to roughly 53% by May 2026, while Gemini rose from under 9% to around 27 to 28% and Claude from about 2% to close to 9%. A channel that only matches ChatGPT now misses a growing share.

Track AI search traffic GA4 2026 context, share of generative AI visits, ChatGPT about 53%, Gemini around 27 to 28%

Figure: share of visits to generative AI websites, June 2025 and May 2026, from Similarweb. This is visits to the assistants, not referrals they send.

The AI Assistant channel Google added in May 2026

Google's What's new in Google Analytics page dates the change to 13 May 2026: "Google Analytics now provides a dedicated way to measure and analyze traffic originating from popular AI assistants." GA4 now sets the medium to "ai-assistant" and the campaign to "(ai-assistant)" when the referrer matches its list, and shows those sessions in a new AI Assistant channel.

Track AI search traffic in GA4 2026, Google's default AI Assistant channel, medium ai-assistant above Referral

Figure: the AI Assistant and Referral rows in Google's default channel group definitions, Analytics Help, 15 October 2026.

The default channel is a good start, but it has three limits:

  • You cannot see or change the list. The help page says the referrer is matched against "a list of AI Assistants" and names ChatGPT, Gemini, Deepseek, Copilot and Grok as examples. The full list is not published, and Google says "it's not possible to edit the Google Analytics default channel group."

  • Older data may still sit in Referral. Google does not say whether the new channel was applied to sessions before May 2026. Custom channel groups, by contrast, "can be applied to your reports retroactively," per the custom channel groups help page.

  • Source Group helps, but is broad. On 11 June 2026 Google added a Source Group dimension with "built-in grouping for emerging traffic sources like ChatGPT (OpenAI) and Perplexity." Google says it is populated retroactively, which makes it useful for a quick look back.

So keep the default channel for quick checks, and build your own group for reporting you can explain line by line.

Build a custom channel group for AI traffic

You need Editor access or higher on the property. Standard GA4 properties can have 2 custom channel groups (5 on GA4 360), each with up to 50 channels.

  1. In Admin, under Data display, open Channel groups.

  2. Click Create new channel group. GA4 starts you with a copy of the default group, so all existing channels stay in place.

  3. Name it, for example "Channels with AI".

  4. Click Add new channel and name it "AI assistants".

  5. Add a condition: Source, matches regex, and paste the regex below.

  6. Save the channel, click Reorder and drag "AI assistants" to the top of the list, above Referral and Organic Search. Google's rule is that traffic goes into "the first channel whose definition it matches given the current order."

  7. Click Save group.

Track AI search traffic in GA4 2026, Google's AI assistants custom channel example with matches regex and the reorder step

Figure: Google's own example for an AI assistants channel, custom channel groups help page, 15 October 2026.

The regex

GA4 regex is full match and case sensitive by default, per Google's regex help page. The pattern below is anchored to the end of the domain, so a lookalike such as chatgpt.com.example.net or sosmeta.ai does not match, while (.*\.)? still allows subdomains such as www.perplexity.ai. Source values for these referrers are lowercase domains, so keep the pattern lowercase:

^(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|chat\.deepseek\.com|grok\.com|chat\.mistral\.ai|meta\.
Track AI search traffic GA4 regex 2026 test, GROU pattern matches 11 assistant domains, rejects lookalikes like sosmeta.ai

Figure: the GROU regex and Google's help page sample tested against real source values. GROU test with Python full match, 15 October 2026.

Why not paste Google's sample? Its regex starts with ^.*ai|, which matches any source that ends in "ai", and .*gpt.* and .*copilot.*, which match any source containing those letters. In our test it counted notion.ai, jasper.ai and copilot.github.com as AI assistants, and it missed chat.deepseek.com and grok.com. A loose pattern such as .*(chatgpt\.com|meta\.ai).* has the opposite problem in places: it also matches lookalikes like chatgpt.com.example.net and sosmeta.ai. Listing exact, anchored domains is longer, but every match is one you chose. Update the list when a new assistant matters to your buyers, as Google itself advises.

Reports to build once the channel exists

Custom channel groups work as a primary dimension in the Acquisition reports and as a dimension in explorations, so you can answer the questions that matter for B2B.

Traffic by assistant. Open Reports > Acquisition > Traffic acquisition, switch the primary dimension to your new channel group, then add Session source as a secondary dimension. You now see sessions, engaged sessions and key events for each assistant.

Landing pages. In Explore, start a Free form exploration. Add your channel group, Session source and Landing page + query string as dimensions, and Sessions, Engaged sessions and Key events as metrics. Filter to the "AI assistants" channel. This shows which pages AI answers send people to. Expect a lot of homepage traffic: Similarweb's desktop panel data shows that after ChatGPT made brand links more prominent on 7 May 2026, the share of its desktop referrals landing on a brand's homepage jumped from roughly 26 to 32% to around 60%.

Key events. Mark your demo request, contact form and trial sign-up as key events (Admin > Data display > Events, then the star icon). Then compare key event rate for AI assistants against Organic Search and Referral. Small numbers swing hard, so read this quarterly, not weekly.

Trend. Set the date range to 12 months and compare month by month. Because custom channel groups apply to past data, your chart starts before the May 2026 change.

If you want to act on the accounts behind those visits, not only count them, visitor identification tools are the next step. Our RB2B pricing guide and signal-based lead generation playbook cover how teams turn site visits into a daily list.

What GA4 cannot see

GA4 only sees clicks. Most of what happens in AI search never becomes a click on your site, and some clicks arrive with no label.

Track AI search traffic in GA4 2026, where AI visits land: AI Assistant, Organic Search or Direct, plus GSC and Bing

Figure: where AI search activity shows up, based on Google Analytics, Search Console and Bing Webmaster Tools documentation, 15 October 2026.

  • AI Overviews and AI Mode clicks count as Organic Search. You cannot split them out in GA4.

  • Dark traffic lands in Direct. If the browser or app passes no referrer and the link has no UTM tag, GA4 records the session as Direct: source "(direct)", medium "(none)". Copied links, links opened from some desktop and mobile apps, and people who read an answer and then type your URL all end up here.

  • Mentions without clicks are invisible. If an assistant names your company and the reader books a call a week later from a Google search, GA4 credits Organic Search.

  • ChatGPT's tag names a source only. OpenAI documents utm_source=chatgpt.com and says nothing about a medium, so check in your own property whether those sessions sit in AI Assistant, Referral or Unassigned before you report on the default channel. Matching on Source, as the regex above does, avoids the question.

That is why the honest way to report AI traffic is as a floor, not a total. Pair it with a "How did you hear about us?" field on your demo form, and read answers that mention ChatGPT or "AI" alongside the GA4 numbers.

Search Console and Bing: visibility before the click

Google launched Search generative AI performance reports in Search Console on 3 June 2026, and rolled them out "to all websites worldwide" as of 31 August 2026. The report shows impressions only: how often links to your site appeared in AI Overviews and AI Mode, by page, country, device and date. It does not show clicks or queries. The same data stays inside the Web search type of the main Performance report.

Bing went further on one point. AI Performance in Bing Webmaster Tools, in public preview since 10 February 2026, shows how often your content is cited in Microsoft Copilot and Bing's AI summaries, which URLs are cited and a sample of the "grounding queries" the AI used to find them.

Together they answer the question GA4 cannot: are we being shown at all? Use them for pages and topics, and GA4 for sessions and key events. Our GEO guide for B2B covers how to raise those citation numbers, and our roundup of AI visibility tools covers trackers that sample prompts across assistants.

Server logs: which AI crawlers read your pages

Assistants can only cite pages they can fetch. Your server or CDN logs show which AI bots visit, how often and which URLs they request. Each company publishes its user agents.

Track AI search traffic GA4 2026, AI crawler user agents GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot and purpose

Figure: AI crawler and fetcher user agents and what each is for, from OpenAI, Perplexity, Anthropic and Google documentation, 15 October 2026.

  • OpenAI lists OAI-SearchBot, GPTBot, ChatGPT-User and OAI-AdsBot. OAI-SearchBot decides whether pages can appear in ChatGPT search; GPTBot crawls for model training. OpenAI says the two settings are independent, and that robots.txt changes take about 24 hours to apply to search. ChatGPT-User fetches pages when a user asks, and "robots.txt rules may not apply."

  • Perplexity lists PerplexityBot and Perplexity-User. PerplexityBot surfaces sites in Perplexity search; Perplexity-User "generally ignores robots.txt rules" because a user requested the fetch.

  • Anthropic lists ClaudeBot (training), Claude-User (user requests) and Claude-SearchBot (search indexing) on its crawler help page.

  • Google has no separate AI user agent. Google-Extended is a robots.txt token only, and Google says it "does not impact a site's inclusion in Google Search."

A quick first check on a standard access log:

That lists the 50 URLs AI bots requested most. Anyone can fake a user agent, so for anything you act on, check the IP against the lists OpenAI and Perplexity publish (for example openai.com/searchbot.json and perplexity.com/perplexitybot.json). If your key pages never show up, check robots.txt and your CDN's bot rules before you rewrite content. Pages that bots fetch but assistants never cite are the ones to improve; our content refresh playbook covers how.

A monthly AI traffic report in five lines

Once the setup is done, one short report each month is enough:

  1. Sessions and key events from the "AI assistants" channel, by assistant.

  2. Top 10 landing pages from AI assistants.

  3. Search Console generative AI impressions, top pages.

  4. Bing AI Performance citations, top pages.

  5. AI crawler hits on your 20 most important URLs.

Put the 2026 total in your year-end review. Our B2B marketing year in review covers how search clicks moved across 2026, which is the context for whatever your own numbers show.

FAQ

Does GA4 track ChatGPT traffic?

Yes. ChatGPT adds utm_source=chatgpt.com to its links, so visits show chatgpt.com as the source. Since 13 May 2026, GA4 also puts recognised AI assistant referrals in a default AI Assistant channel. Visits with no referrer and no tag still land in Direct.

What is the AI Assistant channel in GA4?

It is a channel Google added to the default channel group on 13 May 2026. When the referrer matches Google's list of AI assistants, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant). It excludes Google's AI Overviews and AI Mode.

What regex should I use for AI traffic in GA4?

Use a Source "matches regex" condition with exact, anchored, lowercase domains, for example ^(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|chat\.deepseek\.com|grok\.com|chat\.mistral\.ai|meta\.ai)$, and place the channel above Referral.

Can I see AI Overviews and AI Mode traffic in GA4?

No. GA4 counts those clicks as Organic Search. Search Console's generative AI performance report shows impressions in AI Overviews and AI Mode, by page, but not clicks.

Why is my AI traffic so low in GA4?

GA4 only records clicks that carry a referrer or UTM tag. Mentions without clicks, copied links and some app traffic are invisible or land in Direct, so treat GA4's AI number as a floor.

Which user agents do AI crawlers use?

The main ones are GPTBot, OAI-SearchBot and ChatGPT-User (OpenAI), PerplexityBot and Perplexity-User (Perplexity), and ClaudeBot, Claude-User and Claude-SearchBot (Anthropic). Google uses its normal crawlers, with Google-Extended as a robots.txt token only.

Bottom line

Tracking AI search traffic in GA4 comes down to one setup step: a custom channel group with an exact-domain regex, placed above Referral, on top of the AI Assistant channel Google added in May 2026. That gives you sessions, landing pages and key events by assistant, including history. It will never be the full picture, because AI Overviews clicks count as Organic Search and unlabelled clicks count as Direct, so pair it with Search Console's generative AI report, Bing's AI Performance report and your server logs.

If you want AI visibility to turn into booked meetings, book a call with GROU.

About this guide

We are GROU, a B2B pipeline agency that runs lead generation, outbound and LinkedIn content for B2B companies. The steps and definitions in this guide come from Google Analytics, Google Search Central, Bing, OpenAI, Perplexity and Anthropic documentation and Similarweb data, checked on 15 October 2026.

This article has no affiliate links.

How to track AI search traffic in GA4 in 2026

TL;DR

  • Since 13 May 2026, GA4's default channel group has an AI Assistant channel for visits from chatbots like ChatGPT, Gemini and Claude. Clicks from Google's AI Overviews and AI Mode still count as Organic Search.

  • Google does not publish the list of assistants behind that channel, so build a custom channel group with your own regex. Custom groups apply to past data, and you control which domains count.

  • ChatGPT adds utm_source=chatgpt.com to its links. Visits that arrive with no referrer and no UTM tag land in Direct, so GA4 will always undercount AI traffic.

  • Fill the gaps with Search Console's generative AI report (impressions in AI Overviews and AI Mode, live for all sites since 31 August 2026), Bing's AI Performance report and your server logs for AI crawlers.

To track AI search traffic in GA4, use two things: the AI Assistant channel Google added to the default channel group in May 2026, and a custom channel group with a regex that matches the referrer domains of the assistants you care about. That gives you sessions, landing pages and key events from ChatGPT, Perplexity, Gemini, Copilot, Claude and others. This guide gives the exact regex, the setup steps, the reports to build and what GA4 cannot see, with the Search Console, Bing and server log checks that fill the gap.

Which AI assistants send traffic, and how they show up in GA4

When someone clicks a link inside an AI answer, the visit reaches your site like any other referral. GA4 reads the referrer (or the UTM tag, if there is one) and records the domain as the session source. So the first job is to know which domains the assistants run on.

Track AI search traffic in GA4 2026, referrer domains for ChatGPT, Perplexity, Gemini, Copilot, Claude and 5 more

Figure: the domains each AI assistant runs on, checked 15 October 2026. Google's AI Overviews and AI Mode have no separate domain.

Three details matter before you build anything:

  • ChatGPT tags its links. OpenAI's publishers and developers FAQ says "ChatGPT automatically includes the UTM parameter utm_source=chatgpt.com in referral URLs." That makes ChatGPT the easiest assistant to track, because the source survives even when the browser drops the referrer.

  • chat.openai.com is legacy. It now redirects to chatgpt.com, but keep it in your regex so older links and bookmarks are counted.

  • Google's own AI features are not separate. GA4's default channel group definitions say Organic Search includes "Google's AI Overviews and AI Mode." There is no referrer that tells a click from an AI Overview apart from a normal blue link.

ChatGPT is still the biggest assistant, but not by as much as a year ago. Similarweb's 2026 generative AI data shows ChatGPT's share of visits to generative AI websites fell from about 76% in June 2025 to roughly 53% by May 2026, while Gemini rose from under 9% to around 27 to 28% and Claude from about 2% to close to 9%. A channel that only matches ChatGPT now misses a growing share.

Track AI search traffic GA4 2026 context, share of generative AI visits, ChatGPT about 53%, Gemini around 27 to 28%

Figure: share of visits to generative AI websites, June 2025 and May 2026, from Similarweb. This is visits to the assistants, not referrals they send.

The AI Assistant channel Google added in May 2026

Google's What's new in Google Analytics page dates the change to 13 May 2026: "Google Analytics now provides a dedicated way to measure and analyze traffic originating from popular AI assistants." GA4 now sets the medium to "ai-assistant" and the campaign to "(ai-assistant)" when the referrer matches its list, and shows those sessions in a new AI Assistant channel.

Track AI search traffic in GA4 2026, Google's default AI Assistant channel, medium ai-assistant above Referral

Figure: the AI Assistant and Referral rows in Google's default channel group definitions, Analytics Help, 15 October 2026.

The default channel is a good start, but it has three limits:

  • You cannot see or change the list. The help page says the referrer is matched against "a list of AI Assistants" and names ChatGPT, Gemini, Deepseek, Copilot and Grok as examples. The full list is not published, and Google says "it's not possible to edit the Google Analytics default channel group."

  • Older data may still sit in Referral. Google does not say whether the new channel was applied to sessions before May 2026. Custom channel groups, by contrast, "can be applied to your reports retroactively," per the custom channel groups help page.

  • Source Group helps, but is broad. On 11 June 2026 Google added a Source Group dimension with "built-in grouping for emerging traffic sources like ChatGPT (OpenAI) and Perplexity." Google says it is populated retroactively, which makes it useful for a quick look back.

So keep the default channel for quick checks, and build your own group for reporting you can explain line by line.

Build a custom channel group for AI traffic

You need Editor access or higher on the property. Standard GA4 properties can have 2 custom channel groups (5 on GA4 360), each with up to 50 channels.

  1. In Admin, under Data display, open Channel groups.

  2. Click Create new channel group. GA4 starts you with a copy of the default group, so all existing channels stay in place.

  3. Name it, for example "Channels with AI".

  4. Click Add new channel and name it "AI assistants".

  5. Add a condition: Source, matches regex, and paste the regex below.

  6. Save the channel, click Reorder and drag "AI assistants" to the top of the list, above Referral and Organic Search. Google's rule is that traffic goes into "the first channel whose definition it matches given the current order."

  7. Click Save group.

Track AI search traffic in GA4 2026, Google's AI assistants custom channel example with matches regex and the reorder step

Figure: Google's own example for an AI assistants channel, custom channel groups help page, 15 October 2026.

The regex

GA4 regex is full match and case sensitive by default, per Google's regex help page. The pattern below is anchored to the end of the domain, so a lookalike such as chatgpt.com.example.net or sosmeta.ai does not match, while (.*\.)? still allows subdomains such as www.perplexity.ai. Source values for these referrers are lowercase domains, so keep the pattern lowercase:

^(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|chat\.deepseek\.com|grok\.com|chat\.mistral\.ai|meta\.
Track AI search traffic GA4 regex 2026 test, GROU pattern matches 11 assistant domains, rejects lookalikes like sosmeta.ai

Figure: the GROU regex and Google's help page sample tested against real source values. GROU test with Python full match, 15 October 2026.

Why not paste Google's sample? Its regex starts with ^.*ai|, which matches any source that ends in "ai", and .*gpt.* and .*copilot.*, which match any source containing those letters. In our test it counted notion.ai, jasper.ai and copilot.github.com as AI assistants, and it missed chat.deepseek.com and grok.com. A loose pattern such as .*(chatgpt\.com|meta\.ai).* has the opposite problem in places: it also matches lookalikes like chatgpt.com.example.net and sosmeta.ai. Listing exact, anchored domains is longer, but every match is one you chose. Update the list when a new assistant matters to your buyers, as Google itself advises.

Reports to build once the channel exists

Custom channel groups work as a primary dimension in the Acquisition reports and as a dimension in explorations, so you can answer the questions that matter for B2B.

Traffic by assistant. Open Reports > Acquisition > Traffic acquisition, switch the primary dimension to your new channel group, then add Session source as a secondary dimension. You now see sessions, engaged sessions and key events for each assistant.

Landing pages. In Explore, start a Free form exploration. Add your channel group, Session source and Landing page + query string as dimensions, and Sessions, Engaged sessions and Key events as metrics. Filter to the "AI assistants" channel. This shows which pages AI answers send people to. Expect a lot of homepage traffic: Similarweb's desktop panel data shows that after ChatGPT made brand links more prominent on 7 May 2026, the share of its desktop referrals landing on a brand's homepage jumped from roughly 26 to 32% to around 60%.

Key events. Mark your demo request, contact form and trial sign-up as key events (Admin > Data display > Events, then the star icon). Then compare key event rate for AI assistants against Organic Search and Referral. Small numbers swing hard, so read this quarterly, not weekly.

Trend. Set the date range to 12 months and compare month by month. Because custom channel groups apply to past data, your chart starts before the May 2026 change.

If you want to act on the accounts behind those visits, not only count them, visitor identification tools are the next step. Our RB2B pricing guide and signal-based lead generation playbook cover how teams turn site visits into a daily list.

What GA4 cannot see

GA4 only sees clicks. Most of what happens in AI search never becomes a click on your site, and some clicks arrive with no label.

Track AI search traffic in GA4 2026, where AI visits land: AI Assistant, Organic Search or Direct, plus GSC and Bing

Figure: where AI search activity shows up, based on Google Analytics, Search Console and Bing Webmaster Tools documentation, 15 October 2026.

  • AI Overviews and AI Mode clicks count as Organic Search. You cannot split them out in GA4.

  • Dark traffic lands in Direct. If the browser or app passes no referrer and the link has no UTM tag, GA4 records the session as Direct: source "(direct)", medium "(none)". Copied links, links opened from some desktop and mobile apps, and people who read an answer and then type your URL all end up here.

  • Mentions without clicks are invisible. If an assistant names your company and the reader books a call a week later from a Google search, GA4 credits Organic Search.

  • ChatGPT's tag names a source only. OpenAI documents utm_source=chatgpt.com and says nothing about a medium, so check in your own property whether those sessions sit in AI Assistant, Referral or Unassigned before you report on the default channel. Matching on Source, as the regex above does, avoids the question.

That is why the honest way to report AI traffic is as a floor, not a total. Pair it with a "How did you hear about us?" field on your demo form, and read answers that mention ChatGPT or "AI" alongside the GA4 numbers.

Search Console and Bing: visibility before the click

Google launched Search generative AI performance reports in Search Console on 3 June 2026, and rolled them out "to all websites worldwide" as of 31 August 2026. The report shows impressions only: how often links to your site appeared in AI Overviews and AI Mode, by page, country, device and date. It does not show clicks or queries. The same data stays inside the Web search type of the main Performance report.

Bing went further on one point. AI Performance in Bing Webmaster Tools, in public preview since 10 February 2026, shows how often your content is cited in Microsoft Copilot and Bing's AI summaries, which URLs are cited and a sample of the "grounding queries" the AI used to find them.

Together they answer the question GA4 cannot: are we being shown at all? Use them for pages and topics, and GA4 for sessions and key events. Our GEO guide for B2B covers how to raise those citation numbers, and our roundup of AI visibility tools covers trackers that sample prompts across assistants.

Server logs: which AI crawlers read your pages

Assistants can only cite pages they can fetch. Your server or CDN logs show which AI bots visit, how often and which URLs they request. Each company publishes its user agents.

Track AI search traffic GA4 2026, AI crawler user agents GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot and purpose

Figure: AI crawler and fetcher user agents and what each is for, from OpenAI, Perplexity, Anthropic and Google documentation, 15 October 2026.

  • OpenAI lists OAI-SearchBot, GPTBot, ChatGPT-User and OAI-AdsBot. OAI-SearchBot decides whether pages can appear in ChatGPT search; GPTBot crawls for model training. OpenAI says the two settings are independent, and that robots.txt changes take about 24 hours to apply to search. ChatGPT-User fetches pages when a user asks, and "robots.txt rules may not apply."

  • Perplexity lists PerplexityBot and Perplexity-User. PerplexityBot surfaces sites in Perplexity search; Perplexity-User "generally ignores robots.txt rules" because a user requested the fetch.

  • Anthropic lists ClaudeBot (training), Claude-User (user requests) and Claude-SearchBot (search indexing) on its crawler help page.

  • Google has no separate AI user agent. Google-Extended is a robots.txt token only, and Google says it "does not impact a site's inclusion in Google Search."

A quick first check on a standard access log:

That lists the 50 URLs AI bots requested most. Anyone can fake a user agent, so for anything you act on, check the IP against the lists OpenAI and Perplexity publish (for example openai.com/searchbot.json and perplexity.com/perplexitybot.json). If your key pages never show up, check robots.txt and your CDN's bot rules before you rewrite content. Pages that bots fetch but assistants never cite are the ones to improve; our content refresh playbook covers how.

A monthly AI traffic report in five lines

Once the setup is done, one short report each month is enough:

  1. Sessions and key events from the "AI assistants" channel, by assistant.

  2. Top 10 landing pages from AI assistants.

  3. Search Console generative AI impressions, top pages.

  4. Bing AI Performance citations, top pages.

  5. AI crawler hits on your 20 most important URLs.

Put the 2026 total in your year-end review. Our B2B marketing year in review covers how search clicks moved across 2026, which is the context for whatever your own numbers show.

FAQ

Does GA4 track ChatGPT traffic?

Yes. ChatGPT adds utm_source=chatgpt.com to its links, so visits show chatgpt.com as the source. Since 13 May 2026, GA4 also puts recognised AI assistant referrals in a default AI Assistant channel. Visits with no referrer and no tag still land in Direct.

What is the AI Assistant channel in GA4?

It is a channel Google added to the default channel group on 13 May 2026. When the referrer matches Google's list of AI assistants, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant). It excludes Google's AI Overviews and AI Mode.

What regex should I use for AI traffic in GA4?

Use a Source "matches regex" condition with exact, anchored, lowercase domains, for example ^(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|chat\.deepseek\.com|grok\.com|chat\.mistral\.ai|meta\.ai)$, and place the channel above Referral.

Can I see AI Overviews and AI Mode traffic in GA4?

No. GA4 counts those clicks as Organic Search. Search Console's generative AI performance report shows impressions in AI Overviews and AI Mode, by page, but not clicks.

Why is my AI traffic so low in GA4?

GA4 only records clicks that carry a referrer or UTM tag. Mentions without clicks, copied links and some app traffic are invisible or land in Direct, so treat GA4's AI number as a floor.

Which user agents do AI crawlers use?

The main ones are GPTBot, OAI-SearchBot and ChatGPT-User (OpenAI), PerplexityBot and Perplexity-User (Perplexity), and ClaudeBot, Claude-User and Claude-SearchBot (Anthropic). Google uses its normal crawlers, with Google-Extended as a robots.txt token only.

Bottom line

Tracking AI search traffic in GA4 comes down to one setup step: a custom channel group with an exact-domain regex, placed above Referral, on top of the AI Assistant channel Google added in May 2026. That gives you sessions, landing pages and key events by assistant, including history. It will never be the full picture, because AI Overviews clicks count as Organic Search and unlabelled clicks count as Direct, so pair it with Search Console's generative AI report, Bing's AI Performance report and your server logs.

If you want AI visibility to turn into booked meetings, book a call with GROU.

About this guide

We are GROU, a B2B pipeline agency that runs lead generation, outbound and LinkedIn content for B2B companies. The steps and definitions in this guide come from Google Analytics, Google Search Central, Bing, OpenAI, Perplexity and Anthropic documentation and Similarweb data, checked on 15 October 2026.

This article has no affiliate links.

How to track AI search traffic in GA4 in 2026

TL;DR

  • Since 13 May 2026, GA4's default channel group has an AI Assistant channel for visits from chatbots like ChatGPT, Gemini and Claude. Clicks from Google's AI Overviews and AI Mode still count as Organic Search.

  • Google does not publish the list of assistants behind that channel, so build a custom channel group with your own regex. Custom groups apply to past data, and you control which domains count.

  • ChatGPT adds utm_source=chatgpt.com to its links. Visits that arrive with no referrer and no UTM tag land in Direct, so GA4 will always undercount AI traffic.

  • Fill the gaps with Search Console's generative AI report (impressions in AI Overviews and AI Mode, live for all sites since 31 August 2026), Bing's AI Performance report and your server logs for AI crawlers.

To track AI search traffic in GA4, use two things: the AI Assistant channel Google added to the default channel group in May 2026, and a custom channel group with a regex that matches the referrer domains of the assistants you care about. That gives you sessions, landing pages and key events from ChatGPT, Perplexity, Gemini, Copilot, Claude and others. This guide gives the exact regex, the setup steps, the reports to build and what GA4 cannot see, with the Search Console, Bing and server log checks that fill the gap.

Which AI assistants send traffic, and how they show up in GA4

When someone clicks a link inside an AI answer, the visit reaches your site like any other referral. GA4 reads the referrer (or the UTM tag, if there is one) and records the domain as the session source. So the first job is to know which domains the assistants run on.

Track AI search traffic in GA4 2026, referrer domains for ChatGPT, Perplexity, Gemini, Copilot, Claude and 5 more

Figure: the domains each AI assistant runs on, checked 15 October 2026. Google's AI Overviews and AI Mode have no separate domain.

Three details matter before you build anything:

  • ChatGPT tags its links. OpenAI's publishers and developers FAQ says "ChatGPT automatically includes the UTM parameter utm_source=chatgpt.com in referral URLs." That makes ChatGPT the easiest assistant to track, because the source survives even when the browser drops the referrer.

  • chat.openai.com is legacy. It now redirects to chatgpt.com, but keep it in your regex so older links and bookmarks are counted.

  • Google's own AI features are not separate. GA4's default channel group definitions say Organic Search includes "Google's AI Overviews and AI Mode." There is no referrer that tells a click from an AI Overview apart from a normal blue link.

ChatGPT is still the biggest assistant, but not by as much as a year ago. Similarweb's 2026 generative AI data shows ChatGPT's share of visits to generative AI websites fell from about 76% in June 2025 to roughly 53% by May 2026, while Gemini rose from under 9% to around 27 to 28% and Claude from about 2% to close to 9%. A channel that only matches ChatGPT now misses a growing share.

Track AI search traffic GA4 2026 context, share of generative AI visits, ChatGPT about 53%, Gemini around 27 to 28%

Figure: share of visits to generative AI websites, June 2025 and May 2026, from Similarweb. This is visits to the assistants, not referrals they send.

The AI Assistant channel Google added in May 2026

Google's What's new in Google Analytics page dates the change to 13 May 2026: "Google Analytics now provides a dedicated way to measure and analyze traffic originating from popular AI assistants." GA4 now sets the medium to "ai-assistant" and the campaign to "(ai-assistant)" when the referrer matches its list, and shows those sessions in a new AI Assistant channel.

Track AI search traffic in GA4 2026, Google's default AI Assistant channel, medium ai-assistant above Referral

Figure: the AI Assistant and Referral rows in Google's default channel group definitions, Analytics Help, 15 October 2026.

The default channel is a good start, but it has three limits:

  • You cannot see or change the list. The help page says the referrer is matched against "a list of AI Assistants" and names ChatGPT, Gemini, Deepseek, Copilot and Grok as examples. The full list is not published, and Google says "it's not possible to edit the Google Analytics default channel group."

  • Older data may still sit in Referral. Google does not say whether the new channel was applied to sessions before May 2026. Custom channel groups, by contrast, "can be applied to your reports retroactively," per the custom channel groups help page.

  • Source Group helps, but is broad. On 11 June 2026 Google added a Source Group dimension with "built-in grouping for emerging traffic sources like ChatGPT (OpenAI) and Perplexity." Google says it is populated retroactively, which makes it useful for a quick look back.

So keep the default channel for quick checks, and build your own group for reporting you can explain line by line.

Build a custom channel group for AI traffic

You need Editor access or higher on the property. Standard GA4 properties can have 2 custom channel groups (5 on GA4 360), each with up to 50 channels.

  1. In Admin, under Data display, open Channel groups.

  2. Click Create new channel group. GA4 starts you with a copy of the default group, so all existing channels stay in place.

  3. Name it, for example "Channels with AI".

  4. Click Add new channel and name it "AI assistants".

  5. Add a condition: Source, matches regex, and paste the regex below.

  6. Save the channel, click Reorder and drag "AI assistants" to the top of the list, above Referral and Organic Search. Google's rule is that traffic goes into "the first channel whose definition it matches given the current order."

  7. Click Save group.

Track AI search traffic in GA4 2026, Google's AI assistants custom channel example with matches regex and the reorder step

Figure: Google's own example for an AI assistants channel, custom channel groups help page, 15 October 2026.

The regex

GA4 regex is full match and case sensitive by default, per Google's regex help page. The pattern below is anchored to the end of the domain, so a lookalike such as chatgpt.com.example.net or sosmeta.ai does not match, while (.*\.)? still allows subdomains such as www.perplexity.ai. Source values for these referrers are lowercase domains, so keep the pattern lowercase:

^(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|chat\.deepseek\.com|grok\.com|chat\.mistral\.ai|meta\.
Track AI search traffic GA4 regex 2026 test, GROU pattern matches 11 assistant domains, rejects lookalikes like sosmeta.ai

Figure: the GROU regex and Google's help page sample tested against real source values. GROU test with Python full match, 15 October 2026.

Why not paste Google's sample? Its regex starts with ^.*ai|, which matches any source that ends in "ai", and .*gpt.* and .*copilot.*, which match any source containing those letters. In our test it counted notion.ai, jasper.ai and copilot.github.com as AI assistants, and it missed chat.deepseek.com and grok.com. A loose pattern such as .*(chatgpt\.com|meta\.ai).* has the opposite problem in places: it also matches lookalikes like chatgpt.com.example.net and sosmeta.ai. Listing exact, anchored domains is longer, but every match is one you chose. Update the list when a new assistant matters to your buyers, as Google itself advises.

Reports to build once the channel exists

Custom channel groups work as a primary dimension in the Acquisition reports and as a dimension in explorations, so you can answer the questions that matter for B2B.

Traffic by assistant. Open Reports > Acquisition > Traffic acquisition, switch the primary dimension to your new channel group, then add Session source as a secondary dimension. You now see sessions, engaged sessions and key events for each assistant.

Landing pages. In Explore, start a Free form exploration. Add your channel group, Session source and Landing page + query string as dimensions, and Sessions, Engaged sessions and Key events as metrics. Filter to the "AI assistants" channel. This shows which pages AI answers send people to. Expect a lot of homepage traffic: Similarweb's desktop panel data shows that after ChatGPT made brand links more prominent on 7 May 2026, the share of its desktop referrals landing on a brand's homepage jumped from roughly 26 to 32% to around 60%.

Key events. Mark your demo request, contact form and trial sign-up as key events (Admin > Data display > Events, then the star icon). Then compare key event rate for AI assistants against Organic Search and Referral. Small numbers swing hard, so read this quarterly, not weekly.

Trend. Set the date range to 12 months and compare month by month. Because custom channel groups apply to past data, your chart starts before the May 2026 change.

If you want to act on the accounts behind those visits, not only count them, visitor identification tools are the next step. Our RB2B pricing guide and signal-based lead generation playbook cover how teams turn site visits into a daily list.

What GA4 cannot see

GA4 only sees clicks. Most of what happens in AI search never becomes a click on your site, and some clicks arrive with no label.

Track AI search traffic in GA4 2026, where AI visits land: AI Assistant, Organic Search or Direct, plus GSC and Bing

Figure: where AI search activity shows up, based on Google Analytics, Search Console and Bing Webmaster Tools documentation, 15 October 2026.

  • AI Overviews and AI Mode clicks count as Organic Search. You cannot split them out in GA4.

  • Dark traffic lands in Direct. If the browser or app passes no referrer and the link has no UTM tag, GA4 records the session as Direct: source "(direct)", medium "(none)". Copied links, links opened from some desktop and mobile apps, and people who read an answer and then type your URL all end up here.

  • Mentions without clicks are invisible. If an assistant names your company and the reader books a call a week later from a Google search, GA4 credits Organic Search.

  • ChatGPT's tag names a source only. OpenAI documents utm_source=chatgpt.com and says nothing about a medium, so check in your own property whether those sessions sit in AI Assistant, Referral or Unassigned before you report on the default channel. Matching on Source, as the regex above does, avoids the question.

That is why the honest way to report AI traffic is as a floor, not a total. Pair it with a "How did you hear about us?" field on your demo form, and read answers that mention ChatGPT or "AI" alongside the GA4 numbers.

Search Console and Bing: visibility before the click

Google launched Search generative AI performance reports in Search Console on 3 June 2026, and rolled them out "to all websites worldwide" as of 31 August 2026. The report shows impressions only: how often links to your site appeared in AI Overviews and AI Mode, by page, country, device and date. It does not show clicks or queries. The same data stays inside the Web search type of the main Performance report.

Bing went further on one point. AI Performance in Bing Webmaster Tools, in public preview since 10 February 2026, shows how often your content is cited in Microsoft Copilot and Bing's AI summaries, which URLs are cited and a sample of the "grounding queries" the AI used to find them.

Together they answer the question GA4 cannot: are we being shown at all? Use them for pages and topics, and GA4 for sessions and key events. Our GEO guide for B2B covers how to raise those citation numbers, and our roundup of AI visibility tools covers trackers that sample prompts across assistants.

Server logs: which AI crawlers read your pages

Assistants can only cite pages they can fetch. Your server or CDN logs show which AI bots visit, how often and which URLs they request. Each company publishes its user agents.

Track AI search traffic GA4 2026, AI crawler user agents GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot and purpose

Figure: AI crawler and fetcher user agents and what each is for, from OpenAI, Perplexity, Anthropic and Google documentation, 15 October 2026.

  • OpenAI lists OAI-SearchBot, GPTBot, ChatGPT-User and OAI-AdsBot. OAI-SearchBot decides whether pages can appear in ChatGPT search; GPTBot crawls for model training. OpenAI says the two settings are independent, and that robots.txt changes take about 24 hours to apply to search. ChatGPT-User fetches pages when a user asks, and "robots.txt rules may not apply."

  • Perplexity lists PerplexityBot and Perplexity-User. PerplexityBot surfaces sites in Perplexity search; Perplexity-User "generally ignores robots.txt rules" because a user requested the fetch.

  • Anthropic lists ClaudeBot (training), Claude-User (user requests) and Claude-SearchBot (search indexing) on its crawler help page.

  • Google has no separate AI user agent. Google-Extended is a robots.txt token only, and Google says it "does not impact a site's inclusion in Google Search."

A quick first check on a standard access log:

That lists the 50 URLs AI bots requested most. Anyone can fake a user agent, so for anything you act on, check the IP against the lists OpenAI and Perplexity publish (for example openai.com/searchbot.json and perplexity.com/perplexitybot.json). If your key pages never show up, check robots.txt and your CDN's bot rules before you rewrite content. Pages that bots fetch but assistants never cite are the ones to improve; our content refresh playbook covers how.

A monthly AI traffic report in five lines

Once the setup is done, one short report each month is enough:

  1. Sessions and key events from the "AI assistants" channel, by assistant.

  2. Top 10 landing pages from AI assistants.

  3. Search Console generative AI impressions, top pages.

  4. Bing AI Performance citations, top pages.

  5. AI crawler hits on your 20 most important URLs.

Put the 2026 total in your year-end review. Our B2B marketing year in review covers how search clicks moved across 2026, which is the context for whatever your own numbers show.

FAQ

Does GA4 track ChatGPT traffic?

Yes. ChatGPT adds utm_source=chatgpt.com to its links, so visits show chatgpt.com as the source. Since 13 May 2026, GA4 also puts recognised AI assistant referrals in a default AI Assistant channel. Visits with no referrer and no tag still land in Direct.

What is the AI Assistant channel in GA4?

It is a channel Google added to the default channel group on 13 May 2026. When the referrer matches Google's list of AI assistants, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant). It excludes Google's AI Overviews and AI Mode.

What regex should I use for AI traffic in GA4?

Use a Source "matches regex" condition with exact, anchored, lowercase domains, for example ^(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|chat\.deepseek\.com|grok\.com|chat\.mistral\.ai|meta\.ai)$, and place the channel above Referral.

Can I see AI Overviews and AI Mode traffic in GA4?

No. GA4 counts those clicks as Organic Search. Search Console's generative AI performance report shows impressions in AI Overviews and AI Mode, by page, but not clicks.

Why is my AI traffic so low in GA4?

GA4 only records clicks that carry a referrer or UTM tag. Mentions without clicks, copied links and some app traffic are invisible or land in Direct, so treat GA4's AI number as a floor.

Which user agents do AI crawlers use?

The main ones are GPTBot, OAI-SearchBot and ChatGPT-User (OpenAI), PerplexityBot and Perplexity-User (Perplexity), and ClaudeBot, Claude-User and Claude-SearchBot (Anthropic). Google uses its normal crawlers, with Google-Extended as a robots.txt token only.

Bottom line

Tracking AI search traffic in GA4 comes down to one setup step: a custom channel group with an exact-domain regex, placed above Referral, on top of the AI Assistant channel Google added in May 2026. That gives you sessions, landing pages and key events by assistant, including history. It will never be the full picture, because AI Overviews clicks count as Organic Search and unlabelled clicks count as Direct, so pair it with Search Console's generative AI report, Bing's AI Performance report and your server logs.

If you want AI visibility to turn into booked meetings, book a call with GROU.

About this guide

We are GROU, a B2B pipeline agency that runs lead generation, outbound and LinkedIn content for B2B companies. The steps and definitions in this guide come from Google Analytics, Google Search Central, Bing, OpenAI, Perplexity and Anthropic documentation and Similarweb data, checked on 15 October 2026.

This article has no affiliate links.

Trusted by industry leaders

Trusted by industry leaders

Trusted by industry leaders

Ready to build qualified pipeline?

Ready to build qualified pipeline?

Ready to build qualified pipeline?

Book a call to see if we're the right fit, or take the 2-minute quiz to get a clear starting point.

Book a call to see if we're the right fit, or take the 2-minute quiz to get a clear starting point.

Book a call to see if we're the right fit, or take the 2-minute quiz to get a clear starting point.