Best AI Referral Traffic Analytics Tools (2026)
GA4, Microsoft Clarity, Matomo and Plausible each give AI assistants their own channel, but none can tell a click in Google's AI Overviews from an ordinary search click. Apps built on OpenAI's search models are another gap: 99.7% of 37,470 citations we collected from them were tagged utm_source=openai, which Matomo and Plausible file outside their AI channels. Here are seven tools and what each misses.
For most sites, the best AI referral traffic tool is one you already have. Google added an AI Assistant channel to Google Analytics 4 on 13 May 2026, for visits from assistants like ChatGPT and Gemini, and a custom channel group catches the ones Google's list leaves out. Microsoft Clarity, also free, adds recordings of what those visitors do. If you're choosing a new analytics tool, Matomo can also show when an assistant fetches your pages to answer someone, and Plausible moved your past AI visits into its AI channel when it launched one.
All of them share two blind spots. A click from Google's AI Overviews or AI Mode looks like any other Google search click, so none of them can single it out. And a visit with neither a referrer nor a campaign tag shows up as Direct in every one of them. The last two entries on the list cover what an analytics script can't see: the crawlers that reach your server, and how often AI answers show or cite your pages.
There's a third gap, and it's specific to OpenAI. ChatGPT itself is covered: OpenAI's publisher FAQ says ChatGPT tags the links in its search results utm_source=chatgpt.com, and all four analytics tools here recognise ChatGPT. Apps built on OpenAI's search models are different. Of the 37,470 citations in the answers we collected from those models through OpenAI's API, 99.7% carried utm_source=openai, including every one from the current model. So a click on one of those links inside such an app, if the app keeps the link as it is, arrives tagged openai. Neither Matomo nor Plausible counts openai as an AI assistant, and Google doesn't name it among its examples, so the only setup here that counts those visits as AI for certain is a GA4 custom channel group that names it.
How We Ranked Them
The first five count people who click through from an assistant. They start with the tool most sites already run and end with the two you would switch to. The last two count what a script on your pages cannot. For each one we checked three things against the vendor's own documentation, and for Matomo and Plausible against their open-source code: what it counts as an AI visit, what it misses, and what it costs.
The Seven Tools
1. Google Analytics 4
Best for sites already running GA4
Google's launch note of 13 May 2026 describes it: GA4 sets a session's medium to ai-assistant when its referrer matches Google's list of AI assistants, and the default channel group collects those sessions as AI Assistant. There is nothing to set up.
- Counts
- Sessions whose referrer is on a list Google keeps but does not publish. Its channel definitions name ChatGPT, Gemini, DeepSeek, Copilot and Grok as examples, and the launch note adds Claude.
- Misses
- Clicks from AI Overviews and AI Mode, which the same definitions put in Organic Search. Any assistant that is not on the list; neither page names Perplexity. AI crawlers, which run no JavaScript, so the tag never fires.
- Costs
- Free.
Our GA4 guide shows where each kind of AI visit lands, and how to check where an assistant's visits went in your own property.
2. GA4 with a custom channel group
Best for catching the assistants GA4's list leaves out
A custom channel group is a set of rules you write, and GA4 applies it to past data as well as new. Standard properties get 2 of them besides the default. Copy the default group and add an OR condition to its AI Assistant channel, Source matches regex, with the pattern below; if your copy has no AI Assistant channel, add one with that condition. Keep it above Referral: a session goes to the first channel whose rule it matches.
^(chatgpt\.com|chat\.openai\.com|openai|perplexity\.ai|www\.perplexity\.ai|claude\.ai|gemini\.google\.com|grok\.com|grok\.x\.ai|copilot\.microsoft\.com|deepseek\.com|chat\.deepseek\.com|meta\.ai)$- Counts
- Every source the pattern names. This one is the list behind our own traffic reporting, with openai counted under ChatGPT, so clicks on links from OpenAI's search model are included.
- Misses
- Clicks from AI Overviews and AI Mode, which still arrive as google / organic. Assistants the pattern does not name. AI crawlers.
- Costs
- Free. The list is yours to keep current: once a month, look through the sources in Referral and Unassigned for assistants to add.
The setup step by step, and why an exact list works better than Google's own example pattern, is in our GA4 guide.
3. Microsoft Clarity
Best for seeing what AI visitors do on the page, free
Clarity added two channels on 29 August 2025: AIPlatform for clicks on ordinary links in an AI chat, and PaidAIPlatform for clicks on ads shown inside one. Because Clarity records sessions, you can filter its recordings and heatmaps to AI visitors and watch what they do once they arrive, which a channel report alone cannot tell you.
- Counts
- Visits from the standalone sites of ChatGPT, Claude, Copilot, Gemini and Perplexity, recognised by their referrers.
- Misses
- AI inside search engines and office tools, which Microsoft leaves out, so clicks from AI Overviews and AI Mode do not count as AI. Visits whose source is hidden, which show as Direct. Everything before the release, which was not reclassified. AI crawlers, which run no JavaScript.
- Costs
- Free, with no traffic limit.
4. Matomo
Best for AI clicks and assistant fetches in one tool
Matomo added an AI Assistants channel in version 5.5.0, released on 8 October 2025, and it is in both Matomo Cloud and the edition you host yourself. Its list of assistants is public, and its code checks the referrer first, then a utm_source that names an assistant's site, such as chatgpt.com.
Version 5.8.0, released on 4 March 2026, added reports for a second kind of AI traffic: the requests an assistant makes to read your page while answering someone, such as ChatGPT-User, Claude-User and Perplexity-User. They arrive through an integration on Cloudflare, Amazon CloudFront or WordPress, and Matomo keeps them out of your visit counts, though the All Websites dashboard adds them to its Total Hits.
- Counts
- Visits from the assistants on its list, which includes ChatGPT, Claude, Le Chat, Meta AI and DeepSeek, in Acquisition under AI Assistants. With the integration, the fetches assistants make for a user.
- Misses
- Visits from before the update, which keep their old channel. Links tagged utm_source=openai: openai is not on the list, and Matomo's default settings read utm_source as a campaign name, so the visit is filed as a campaign called openai. Clicks from AI Overviews, which arrive from Google as search. Training crawlers such as GPTBot, which the chatbot reports leave out.
- Costs
- Free to host yourself. Matomo Cloud is a paid subscription with a free trial.
5. Plausible
Best for a simple dashboard, with past AI visits reclassified
Plausible added an AI Assistants channel on 10 June 2026 and reclassified historical traffic into it, so visits from before the change count too. It filters known AI crawlers and other bots out of your stats.
- Counts
- Visits whose source is one of the eight assistants in its code: ChatGPT, Claude, Perplexity, Gemini, Copilot, Grok, DeepSeek and Phind.
- Misses
- Links tagged utm_source=openai. A UTM tag takes priority over the referrer, and openai is not a known source, so the visit is filed under Referral as the source openai. Clicks from AI Overviews count as Organic Search. Crawlers are filtered out, not reported.
- Costs
- From $9 a month for up to 10,000 monthly pageviews, after a 30-day free trial. The code is open source if you would rather host it yourself.
6. Server logs and your CDN
Best for crawlers and the fetches assistants make
Every request reaches your server or CDN, whether or not it runs JavaScript, so this is the only layer where crawlers show up. A standard access log records each request's user agent, such as GPTBot, OAI-SearchBot or ChatGPT-User, and OpenAI publishes the IP ranges each of its crawlers uses, so you can check that a request claiming to be one is genuine.
On Cloudflare, AI Crawl Control does the grouping for you on every plan, sorting crawler requests by company, from OpenAI and Anthropic to Google and Meta. Its counts of visits referred by AI platforms are for paid plans only.
- Counts
- Every request, with its user agent, its referrer when one is sent, and the full URL, so a utm_source=openai tag is there to read as well.
- Misses
- Where a click came from when it carried no referrer and no tag: in the log it is a direct request like any other. Not every host gives you its access logs, and raw logs need parsing before they tell you anything.
- Costs
- Nothing extra where your host gives you its access logs. AI Crawl Control is included in every Cloudflare plan.
Our AI traffic funnel post walks through the four kinds of AI traffic a server sees, from training crawls to the human click.
7. Search Console and Bing Webmaster Tools
Best for seeing how often AI answers show or cite your pages
These two count appearances, not visits. Since 31 August 2026, Google's generative AI performance reports have been open to every site, showing impressions in AI Overviews and AI Mode by page, country, device and date. Bing's AI Performance report, in public preview since 10 February 2026, counts how often Copilot, Bing's AI summaries and some partner products cite your pages, which pages, and a sample of the queries the AI used to find them.
- Counts
- Impressions in Google's AI features; citations in Microsoft's.
- Misses
- Clicks. Search Console puts clicks from AI Overviews and AI Mode in its ordinary Web search type, mixed with every other Google click, and a site with too few impressions in AI features may not see the report at all.
- Costs
- Free.
Side by Side
The same seven, on one page. Read down the AI Overviews and AI Mode column: no tool here counts those clicks as AI.
| Tool | Clicks from AI assistants | Clicks from AI Overviews and AI Mode | Links tagged utm_source=openai | Crawlers and assistant fetches | Cost |
|---|---|---|---|---|---|
| GA4, default channels | AI Assistant channel; Google's list is unpublished | Organic Search | Not among Google's examples | No | Free |
| GA4, custom channel group | Every source your regex names, past data included | Organic Search | Yes, when the regex lists it | No | Free |
| Microsoft Clarity | Five assistants' own sites | Not counted as AI | Not documented | No | Free |
| Matomo | A public list of assistants | Search Engines | No: read as a campaign | Assistant fetches, through a CDN or WordPress | Free to host yourself; Cloud is paid |
| Plausible | Eight assistants, past data reclassified | Organic Search | No: filed under Referral | Filtered out | From $9 a month |
| Server logs and CDN | The referrer on each request, when one is sent | Google, like any search click | Visible in the requested URL | Every request, by user agent | Free where your host exposes logs; Cloudflare's AI referrals need a paid plan |
| Search Console and Bing | No visits | Impressions only, in Google's AI report | No visits to count | No | Free |
Each cell restates a fact from the tool's entry above and the source linked there. The utm_source=openai column describes the code Matomo and Plausible publish, and what GA4 and Clarity document.
What None of Them Can See
A visit with no referrer and no tag
When an app opens a link without sending a referrer, or someone copies a link out of an answer without its query string, the visit arrives with nothing that names its source. Every tool here that counts visits treats it as direct traffic, a server log shows a request with an empty referrer, and nothing recovers its source later. Our dark AI traffic post explains why no honest count of these visits exists.
Why the visits moved
A traffic report tells you that visits from an assistant rose or fell, not why. Visits move for many reasons, so they confirm a change in AI answers late and loosely. To check whether a specific change worked, count the answers it was meant to change, as our measurement guide sets out, and read traffic as supporting evidence.
How Ranqo Does It
We built Ranqo's Traffic page on two of the entries above, because each sees what the other cannot.
Traffic
Humans arriving from AI answers, search and social, plus the AI crawlers reading your site.
Server-side · bots + humans
People landing on your site
124,884
Across 6 active channels
Bots and humans combined
674,270
Authenticated crawler share
97.2%
311,840 of 320,823 checkable visits
Unique paths hit by any agent
486
ChatGPT
2,41244%Gemini
1,03619%Perplexity
78414%Claude
61211%Copilot
3416%Grok
1483%DeepSeek
872%Meta AI
541%
Why agents are visiting your site
- Training218,45632.4%
- Search Engine140,23220.8%
- Indexing129,68419.2%
- Human (Direct)119,41017.7%
- Agentic31,8734.7%
- Social Preview29,1414.3%
- Human (AI Referral)5,4740.8%
Google Analytics
With a GA4 property connected, read-only, Ranqo shows the sessions GA4 attributes to AI assistants and search engines, by source, with engagement, conversions and landing pages, synced daily. Its assistant list is the pattern in entry 2, openai included.
Site Tracking
Site Tracking is entry 6 without the parsing. A snippet on your server or edge reports each page request, and Ranqo sorts the crawlers by why they came (training, indexing, or an assistant fetching a page for someone) and checks the ones whose operators publish IP ranges. It counts a human visit as AI by its referrer alone, so a tagged link opened without a referrer counts as Direct there.
Ranqo does not tie a visit to the answer that sent it. The rest of the product covers the cause instead: it tracks whether AI answers in your category name you, and the Action Center turns the gaps into recommendations.
See the AI crawlers your analytics miss
Ranqo tracks whether AI answers name you, turns the gaps into recommendations in the Action Center, and, with GA4 or Site Tracking connected, shows the visits AI platforms send to your site, and with Site Tracking, the AI crawlers reading it. For the GA4 side in detail, read how to track AI traffic in GA4.
Start a 7-day trialWritten by
Nisha Kumari
Nisha Kumari is Co-Founder at Ranqo, where she leads growth strategy and client acquisition. With a background in digital marketing and financial management, she specializes in SEO, Generative Engine Optimization, and helping brands build visibility across AI platforms.
Share this article
Related articles
How to Track AI Traffic in GA4: What the AI Assistant Channel Misses
Google Analytics 4 now gives AI assistants like ChatGPT and Gemini their own channel, but not every AI visit lands there. Clicks from Google's AI Overviews and AI Mode still count as Organic Search, and links in answers from OpenAI's search models are tagged "openai", which a rule for chatgpt.com misses (99.7% of the 37,470 we collected were). Here's where each AI visit lands, and a channel setup that catches more of them.
Dark AI Traffic: Why Most AI Visits Never Look Like AI Visits
The statistic that roughly 70% of AI traffic is invisible is not a measurement, and it cannot be one: a referrer-less visit carries no evidence of where it came from, so the denominator is the thing being estimated. The gap is still real. Here are the five loss classes, which ones you can actually recover, and why server-side tracking fixes fewer of them than everyone claims.
The AI Traffic Funnel: Training, Indexing, Agentic, Visit (and What GA4 Misses)
GA4 collapses every AI bot visit and every AI-referred human into one rolled-up percentage. That number hides four different intents on four different timescales. This deep dive breaks down the Training → Indexing → Agentic → Visit funnel per AI platform, why client-side analytics misses most of it, and the server-side architecture that doesn't.