Key takeaways
- A large share of AI-referred visits appear as Direct in GA4 because referrers are stripped or normalised away
- Custom channel groups for chatgpt.com, perplexity.ai, claude.ai, and gemini.google.com are the minimum viable fix
- Brand search growth in Google Search Console often correlates with AI visibility even when referral data is incomplete
- Pair GA4 with weekly citation monitoring — traffic proves visits; citations prove share of voice in answers
- Document baseline before GEO changes so you can show uplift at 60–90 days
Marketing teams invest in GEO without a reporting line — then leadership asks why AI traffic “does not show up.” Often it is showing up as Direct, or only partially attributed.
This guide is a practical GA4 setup for UK/EU marketing teams using Google Analytics 4 in 2026. No data science degree required.
Why AI Traffic Hides in Direct
Common causes:
- Referrer stripping in in-app browsers and privacy tools
- HTTPS → HTTP transitions dropping referrer headers
- UTM-less links from AI answers
- Misconfigured default channel grouping
~70%
of AI-referred sessions misclassified as Direct in typical GA4 setups before custom channel rules — industry rule of thumb
GEO practitioner reports, 2024–2026
Direct is not a strategy channel
A rising Direct line after a GEO project may be success, not failure. Re-segment before killing a programme.
Step 1 — Create an AI Referrals Channel Group
In GA4: Admin → Data display → Channel groups → Custom channel group.
Add channels (order matters — specific before generic):
| Channel name | Condition (session source) |
|---|---|
| AI - ChatGPT | contains chatgpt.com OR chat.openai.com |
| AI - Perplexity | contains perplexity.ai |
| AI - Claude | contains claude.ai |
| AI - Gemini | contains gemini.google.com |
| AI - Other | regex for other known AI referrers you discover |
Save and apply to explorations.
Step 2 — Baseline Exploration Report
Build a Free form exploration:
- Rows:
Session default channel group(or your custom AI group) - Values: Sessions, Engaged sessions, Conversions
- Filter: Last 90 days
Export a screenshot — this is your “before GEO” slide for internal decks.
Step 3 — Pair With Search Console Brand Queries
AI visibility often lifts brand search before referral data clean up. Track branded impressions and clicks in GSC alongside GA4.
Step 4 — Pair With Citation Monitoring
GA4 shows who arrived. Citation Alert shows whether you were named in the answer for commercial keywords.
Track citations while GA4 tracks sessions
AI Citation Alert
ProWeekly digest · monitors ChatGPT, Claude, Perplexity · Pro plan
Audit pages before claiming analytics gaps are content gaps
GEO Score Checker
30-second analysis · 9 signals · no account needed
What to Report Monthly (One Slide)
- AI channel sessions (total + by engine)
- AI channel conversion rate vs organic
- Top landing pages from AI referrals
- Citation rate on 3–5 monitored keywords
- One GEO fix shipped (page + signal improved)
When to Escalate to Done-for-You
If setup stalls on governance, tagging, or executive reporting, external help on GA4 + GEO implementation is often faster than another quarter of mislabeled Direct. See pricing for self-serve vs service.
Related reading
Frequently Asked Questions
Will this break existing reports? Custom channel groups add views; they do not delete default reporting.
Does consent mode affect AI attribution? Yes in EEA — document limitations in privacy policy; use modeled data where available.
How soon after GEO fixes will AI channels rise? Often 60–90 days for meaningful session volume; citations can appear earlier.
Do I need Google Tag Manager? Helpful for UTM discipline; not mandatory for referrer-based channel rules.