The visitors who clicked through to your site from an assistant — sessions, new users, engagement rate and key events. A real visit, attributable like any other channel.
Feature
See exactly how many people arrive from ChatGPT, Copilot, Perplexity and the rest, and what they do next. Grouped into one channel from your own GA4 data, which GA4 won't do on its own.
Share of sessions
4.2%
of 322,140 attributed sessions
AI sessions
13,533
vs 8,254 last period
Assistants sending
4 / 13
tracked assistants
AI sessions over time 13,533 in this period
| Assistant | Sessions | New users | Engagement rate | Key events |
|---|---|---|---|---|
| ChatGPT | 10,241+38% | 7,904 | 57% | 214 |
| Claude | 1,422+133% | 1,090 | 61% | 38 |
| Perplexity | 1,085+33% | 812 | 49% | 21 |
| Gemini | 785+12% | 640 | 45% | 9 |
| Copilot | 0 | — | — | — |
What you get
Assistant referrals land in GA4 scattered across hostnames. This groups them, then reports each one properly.
What proportion of your attributed traffic came from an assistant, so a small channel is still a number you can act on.
The trend across the period, against the previous one, so you can see whether the channel is actually growing.
Sessions, new users, engagement rate and key events for each assistant, side by side rather than lumped into referral traffic.
How many of the tracked assistants actually sent anyone, the ones on zero are shown too, not quietly dropped.
Engagement rate and key events per assistant, so twenty visits that convert don't read the same as twenty that bounce.
Attribution comes from your Analytics property. No tag to install, no sampling, and nothing estimated on your behalf.
Assistants tracked
The others bucket catches emerging tools like You.com, Poe, Phind and Mistral. An assistant that sent nothing still appears at zero, so you can tell no traffic apart from not tracked.
Setup
This reads the GA4 property you already own. No tag to install, no snippet, no change to how your pages load.
Sign in and pick the GA4 property you already report on. Read-only, and there is no tag, snippet or code to add to your site.
AI traffic · one channel
GA4 scatters them across hostnames, so the traffic is real but the total never is. Each one is matched to the assistant it belongs to — 13 of them, tracked by name.
Assistant
Sessions, new users, engagement rate and key events, per assistant and over time — and the same figures drop straight into a client report.
Read-only access to the property you choose.
In the report
How much is arriving, where it lands, and whether it is growing — each read from your own GA4 property, so the numbers match the ones you already report.
AI sessions
13,533
By assistant
GA4 files assistant referrals under a dozen different hostnames, so the traffic is real but the total never is. Each one is matched to the assistant it belongs to and reported together, with an assistant that sent nothing shown at zero rather than left out.
Landing pages
Where assistant referrals arrive
| Page | Sessions | Engaged |
|---|---|---|
| /pricing | 3,940 | 71% |
| /rank-tracker | 2,180 | 64% |
| /blog/ai-search | 1,905 | 58% |
| /integrations | 742 | 49% |
An assistant does not send traffic to your homepage. Landing pages are broken out with sessions and engagement side by side, so a page that pulls visitors and a page that keeps them are told apart rather than averaged together.
AI sessions over time
+64%vs previous 30 days
AI referrals are small enough that a single week says nothing. The series runs over your chosen range against the period before it, so a rise is a trend you can show a client rather than a good Tuesday.
Worth separating
Two different questions. Most brands need both answers, and confusing them leads to the wrong conclusion.
The visitors who clicked through to your site from an assistant — sessions, new users, engagement rate and key events. A real visit, attributable like any other channel.
Whether an assistant named or cited you at all. Most of those answers end without a click, so nothing about them ever reaches analytics — the only way to see it is to ask the questions and read the replies.
Easy Fetcher answers both, on the same account — so a quiet month in analytics and a strong month in AI answers are two findings, not a contradiction.
Questions
It reads your Google Analytics 4 property and attributes sessions whose referral source is an AI assistant, then groups them into a channel of their own. There is no extra tag to install, if GA4 already recorded the visit, Easy Fetcher can classify it.
Connect GA4 in about two minutes and see the channel broken out per assistant.
Get Started