How to Track AI Traffic in GA4 Without the Gaps
Track AI traffic in GA4: the AI Assistant channel in Google Analytics misses visits in Referral, Unassigned and Direct. Catch them with a tested regex.

On this page 14 sections
- How do you track AI traffic in GA4?
- What counts as AI traffic in Google Analytics?
- Does Google Analytics 4 track AI traffic by default?
- Where does GA4 put the AI traffic the channel misses?
- How do you build a custom AI channel group in GA4?
- Which AI regex patterns go wrong in GA4?
- Why does GA4 show zero AI traffic?
- How do you see which pages AI assistants send people to?
- How do you measure conversions from AI traffic in GA4?
- How much traffic are AI assistants sending?
- What can't GA4 tell you about AI traffic?
- Tracking AI traffic in GA4: the audit checklist
- How RankX AI reports AI traffic
- Follow an AI referral through the store, not just the channel
Short answer: To track AI traffic in GA4, read the AI Assistant row in Traffic acquisition, then switch to Session source / medium to find AI visits sitting in Referral, Unassigned and Organic Search, and add a custom channel group that matches confirmed AI sources. Rules can regroup recorded data; they cannot recover a missing referrer, an unrecorded visit or proof of a sale.
How do you track AI traffic in GA4?
Track AI traffic in Google Analytics 4 in two layers: read the native AI Assistant channel, then catch what it misses with a custom channel group. Older guides tell you to build a regex channel from scratch because they predate the channel Google shipped in May 2026, and newer ones say the native channel is enough. It isn't.
Read the native channel
In Reports, open Acquisition and then the Traffic acquisition report, keep Session default channel group as the primary dimension, and find the AI Assistant row.
Find the AI traffic it missed
In the same GA4 report, switch the primary dimension to Session source / medium and search for chatgpt, perplexity, claude, gemini and copilot. Any row not labelled ai-assistant is AI traffic sitting in another channel.
Build a custom channel group
In Admin, under Data display, create an AI channel that matches session source only, and order it above Referral.
Add the landing page
Use Landing page as a secondary dimension to see which pages assistants send people to.
Compare outcomes
Set up key events and compare the AI channel's key event rate with Organic Search over at least 90 days.
When we built the AI-traffic reporting in RankX AI, we checked where AI visits actually landed on three live GA4 properties, on 25 September 2026. Visits from the same assistants turned up in four places: the AI Assistant channel, Referral, Unassigned and Organic Search.
The first two steps take five minutes on any GA4 property. The third fixes the numbers, so it gets its own section below.
What counts as AI traffic in Google Analytics?
AI traffic in GA4 means human visits from an AI platform: someone reads an answer in an AI tool such as ChatGPT, Perplexity, Claude, Gemini or Copilot and clicks through to your site. That is AI referral traffic, and it is the only kind of AI traffic Google Analytics is built to attribute.
Keep three records separate, because they measure different things.
Record | What it is | Where it lives |
|---|---|---|
AI referrals | Identifiable human visits from an AI assistant | GA4 traffic sources |
Google organic traffic | Clicks from Google, including AI Overviews and AI Mode | GA4 Organic Search; Google Search Console |
Crawler requests | Automated fetches such as GPTBot and ClaudeBot | Server logs, not GA4 |
Google's channel documentation excludes AI Overviews and AI Mode from AI Assistant, and a crawler request is not a shopper session. Mix the three and you will either undercount AI referrals or credit ordinary organic search traffic to AI tools that never sent it.
Does Google Analytics 4 track AI traffic by default?
Google Analytics 4 tracks some AI traffic by default through its AI Assistant channel, a default channel Google announced on 13 May 2026 and rolled out to properties gradually. When a visit's referrer matches Google's list of AI assistants, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant), and the source keeps the hostname, such as chatgpt.com or perplexity.ai.
Google doesn't publish the list, and its two help pages give different examples. The launch note (opens in a new tab) names ChatGPT, Gemini and Claude, while the channel definition names ChatGPT, Gemini, DeepSeek, Copilot and Grok and says AI Overviews and AI Mode stay in Organic Search.
Practitioner reports disagree. Itamar Blauer, writing in Search Engine Journal on 15 July 2026, noted that Claude had dropped out of Google's documented examples and reported Perplexity landing in Referral.
Our data differs on Perplexity. On three GA4 properties measured on 25 September 2026, visits from chatgpt.com, claude.ai, perplexity.ai, gemini.google.com, copilot.com and copilot.microsoft.com all carried the ai-assistant medium.
So don't trust anyone's list, ours included. Google can change an unpublished list whenever it likes, and the only list that matters is the one in your own Session source / medium report this month.
The AI Assistant channel isn't retroactive
The AI Assistant channel only labels visits from the date it reached your property. On the one property we measured with older history, the same AI hosts carried medium referral up to 10 June 2026 and ai-assistant from 11 June; the visits didn't change, only the label did.
That catches people out on trend charts. Plot the default channel group across that date and AI traffic appears from nowhere in June, which is a relabelling rather than growth, so check this first if you have shown a client a sudden AI jump in May or June 2026.
Where does GA4 put the AI traffic the channel misses?
GA4 puts the AI traffic its AI Assistant channel misses into four other channels, and each needs a different fix. We call this the AI traffic leak map, and the source / medium values below are the ones we actually found.
- AI referrer
Inspect the session source.
- Channel rules
Review how that source was grouped.
- Other channels
Check Referral and Unassigned as well.
A channel label is a classification. It does not capture every AI-origin visit.
Where it lands | What it looks like | Why it lands there | Can you recover it? |
|---|---|---|---|
Referral | chatgpt.com / referral, vertexaisearch.cloud.google.com / referral | Visits from before the channel reached your property, and AI hosts not on Google's list | Yes, with a source-only custom channel, retroactively |
Unassigned | openai / (not set), copilot.com / (not set) | The link carried a UTM source but no referrer and no medium | Yes, with the same source-only rule |
Organic Search | chatgpt.com / organic, and google / organic for AI Overviews and AI Mode | A tag set the medium to organic, or the click came from Google's own AI surfaces | The first, yes. Google's AI surfaces, no |
Direct | (direct) / (none) | No referrer and no tag: a copied link, or an app that sends neither | No. Estimate it, and say it's an estimate |
Unassigned is the one people skip, and it is where tagged AI visits without a referrer end up. OpenAI says ChatGPT adds utm_source=chatgpt.com to its referral links (opens in a new tab), so a click that arrives with that tag and no referrer keeps a source but has no medium.
GA4 assigns the AI Assistant channel by referrer, so nothing claims that session and the traffic from ChatGPT lands in Unassigned. If a campaign tag preserved the source, a channel rule can classify it; if the source is missing, no rule can reconstruct it.
One more source to know is vertexaisearch.cloud.google.com, the redirect used when a third-party app grounds its answers on Google's Gemini models. GA4 files it under Referral. Count it as AI traffic in its own channel rather than crediting Gemini, because the visitor was in somebody else's app.
How do you build a custom AI channel group in GA4?
A custom channel group applies your own classification rules to the traffic-source data GA4 recorded. Inspect both source and medium before choosing rules and their order, and preserve paid classifications: an AI-host source with a paid medium should not silently become an unpaid referral.
Create the channel group
In Admin, open Data display, then Channel groups, and create a new channel group called something like Default with AI.
Add an AI assistants channel
Use one condition: Source, matches regex, with the pattern below.
Leave the medium out
The medium is exactly what differs between the ai-assistant, referral and (not set) versions of the same visit, so matching on it splits ChatGPT across three channels again.
Add an AI grounding channel
Source exactly matches vertexaisearch.cloud.google.com.
Add a Paid AI channel if you buy ads inside assistants
Source matches the same pattern, and Medium matches cpc, ppc, paid, paidsearch, paid_search, cpm, display or sponsored.
Reorder and save
Put Paid AI first, then AI assistants and AI grounding, all above Referral and Organic Search, then choose the group as the primary dimension in Traffic acquisition.
The paid medium condition as a regex is (cpc|ppc|paid|paidsearch|paid_search|cpm|display|sponsored). This is the source pattern we use, built from the answer hosts and UTM values we have seen in real GA4 data plus the other answer hosts Google's channel definition names:
(www\.)?(chatgpt\.com|chat\.openai\.com|chatgpt|openai|perplexity\.ai|perplexity|claude\.ai|claude|gemini\.google\.com|gemini|copilot\.microsoft\.com|copilot\.com|copilot|grok\.com|meta\.ai|chat\.deepseek\.com|chat\.mistral\.ai)([/?#:].*|https?:.*)?
It lists exact answer hosts, the bare UTM values assistants and tagged links actually send, and a tail that tolerates malformed sources. We found one in the wild: a page had concatenated URLs into its utm_source, producing a source that began chatgpt.comhttps://.
The pattern is 249 characters, inside the 250 Google allows for regex in report filters, so it also fits a temporary report filter. Google's regex documentation says matching is a full match by default, so the pattern needs no anchors.
Case depends on where you paste it. Google says channel group definitions aren't case-sensitive, but report filters are, so a temporary filter using this pattern will miss a source tagged ChatGPT with a capital.
Test the rule on known rows before you trust the total
Compare a small set of known positive and negative rows before relying on the grouped total. Keep the original source and medium beside the grouped label, so someone else can reproduce each verdict.
Session source / medium | Expected channel | Why |
|---|---|---|
chatgpt.com / referral | AI assistants | A known answer host, classified by source |
chatgpt.com / ai-assistant | AI assistants | The same visit after the native channel arrived |
openai / (not set) | AI assistants | A tagged visit with no referrer, recovered by source |
chatgpt.com / cpc | Paid AI | Paid context is kept above the unpaid rule |
vertexaisearch.cloud.google.com / referral | AI grounding | A third-party app grounded on Gemini |
notchatgpt.com / referral | Not AI | Full match means a look-alike host does not match |
help.openai.com / referral | Not AI | Documentation, not an answer |
Which AI regex patterns go wrong in GA4?
Three mistakes recur in AI regex patterns shared online, and Google's own example makes two of them. We tested Google's example and a widely linked URL-style pattern against GA4's full-match rule, using 16 AI sources (nine found in real GA4 data, seven known answer hosts) and 17 sources that aren't assistants.
- Matching a vendor's whole domain. openai.com, anthropic.com and x.ai are corporate sites, platform.openai.com is a developer console and help.openai.com is documentation. A visit from any of them is a developer reading docs, not someone who followed an answer.
- Matching anything ending in ai. Google's own example pattern begins
^.*ai, which under full-match rules counts every source ending in those letters, such as jasper.ai, copy.ai and otter.ai, and its.*gemini.*also matches gemini.com, a cryptocurrency exchange. On our test set it matched 11 of the 17 non-assistant sources, two of them invented look-alikes, and missed grok.com and chat.deepseek.com, two assistants Google's own channel definition names. - Applying a URL pattern to Source. Patterns that begin
^https:\/\/are correct on the Page referrer dimension, which holds a full URL. On Session source, which holds a bare hostname such as chatgpt.com, the same pattern matches nothing, and the channel stays silently empty.
Keep your list to the hosts answers are actually served from, and review it every quarter. New AI platforms launch, existing ones change domains, and GA4's own list moves without notice.
Why does GA4 show zero AI traffic?
When a GA4 AI traffic channel shows zero visits from AI, check four things before you decide assistants send you nobody. Each one produces an empty channel with no error message.
Check | Why the channel is empty | Fix |
|---|---|---|
The report is still on the default group | A custom channel group only appears when chosen as the primary dimension | Select it, or make it the property's primary channel group |
The date range predates the channel | The native channel shows nothing before it reached your property | Widen the range, or use the custom group, which is retroactive |
The channel sits below Referral | Traffic goes to the first channel whose rules it matches, in order | Move the AI channels above Referral and Organic Search |
The regex can never match | A pattern written for full URLs matches nothing on Session source | Use a hostname pattern like the one above |
How do you see which pages AI assistants send people to?
To see which pages AI assistants send people to, add Landing page as a secondary dimension in Traffic acquisition with your AI channel group as the primary dimension. For more control, build a free-form Exploration with Session source and Landing page as dimensions, sessions, engaged sessions and key events as metrics, and a filter on your custom channel group.
Keep Session source in the table, so you compare engagement rate assistant by assistant instead of averaging every AI platform into one figure. Explorations only reach back as far as your data retention setting, 2 or 14 months on a standard property, while standard GA4 reports aren't limited by it.
Expect the homepage to lead. ChatGPT replaced footnote-style citations with clickable brand names in May 2026, and Similarweb's data through late May showed homepage referrals growing several times faster than ChatGPT referrals overall, so judge your deeper pages on their own rows.
Then take product flows out. On properties whose product connects to ChatGPT or Claude, we found GA4 counting sessions that landed on OAuth consent, login and account pages as AI Assistant traffic.
Those are users connecting an integration, not an answer recommending you. Exclude landing paths such as /login, /oauth and /account from the AI view before you report anything.
How do you measure conversions from AI traffic in GA4?
Measure conversions from AI traffic in GA4 by marking the actions that matter as key events, then comparing your AI channel's key event rate with Organic Search on the same report over at least 90 days. AI sessions are few on most sites, and on 30 sessions a single conversion moves the rate by more than three points.
- Landing page
Find the pages receiving identifiable AI visits.
- Key event
Inspect the conversion event you configured.
- Interpretation
Keep attributed visits separate from unknown traffic.
An AI referral is not automatically a sale. Attribution can be incomplete.
Check which key events are real first. Every Google Analytics 4 property we inspected carried purchase as a default key event, so a lead-generation site can look configured while recording nothing; add the events that represent your actual outcomes, such as a demo request or a trial sign-up.
Keep paid clicks out of the comparison. Ads now run inside ChatGPT, and Similarweb's 2026 generative AI report, summarised on its blog in July 2026, puts roughly 26 per cent of ChatGPT responses as containing one, without stating the market; that is what the Paid AI channel is for.
Be wary of published conversion multipliers. Most come from one company's own site or from modelled value rather than measured rates, and none of them is your funnel.
The AI referral traffic glossary entry covers why volume alone misreads this channel. Your own 90-day comparison is the number worth reporting.
How much traffic are AI assistants sending?
AI assistants send a small share of total traffic for most sites. Conductor's AEO and GEO benchmarks, drawn from 1,215 of its enterprise customers' domains and more than 3.3 billion US sessions between May and September 2025, put AI referrals at 1.08 per cent of website traffic (opens in a new tab), with Information Technology highest at 2.8 per cent.
ChatGPT still sends most of it: it accounted for 87.4 per cent of the AI referrals in Conductor's data. Statcounter, which measures page views across the more than 1 million sites running its tracking code, put each assistant's share of AI chatbot traffic as follows in September 2026.
Assistant | Statcounter AI chatbot share, September 2026 |
|---|---|
ChatGPT | 80.48 per cent |
Google Gemini | 10.91 per cent |
Perplexity | 5.85 per cent |
Microsoft Copilot | 1.79 per cent |
Claude | 0.95 per cent |
A setup that only matches chatgpt.com would leave out roughly a fifth of what Statcounter counts. That is why the pattern above lists every answer host.
What can't GA4 tell you about AI traffic?
GA4 can't see four kinds of AI influence, and for three of them there is a better instrument than analytics.
Clicks from Google AI Overviews and AI Mode
Clicks from Google AI Overviews and AI Mode arrive as google / organic, counted as organic traffic and indistinguishable from ordinary search clicks, and Google's channel definition excludes them from the AI Assistant channel. Google Search Console's generative AI performance report shows their impressions by page, country, device and date, with no clicks or queries.
Our guide to Search Console impressions without clicks covers what that report can and can't show. AI Mode versus AI Overviews explains why the two are reported together.
Visits that carry no source at all
A copied link, or a click from an app that sends no referrer and no tag, reaches GA4 as Direct. Cloudflare stated in July 2025 that traffic referred by Claude's native app carries no Referer header, and no setting recovers these visits after the fact because the information never reached your site.
You will see a figure claiming 70.6 per cent of AI traffic lands in Direct. It comes from Loamly, an AI-traffic vendor, and in a February 2026 update describes 14,413 of 20,428 AI visits in its own database of 446,405 visits, classified by detection models whose weaker layers score confidence between 0.35 and 0.65.
It is an estimate of what direct traffic contains rather than a measurement of GA4, and it should be reported as one. By the mechanism above, a visit that keeps its utm_source lands in Unassigned rather than Direct, so the label overstates even on its own terms.
Two honest proxies work better than any single number. Watch new-user Direct sessions that land on deep informational pages, which nobody types from memory, and add a "How did you hear about us?" field to your highest-value form with ChatGPT and other assistants as options.
Sessions inside AI browsers
AI browsers don't announce themselves. Statcounter reports that Perplexity's Comet, The Browser Company's Dia and OpenAI's ChatGPT Atlas all identify as Chrome, so a session inside one of them looks like any other Chrome session in GA4's browser report.
Being named without a click
Most AI answers carry no link at all: Similarweb found a citation in about 6.8 per cent of US ChatGPT prompts in May 2026. Crawlers such as GPTBot and ClaudeBot never run your GA4 tag either, so a brand can be recommended daily and show almost nothing in analytics.
Tracking brand mentions in AI search covers the answers themselves, and tracking AI bots covers the crawlers in your server logs. Measuring AI search visibility sets out how the layers fit together.
Tracking AI traffic in GA4: the audit checklist
Run this checklist on a GA4 property before trusting any AI traffic data from it. It takes about 20 minutes once you know where to look.
Find the date the AI Assistant channel reached the property
Never chart the default channel group across it.
Search Session source / medium for every AI host
Note each medium it appears with.
Open Unassigned
Look for AI sources with a (not set) medium.
Create a source-only custom channel group
Order the AI rules above Referral and Organic Search.
Test the regex against your real Source values
Include known positive and negative rows before you trust the channel.
Remove vendor corporate and developer domains from the pattern
Give vertexaisearch.cloud.google.com its own channel
Exclude login, OAuth and account landing pages from the AI view
Split paid AI clicks into their own channel
Only needed if you run ads inside assistants.
Replace the default purchase key event
Use the outcomes your business actually records.
Note what GA4 can't see next to every AI figure
AI Overviews, AI Mode, AI browsers and untagged Direct visits.
How RankX AI reports AI traffic
RankX AI shows the visits, enquiries and sales that start at an AI assistant, read from your Google Analytics in the web app. On WooCommerce it can add your store's orders when you switch them on; the Shopify app focuses on AI answers and shopping, so this report lives in the web app.
Verify any classification against the underlying GA4 source rows. Do not assume that every report excludes the same account pages, separates every paid click or recovers visits that arrived with no identifiable source.
Use identifiable referral sessions and repeated assistant observations as separate evidence. They can differ because the prompt panel misses a question, an answer links to another merchant, the visit loses its source or analytics does not record it.
Neither a mention without a session nor a session without a mention establishes the cause. AI Visibility records the answers, and you can start a 7-day trial with 1,000 credits and no credit card to put both side by side.
Follow an AI referral through the store, not just the channel
Use a small diagnostic sample before publishing a new channel rule. In a fictional check, chatgpt.com / referral is a candidate for an AI referral classification, while chatgpt.com / cpc must retain its paid context.
- Visit
Verify source, host and landing page.
- Action
Check the actual event definition.
- Order
Reconcile purchases separately.
If the session has no usable source, keep its origin unknown rather than assigning it to AI from the landing page alone.
A source such as notchatgpt.com should not match an exact assistant-host rule. Keep the original source and medium beside the grouped label so someone else can reproduce the verdict.
Choose one public product landing page and compare the same complete reporting window. Record sessions, product views, add-to-carts and configured purchase events separately.
Reconcile any reported transaction IDs and revenue against authorised order reporting before calling those visits sales. If the session has no usable source, keep its origin unknown rather than assigning it to AI from the landing page alone.
Next, measure mentions separately or inspect the buyer questions.
Questions about AI Visibility & Analytics
Does GA4 track AI traffic by default?
Partly. Google announced an AI Assistant channel on 13 May 2026 and rolled it out gradually, and GA4 now puts visits whose referrer matches its list of assistants there. Visits that arrive with a ChatGPT tag but no referrer fall into Unassigned instead, so you still need a custom channel group on session source.
Why does ChatGPT traffic show as Unassigned in GA4?
Because the visit carried utm_source=chatgpt.com but no referrer and no medium, which happens when an app or browser drops the referrer. GA4 assigns the AI Assistant channel by referrer, so the session matches no channel rule and lands in Unassigned. A source-only custom channel rule recovers it.
Is the GA4 AI Assistant channel retroactive?
No. The channel applies from the date it reached your property, and earlier visits from the same assistants stay in Referral; on the property we measured with older history, the switch happened on 11 June 2026. A custom channel group, by contrast, applies to your reports retroactively.
Can GA4 show traffic from Google AI Overviews?
No. Clicks from AI Overviews and AI Mode arrive as google / organic, and Google states the AI Assistant channel excludes them. Search Console's generative AI performance report shows their impressions by page, country, device and date, but it doesn't show clicks or queries.
Does Perplexity traffic appear in the AI Assistant channel?
On the three GA4 properties we measured on 25 September 2026, yes: perplexity.ai visits carried the ai-assistant medium. Some practitioners report Perplexity missing, and Google doesn't publish its list. Check your own Session source / medium report rather than relying on anyone's list, ours included.
Do I need admin access to track AI traffic in GA4?
You need the Editor role or above to create a custom channel group. Without it you can still read the AI Assistant row in Traffic acquisition, or add a temporary filter on Session source using matches regex. That filter only applies to your current view and isn't saved for anyone else.
Sources
- RankX AI, GA4 source and channel audit across three live properties, 25 September 2026: the AI hosts carrying the ai-assistant medium, the channel's start date of 11 June 2026, and the visits found in Referral, Unassigned and Organic Search Checked 2026-10-06.
- RankX AI, regex test of 6 October 2026: 16 AI sources (nine observed in GA4 data, seven known answer hosts) and 17 non-assistant sources, two of them invented look-alikes, against GA4's full-match rule. Google's example pattern matched 11 of the 17 and missed two assistants; the RankX AI pattern: no misses and no false positives, at 249 characters Checked 2026-10-06.
- Google Analytics Help, What's new in Google Analytics: New AI Assistant traffic measurement, 13 May 2026 (names ChatGPT, Gemini and Claude; medium ai-assistant, campaign (ai-assistant)) (opens in a new tab) Checked 2026-10-06.
- Google Analytics Help, Default channel group: AI Assistant channel definition (ChatGPT, Gemini, DeepSeek, Copilot or Grok; excludes AI Overviews and AI Mode; medium set when the referrer matches a list) (opens in a new tab) Checked 2026-10-06.
- Google Analytics Help, Custom channel groups: applied to reports retroactively, channel definitions not case-sensitive, Editor role required, two custom groups on standard properties, first matching channel wins, and Google's example AI assistants regex (opens in a new tab) Checked 2026-10-06.
- Google Analytics Help, About regular expressions: full match by default (opens in a new tab) Checked 2026-10-06.
- Google Analytics Help, Filter report data: regular expressions are case-sensitive and limited to 250 characters (opens in a new tab) Checked 2026-10-06.
- Google Analytics Help, Data retention: 2 or 14 months for standard properties, applying to explorations and funnel reports but not standard reports (opens in a new tab) Checked 2026-10-06.
- OpenAI Help Center, Publishers and developers FAQ: ChatGPT automatically includes utm_source=chatgpt.com in referral URLs (opens in a new tab) Checked 2026-10-06.
- Search Engine Journal, How to track AI traffic in GA4 without undercounting it. Itamar Blauer, 15 July 2026: notes Claude dropped from Google's documented examples and reports Perplexity landing in Referral (opens in a new tab) Checked 2026-10-06.
- Cloudflare, The crawl before the fall of referrals, 1 July 2025: referrals counted by Referer header, and traffic referred by Claude's native app carries none (opens in a new tab) Checked 2026-10-06.
- Similarweb, AI Search Stats 2026: Market Share, Referral, and Citation Data, 29 July 2026: citations in about 6.8% of US ChatGPT prompts by May 2026; roughly 26% of ChatGPT responses carry an ad, per its 2026 generative AI report; homepage referrals after the May 2026 brand-link change (opens in a new tab) Checked 2026-10-06.
- Statcounter Global Stats, AI Chatbot Market Share Worldwide, September 2026: ChatGPT 80.48%, Google Gemini 10.91%, Perplexity 5.85%, Microsoft Copilot 1.79%, Claude 0.95%. Built from page views on the more than 1 million sites running Statcounter's code (opens in a new tab) Checked 2026-10-06.
- Statcounter Global Stats, FAQ: Comet from Perplexity, Dia from The Browser Company and ChatGPT Atlas from OpenAI all identify as the Chrome browser (opens in a new tab) Checked 2026-10-06.
- Conductor, AEO and GEO Benchmarks Report: traffic findings from 1,215 enterprise customer domains and more than 3.3 billion US sessions, May to September 2025. AI referrals 1.08% of website traffic, IT 2.8%, ChatGPT 87.4% of AI referrals (opens in a new tab) Checked 2026-10-06.
- Loamly, The AI traffic attribution crisis, February 2026 update: 14,413 of 20,428 AI visits (70.6%) without referrer across 446,405 visits in Loamly's database, classified by detection layers with stated confidence from 0.35 to 0.99 (opens in a new tab) Checked 2026-10-06.
- Google Search Central: using Search Console and Analytics together (opens in a new tab) Checked 20 Oct 2026.
- Google Analytics: custom channel groups (opens in a new tab) Checked 2026-10-21.
- Google Analytics: default channel definitions (opens in a new tab) Checked 2026-10-21.
CoversThis article covers the AI Visibility & Analytics topic, the AI Visibility feature and the AI Visibility Checker tool.
Terms usedAI Referral Traffic, Zero-Click Search, AI Citation, AI Mention, ChatGPT-User and AI Overview.
Read this page asMarkdown: /blog/track-ai-traffic-ga4.md.
All articlesEverything RankX AI publishes is listed on the blog index.
Ask an assistantAsk ChatGPT (opens in a new tab), Ask Claude (opens in a new tab) or Ask Perplexity (opens in a new tab).
Preferred sourceIf Google is your front door, you can add RankX AI as a preferred source (opens in a new tab), which asks your own results to surface more of what we publish.


