Metrivo

AI visibility vs AI revenue attribution

These get sold as the same thing and they are not. One measures whether an AI engine names you when a buyer asks. The other measures what happened to the people who arrived because it did. They break independently, they need different fixes, and confusing them is how founders spend a quarter on the wrong problem.

The short answer

AI visibility is measured by asking the engines questions and recording which brands they name. AI revenue attribution is measured on your own site, by joining a session that arrived from an AI engine to a confirmed payment. Visibility can be measured before you install anything; attribution cannot. Visibility cannot be turned into a revenue number; attribution can, but only for the visits that carried evidence.

Side by side

DimensionAI visibilityAI revenue attribution
Question answeredWhen a buyer asks an AI engine about this category, are we named?Of the people who arrived from an AI engine, how many became customers?
Where the data comes fromAsking the engines directly, on a schedule, with fixed buyer prompts.Your own sessions, referrers, UTM values, landing URLs, and payment events.
What one data point isA dated model observation: engine, model, prompt, answer, brands cited.A revenue path: source, session, signup, checkout, confirmed payment.
Unit of measurementCitation frequency, position in the answer, sentiment, share of voice.Sessions, conversion rate, attributed revenue, confidence label.
DeterminismNon-deterministic. The same prompt can return different answers between runs.Deterministic where evidence exists; explicitly unknown where it does not.
Works before the tracker is installedYes. It reads engines, not your traffic.No. It needs the tracking script and a connected payment provider.
Typical failure it exposesCompetitors are recommended and you are absent from the answer entirely.AI traffic arrives, then dies on the pricing page or in checkout.
What a bad result meansYou are not crawlable, not citable, or not making a checkable claim.Your funnel, pricing, or onboarding is losing people who already found you.
The honest limitA mention is influence, not a visit. It cannot be converted into a revenue number.Referrer-stripped AI visits stay 'unknown' rather than being credited to AI.
Where Metrivo does itAI Visibility: controlled prompt scans, citations, share of voice, crawler log.AI Search Attribution: AI referrer events joined to payment evidence.

The four states you can be in

Because the two measurements are independent, there are four combinations, and each one calls for completely different work. Getting the diagnosis right is worth more than any individual tactic.

Invisible and no traffic. You are not named in answers and almost no AI traffic arrives. Check crawler access before anything else. If GPTBot and PerplexityBot have never fetched the pages that would answer your buyers' questions, the problem is robots.txt, server-side rendering, or a signup wall, not your writing.

Visible but no traffic. Engines name you and almost nobody arrives. This is partly real and partly an illusion. Being mentioned in an answer does not guarantee a click, and many of the clicks you do get arrive with the referrer stripped, so they land in your direct bucket. Before concluding that citations are worthless, check whether direct traffic rose alongside your visibility trend.

Visible with traffic that does not convert. The engines send people and the funnel loses them. This is the most tractable state, because you have live sessions to inspect. Look at where the AI-referred cohort drops out compared with your other sources. AI-referred visitors often arrive with an expectation set by the answer they read, and a mismatch between that expectation and your landing page is a common cause.

Visible, converting, and growing. Now the work is defending the position. Track share of voice against named competitors, watch for sentiment slipping from recommended to merely mentioned, and keep the pages that earn citations accurate and current.

Why one number for both is a bad idea

It is tempting to combine mentions, traffic, and revenue into a single AI score. Resist it. The inputs have different reliability: a citation is a non-deterministic model output, a session is an observed fact, and a payment is a confirmed fact from a provider webhook. Averaging a guess with a fact produces a guess wearing a fact's clothing.

Worse, a composite hides the diagnosis. A score that drops could mean you lost citations, or that traffic fell, or that conversion dropped, or that a payment integration broke. Those need four different responses, and a single number tells you none of them. Metrivo keeps crawl access, citations, sentiment, AI sessions, and attributed revenue as separate readings for that reason.

The same logic applies to converting citations into estimated revenue. There is no defensible multiplier from "named in an answer" to "dollars." Click-through from generated answers varies enormously by question type and answer format, and nobody publishes reliable figures for your category. A model that invents one will be confidently wrong.

What most tools actually cover

The market splits cleanly. AI visibility monitors run prompts across engines and report mentions, sentiment, and share of voice. They are good at that and structurally blind to your funnel, because they have no tracking on your site and no connection to your payment provider. If you buy one, you will learn whether you are recommended and nothing about whether it pays.

Analytics and attribution tools work from the opposite end. They see sessions, referrers, and payments, so they can tell you what AI-referred visitors did, but they never ask an engine anything. If you buy one of those alone, you will optimise the conversion of whatever traffic you happen to get and never learn that a competitor is being recommended ahead of you.

Metrivo runs both halves and keeps them labelled. Read the AI Visibility page for how the prompt scans and crawler log work, and AI Search Attribution for how AI sessions are joined to payment evidence. The detection limits that apply to both are written out in AI traffic detection.

Frequently asked questions

What is the difference between AI visibility and AI revenue attribution?

AI visibility measures whether an AI engine names your product when a buyer asks a question in your category. It is measured by asking the engines directly with fixed prompts and recording which brands they cite. AI revenue attribution measures what happened to people who arrived on your site from an AI engine, and it is measured from your own sessions and payment events. Visibility is about being in the answer; attribution is about what the answer produced.

Which one should I measure first?

Measure visibility first if you have almost no AI-referred traffic, because that usually means you are not in the answers at all and attribution has nothing to work with. Measure attribution first if AI traffic is already arriving but you cannot tell whether it converts. In practice a visibility scan is cheaper to start because it needs no tracking script, so it is a reasonable first diagnostic either way.

Can I calculate revenue from AI visibility data?

No, and any tool that offers to should be treated with suspicion. A citation is a mention in a generated answer. It does not record whether a human read it, believed it, or clicked. Multiplying mentions by an assumed click-through rate and an assumed conversion rate produces a number with no evidence behind it. Metrivo keeps citation counts and attributed revenue as separate measurements for exactly this reason.

Why does AI traffic show up as direct instead of as a referral?

Because the referrer is frequently missing. People copy URLs out of AI answers into a new tab, mobile app-to-browser handoffs drop the referrer header, and privacy features strip it. When there is no referrer, no UTM value, and no other supporting evidence, the visit is genuinely unattributable, and Metrivo labels it unknown rather than assigning it to an AI source it cannot prove.

Do I need two separate tools for this?

Some vendors specialise in one side. AI visibility monitors track mentions and share of voice but have no view of your funnel or payments. Analytics tools track AI referrals and revenue but never ask the engines anything. Metrivo runs both and keeps them clearly separated, so a strong visibility trend with weak conversion reads as a funnel problem rather than getting averaged into a single misleading score.

If both look bad, which do I fix first?

Fix crawl access first, because everything else depends on it. If GPTBot, ClaudeBot, and PerplexityBot cannot reach the pages that would answer your buyers' questions, no content or funnel work will change the outcome. After that, fix visibility before conversion: a funnel improvement multiplies traffic you already have, and if you are absent from the answers there is very little to multiply.

Measure both, and keep them apart.

Your first visibility scan runs before the tracker is installed. Attribution starts once tracking and one payment path are connected. Seven-day trial, no card required.