MentionLeads field guide
AI Referral Traffic: Find ChatGPT Visits in GA4 and Logs
Which AI visits you can measure: GA4's AI Assistant channel, the utm_source tag ChatGPT adds, three log commands and a click test for other assistants.
By MentionLeads · Published October 2, 2026 · 9 min read
In short: To track AI referral traffic, check the AI Assistant channel in Google Analytics 4, search server logs for the utm_source=chatgpt.com tag OpenAI documents, and click-test every other assistant yourself, because vendors document tracking unevenly. Google reports AI Overviews and AI Mode clicks inside ordinary Search results, not as a separate AI source.
AI referral traffic is easy to over- or under-count, because each AI product tags its links differently and some do not document how at all. This guide separates what vendors document from what you can only observe, then gives you the Google Analytics 4 (GA4) steps, three log commands and a click test that show how each assistant's visits arrive on your site. Vendor facts were checked against the vendors' own pages on 2 October 2026.
What is AI referral traffic, and what is it not?
AI referral traffic is the set of human visits that start with a click on a link inside an AI assistant's answer, such as ChatGPT, Gemini, Copilot or Perplexity. It is not crawler traffic, where an AI company's bot fetches your page, and it is not a citation that was read and never clicked, which leaves no visit in your analytics.
| What happens | Is it a visit? | Where you can see it |
|---|---|---|
| A person clicks a link in an AI answer | Yes | GA4 and server logs |
| A search crawler fetches your page (OAI-SearchBot, PerplexityBot, Claude-SearchBot) | No, a bot request | Server logs, by user-agent name |
| An assistant fetches your page because a user asked (ChatGPT-User, Perplexity-User, Claude-User) | No, a bot request made on someone's behalf | Server logs, by user-agent name |
| A training crawler fetches your page (GPTBot, ClaudeBot) | No, a bot request | Server logs, by user-agent name |
| An answer cites you and nobody clicks | No | Not in your analytics; Bing's AI Performance report counts citations for Copilot and Bing AI summaries |
Which AI assistants document how their links are tracked?
As of 2 October 2026, OpenAI documents a tracking tag for ChatGPT search links, Google documents where AI Overviews and AI Mode clicks are reported, and Microsoft documents citation reporting for Copilot. The Perplexity and Anthropic pages that describe their crawlers say nothing about referral tagging, so those assistants need the click test below.
| Surface | What you can measure | How it shows up | Where the vendor says so |
|---|---|---|---|
| ChatGPT search | Clicks | ChatGPT adds the UTM parameter utm_source=chatgpt.com to referral URLs | OpenAI Help Center, "Publishers and Developers - FAQ" (help.openai.com) |
| Google AI Overviews and AI Mode | Clicks and impressions, mixed into Search | Search Console Performance report, Web search type; GA4 counts them in Organic Search | Google Search Central, AI features and your website; Google Analytics Help, "Default channel group" (support.google.com) |
| Assistants GA4 names (ChatGPT, Gemini, Deepseek, Copilot, Grok) | Visits | GA4's AI Assistant channel, with medium "ai-assistant" when the referrer matches Google's list | Google Analytics Help, "Default channel group" (support.google.com) |
| Microsoft Copilot and Bing AI summaries | Citations, not clicks | Bing Webmaster Tools, AI Performance | Bing Webmaster Blog, "Introducing AI Performance in Bing Webmaster Tools Public Preview" (blogs.bing.com, 10 February 2026) |
| Perplexity | Not documented on its crawler page | Run the click test | Perplexity docs, "Perplexity Crawlers" (docs.perplexity.ai) |
| Claude | Not documented in Anthropic's crawler article | Run the click test | Claude Help Center, "Does Anthropic crawl data from the web, and how can site owners block the crawler?" (support.claude.com) |
How do you find ChatGPT and other AI visits in GA4?
Open Reports, then Acquisition, then Traffic acquisition, and look for the AI Assistant row in the Session default channel group. Google's default channel group lists AI Assistant as the channel for sources like ChatGPT, Gemini, Deepseek, Copilot and Grok, and it excludes AI Overviews and AI Mode, which count under Organic Search.
- Check the channel. In Reports > Acquisition > Traffic acquisition, the first column defaults to Session default channel group. Look for AI Assistant.
- Check the sources. Switch the first column to Session source / medium and type chatgpt, perplexity, claude, gemini or copilot into the search bar above the table, one at a time.
- Expect gaps in the medium. OpenAI documents only utm_source, and Google says missing UTM parameters result in (not set) values in reporting, so a ChatGPT-tagged visit can show (not set) in medium or campaign. The documentation does not say which channel such a visit lands in, so check your own report.
- Add a custom channel if a source is missing. In Admin > Data display > Channel groups, add a channel with the condition Source matches regex and the pattern below, then move it above Referral, because Google applies the first channel a visit matches. Custom channel groups can be applied to past data.
Pattern for the custom channel: `.*(chatgpt|openai|perplexity|claude|gemini|copilot|grok|deepseek).*`. After saving, scan the matching rows in Session source, because short names can match unrelated sites. Google also says its default channel definitions may evolve, so re-check the AI Assistant list from time to time.
How do you find AI referral traffic in server logs?
Search the access log for the utm_source=chatgpt.com parameter to count ChatGPT clicks, and search the user-agent field for the vendors' documented bot names to separate crawler fetches from visits. Server logs are not affected by ad blockers or consent banners, so they are the cross-check for GA4.
- Count ChatGPT-tagged requests: `grep -c "utm_source=chatgpt.com" access.log`
- List the pages those visits landed on: `grep "utm_source=chatgpt.com" access.log | cut -d' ' -f7 | cut -d'?' -f1 | sort | uniq -c | sort -rn | head -20`
- Count documented AI bot fetches by name: `grep -o -E "OAI-SearchBot|GPTBot|ChatGPT-User|PerplexityBot|Perplexity-User|ClaudeBot|Claude-User|Claude-SearchBot" access.log | sort | uniq -c | sort -rn`
The second command assumes the common combined log format, where the seventh field is the path; adjust the field number for your format. A ChatGPT-User line means ChatGPT fetched a page to answer someone, which shows an assistant read you but not that a person clicked. If your host or CDN strips query strings from its logs, test with a URL you tag yourself before trusting the counts.
How do you test how Perplexity, Claude or Gemini clicks arrive?
Click-test each assistant yourself: ask a question your page answers, click your page's citation, then read the address bar for tags and run `document.referrer` in the browser console to see the referring site. Compare both with how GA4 classifies the visit once it has processed, because vendors can change how links are tagged and a test records how they work today.
- Ask the assistant a question your page answers and confirm that it cites your page.
- Click the citation and note any utm_ parameters in the address bar.
- Open the browser console and run `document.referrer`. An empty result means no referrer arrived.
- Later, open Reports > Acquisition > Traffic acquisition and look for the source and channel your test visit landed in. Google says attribution in the Realtime report is limited and recommends the Acquisition reports.
- Record the result in the sheet below, then repeat on the phone and app your visitors use.
| Assistant | Cited my page? | Address-bar tag | document.referrer | GA4 source / medium | GA4 channel |
|---|---|---|---|---|---|
| ChatGPT | yes or no | utm_source=... or none | URL, origin or empty | [fill in] | [fill in] |
| Perplexity | yes or no | utm_source=... or none | URL, origin or empty | [fill in] | [fill in] |
| Claude | yes or no | utm_source=... or none | URL, origin or empty | [fill in] | [fill in] |
| Gemini | yes or no | utm_source=... or none | URL, origin or empty | [fill in] | [fill in] |
| Copilot | yes or no | utm_source=... or none | URL, origin or empty | [fill in] | [fill in] |
Why does AI traffic sometimes show up as direct, and how do you fix it?
AI traffic shows up as direct when a visit arrives with no referrer and no campaign tag, which GA4 files under (direct) / (none). Google lists redirects that strip UTM parameters, URL shorteners and ad blockers among the causes, so the first fix is to make sure your own redirects keep the query string.
- Open `https://yourdomain.com/?utm_source=test&utm_medium=ai-test` through each entry you use (http, https, www and non-www) and watch the address bar.
- If the tag disappears after a redirect, a ChatGPT-tagged click would lose it the same way; change the redirect to pass the query string through.
- Use a test source name you will recognize and exclude later, so the test does not pollute real reports.
- Cross-check GA4 against the log commands above; logs still show the tag when a script is blocked.
Do AI visitors convert, and how do you check?
No one can tell you from outside whether your AI visitors convert; the check is yours. Compare key events per session for the AI Assistant channel with Organic Search over the same dates, and wait until you have enough sessions that one visit cannot swing the result. Revenue needs one more link: the visit's source has to be stored with the customer or order, which is what analytics tools that join sessions to payments do. For a cookieless route, see privacy-first SaaS analytics, and for Reddit-specific tagging see tracking Reddit leads in GA4.
Frequently asked questions
How do I track ChatGPT traffic in Google Analytics 4?
Open Reports, Acquisition, Traffic acquisition, look for the AI Assistant channel, then switch the first column to Session source / medium and search for chatgpt. OpenAI says ChatGPT adds utm_source=chatgpt.com to referral URLs, so the source should read chatgpt.com. Click-test once yourself to see how your property records it.
Does traffic from Google AI Overviews and AI Mode count as AI referral traffic?
Not in GA4's AI Assistant channel, which excludes them; Google counts those clicks under Organic Search. Search Console reports them inside the Web search type with the rest of Search, and Google's AI features page describes no separate AI filter.
Why is my AI referral traffic showing as direct?
GA4 files visits with no referrer and no campaign tag under (direct) / (none), and Google names redirects that strip UTM parameters, URL shorteners and ad blockers among the causes. Test your redirects with a tagged URL and use server logs as a cross-check.
Start here
Spend one hour: check the AI Assistant channel, run the three log commands and click-test the assistants your buyers use. Then write down what each one does, because that sheet is more reliable than any list of rules.
- Open Traffic acquisition and note the AI Assistant row, plus any chatgpt, perplexity or claude sources.
- Run the three log commands against a week of logs and compare the counts with GA4.
- Fill in the click-test sheet for ChatGPT, Perplexity, Claude, Gemini and Copilot, and test your redirects with a tagged URL.
MentionLeads, a Reddit lead generation tool, also includes Live 3D Analytics: a live visitor globe with day and night, visitor sources that include AI answers such as ChatGPT and Perplexity, and visitors connected to Stripe revenue, on every plan. Its AI visibility page tracks AI crawlers, and SaaS analytics covers the revenue side. Disclosure: MentionLeads publishes this guide, and everything above works with GA4 and your own logs.
Turn public conversations into a repeatable growth channel.
MentionLeads discovers buyer signals across Reddit, X, LinkedIn, and Hacker News, then helps you qualify, respond, and measure what happens next.
Start your 7-day Pro trial$1 today, then $29/month after 7 days. Cancel anytime before day 8.