Feature

AI Traffic Analytics

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.

Your own GA4 data No extra tag to install Never uses AI credits

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

Sessions, new users, engagement rate and key events for each assistant
AssistantSessionsNew usersEngagement rateKey events
ChatGPT10,241+38%7,90457%214
Claude1,422+133%1,09061%38
Perplexity1,085+33%81249%21
Gemini785+12%64045%9
Copilot0

What you get

A channel of its own, not a line in referrals

Assistant referrals land in GA4 scattered across hostnames. This groups them, then reports each one properly.

Share of sessions

What proportion of your attributed traffic came from an assistant, so a small channel is still a number you can act on.

AI sessions over time

The trend across the period, against the previous one, so you can see whether the channel is actually growing.

Per-assistant breakdown

Sessions, new users, engagement rate and key events for each assistant, side by side rather than lumped into referral traffic.

Assistants sending

How many of the tracked assistants actually sent anyone, the ones on zero are shown too, not quietly dropped.

Quality, not just volume

Engagement rate and key events per assistant, so twenty visits that convert don't read the same as twenty that bounce.

Your own GA4 data

Attribution comes from your Analytics property. No tag to install, no sampling, and nothing estimated on your behalf.

Assistants tracked

ChatGPTCopilotPerplexityClaudeGeminiMeta AIGrok+ others

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

One connection, and nothing added to your site

This reads the GA4 property you already own. No tag to install, no snippet, no change to how your pages load.

  1. 1
    Read-only access

    Connect Google Analytics

    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.

  2. 2
    • chatgpt.com
    • copilot.microsoft
    • perplexity.ai

    AI traffic · one channel

    Assistant referrals get grouped

    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.

  3. 3

    Assistant

    • ChatGPT10,241
    • Claude1,422
    • Perplexity1,085

    Read it as one channel

    Sessions, new users, engagement rate and key events, per assistant and over time — and the same figures drop straight into a client report.

Connect Google Analytics

Read-only access to the property you choose.

In the report

Three questions your AI traffic has to answer

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

  • ChatGPT10,241
  • Claude1,422
  • Perplexity1,085
  • Gemini785

Every assistant, counted as one channel

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

PageSessionsEngaged
/pricing3,94071%
/rank-tracker2,18064%
/blog/ai-search1,90558%
/integrations74249%

The pages assistants actually send people to

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.

Today7D30D

AI sessions over time

+64%vs previous 30 days

Whether the channel is growing

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

AI traffic is not AI visibility

Two different questions. Most brands need both answers, and confusing them leads to the wrong conclusion.

You want to know“How many people actually came?”

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.

Read from your GA4 propertyAI Traffic
You also want to know“Were we even in the answer?”

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

AI traffic, answered

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.

Find out what the assistants are actually sending you.

Connect GA4 in about two minutes and see the channel broken out per assistant.

Get Started