Referral Traffic in GA4 and Visits From AI Assistants
Referral traffic in Google Analytics 4 is the set of visits that arrive through non-ad links on other sites and apps. Since May 2026, GA4 splits visits from popular AI assistants such as ChatGPT, Gemini and Copilot into a separate AI Assistant channel. Traffic from AI Overviews and AI Mode doesn't go there, and some assistant visits pass no source at all and land in direct traffic. To read these numbers reliably you need to know how GA4 identifies a source, what to exclude and what the data can't tell you.
What Referral Traffic Means in GA4
In its description of the default channel group, Google defines Referral as the channel through which users arrive via non-ad links on other sites or apps, such as blogs or news sites. The rule is simple: a session goes into this channel when its medium is "referral", "app" or "link".
Channels are rules applied to two dimensions: source and medium. Source says where the visit came from, for example "facebook.com" or "google". Medium says what kind of traffic it was: "organic" for unpaid search results, "cpc" for paid ones, "referral" for referrals. The default channel group can't be edited, because Google maintains it as a universal reference for all users. Your own rules go into a separate, custom channel group.
The same split appears in three dimensions with different scopes. Session default channel group describes where a given session came from. First user default channel group says where a user arrived from the first time. Default channel group applies to key events and depends on the attribution model set for the property. "How many visits did referrals bring" needs the first of these, while "which channel brought quote requests" needs the third.
How GA4 Identifies the Referring Site
The referral source comes from the HTTP Referer header the browser sends after a link is clicked. Google describes this precisely in its documentation on identifying Google Search traffic in analytics: the header carries the address of the page the visit came from, and for Google Search only the scheme and host, without the path or query parameters.
The header is sometimes empty. Google lists situations in which the browser or operating system omits it: private browsing and anti-fingerprinting protections, opening a link in a new tab in some browsers, moving from a native search widget or app to an external browser, and privacy extensions. A visit without the header has no clear source. According to GA4 Help on direct traffic, such a session lands in "(direct) / (none)", as do visits from links without UTM parameters, visits whose source data was stripped by a redirect or a URL shortener, visits from links in PDFs and documents, and some visits from people using ad blockers.
For AI assistant traffic this has practical consequences. Clicking a link in a chat answer in a browser usually leaves a source trail. Clicking in a mobile app that opens the page in an external browser may not. How many visits get lost this way can't be determined from analytics alone.
The AI Assistant Channel: What It Covers and What It Doesn't
In May 2026 Google added a new channel to the default channel group. The May 13, 2026, entry in What's new in Google Analytics announces dedicated measurement of traffic from popular AI assistants and gives ChatGPT, Gemini and Claude as examples. The channel description in the documentation names ChatGPT, Gemini, DeepSeek, Copilot and Grok as example sources.
The mechanism relies on a list. When the referrer matches a list of AI assistants maintained by Google, GA4 sets the medium to "ai-assistant" and the campaign name to "(ai-assistant)". The AI Assistant rule sits in the table before the Referral rule, so these visits no longer count as referrals. In Acquisition > Traffic acquisition the channel appears as a separate row, and switching the dimension to session source / medium shows which assistant sent the visit.
Two boundaries are worth knowing before drawing conclusions. First, Google explicitly excludes AI Overviews and AI Mode from this channel. According to the documentation on AI features in Search, clicks from these features are counted in Search Console's Performance report under the "Web" search type, together with the rest of Google Search traffic. Second, the channel description gives examples, not a full list. Perplexity isn't named in it. Whether visits from a given assistant land in AI Assistant or in Referral is easiest to check in your own report by source.
Your Own AI Channel: When It Makes Sense
If Google's default list doesn't cover a source you care about, or you want to compare data from before May 2026, a custom channel group helps. Google notes that custom channel groups can be applied retroactively and used as the primary dimension in acquisition reports.
GA4 Help shows an example "AI assistants" channel built on a regular expression matching the source, with the advice to place it above Referral in the channel order. The example expression is very broad, though: its first alternative matches any source containing the letters "ai", so it also catches domains that have nothing to do with AI assistants. Narrow the expression to specific domains and test it against the list of sources from recent months before you build reports on it.
What to Exclude From Referrals Before You Read Them
The most common noise in referrals is traffic that isn't a referral at all. Google covers this in its help article on unwanted referrals. GA4 recognizes your own domain and its subdomains automatically and doesn't count them as a new source. It treats moves between domains configured for cross-domain measurement the same way.
Domains that are part of a process on your site rather than a source of traffic have to be added by hand. Google gives two examples: a third-party payment processor that the customer returns from after checkout, and an email domain through which a user returns to the site after clicking a password-reset link. The list is set in Admin, under Data collection and modification: Data streams, the web data stream, Configure tag settings and List unwanted referrals. A single data stream allows up to 50 of them.
The exclusion doesn't work backward for users who already arrived from that domain. Google explains that when such a person returns from a bookmark, the session can still be attributed to the earlier source, because session attribution skips direct visits and looks for the last known source.
How to Read Referrals and AI Traffic
Once the data is clean, referrals show which external sites actually send people. Switch the report to session source / medium and look at engagement and key events, not just the number of sessions. A referral from an industry directory that produces a quote request is worth more than many visits from an aggregator that end after a few seconds.
With AI assistant traffic, keep three limits in mind. A click is only part of the contact with a brand: an AI answer can mention a company without a link, or with a link nobody clicks. Some clicks disappear into direct traffic when an app doesn't pass the source. And GA4 numbers won't match tools that count clicks on their own side, because GA4 records a visit only after the page loads and the tag runs, that is, after cookie consent and browser blocking.
If you send traffic from paid placements in AI answers, tag the links with UTM parameters. Then source and medium don't depend on the Referer header. How to prepare such links for ads in ChatGPT and AI Overviews is covered in our article on ads in AI answers. And for an assistant to link to your site at all, its search crawler needs access to it, which we discuss in the piece on AI bot policy.
How We Read Referral and AI Assistant Traffic
Clean-up first, conclusions second. Before interpreting referrals, we check whether the sources include the site's own domain, a payment gateway or a booking system. That kind of noise can inflate referrals and at the same time take credit away from the channels that actually brought the customer.
We read AI traffic as a signal, not as a measure of visibility. The AI Assistant channel shows that someone clicked a link in a chat answer. It doesn't say how often the brand appears in answers or in what context. That's why we compare it with Search Console data and with manual checks of answers to the questions a given company's customers ask.
We compare periods under the same definition. The AI Assistant channel has existed since May 2026. When comparing with earlier months, we use a custom channel group with the same rule for the whole period, so the new channel doesn't look like a sudden jump.
Summary
Referral traffic in GA4 is visits from links on other sites, identified through the Referer header and a medium of "referral", "app" or "link". Since May 2026, visits from AI assistants on Google's list go into a separate AI Assistant channel, which excludes AI Overviews and AI Mode. Some assistant visits pass no source and land in direct traffic, and the example rules in Google's help are worth narrowing before use.
Before drawing conclusions, remove your own domains and payment gateways from referrals, read the report by session source / medium and key events, and treat AI traffic as one of several signals of presence in answers. We measure and grow visibility in AI search as part of our GEO service. If you want to put your analytics in order before that kind of measurement, request a quote.