AI traffic analytics

AI traffic analytics: track what AI answers send you

AI answers send visits that Search Console never labels and GA4 often undercounts. This console records AI referral clicks per landing page, keeps them separate from AI Overview clicks, and joins both with GA4 sessions and crawler activity — with the attribution limits stated.

Last reviewed 2026-11-13

Open the console See the AI Overview tracker

Referral analytics needs the probe or page beacon; both plans include it — see pricing.

AI traffic analytics: three channels, three methods

They arrive through different paths and need different evidence. Mixing them into one “AI traffic” number is how a report ends up describing nothing.

AI referral visits

A visit whose referrer is an AI surface: chatgpt.com, perplexity.ai, copilot.microsoft.com and similar. The probe or page beacon records the referrer and the landing page, so the count is first-party rather than inferred from a channel grouping.

How telemetry works

AI Overview clicks

A click from a Google result page that showed an AI Overview. Google does not label these clicks, so the console compares clicks on queries where an AI Overview cited you against queries where it did not — an impact estimate, not a per-click label.

How the comparison works

AI crawler fetches

Not traffic, but the supply side of it: which agents fetched which paths, what they read and what was blocked. A crawler that cannot fetch a page cannot send a visit from it later.

Browse the crawler directory

How to track AI referral traffic in Google Analytics

GA4 can show AI referrals, but only after you tell it what counts. The steps below are the shortest path to a number you can defend; the caveats are part of the number.

Step 1
Start from GA4's default grouping
GA4 puts most AI referrers into Referral or Organic Search. A custom channel group can match session source against the AI domains you care about, but it only sees referrals that actually arrive.
Step 2
Check the landing-page report
Segment by landing page before drawing conclusions. A drop in total AI referrals usually means one page lost its referrer or one assistant changed how it links out.
Step 3
Compare with first-party records
The probe and beacon capture the referrer before analytics tooling can reclassify or sample it. When GA4 and the console disagree, the first-party record is the floor and the difference is usually stripping or sampling.
Step 4
Join sessions to outcomes
Use the per-page join — clicks, sessions, AI fetches, AI visits and open findings — to see whether the pages AI answers send people to are also the pages that convert.

How to check AI traffic by landing page

Open the traffic report, filter to AI referrals and group by landing page. Each row keeps the page path, visit count, referrer domain and the window that was read. Sort by visits to find the pages AI answers actually send people to, then compare the same paths against GA4's landing-page report.

When a page has first-party referrals but no GA4 session, suspect referrer stripping, a redirect chain or a consent banner. The first-party record is the floor, not the total. Put the next fix on a page that already has demand: compare its AI visits with open findings and crawler fetch health in the same report. The telemetry guide covers installation.

What the report shows

Four channels, each with its own source and window. The report keeps them separate so a referrer outage cannot look like a citation loss.

AI traffic channels, their sources, windows and limits
Channel	Source	Window	Limit
AI referral visit	Server probe or page beacon	Visit window, by landing page	Referrer stripping and privacy browsers make this a floor.
AI Overview click impact	Search Console plus AI Overview samples	Last 28 days vs previous 28	An estimate from cited vs non-cited queries, not a per-click label.
Crawler fetch	Server probe or CDN logs	Rolling window, by agent and path	Proves access, not that an answer sent a visit.
GA4 session	GA4 property	Your selected date range	Thresholding and sampling can hide small AI segments.

AI referrals by landing page

Traffic · 28-day window

/guides/ai-overviews148 visits · top referrer chatgpt.com
Pass
/pricing41 visits · top referrer perplexity.ai
Warn
/blog/ai-brand-mentions12 visits · referrer stripped
N/A

Sample data. Referrer stripped = floor, not total.

Attribution limits, stated up front

Every number below is a floor with a known blind spot. The console reports them separately instead of summing them into a total that looks more certain than it is.

Referrer stripping. Apps and privacy browsers can drop the referrer entirely, so AI referral counts are a floor, not a total.
No click-level AI Overview label. Google reports the click like any other search click; the console estimates impact by comparing cited and non-cited queries.
GA4 thresholds and sampling. Small AI segments can be hidden by thresholding, which is why the report states its window and source.
No user-level attribution. The console joins by landing page and session, never by person, and it does not claim to know which answer convinced a visitor.

Frequently asked questions

Definitions

What is AI traffic analytics?

It is the measurement of visits that arrive from AI surfaces and of the crawler activity that makes those visits possible: AI referral clicks, landing pages, sessions, crawler fetches and blocked paths. It is not a count of AI mentions.

Is AI Overview traffic different from AI referral traffic?

Yes. An AI Overview click arrives from a Google results page and looks like ordinary search traffic. An AI referral visit arrives from an assistant or AI app with its own referrer. The console measures them with separate methods.

GA4 & attribution

How do I track AI referral traffic in Google Analytics?

Create a custom channel group in GA4 that matches session source against AI domains, then read it by landing page. Expect undercounting: referrers get stripped and small segments get thresholded. Pair it with a first-party record if you need a reliable floor.

Can I attribute traffic from ChatGPT or Perplexity?

Partially. When the referrer survives, the console records the visit and the landing page, so page-level attribution works. It cannot tell you which answer or which user, and it cannot recover a visit whose referrer was stripped.

Does Search Console show AI traffic?

Search Console shows clicks, impressions and position for queries; it does not label a click as coming from an AI Overview. The AI click impact report works around that by comparing cited and non-cited queries over the same window.

What to do next

What should I do with AI traffic data?

Fix the pages that already earn AI referrals, check that their crawler access still passes, and compare their conversion behaviour with the rest of the site. Traffic without a next action is just a chart.

Measure the visit, not the guess

See what AI answers send your way

Install the probe or page beacon to record AI referral visits and their landing pages.