TL;DR
Measure AI referral traffic in your web analytics: use GA4's AI Assistant channel (or a custom channel above Referral), match utm_source=chatgpt.com, look at landing pages and key events, and store the first-touch source in your CRM to connect it to revenue. Treat the result as a floor. On otterly.ai, AI assistants referred 2,814 visits in 30 days, 93% from ChatGPT, and bot activity was a poor predictor of human visits.
Key takeaways
- Referrals are people, crawlers are bots. Measure them in different places.
- GA4 has an AI Assistant channel, but it excludes Google AI Overviews and AI Mode.
- ChatGPT tags its links with utm_source=chatgpt.com. Use it.
- Revenue attribution needs your CRM, plus a "How did you hear about us?" field.
- Report it as a floor, next to your AI visibility, not instead of it.
The short answer: how to measure AI referral traffic
AI referral traffic is the people who click a link in ChatGPT, Gemini, Claude, Perplexity or Copilot and land on your site. You measure it in your web analytics, not in your server logs, and you need four things:
- A dedicated channel. GA4's default channel group now has an AI Assistant channel for visitors from sources like ChatGPT, Gemini, Deepseek, Copilot or Grok. If your property or tool doesn't have one, build a custom channel that matches AI assistant domains and place it above Referral.
- The ChatGPT UTM. OpenAI's publisher FAQ says ChatGPT adds
utm_source=chatgpt.comto referral links from ChatGPT search. Match on that value as well as on the referrer. - A landing-page view. Break AI-referred sessions down by landing page and key event, so you see which pages assistants send people to and whether those people convert.
- A path into your CRM. Store the first-touch source on the lead or account, or you'll never connect a ChatGPT click to revenue.
Then treat the number as a floor: clicks without a referrer land in Direct, Google's AI Overviews and AI Mode are counted as normal Google search, and most AI answers never produce a click at all.
What counts as AI referral traffic, and what doesn't
"AI traffic" gets used for four different things. Only one of them is a human visitor you can see in analytics:
| Signal | What it is | Where you see it |
|---|---|---|
| AI assistant referrals | A person clicks a cited link in ChatGPT, Gemini, Claude, Perplexity or Copilot | Web analytics (GA4 AI Assistant channel, referrer, utm_source=chatgpt.com) |
| Google AI Overviews and AI Mode clicks | A person clicks a link inside Google's AI features | Counted inside Google organic search. Google says these appear in Search Console's Performance report under the "Web" search type, and GA4's AI Assistant channel excludes them |
| AI agent and crawler visits | A bot reads your page to train, index or answer a prompt | Server or CDN logs only, because bots don't run your analytics tag. See my guide to tracking AI crawlers |
| No-click influence | An assistant recommends you, and the buyer later types your URL or searches your name | Not directly measurable. Shows up as Direct, branded search or "how did you hear about us?" answers |
Mixing these up is the most common reporting mistake I see. A big crawler number is not traffic, and a small referral number doesn't mean AI search doesn't matter to you.
What 30 days of AI referral traffic to otterly.ai show
Here's the analysis run on us. On otterly.ai we use our User Analytics (rolling out) next to our Agent Analytics, so we see both the people the assistants send and the bots that read our pages. For 18 October – 16 November 2026:
The interesting part is putting human referrals next to AI agent visits for the same 30 days:
| Engine | AI agent visits (bots) | Human visits it referred |
|---|---|---|
| ChatGPT | 11,211 | 2,623 |
| Claude | 34,551 | 71 |
| Microsoft Copilot | 15,359 | 0 |
| Perplexity | 1,884 | 29 |
| Google (all AI surfaces) | 520 | 91 |
Four things stood out to me:
- Bot visits don't predict human visits. Claude read our site three times as often as ChatGPT did, but sent us 71 visitors to ChatGPT's 2,623. Copilot's crawler made over 15,000 visits and we recorded zero visits referred by Copilot. If you only watch crawler logs, you'll overrate some engines and underrate others.
- ChatGPT is almost the whole channel, for now. 2,623 of 2,814 AI-referred visits (93%) came from ChatGPT. In this data, Google covers all Google AI surfaces, including AI Overviews, AI Mode and Gemini. That's different from GA4, where the AI Assistant channel excludes AI Overviews and AI Mode and counts those clicks as regular Google search, so Google's AI influence looks smaller there than it does here.
- Assistants read your pricing page; people click your homepage. In our crawler data, /pricing/ was the most-fetched page by far. In the human data, 1,368 visits (49%) landed on the homepage and 374 (13%) on pricing, followed by our AI citations report with 166. Your homepage has to do the job a landing page normally does.
- It's global. Fewer than one in five AI-referred visits (529) came from the US. If you report AI traffic for one market only, you'll miss most of it.
The numbers are small next to our total traffic, and that's the point: AI referral traffic is a high-intent trickle you can measure precisely, not a flood. The influence of AI answers is much bigger than the clicks, which is why I report it next to visibility, not instead of it.
How to set it up in GA4
- Check the AI Assistant channel. In GA4, open Reports → Acquisition → Traffic acquisition and switch the dimension to Session default channel group. Google's documentation defines AI Assistant as visitors arriving from sources like ChatGPT, Gemini, Deepseek, Copilot or Grok, excluding AI Overviews and AI Mode.
- Add a custom channel group if you need more control. Create a channel called "AI assistants", set it to match when the session source matches a regex of assistant domains or
utm_sourceis chatgpt.com, and move it above Referral so those sessions aren't swallowed by it. - Build one exploration. Rows: landing page. Columns: session source. Values: sessions, engaged sessions and your key events (demo request, signup, purchase). This is the report I'd look at monthly.
- Compare 4-week windows, not days. AI referral numbers are small and spiky. Week-over-week noise will mislead you.
An example source rule, to check against the referrers you actually see in your own data before you use it:
^(chatgpt\.com|chat\.openai\.com|(www\.)?perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai)$
Assistants change domains and apps, so re-check the list every quarter. A stale rule quietly moves traffic back into Referral or Direct.
How to attribute revenue to ChatGPT traffic
Analytics tells you a ChatGPT visitor converted on a form. Revenue happens later, in your CRM or billing system. To connect the two:
- Capture the source on the first visit. Store the referrer,
utm_sourceand landing page in a first-party cookie or session, and pass them into hidden form fields or your signup payload. - Persist it on the lead or account. Write "first-touch source = ChatGPT" (and last-touch, if you track both) to the CRM record, so it survives long sales cycles, device switches and cookie expiry.
- Join it to revenue. Report pipeline and closed revenue by first-touch AI source. With few deals, show counts and values, not percentages.
- Ask people. Add a free-text "How did you hear about us?" field to your demo or signup form. Answers like "ChatGPT recommended you" catch the no-click influence that analytics can't see.
- Report it as a floor. Click-based attribution undercounts AI search, because most answers never produce a click. Show it next to your visibility trend, not as the whole story.
My honest view as the CEO of a company that measures AI search: nobody can give you exact revenue attribution for AI answers today, and anyone who promises it is selling the dashboard, not the data. What you can do is measure the clicks precisely, collect self-reported answers, and watch whether both move with your visibility.
What I'd report to leadership
Three numbers, every month, on the same page:
- Visibility: brand coverage on a fixed set of buyer prompts (how often AI answers mention you). This is the leading indicator.
- AI-referred visits and conversion rate: sessions from the AI assistant channel, and how many become key events.
- AI-sourced pipeline (a floor): first-touch AI source in the CRM plus self-reported answers.
If visibility rises and referrals and self-reported mentions follow a few weeks later, you have a story your CFO will accept. I walk through the full one-page format in the monthly AI search report I want as a CEO, and how to pick the prompts in my prompt research playbook.
Mistakes to avoid
- Counting bots as traffic. Crawler and agent visits belong in log analysis, not in your traffic report.
- Leaving AI in Referral. Without a dedicated channel, ChatGPT sessions get mixed with every other referring site.
- Looking for AI Overviews in referrals. Those clicks are part of Google organic. Use Search Console and your visibility tracking for Google's AI features.
- Reporting US-only. On our site most AI-referred visitors came from outside the US.
- Calling it ROI. Click-based numbers are a floor. Label them that way and you keep your credibility when someone asks hard questions.
How we do it at OtterlyAI
Disclosure, and what OtterlyAI offers here
I'm the CEO of OtterlyAI, so weigh this accordingly. OtterlyAI tracks how often AI answers mention and cite your brand for your buyers' prompts. For traffic, we offer a free Looker Studio report for GA4 that shows which AI search engines send you visitors (it doesn't cover Google AI Overviews or AI Mode). Agent Analytics shows the AI bots and agents reading your pages, from a lightweight server, edge or CDN integration that runs alongside GA4; it's available on the Standard, Premium and Custom plans.
Sources
- Google Analytics Help, Default channel group (AI Assistant channel definition, checked 17 Nov 2026)
- Google Search Central, AI features and your website (AI Overviews and AI Mode traffic in Search Console's "Web" search type)
- OpenAI Help Center, Publishers and developers FAQ (
utm_source=chatgpt.comon ChatGPT search referrals) - OtterlyAI Help Center, Can I measure AI search traffic via GA4? and Agent Analytics FAQs
- OtterlyAI first-party data for otterly.ai, from User Analytics (rolling out) and Agent Analytics (AI-referred visits and AI agent visits, 18 Oct – 16 Nov 2026), pulled 17 Nov 2026.
Related reading: AI crawlers: how to track them, how to track brand mentions in AI search and SEO for ChatGPT.
FAQs
How do I measure how much website traffic AI assistants send me?
Use your web analytics. In GA4, the default channel group has an AI Assistant channel for visitors from sources like ChatGPT, Gemini, Copilot and others; otherwise create a custom channel that matches AI assistant domains and utm_source=chatgpt.com, placed above Referral. Then break it down by landing page and key event over 4-week windows. OtterlyAI also offers a free Looker Studio report for GA4 that shows which AI search engines send you visitors.
How do I attribute revenue to traffic that came from ChatGPT?
Capture the referrer and utm_source=chatgpt.com on the first visit, pass them into your form or signup, store first-touch source on the lead or account in your CRM, and report pipeline and closed revenue by that source. Add a "How did you hear about us?" field to catch buyers who saw you in ChatGPT but never clicked. Report the result as a floor, because most AI answers produce no click.
Does GA4 track traffic from ChatGPT?
Yes, when the visitor clicks a link. ChatGPT sessions appear with chatgpt.com as the source, and GA4's default channel group puts AI assistant visits in an AI Assistant channel. Visits without a referrer, for example from copied links or some apps, show up as Direct.
Can I see traffic from Google AI Overviews and AI Mode?
Not separately. Google says clicks from AI features are included in Search Console's Performance report under the "Web" search type, and GA4's AI Assistant channel excludes AI Overviews and AI Mode. They're counted as regular Google organic traffic.
Is there a GEO platform that connects to GA4?
OtterlyAI, the company I run, offers a free Looker Studio report that reads your GA4 data and shows which AI search engines send you visitors. It's a report template on top of GA4, not a two-way integration, and it doesn't cover Google AI Overviews or AI Mode. Whatever tool you use, check whether it reads GA4 data, writes into GA4, or both.
Are AI crawler visits the same as AI referral traffic?
No. Crawler and agent visits are bots reading your pages and only show up in server or CDN logs. Referral traffic is people clicking through from an AI answer. On otterly.ai, Claude's bots visited three times as often as ChatGPT's in 30 days, but ChatGPT sent 37 times as many human visitors.