AI Search & GEO

How to Measure AI Referral Traffic in GA4: Step-by-Step (2026)

By BacklinkPrice Team · Nov 18, 2026 · Updated Nov 20, 2026 · 11 min read
Illustrated cover for How to Measure AI Referral Traffic in GA4

Open the Traffic acquisition report, find the AI Assistant channel, and check Session source for assistant domains. A custom channel group catches Perplexity and Claude too.

You measure AI referral traffic in GA4 by opening the Traffic acquisition report, finding the AI Assistant channel, and checking Session source for chatgpt.com, perplexity.ai, and other assistant domains. Google added the AI Assistant channel on May 13, 2026, so visits from recognized assistants now sit in their own row instead of hiding inside Referral.

Key takeaways

  • Google added an AI Assistant channel to GA4 on May 13, 2026. It sets the medium to ai-assistant and the campaign to (ai-assistant) for visits from recognized assistants (Google Analytics, 2026).
  • ChatGPT sent 2.7 million visitors across 74,752 sites in March 2026, about 10 times more than Perplexity or Gemini, which sent about 230,000 each (Ahrefs, 2026).
  • Perplexity and Claude are not on Google's recognized list as of November 2026, so their visits still land in Referral or Direct.
  • ChatGPT adds utm_source=chatgpt.com to referral links, so GA4 can name the source even when the browser sends no referrer (OpenAI, 2026).
  • GA4 counts clicks only, so treat the AI number as a floor. Mentions with no click and app visits with no referrer never appear in it.

What AI referral traffic is

AI referral traffic is a visit from a person who clicked a link inside an AI assistant answer and landed on your site. The assistant cites your page as a source, the reader clicks the citation, and the browser passes the assistant domain as the referrer.

That click is different from crawler traffic. Crawlers such as GPTBot and ClaudeBot fetch your pages so AI systems can read them, but they send no human visitor.

Ahrefs makes the same split in its 2026 guide: chatbot traffic means human visitors who clicked out of a chatbot, not bots reading pages. An AI citation is the link in the answer that starts the visit.

The sources to watch are the assistant domains themselves: chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, claude.ai, chat.deepseek.com, and grok.com. Older ChatGPT links may still show chat.openai.com. Check your own data for variants before you trust a fixed list, because assistant domains change as products change.

Why AI referral traffic matters in 2026

AI referral traffic is small today, but the visitors it sends are often close to a decision, so the channel deserves its own row in your reports.

Ahrefs tracked 74,752 sites in March 2026 and found all AI chatbots combined sent 3.5 million visitors, just 0.28% of total web traffic. Google sent 345.2 million visitors in the same month, a 28.12% share.

ChatGPT sent 2.7 million of the AI visits, about 10 times more than Perplexity or Gemini at about 230,000 each. That small share is still worth tracking, because AI visibility now shapes which brands buyers meet first.

Claude grew fastest in that data, up 153.5% month over month in March 2026, after Anthropic expanded its web search features. Growth is uneven across assistants, so a single month can mislead you. Watch the trend over a quarter instead.

The quality case is stronger than the volume case. In Ahrefs' own data from June 2025, AI search visitors were 0.5% of traffic but brought 12.1% of new signups, converting at 23 times the rate of traditional organic search visitors.

Ahrefs also modeled that AI search users click links 75% less than users of traditional organic search. Few clicks arrive, and the ones that do are often ready to act.

How to find AI referral traffic in GA4

Start with the built-in channel, then drop to source level to see which assistant sent each visit.

Step 1: Open the AI Assistant channel

Open Reports, then Acquisition, then Traffic acquisition, with Session default channel group as the dimension. Find the AI Assistant row. Google added this channel on May 13, 2026, and it needs no setup. It covers visits whose referrer matches a recognized assistant, and it sets the medium to ai-assistant and the campaign to (ai-assistant).

Step 2: Add Session source as a second dimension

Click the plus icon next to the first column header and add Session source. Rows such as chatgpt.com with the medium ai-assistant show which assistant sent each visit. This split matters because the channel total hides the mix, and ChatGPT usually sends most of it.

Step 3: Search Session source / medium for the assistants Google misses

Change the primary dimension to Session source / medium and search for chatgpt, perplexity, claude, gemini, and copilot. Use at least the last 90 days, because small sources can show zero in a single week. Any assistant domain with the medium referral is one the built-in channel does not recognize.

Which assistant lands where in GA4

Each assistant lands in a different GA4 row, so read the source table before you trust the channel total.

AssistantSession source to look forWhere it lands in GA4
ChatGPTchatgpt.comAI Assistant
Geminigemini.google.comAI Assistant
Copilotcopilot.microsoft.comAI Assistant
DeepSeekchat.deepseek.comAI Assistant
Grokgrok.comAI Assistant
Perplexityperplexity.aiReferral
Claudeclaude.aiReferral or Direct

Google's list has changed since launch. The May 2026 announcement named ChatGPT, Gemini, and Claude, while later documentation names ChatGPT, Gemini, DeepSeek, Copilot, and Grok.

Clicks from Google's AI Overviews and AI Mode are different: they arrive from Google and count as Organic Search, not as AI referrals. Our guide to how Google AI Overviews choose sources explains that side in more detail.

How to build a custom channel group that catches the rest

A custom channel group groups the assistants Google leaves out with the ones it recognizes, and it applies to your older data too.

Step 1: Copy the default group

Go to Admin, then Data display, then Channel groups, and copy the default channel group. A standard GA4 property can have 2 custom channel groups, while GA4 360 allows 5 (AI Search Handbook, 2026). Starting from a copy keeps all the standard channels intact.

Step 2: Add an AI channel with two conditions

Add a channel named AI search with two conditions joined by OR: medium exactly matches ai-assistant, or session source matches a regex of assistant domains. The first condition picks up everything Google already classifies. The second adds Perplexity, Claude, and the smaller assistants, and it catches sessions from before May 2026.

chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|chat\.deepseek\.com|grok\.com|chat\.mistral\.ai|you\.com|phind\.com

Step 3: Move it above Referral and check it

Drag the new channel above Referral, because GA4 checks channels from top to bottom and uses the first match. New groups can take a day or so to fill in. Then ask an assistant a question that cites your site, click the link, and check the Realtime report for the visit under your new channel.

What GA4 cannot see

GA4 counts only visits that arrive with a signal it can read, so part of your AI-driven traffic will always sit in other rows.

Visits from assistant apps often arrive with no referrer, and GA4 files them under Direct. The same happens when a reader copies a link out of an answer and pastes it into a new tab.

Consent Mode adds a gap: visitors who decline analytics send only cookieless signals, so reports can show modeled or reduced numbers. A brand mention in AI search can still shape a decision even when it sends no visit at all.

A mention with no click leaves no trace. Analytics measures visits, not appearances in answers, so a page can be cited often and still show few AI sessions. Track mentions separately by running the questions your buyers ask and recording whether you are cited, mentioned, or absent.

Clicks from Google's AI Overviews and AI Mode count as Organic Search in GA4. Search Console is the better place to look for that visibility: its Generative AI performance report shows how often your pages appeared in those features by page, country, device, and date, but it reports impressions, not clicks.

See our Google Search Console performance overview for how that report fits with the rest of Search Console.

Tools and time needed

You need GA4, Search Console, and a small prompt list. The setup takes under an hour, and a monthly check takes about 15 minutes once the reports exist.

GA4 holds the referral data, and its Traffic acquisition report and custom channel groups do the main work.

Search Console adds the Google side through its Generative AI performance report, which covers AI Overviews and AI Mode impressions. Bing Webmaster Tools adds a third view: filter Search Performance by Generative to isolate clicks from Copilot AI answers, broken down by page and by prompt (Ahrefs, 2026).

Before you trust the numbers, check that AI crawlers can reach your pages. OpenAI's OAI-SearchBot must be allowed in robots.txt for a page to appear in ChatGPT search summaries, and OpenAI says search changes take about 24 hours after a robots.txt update. Our guide to OAI-SearchBot covers what that crawler does and how to allow it.

A prompt list is the last tool. Write down 10 to 20 questions your buyers ask, run them in ChatGPT, Perplexity, and Gemini once a month, and record which pages each assistant cites. That list is what turns a session count into a picture of your visibility.

How to measure results

Judge AI referral traffic by what visitors do, not by how many arrive. Compare it with Organic Search.

In the Traffic acquisition report, read key events and engagement rate for the AI channel next to Organic Search. In Ahrefs' June 2025 data, AI search visitors bounced less and viewed more pages per visit than search visitors, but spent less time on the site. Compare channels on your property before you draw conclusions.

Add Landing page as a second dimension to see which pages the assistants send people to. Pages that already attract AI visits are worth deepening. It helps to know how ChatGPT chooses which sources to cite before you rewrite a page.

Use the User acquisition report for a first-touch view: first user source shows people whose first visit came from an assistant. Last-touch key events undercount AI search: people often learn about a company from an assistant, then return by typing the address or searching the name.

Add a "How did you hear about us?" field to contact and sign-up forms. It is the only method in this guide that captures people who saw you in an answer and never clicked.

With a few dozen AI sessions a month, one sale moves the conversion rate a lot, so read trends over months, not single weeks.

Common mistakes

  • Counting only the AI Assistant row and missing Perplexity and Claude, which still land in Referral or Direct.
  • Relabeling Direct traffic as AI traffic. A visit with no referrer and no tag could have come from anywhere, so report it as unattributed.
  • Comparing a period before May 13, 2026 with one after it. The channel did not exist before that date, so older AI visits keep their old classification.
  • Adding utm_source=chatgpt.com to your own links. That tag would label every visitor who uses the link as ChatGPT traffic.
  • Expecting GA4 to name the prompt that sent a visitor. Assistants do not pass the prompt to your site, so the landing page is the best clue.
  • Judging the channel on one week of data. Small sites can see zero AI sessions in a week and a real trend over a quarter.

Frequently Asked Questions

Does GA4 track ChatGPT traffic automatically?

Yes, since May 13, 2026. When a visit arrives with a referrer from a recognized assistant, GA4 sets the medium to ai-assistant and puts the session in the AI Assistant channel. Older visits keep their original classification, so check the months before May 2026 with a custom channel group instead.

Why does some ChatGPT traffic show up as Direct?

Visits from the ChatGPT app and from copied links often arrive with no referrer, so GA4 has nothing to attribute and files them under Direct. The utm_source=chatgpt.com tag survives when the referrer does not, which is why tagged sessions can still show chatgpt.com as the source.

Where does Perplexity traffic show up in GA4?

Perplexity is not on Google's recognized list as of November 2026, so its visits appear as perplexity.ai with the medium referral, inside the Referral channel. A custom channel group that matches the perplexity.ai source puts those visits together with the rest of your AI traffic.

Can GA4 show which prompt sent a visitor?

No. Assistants do not pass the prompt to your site, and GA4 cannot recover it from the session. The landing page is the best clue to the question that was answered, and a monthly prompt list shows which of your pages the assistants cite for each question.

Does GA4 count AI Overview clicks as AI referral traffic?

No. Clicks from Google's AI Overviews and AI Mode arrive from Google and count as Organic Search in GA4. The AI Assistant channel excludes them by design. Use Search Console's Generative AI performance report to see how often your pages appeared in those features.

Sources

To turn these visits into more citations, start with our guide to generative engine optimization.

BacklinkPrice Team
Written by
BacklinkPrice Team
Link building and backlink pricing research

The BacklinkPrice Team researches backlink prices, publisher sites and link building tools. We check prices and plans against each provider's own pages and date them, so you know how current the numbers are.

More from BacklinkPrice Team

Related guides