How to Track ChatGPT and AI Referral Traffic in GA4
To track AI traffic in GA4, open Traffic acquisition and use Session default channel group to find AI Assistant visits, then add Session source for detail. Review ChatGPT referrals and key events separately. Google AI Overviews and AI Mode stay under Organic Search, so compare trends without treating referrals as proof of rankings or sales.
Open Traffic acquisition
In GA4, choose Reports, Acquisition, then Traffic acquisition. Set the date range you want to review and note whether the period is complete.
Select the AI Assistant channel
Use Session default channel group and find AI Assistant. Current GA4 properties classify recognized assistant referrals here automatically, so start with the native channel.
Add the source detail
Add or switch to Session source to separate chatgpt.com and other recognized sources. Preserve the channel view so source rows still have their reporting context.
Compare meaningful actions
Add the key events your business already measures, compare consistent periods, annotate site or campaign changes, and report small counts plainly without claiming the source caused them.
Where is AI Assistant traffic in GA4?
Google Analytics added AI Assistant to its Default Channel Group on May 13, 2026. Recognized referrals from sources such as ChatGPT, Gemini, DeepSeek, Copilot, and Grok can receive the ai-assistant medium and the AI Assistant channel automatically.
Start with Session default channel group in Traffic acquisition. You do not need a custom channel for the normal current view; a custom definition is useful only when your reporting needs differ and you document the consequence.
How do you see ChatGPT referral traffic separately?
Add Session source and look for chatgpt.com within AI Assistant. OpenAI says ChatGPT search referral links include utm_source=chatgpt.com, which can make inbound visits easier to identify when the referral data reaches your analytics setup.
Keep source and medium together when troubleshooting. Privacy choices, apps, redirects, browser behavior, consent settings, tag configuration, and missing referral information can all affect what GA4 receives.
Where do Google AI Overviews and AI Mode appear?
GA4 explicitly excludes Google AI Overviews and AI Mode from AI Assistant. Their visits remain in Organic Search, so do not move all Google organic traffic into an AI bucket.
The default channel alone cannot separate those generative Google experiences from other Google organic visits. Use Google's own Search reporting where available and describe its scope rather than estimating an AI-only split from GA4.
What does a simple GA4 example look like?
This is fictional data for Aster & Vale, not RankEcho customer data or a benchmark. In the example period, four recognized assistant sources total 36 sessions and five key events. The separate Google Organic Search row is not shown because it cannot identify AI Overviews or AI Mode on its own.
| Source and landing page | Sessions | Key events |
|---|---|---|
| chatgpt.com → /products/trailbottle | 18 | 3 |
| gemini.google.com → /guides/choose-a-hiking-bottle | 8 | 1 |
| copilot.microsoft.com → /products/trailbottle | 6 | 0 |
| grok.com → /compare/trailbottle-vs-steel-flask | 4 | 1 |
How should you compare AI traffic and key events?
Choose comparable date ranges, keep channel definitions stable, and annotate launches, campaigns, consent changes, tagging changes, outages, and seasonality. Report sessions, users, landing pages, and the few key events that represent meaningful actions for your business.
Google requires an interaction to be measured as an event and marked as a key event before it appears that way in reports. A key-event count describes recorded activity; it does not identify why the person arrived or what persuaded them to act.
What this can't tell you
GA4 cannot observe an answer impression that produced no click, visits whose source information was unavailable, or every interaction inside an AI product. It also cannot use the default channel to isolate Google AI Overviews and AI Mode from other Google Organic Search visits.
A referral does not prove that your page ranked, was cited, was recommended, or caused a sale. Treat the report as one view of attributable site visits and measured actions, not a complete picture of AI visibility.
How can RankEcho complement GA4 after setup?
GA4 reports visits and on-site actions that reach your property. RankEcho's Proof Loop can organize selected prompt observations after a dated page change. Keep those records separate, align dates and landing pages where useful, and avoid treating correlation as causation.
Begin with the native GA4 report and your existing key events. Add a RankEcho workflow only when you also need a repeatable record of selected AI-answer checks.
Frequently asked questions
Yes. Since May 13, 2026, GA4's Default Channel Group includes AI Assistant for recognized assistant referrals. Use Session default channel group to find it.
Open Traffic acquisition, choose AI Assistant under Session default channel group, and add Session source. Look for chatgpt.com while keeping your date range and reporting scope clear.
No. GA4 excludes Google AI Overviews and AI Mode from AI Assistant; those visits remain under Organic Search and cannot be isolated from that default channel alone.
Not for the standard current view of recognized sources. Use the native AI Assistant channel first. Create a custom channel only for a documented reporting need that the default definition does not meet.
No. GA4 records attributable visits and on-site events, not the complete answer that preceded a click. A referral row does not prove an impression, citation, ranking, or recommendation.
Sources reviewed
Material technical claims below were checked against primary provider documentation. The sources support the documented control or signal, not a guarantee of indexing, ranking, an AI impression, or a citation.
4 claim-level source records
| Claim reviewed | Official source | Review record |
|---|---|---|
| Google Analytics announced on May 13, 2026 that recognized AI-assistant referrals can receive the ai-assistant medium, AI Assistant default channel, and (ai-assistant) campaign values automatically. | Google Analytics: What's new | Checked 2026-09-07 · Google Analytics release note dated May 13, 2026 · This first-party release note supports using the native AI Assistant channel in a current property. It does not show that every AI visit retains a referrer, classify historical rows retroactively, or attribute a visit, key event, sale, or other outcome to an answer appearance. · Confidence: High |
| Google Analytics defines AI Assistant for recognized sources such as ChatGPT, Gemini, DeepSeek, Copilot, and Grok; it excludes Google AI Overviews and AI Mode, which remain in Organic Search. | Google Analytics: default channel group | Checked 2026-09-07 · Current Google Analytics default-channel definitions · This first-party definition supports the channel split shown in the guide. It does not let an analyst separate Google AI Overview or AI Mode clicks from other Organic Search rows, identify visits without usable attribution data, or establish why a person clicked. · Confidence: High |
| Google Analytics documents that an important user interaction must first be measured as an event and then marked as a key event before it can be reported as a key event. | Google Analytics: mark events as key events | Checked 2026-09-07 · Current Google Analytics key-event documentation · This first-party documentation supports comparing a declared business action alongside traffic. It does not define which action matters for a particular business or establish that a referring source, page change, search answer, or RankEcho caused that action. · Confidence: High |
| OpenAI says referral links from ChatGPT search automatically include utm_source=chatgpt.com and can be reviewed in analytics platforms such as Google Analytics. | OpenAI Help: publishers and developers FAQ | Checked 2026-09-07 · Current OpenAI publisher documentation · This first-party note supports checking ChatGPT referral detail and its UTM source. It does not imply that every ChatGPT interaction produces a visit, that every visit is attributable, or that a referral proves a ranking, citation, recommendation, conversion, or sale. · Confidence: High |