AI referrer domains:
what each engine sends, and when it changed
Perplexity, Copilot and Claude on the web usually send a referrer domain. The Gemini app, the Claude app and the ChatGPT Atlas browser often send none, so the visit lands in direct. Behavior changes without notice, so write the date next to every rule you build.
of Gemini app mobile traffic is dark
Searchpilot, via ThriveStack engine guide, Oct 2026share of Perplexity mobile app visits with a referrer vs direct
Searchpilot, via ThriveStack engine guideof mobile ChatGPT visits relied on the tag alone
Graphite, via ThriveStack engine guide2026: GA4 added an AI Assistant default channel
Search Engine Journal, May 2026Four things strip a referrer, and mobile is where it hurts.
A referrer is the domain the browser reports as the page the click came from. If it arrives, GA4 files the visit under that source. If it does not, the visit lands in direct.
- The link carries a noreferrer flag.
- The click happens in an in-app browser.
- An app hands the link to a browser.
- The link is copied and pasted.
Seven AI engines usually send a referrer domain, and three often hide it
Referrer behaviour of 10 AI engines and AI browsers, as of Oct 16, 2026.
Sources: Searchpilot (May 13, 2026), Orbit Media, Trakkr, SE Ranking, MarTech (Nov 2025). Evidence is thin outside ChatGPT and Perplexity, so test your own links.
How to read it. A filled dot means the referrer usually arrives, so a filter on that domain finds the visits. A half dot means it arrives only some of the time. An empty dot means the visit usually lands as direct.
In ThriveStack citedby Referrer domains and the direct traffic that rises beside them are read together, so a missing referrer shows up as a gap. See it for your site →
What each engine sends, and when it changed.
Use this table to decide which signal to match for each engine. The heatmap column scores how often the referrer arrives, from 0 (stripped) to 100 (usually passes). Red is under 40, amber is 40 to 69 and green is 70 and up. It is our reading of the evidence, not a measured rate. Evidence is thin outside ChatGPT, so test your own links.
Referrer behavior by AI engine, as of Oct 16, 2026
| Engine | Referrer compliance | Referrer domain | What arrives | When |
|---|---|---|---|---|
| 85 | chatgpt.com (older: chat.openai.com) | Referrer, plus utm_source=chatgpt.com on cited links | Tag added June 2025. Tag and referrer missing Oct 9 to Oct 15, 2026, then restored. | |
| 25 | gemini.google.com (older: bard.google.com) | Often no referrer on the app. Tags reported on some links. | Tags first seen Sep 10, 2026 and gone after Sep 29. Vendor data, unverified. | |
| 55 | claude.ai | Referrer on the web, but inconsistent. No UTM found. | Searchpilot, May 2026 | |
| 90 | perplexity.ai | Reliable referrer on the web. About 70% referrer and 30% direct on the mobile app. | Searchpilot and MarTech | |
| 80 | copilot.microsoft.com | Plain referral. No UTM found. | Moved from Bing Chat to this domain | |
| 50 | grok.com (also grok.x.com) | Referrer, but little volume | Near zero after summer 2025 (SE Ranking) | |
| 50 | chat.mistral.ai | Referrer, small volume | 0.22% of EU AI referral traffic (Orbit Media, SE Ranking) | |
| 40 | meta.ai | Referrer. No test of Muse linked clicks. | Muse Spark announced April 2026 | |
| 50 | deepseek.com | Referrer, near zero volume | Near zero since Sep 2025. Named in GA4's AI list. | |
| 30 | google.com | Referrer often stripped | Google called it a bug in May 2025. Searchpilot still saw it stripped in May 2026. | |
| Counted as organic | google.com | Counted as organic search | Shows as google / organic in GA4 | |
| 85 | perplexity.ai | Passes a referrer | Nov 2025 (MarTech) | |
| 10 | Often none | Lands as direct or (not set) | Nov 2025 (MarTech, Searchpilot) |
Source: ThriveStack engine guide, Oct 16, 2026, which cites Searchpilot, MarTech, SE Ranking, Orbit Media and Search Engine Journal. For UTM tags by engine see the UTM lesson.
One regex catches the common referrer domains.
Paste this into a GA4 custom channel group or a Looker Studio filter, above the Referral rule. It joins the domains from the table, plus older hostnames and You.com.
^(chatgpt\.com|chat\.openai\.com|perplexity\.ai|www\.perplexity\.ai|gemini\.google\.com|bard\.google\.com|claude\.ai|copilot\.microsoft\.com|deepseek\.com|chat\.deepseek\.com|grok\.com|meta\.ai|chat\.mistral\.ai|you\.com)$Google lists its own AI assistants for the AI Assistant channel, live since May 13, 2026. Google names ChatGPT, Gemini and Claude as examples, and other guides also list DeepSeek, Copilot and Grok. Sources disagree on whether Claude and Perplexity are in it, so check your Traffic acquisition report. Visits before May 13 are not reclassified.
Seven dated changes explain most surprises in your reports.
When AI engines changed how they send traffic
| When | What changed |
|---|---|
| May 2025 | Google calls the stripped AI Mode referrer a bug (PPC Land). |
| June 2025 | ChatGPT adds utm_source=chatgpt.com to citation links. |
| Nov 2025 | Comet passes a perplexity.ai referrer. Atlas often strips it (MarTech). |
| May 13, 2026 | GA4 adds the AI Assistant default channel. |
| May 2026 | Searchpilot: AI Mode referrer still stripped, and Claude sends no UTM. |
| Sep 10 to 29, 2026 | Gemini UTM tags seen, then gone (Vizzybl, vendor data, unverified). |
| Oct 9 to 15, 2026 | ChatGPT links lose the tag and the referrer after GPT-6, then the fix rolls out. |
Normalize and deduplicate AI referrers in four steps.
Two engines can describe the same click in two ways. A short rule set keeps your reports from counting it twice.
- 1
Keep one source field
Copy the referrer domain or utm_source into one field on the first visit.
- 2
Use one name per AI engine
Map chatgpt.com and chat.openai.com to ChatGPT, and do the same for every engine.
- 3
Count each session once
A click can carry a referrer and a tag. Prefer the tag, and count the session once.
- 4
Date every rule you add
Engines change how they send traffic. Write the date next to each rule so you know when to retest.
ThriveStack citedby runs your prompt panel across 10+ AI engines, reads server-log crawler hits, matches human visits to signups and reports AI-sourced and AI-influenced pipeline.
AI referrers, answered.
Which AI engines send a referrer?
Perplexity on the web, Copilot and Claude on the web usually do. The Gemini app, the Claude app and the ChatGPT Atlas browser often do not.
Why does my AI traffic show as direct?
A click lands in direct when it has no tag and no referrer. Apps, in-app browsers, noreferrer links and copy and paste all strip the referrer.
Is a referrer or a UTM tag more reliable?
Neither alone. ChatGPT sends both when it works, but its tag vanished for six days in October 2026. Referrers vanish in apps. Read both together.
Sources for this lesson
- ThriveStack citedby research: AI engines, referrers and utm_source (Oct 16, 2026)
- Search Engine Journal: Google Analytics adds an AI Assistant default channel (May 2026)
- Search Engine Roundtable: OpenAI drops UTM parameters from ChatGPT results (Oct 2026)
- PPC Land: ChatGPT adds utm parameters to more links
Figures were checked against each page in Nov 2026. Vendor studies are marked by their sample. Evidence is thin outside ChatGPT.
All 5 questions this lesson answers
How do AI assistants pass referrers?
Most chat products on the web send a referrer domain, such as perplexity.ai, copilot.microsoft.com or claude.ai. Apps, in-app browsers, the noreferrer flag and copy and paste strip it. Then the visit lands in direct. The Gemini app is about 91% dark on mobile (Searchpilot).
AI traffic referrer regex list
Start with this list and test it against your own Session source report: chatgpt.com, chat.openai.com, perplexity.ai, gemini.google.com, bard.google.com, claude.ai, copilot.microsoft.com, deepseek.com, grok.com, meta.ai, chat.mistral.ai and you.com. The regex above joins them. Treat it as a starter list, not a standard.
Server-side attribution of AI referrals
Your server sees the referrer header and the full URL on each request, even when your analytics tag does not fire. Log both, and match them to the engine list. Server logs also show AI crawler hits, which analytics never records. See the server logs lesson.
AI traffic source normalization
Copy the referrer domain or utm_source into one field on the first visit. Then map every variant to one engine name, so chatgpt.com and chat.openai.com both read ChatGPT. Add a date to each rule, because engines change how they send traffic.
How to deduplicate AI referral attribution
One click can carry both a referrer and a tag. Count it once per session, and prefer the tag when both arrive. Do not add referral visits and tagged visits together. Keep the engine map in one place so your reports agree.