How to Track AI Traffic in GA4, Plausible and Matomo (2026)

You can track clicks from AI assistants by their referrer: GA4, Plausible and Matomo now all have a built-in AI channel, and you can add a regex-based one yourself. Two limits apply to every tool. Visits that arrive without a referrer land in Direct, and a mention that nobody clicks never shows up in analytics at all. Analytics tells you about clicks; to know whether assistants name you, you need to ask them. Nodpick does that part for your own brand, every week, and this post shows how the two fit together.

This post gives the setup for each tool, a starting regex, and the caveats we could verify. Referrer behavior changes with every app update, so treat lists here as a starting point and check your own data.

How do I track traffic from ChatGPT and other AI assistants?

Track traffic from ChatGPT and other AI assistants by their referrer or UTM tag: a visit counts as AI traffic when the click arrives with a recognized assistant domain such as chatgpt.com or a utm_source value. As of 1 November 2026, GA4, Plausible and Matomo each ship an AI channel for this (details below). The glossary entry on AI referral traffic defines the term.

When a person clicks a link in an assistant's answer, the browser may send a referrer (the page or site they came from), and the link itself may carry UTM parameters. Two verified examples:

• OpenAI states that ChatGPT adds utm_source=chatgpt.com to referral URLs, so analytics tools such as Google Analytics can track this traffic (OpenAI publishers FAQ). Check it in your own data before you rely on it.
• Plausible says it attributes a visit to an assistant only when it carries referral information or a UTM tag (Plausible).

What you cannot see: the prompt, the answer, or the assistant's decision to mention you. Plausible says it directly: private conversations and prompts are not visible; only traffic and conversions after a click are measured.

How do I track AI traffic in GA4?

Option 1: the built-in channel. Google's Analytics release notes for May 13, 2026 describe an AI Assistant channel in the Default Channel Group: visits are categorized there when the referrer matches a recognized AI assistant, with the medium ai-assistant assigned automatically and the campaign shown as (ai-assistant). ChatGPT, Gemini and Claude are named as examples (Google Analytics Help). The full list of recognized referrers is not published there, so do not assume every assistant is on it.

Option 2: a custom channel group. It lets you control the list and apply it in your reports. In GA4 go to Admin, then Data display, then Channel groups, and create a new group. Add a channel named "AI assistants" with the condition Source matches regex:

^(chatgpt\.com|chat\.openai\.com|perplexity\.ai|www\.perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|grok\.com|chat\.mistral\.ai|chat\.deepseek\.com|kimi\.com)$

Put this channel above Referral in the rule order, because GA4 assigns a session to the first matching rule. Hostnames are our best known list, not an official one; some assistants use several domains, and they change. Open your Traffic acquisition report by session source and look at what actually arrives before you trust the list.

Do not add bare root domains such as google.com or openai.com to the regex: google.com matches ordinary Google traffic, and OpenAI's own domain can be docs or marketing visits.

Check in an exploration. Build a free-form exploration with Session source / medium as rows and Sessions, Engaged sessions and Key events as values. Filter for chatgpt.com, perplexity and the rest. Compare against your direct traffic trend.

How do I track AI traffic in Plausible?

Plausible groups visits from known assistants such as ChatGPT, Claude, Perplexity, Gemini and Copilot into one AI Assistants channel in the Channels report, with no segment to maintain. Open the channel to compare individual sources, then filter by it to see entry pages, goals, funnels and revenue for that audience. Plausible also says known AI crawlers and bots are filtered out, so the channel reflects human clicks (Plausible).

Only known assistants are grouped automatically, so check the Sources report for unfamiliar AI domains.

How do I track AI traffic in Matomo?

Matomo has an AI Assistant referrer channel type that classifies visits from tools such as ChatGPT, Copilot, Gemini, Claude, Le Chat, Meta AI, iAsk and Perplexity. It is available on Matomo Cloud, and Matomo's FAQ says it is also available in On-Premise starting with version 5.5.0. You find it under Acquisition, Overview or All Channels, and in a dedicated Acquisition, AI Assistants report. A custom segment Channel Type Is ai compares AI visits across all reports. The channel applies only to data collected after the update; earlier visits stay in Referral or Direct (Matomo FAQ).

If you run an older version, a segment on the referrer URL does the same job. In Matomo's segment syntax, =@ means "contains" and a comma means "or":

referrerUrl=@chatgpt.com,referrerUrl=@perplexity.ai,referrerUrl=@claude.ai,referrerUrl=@gemini.google.com

Where do the missing visits go?

Into Direct. Search Engine Journal's coverage of the new channel notes that AI assistant traffic arriving without a referrer header still lands in Direct (Search Engine Journal). Plausible makes the same point from the other side: no referral and no UTM, no attribution.

Two practical moves:

• Tag the links you control. If you share links in newsletters, profiles or answers, use UTM parameters so you can tell them apart from organic AI clicks.
• Ask new customers. A "How did you hear about us?" field with "ChatGPT / AI assistant" as an option catches visits analytics will not. It is also a data source no tracker has.

How do I track AI Overviews and AI Mode traffic?

Google states that traffic from AI Overviews and AI Mode is included in the overall Search Console data under the Web search type (Google). In analytics those visits arrive as Google organic traffic, so they are not part of an AI Assistant channel. You cannot split them from classic Google clicks with standard reports. Our post on AI Overviews vs. AI Mode and the Google AI Overviews guide explain what each does.

Can server logs help?

They answer a different question. Logs show which bots fetch your pages: OAI-SearchBot, GPTBot, ChatGPT-User, PerplexityBot, Perplexity-User, ClaudeBot, Claude-User, Claude-SearchBot. A fetch by a user-triggered bot such as ChatGPT-User or Perplexity-User means an assistant looked at your page to answer a question (OpenAI, Perplexity, Anthropic). That is not a visit and not proof of a citation, but it is an early signal that your page was considered. Count bot fetches separately from sessions and do not add them together.

What numbers should I watch?

Metric	What it tells you	Watch out for
Sessions from AI channel	Click volume	Small numbers, direct leakage
Engaged sessions / key events per session	Quality of the visits	Compare with organic, not total
Landing pages	Which pages assistants send people to	Pages you did not expect
Bot fetches in logs	Whether crawlers reach you	Not equal to visits
Mentions in answers	Whether you are named at all	Not in analytics

How do I see the part analytics cannot show?

Analytics is the last link in a chain: an assistant names you, shows a link, the person clicks. You can only manage the whole chain if you measure its first part too, and that part is not in any analytics report.

In Nodpick this is one setup step. You add your questions (the ones your buyers would type), and every week Nodpick asks them on ChatGPT, Google AI Overviews, Google AI Mode, Gemini, Perplexity and Claude (Grok, Mistral, DeepSeek and Kimi as an add-on, included on Agency). For each answer it records whether you are named, in which position, who is named instead and which domains are cited, and the answer explorer shows every answer with its sources. Search Console and Bing AI exports (see the Bing AI Performance report) can be shown next to the score, so you read mentions and clicks side by side. Mentions up and clicks flat is a different problem from mentions flat and clicks up. For the definitions see prompt tracking and the tracking guide.

Check your own brand

Your analytics already tell you how many assistant clicks arrive. To see whether assistants name you at all, use the free AI visibility checker: five buyer questions on ChatGPT, Perplexity, Gemini and Claude, plus one question about your brand by name that is not scored. It opens on launch day, and you can join the waitlist on that page to get one email when Nodpick opens. The weekly version, with a range around the score, is on the pricing page.

FAQ

How much traffic do AI assistants send? That depends on your market. Check your own channel before assuming either way; we do not have a reliable general number to give you.

Why does ChatGPT traffic show as Direct in GA4? Referrer behavior depends on the app and link type. OpenAI documents the UTM parameter; whether a referrer header also arrives depends on the client.

Do I need a custom channel if GA4 has one? Only if you want control over which domains count, or need the list to include assistants Google does not recognize.

Is a mention without a click worth anything? Analytics cannot say. The post on whether GEO is worth it goes through the available data, and the tracking guide shows how to measure mentions directly.

Should I exclude bots? Plausible says it filters known AI crawlers from the dashboard. For other tools, check your own reports if numbers look odd.

Sources

• OpenAI: Publishers and developers FAQ
• Google Analytics Help: release notes (AI Assistant channel, May 13, 2026)
• Search Engine Journal: Google Analytics adds AI Assistant as default channel group
• Plausible: AI traffic analytics
• Matomo: how to track and analyse traffic from AI assistants
• Google Search Central: AI features and your website
• OpenAI, Perplexity and Anthropic crawler documentation