From Mention to Money: Tracking AI Referral Traffic to Your Name

A recommendation you cannot measure is a rumor. This is the plumbing that turns "ChatGPT mentioned me" into a number your accountant would accept.

Why track a stream that is only 1% of traffic?

Because the 1% is not like the other 99%. Across ten industries, AI referral traffic averages about 1.08% of all website visits, but the conversion numbers invert the picture: Conductor's 2026 benchmarks put ChatGPT referral conversion at 14.2-15.9%, Perplexity around 10.5%, and Claude as high as 16.8%, against roughly 1.76% for Google organic, as compiled by SEO Sherpa's AI search statistics. A visitor who arrives from an AI answer was not browsing, they were referred. The engine already framed you as the answer before the click happened.

Concentration makes the measurement problem tractable: ChatGPT alone drives about 87.4% of all AI referral traffic, per the same Conductor data, and ChatGPT reached roughly 900 million weekly active users by February 2026, up from about 400 million a year earlier, according to Similarweb's generative AI statistics. Get ChatGPT attribution right and you have captured most of the story. And for anyone doing PEO the stream is even more personal: these clicks are frequently someone checking out a name a machine just gave them, which is why the pages they land on are usually your About page, your knowledge base, or the exact article that made you citable. Which of your questions deserve this treatment is the domain of Money Queries.

How does AI traffic actually show up in GA4?

Three arrival patterns, three very different visibilities:

• Tagged referrals. ChatGPT appends a utm_source=chatgpt.com parameter to many outbound links from its search-backed answers, so those sessions arrive cleanly labeled with session source chatgpt.com. This is the best-behaved slice of the stream.
• Plain referrals. Perplexity, Gemini, Copilot and most others usually pass an ordinary referrer header (perplexity.ai, gemini.google.com, copilot.microsoft.com) with no UTM tagging. GA4 files these under the generic Referral channel, mixed in with every blog that ever linked you.
• Dark arrivals. Clicks from mobile apps and some desktop clients ship no referrer at all. GA4 calls them Direct. This slice is real, material and invisible, which means every number your AI channel shows you is a floor, not a total.

The GA4 setup: a custom AI channel in six steps

1. Open the channel editor. In GA4: Admin, then under Data display choose Channel groups. Do not edit the default group; click Create new channel group so the original stays intact for comparison. Google's reference for this feature is the custom channel groups documentation.
2. Create the channel. Inside your new group, select Add new channel and name it AI Traffic.
3. Define the condition. Set the rule to: Session source matches regex, then paste the pattern below. Session source (not medium) is where both the UTM-tagged and plain-referrer arrivals surface.
4. Order it above Referral. GA4 evaluates channel rules top to bottom, and an AI session that hits the Referral definition first stays a Referral forever. Drag AI Traffic above Referral (and above Organic Search) in the channel list. This single step is the one most setups get wrong.
5. Save and wait. Custom channel groups apply to how data is displayed, so your new channel appears as a selectable dimension in Traffic acquisition reports. Give it a full week of data before judging volumes.
6. Annotate the start date. Note the day you shipped the channel, so nobody later mistakes the appearance of AI Traffic for the appearance of AI traffic.

The regex directory

The matching pattern, current as of July 2026:

chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|grok\.com|meta\.ai|deepseek\.com|you\.com

What each cluster covers:

• chatgpt.com, chat.openai.com: ChatGPT's current and legacy domains. Expect the bulk of your volume here.
• perplexity.ai: Perplexity's answers and its Discover feed. Typically your second-largest AI source.
• claude.ai: Claude's web client, including links surfaced in web-search-backed replies.
• gemini.google.com: the Gemini app. Note that Google AI Overviews clicks are not in this bucket; they arrive as ordinary google organic and cannot be separated inside GA4.
• copilot.microsoft.com: Microsoft Copilot on web and in Windows.
• grok.com, meta.ai, deepseek.com, you.com: small today, cheap to include, occasionally spiky.

Review the list quarterly. Assistants launch, rebrand and change domains constantly, and a regex nobody maintains quietly rots into undercounting.

Which reports turn mentions into money?

Landing pages by AI channel

In Reports, open Traffic acquisition, switch the primary dimension to your new channel group, then drill into AI Traffic by landing page. This report answers the operational question: which of your pages are the engines actually citing and sending people through? If your About page and one or two cornerstone articles dominate, the engines have effectively told you what they consider your canonical proof. Feed that knowledge back into your publishing plan.

The exploration for deeper cuts

For anything the standard reports cannot answer, build a free-form exploration: Explore, new blank exploration, add Session source and Landing page as dimensions, Sessions and Key events as metrics, then filter Session source against the same regex you used for the channel. The exploration works on your historical data too, so it is also how you reconstruct what AI traffic looked like before the day you built the channel. Save it once, revisit monthly.

Key events by channel

Mark your consequential actions as key events (contact form, booking, newsletter signup) and compare completion rates for AI Traffic against Organic Search. This is where the conversion-quality claim stops being an industry statistic and becomes your number, defensible in any budget conversation.

Connecting spikes to causes

Numbers without a changelog are trivia. Keep a simple placement calendar: every article published, every podcast aired, every mention earned, with dates. When the AI channel jumps, you want to look left on the timeline and see the probable cause sitting there. This is also how you learn which kinds of proof move the needle for your name: some people find one well-transcribed podcast outdrives five guest posts, others the reverse. The correlation is never courtroom-grade, but over two or three quarters the pattern gets hard to miss, and it should redirect your effort accordingly.

The quarterly triangulation

GA4 tells you about clicks, but plenty of AI influence never clicks: the buyer hears your name, then Googles you, or types your URL. So triangulate quarterly: your AI channel trend, your branded search impressions in Search Console, and a standing prompt audit of what the engines say about your name. The prompt side of that loop is documented in The 25-Prompt Audit and the tooling landscape in AI Visibility Tools Compared. When all three lines move together after a placement or a content push, you have attribution no single dashboard could give you.

What GA4 cannot show you (and what to do about it)

Be honest about the blind spots. GA4 cannot see the prompts people typed, cannot separate AI Overviews from ordinary Google clicks, and cannot count the dark-referrer sessions hiding in Direct. It measures the click, and the whole point of AI answers is that many recommendations convert without one.

You can still put a rough boundary around the dark slice. Pull Direct traffic by landing page and watch the pages your AI channel already favors: when Direct sessions to those same deep pages climb in step with your AI channel, you are almost certainly looking at unlabeled AI referrals, because humans do not type a long blog URL from memory. Some teams sanity-check this by comparing the ratio month over month; if labeled AI traffic doubles and deep-page Direct doubles alongside it, attribute with appropriate humility and move on.

Treat the AI channel as your floor, watch Direct for unexplained growth to AI-cited landing pages, and keep asking new leads the oldest attribution question in the business: how did you hear about me? "ChatGPT told me" is showing up in that answer far more often than it did a year ago. The broader measurement stack, beyond GA4, is covered in How to Track Your AI Visibility, and if you want the whole loop built and monitored for you, that is what our services exist for.