AI Visibility · 19 July 2026

By Eddie Eastwood, Founder

How to Measure AI-Search ROI: A GA4 and Attribution Guide

The GA4 "Direct" spike nobody ordered

You open Google Analytics on a Monday. Direct traffic is up, noticeably, and you did not run a campaign, print a flyer, or buy an ad. Nothing obvious explains it. A month ago you would have shrugged and moved on. Now you have a suspicion: an AI assistant recommended you, someone tapped through, and the visit arrived with no label attached.

That suspicion is usually right, and the reason it is hard to prove is baked into how analytics tools attribute traffic. This guide walks through what is actually happening, how to see as much of it as the tools allow, and which numbers are worth watching once you can.

Why AI traffic hides in Direct

Google Analytics files a visit as "(direct) / (none)" when it cannot see a clear referral source. Google's own documentation is plain about the causes: "When links to your site lack UTM parameters ... traffic source information is lost," redirects "can strip UTM parameters from the URL," and traffic from "users who visit your website by entering the URL directly ... or through links from offline documents such as PDFs" is classified as direct.^[4] Ad blockers add more of the same.

AI assistants trip several of these at once. Many answer surfaces open links in a way that passes little or no referrer, and few carry campaign tags. So a genuine AI-driven visit frequently arrives looking like someone who typed your address from memory.

This is not a theory. In a study of 3,000 websites, Ahrefs found that 63% of sites receive AI traffic, then added the caveat directly: "some AI traffic will pull through as 'direct' ... this data represents just the visible AI traffic, the minimum amount of AI visitors a website receives."^[1] In other words, whatever you can measure is the floor. The real figure is higher. That single fact reframes the whole exercise: you are not trying to capture every AI visit, you are trying to see enough of the pattern to act on it.

The channel that finally names it: GA4 "AI Assistants"

There is good news for anyone starting this now. Google has added a dedicated default channel for exactly this traffic. Per Google's channel documentation, "AI Assistants is the channel by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok."^[3]

One detail matters enormously and is easy to miss: that same doc states the AI Assistants channel "excludes Google's AI Overviews and AI Mode."^[3] So a click from Google's own AI answer does not land here, it behaves like other Google traffic. The AI Assistants channel captures the standalone assistants, not the AI answers stitched into Google Search. Read your reports with that boundary in mind or you will undercount one and misread the other.

Because it is a default channel group, it applies automatically, with nothing to configure. If you are on an older setup or a custom channel group, this is the moment to check that the AI Assistants channel exists and is not being folded into "Unassigned".

What you can see, and what you can't

Even outside the tidy channel, the assistants that do pass a referrer show up under recognisable hostnames. In your GA4 acquisition reports, filter Session source for values such as chatgpt.com, perplexity.ai, gemini.google.com and copilot.microsoft.com. Those are your confirmed, attributable AI visits.

Everything else, the portion that arrives unlabelled, is the part you infer rather than see. A practical way to sense its scale: watch whether your Direct traffic climbs at the same time your visible AI referrals climb, and whether Direct visitors are landing on deep, specific pages (a single service page, a pricing page) rather than your homepage. People who type your address from memory tend to hit the homepage. People sent by an assistant tend to arrive deep, on the exact page the answer pointed at.

The metrics that replace rankings

The hardest mental shift is not technical, it is deciding what "good" looks like. Ranking position, impressions and click volume were the currency of search. AEO runs on different signals, because an AI recommendation is a smaller number of far warmer visits. Judge it accordingly.

That last row is the point of the whole channel. Semrush's study of over 500 high-value topics found that "the average AI search visitor ... is 4.4 times as valuable as the average visit from traditional organic search, based on conversion rate."^[5] The logic is intuitive: by the time an assistant sends someone to you, it has already answered their questions and compared their options, so they arrive close to a decision. A handful of AI visits can outperform a flood of cold search clicks. Counting raw volume alone will make a genuinely valuable channel look trivial.

Setting it up in GA4, step by step

None of this needs a new tool. Five moves in the analytics you already run turn the guesswork into a repeatable read.

1. Confirm the AI Assistants channel is live. In Reports > Acquisition > Traffic acquisition, set the dimension to Session default channel group and look for "AI Assistants". If it is missing, you are on an older channel grouping, update it.
2. Build an AI referral view. Add a comparison or filter for Session source matching the AI hostnames above. This is your visible-AI baseline, the floor.
3. Tag every link you control. The assistants you cannot fix, but your own newsletters, profiles and PDF documents can carry UTM parameters so they stop dumping into Direct and muddying the signal. Cleaner Direct means a clearer read on the AI-driven portion.
4. Mark your key events. Make enquiries, calls, bookings and form submissions into GA4 key events, so you can measure conversions per AI visit, not just visit counts.
5. Watch Direct as a paired signal. Track Direct alongside your visible AI referrals over time. Correlated rises, especially onto deep pages, are your best proxy for the AI traffic the tools cannot label.

Keep the scale realistic

Set expectations before you read the first report, or a real channel will look like a rounding error. Across roughly 35,000 sites, Ahrefs found AI still sends "just 0.1% of total referral traffic," and that smaller sites see more of it: "Sites receiving under 10K visits can now expect 0.3% of their traffic to come from LLMs, vs. 0.1% for those exceeding 1 million visits."^[2] Among the AI sources, ChatGPT is dominant, "accounting for 50% of AI traffic".^[1]

So the volume is small today and growing. The value per visit is high. That combination is precisely why you measure it now: to catch the trend while it is cheap to act on, and to prove the return before it becomes obvious to everyone. If you want the wider context on why so much search now ends without a click at all, our piece on the zero-click search era and the breakdown of how often Google answers with AI both set the scene.

A quick self-check you can run today

You do not need a new tool to start. Open GA4 and answer three questions:

• Is there an AI Assistants channel with any sessions in it over the last 90 days?
• When you filter Session source to the AI hostnames, are those visitors landing on deep service or pricing pages, and converting at a healthy rate?
• Has Direct risen in a way your own campaigns do not explain, onto those same deep pages?

Three yeses mean AI is already sending you business, and you now have the floor figure to build on. For the broader question of whether the assistants are naming you in the first place, our guide to tracking AI mentions of your business covers the free checks, and ChatGPT versus Google organic traffic unpacks why the two channels behave so differently in your reports.

Where a website check fits

Measuring the traffic tells you what is landing. It does not tell you whether your site is built so the assistants can read, understand and quote you in the first place, which is what decides how much of that traffic you earn.

That is the gap a QBiz Leads AI visibility check fills. It scans your own website, the structure, schema, clarity and machine-legibility that decide whether an AI system can parse and cite you, and returns a plain pass or fail on those signals. It does not query ChatGPT, Gemini or Perplexity on your behalf, and it does not tell you whether you are currently named. It tells you whether your website is readable to the machines doing the naming, which is the part you can actually fix. Pair a clean scan with the GA4 setup above and you can both improve your machine-readiness and watch the measurable return follow.

Get your AI Visibility audit →

Frequently asked questions

Why does my AI traffic show up as Direct in GA4?

Because the assistant often passes no clear referral source. Google classifies a visit as "(direct) / (none)" when links lack UTM parameters, when redirects strip them, or when someone arrives without a trackable referrer. Many AI answer links do exactly that, so a genuine AI visit arrives unlabelled and lands in Direct.

Is there a proper AI channel in Google Analytics?

Yes. GA4 now has a default AI Assistants channel that captures arrivals from sources like ChatGPT, Gemini, Deepseek, Copilot and Grok. Note that it excludes Google's own AI Overviews and AI Mode, which behave like other Google traffic.

How much traffic should I realistically expect from AI?

Not much by volume yet. Independent analysis of around 35,000 sites put AI at roughly 0.1% of total referral traffic, rising to about 0.3% for smaller sites. The value per visit is the point: AI-referred visitors have been measured converting several times better than ordinary organic ones.

Which metrics should replace rankings for AEO?

Stop leading with keyword position and raw click volume. Watch visible AI referrals, movement in Direct onto deep pages, engagement rate on the landing page, and above all conversions per AI visit. AI sends fewer, warmer visits, so value beats volume.

Can I see exactly which AI recommended me?

Only partially. You can attribute the visits that arrive under known AI hostnames or the AI Assistants channel. The share that comes through unlabelled can only be inferred, usually by watching Direct rise in step with your visible AI referrals.