AI Search
AI Referral Traffic
AI referral traffic is the visits a website receives when people click a link in an answer from an AI assistant such as ChatGPT, Perplexity, Gemini or Copilot. Analytics recognises it from the referrer or campaign tags; Google Analytics 4 gives it an AI Assistant channel, while clicks from Google’s AI Overviews and AI Mode count as organic search.
- Industry term
By QueryRev ResearchPublished Updated5 min read
Why it matters.
It is the part of AI search that analytics can see. An AI citation is exposure; a click on it is a visit with a source, a landing page and often a conversion. For a business it is the shortest line from AI search to revenue, and the only part of that line that is observed rather than modeled.
Google Analytics 4 names it. Its AI Assistant channel covers visits from sources such as ChatGPT, Gemini, Deepseek, Copilot or Grok: the medium is set to ai-assistant when the referrer matches GA4’s list of AI assistants, or when a link is tagged with that medium[1]. The channel excludes Google’s AI Overviews and AI Mode, which GA4 counts in Organic Search[1] and Search Console reports within its Web search type[3].
The referrer is the weak point. HTTP lets a browser shorten the Referer header to the referring origin, requires it to be omitted or blank when a link came from a source with no address of its own, such as a bookmark or typed input, and notes that not every request carries it[2]. A click whose referrer was dropped arrives with nothing to tell it apart from the visits GA4 files under Direct, a saved link or a typed address[1]. The channel is a floor, not a total.
Assistants link only to what they can read. Perplexity says Perplexity-User may visit a page to answer a question and include a link to it in the response[4], and OpenAI says a site opted out of OAI-SearchBot will not be shown in ChatGPT search answers[5]. The referral starts with access.
Counting rules decide the number. QueryRev’s study shows the size of the effect on another count: in an earlier study’s own published figures, the 20,171 domains that answered a request for /llms.txt successfully were 2.35 times the 8,598 that served a valid file[6]. Referral reports work the same way: a loose rule for what counts as an AI source inflates the figure, and a strict one misses the visits that lost their referrer.
How it is measured.
In GA4, read the AI Assistant channel of the session default channel group by source and landing page, with engagement, key events and revenue. Keep Organic Search apart: Google’s AI features sit inside it, and Search Console is where their clicks show.
Check the channel against your own referrers. Read the Referral and Direct traffic of the pages AI answers cite: an assistant that sends visits under a source GA4 does not match, or a landing page whose Direct visits jump after it starts being cited, shows how much the channel misses.
Label the figures as what they are. Visits GA4 recorded are GA4-reported; visits estimated from Direct, or from citations without a click, are modeled, and the two are never added into one number.
Measured by
- AI Assistant sessions
- Key events and revenue
- Unexplained Direct visits
A worked example.
Sample data: an invented site, to show the method.
A SaaS company reads one month of GA4. The AI Assistant channel shows 640 sessions, most from chatgpt.com and perplexity.ai, landing on its pricing and comparison pages, with 38 trial sign-ups.
Its pricing page also gained 210 Direct sessions in the weeks after an assistant began citing it, with no campaign or email to explain them. They are reported beside the channel as a modeled estimate, not added to it.
What to do, step by step.
Open GA4’s session default channel group and read AI Assistant by source, landing page and key events.
List the assistants that cite you in your tracked answers, and check that each appears as a source in the channel.
Read Organic Search and Search Console for Google’s AI features, which the AI Assistant channel leaves out.
Check the landing pages AI answers cite for Direct visits that rise after a citation begins.
Tie each landing page to its conversions and revenue, and report the channel’s revenue as GA4-reported.
Keep estimates from Direct visits or from citations without clicks in a separate, modeled line.
Mistakes to avoid.
Treating the AI Assistant channel as all AI traffic. It leaves out AI Overviews and AI Mode, which GA4 puts in Organic Search. Google’s AI is reported there and in Search Console.
Reading the channel as complete. Visits that arrive without a referrer are filed with Direct. The channel holds the visits GA4 could attribute, not every visit an assistant sent.
Judging by sessions alone. A few visits to a pricing page can be worth more than many to a blog post. Read conversions and revenue per landing page.
Folding estimates into reported revenue. Modeled visits and their value are labelled and kept apart from what analytics observed.
How QueryRev treats it.
QueryRev reads AI Assistant sessions from Google Analytics 4 by landing page, with their key events and revenue, and labels them GA4-reported. Pages cited in tracked answers are matched to those visits, and value without a recorded visit is shown as modeled, never mixed into known revenue. See organic revenue attribution and the integrations.
Questions people ask.
How do I see AI referral traffic in GA4?
Use the session default channel group and look for the AI Assistant channel, then break it down by session source and landing page. Visits from Google’s AI Overviews and AI Mode are under Organic Search instead.
Why is my AI referral traffic lower than I expected?
Some clicks arrive without a referrer and are counted as Direct, and GA4 recognises only the assistants on its own list. Many answers are also read without any click. The channel is a floor, not the total.
Is ChatGPT traffic Referral or AI Assistant in GA4?
When GA4 matches the referrer to its list of AI assistants, which names ChatGPT among its examples, the visit goes to the AI Assistant channel rather than Referral.
Sources and citation.
Primary sources only: the search engines, the AI vendors, standards bodies and QueryRev’s own research. Each is cited in the text by its number.
Default channel groupGoogle Analytics Help ·
RFC 9110: HTTP SemanticsIETF ·
AI features and your websiteGoogle Search Central ·
Perplexity CrawlersPerplexity ·
Overview of OpenAI CrawlersOpenAI ·
State of AI crawler access, October 2026QueryRev Research ·
Cite this definition
A suggested citation. Its link goes to the definition, whose anchor does not change.
QueryRev Research. “AI Referral Traffic.” QueryRev AI glossary, 18 October 2026. https://queryrev.com/glossary/ai-referral-traffic#definition
Related terms