The AI visibility KPIs worth reporting to a CMO
Five metrics that survive contact with an exec, three that get you laughed out of the room, and the one-slide monthly format that makes AI visibility a budget line instead of a curiosity.
The short answer
Report five AI visibility KPIs: mention rate, Share of Voice against named competitors, average citation position, sentiment of mentions, and prompt coverage across buyer stages. Skip the vanity metrics, which are raw mention counts, "AI visibility scores" no one can reproduce, and prompted brand recall. The monthly slide is one chart of Share of Voice over time with competitors on it, one number that changed, and one decision you want the CMO to make.
Contents
- The five KPIs that survive an exec meeting
- Mention rate
- Share of Voice against named competitors
- Average citation position
- Sentiment of mentions
- Prompt coverage by buyer stage
- The KPIs to leave out
- The monthly slide
- Cadence, and why weekly reporting to execs is a mistake
- Making the business case in one paragraph
- Building the report without a full-time analyst
- What to do next
A CMO does not want an AI visibility dashboard. They want to know whether the company is being recommended, whether that's improving, who's beating them, and what it costs to fix. Five metrics answer that. Most AI visibility reporting fails not because the data is bad but because it hands an exec twelve numbers and no decision.
The five KPIs that survive an exec meeting
Mention rate
What it is: the percentage of your tracked prompts where your brand appears at all, averaged across runs.
Why it earns a slot: it's the simplest possible read on presence. If it's 12%, you are effectively absent from AI answers in your category, and nothing else on the slide matters until that changes.
How to compute it: appearances / total prompt-runs. If your 25 prompts run three times each on four engines, that's 300 prompt-runs. Appear in 96 of them and your mention rate is 32%.
How it gets abused: reported as a single blended number across engines, hiding the fact that you're at 60% in ChatGPT and 4% in Perplexity. Report it per engine.
Share of Voice against named competitors
What it is: your appearances as a fraction of all brand appearances on the same prompt set.
Why it's the headline metric: it's the only one that answers "are we winning." Mention rate can climb 13 points while Share of Voice moves 1.7, because everyone else got more visible too. That divergence is invisible unless you track both, and it's the difference between a real gain and a rising tide. The full arithmetic, and the four ways people inflate the number, is in the Share of Voice breakdown.
How to present it: a line chart, you and your top four competitors, monthly, over at least six months. This is the chart. If you make one slide, make this one.
Average citation position
What it is: where your brand lands in the answer when it does appear. First brand named, third, seventh.
Why it matters: appearing seventh in a list of nine is not appearing. Buyers read the first two or three names and stop, exactly as they do with search results. Two brands at identical Share of Voice can have completely different commercial outcomes if one is consistently named first.
How to present it: average rank, with the percentage of appearances that are in the top three. "We appear in 40% of prompts, and 62% of those appearances are top-three" is a sentence a CMO understands instantly.
Sentiment of mentions
What it is: the split of your appearances into positive, neutral and negative framing.
Why it matters more than people expect: an AI engine saying "Acme is popular but users report frequent outages" is a negative mention delivered in the neutral register of an authoritative assistant. That does more damage than a bad review, because it doesn't read like an opinion. It reads like a fact the machine looked up.
How to present it: percentage of mentions that are non-positive, plus the actual sentence when it's bad. Show the sentence. Nothing focuses a leadership team like reading the exact words the model uses about them.
Prompt coverage by buyer stage
What it is: your mention rate broken out by prompt archetype: category, comparison, alternatives, problem-led, jobs-to-be-done.
Why it's on the list: it turns a metric into a roadmap. It's the difference between "we're at 32%" and "we're at 55% on category questions and 8% on alternatives questions, which is where deals are decided." The second version tells the CMO what to fund.
How to present it: a five-row table with your rate and your best competitor's rate per archetype. The rows where you're behind are your budget request. Building the archetype split is a function of how you constructed your prompt set, so if the set isn't right, this KPI can't be either.
The KPIs to leave out
| Vanity metric | Why it fails | Report this instead |
|---|---|---|
| Raw mention count | Grows when engines get more verbose, not when you get more visible. A rising line that means nothing | Share of Voice |
| Composite "AI Visibility Score" (0-100) | Usually a vendor's unpublished weighted blend. Not reproducible, not auditable, moves for reasons nobody can explain | The four or five underlying metrics, shown separately |
| Prompted brand recall ("what do you know about Acme?") | You put the name in the prompt. The model describing it back is not visibility | Unprompted mention rate on category questions |
| Number of prompts tracked | An input, not an outcome. Tracking 500 prompts badly is worse than 25 well | Prompt coverage by buyer stage |
| AI referral sessions, reported alone | Only ~1% of users click a link inside an AI summary. Session count wildly understates impact and gets the channel defunded | Conversion rate and revenue per AI session |
| "We rank #1 in ChatGPT" (from one query, one day) | Non-deterministic output. One run is a coin flip | Mention rate across repeated runs |
The referral-sessions one deserves a moment, because it's the trap most likely to kill an AI visibility program. Pew Research found only 8% of users click any result when an AI summary is shown, versus 15% without, and just 1% click a link inside the summary. If you walk into a QBR and lead with "AI sent us 340 sessions," someone will correctly observe that 340 sessions is nothing and cut the budget. What you should say is that 340 clicks, at roughly a 1% click-through from AI answers, implies your brand was read in AI answers a very large number of times, and that the sessions you did get convert far better than average. Measuring the click side properly in GA4 is worth doing. Leading with it is not.
The monthly slide
One slide. Four elements. In this order.
1. The chart. Share of Voice over time, you plus your top four competitors, last six months. Y-axis in percent, starting at zero. No dual axes, no stacked areas. If a competitor crossed you, the crossing point is the most important pixel on the slide and should be annotated.
2. The one number that changed. A single sentence at the top: "Share of Voice went from 15% to 19% this month, and we passed Cinder for the first time." Not five numbers. One, with its cause.
3. The gap table. Five rows, one per prompt archetype, three columns: your mention rate, best competitor's mention rate, delta. This is where the CMO's eyes will actually stop, because it's the only part of the slide that implies an action.
4. The ask. One decision. "We're at 8% on alternatives queries against Bolt's 61%. We need four comparison pages and three third-party placements. That's one writer for six weeks." AI visibility reporting that ends without an ask is a hobby.
What does not go on the slide: engine-by-engine breakdowns (appendix), the prompt list (appendix), screenshots of AI answers (one, maybe, if it's damaging enough to be a wake-up call), and any metric you can't explain in one sentence.
Cadence, and why weekly reporting to execs is a mistake
Measure weekly. Report monthly.
Weekly measurement is right for the team doing the work, because engine outputs drift and you want to catch real movement inside a sprint rather than a month later. But weekly exec reporting takes normal sampling variance and turns it into a fire drill. Your Share of Voice will bounce 2-3 points week to week for reasons that have nothing to do with anything you did. A CMO seeing that bounce every Monday will either learn to ignore the report or start asking you to explain noise. Both outcomes are bad.
Monthly is the right exec cadence. Quarterly is too slow, because AI engines change faster than that: Google AI Overviews expanded to ~48% of tracked queries, up 58% year over year, and ChatGPT referral traffic jumped 157.7% in a single week after one product change. A quarterly report would have missed both while they were still actionable.
Making the business case in one paragraph
If you need to justify the program itself, not just report on it, the case is short.
51% of B2B software buyers now start research in an AI chatbot, up from 29%. 69% chose a different vendor than the one they'd planned on, based on AI guidance, and 33% bought from a vendor they'd never heard of before the AI named it (G2, 1,076 decision-makers). The traffic that does arrive from AI converts at 4.4x the value of an organic search visitor. And the shortlist is being assembled in a place your existing analytics stack cannot see.
That's the argument. Not "AI is the future." Just: the shortlist is being written somewhere you're not measuring, and a third of buyers are choosing vendors they'd never heard of, on the strength of a paragraph you didn't write.
Building the report without a full-time analyst
The mechanical work, running 25 prompts across four engines multiple times a week in clean sessions, storing the responses, computing rates and Share of Voice, is exactly the kind of thing you should not be doing by hand, and exactly the kind of thing that quietly stops happening in month two when the person who owned the spreadsheet gets busy.
Spottlo produces the five KPIs above on a weekly cycle across ChatGPT, Perplexity, Gemini and Google AI Overviews, with all four engines on every plan. That last detail matters for this specific use case: most tools in the category gate engines behind higher tiers, and a per-engine KPI breakdown is impossible if you can only afford to see one engine.
What to do next
- Delete the composite score from your current reporting, whatever tool produced it. If you can't reproduce the formula on a whiteboard, don't put it in front of a CMO.
- Build the Share of Voice chart with your four real competitors on it, going back as far as your data allows. That's your slide.
- Split mention rate by prompt archetype and find the row where you're furthest behind. That's your ask.
- Add negative-mention rate to your tracking, and read the actual sentences. There is usually one that will change someone's mind about funding this.
- Get a baseline scan and put a date on it. Every KPI on this list is a trendline, and a trendline needs a first point.
Frequently asked questions
What is the single most important AI visibility metric? +
Share of Voice against your named competitors, on a fixed prompt set. It's the only metric that captures both whether you appear and whether you're winning. Mention rate alone can rise while you lose ground, if the engines simply started listing more brands per answer.
Which AI visibility metrics are vanity metrics? +
Raw mention counts, because they grow when engines get more verbose rather than when you get more visible. Composite 'AI visibility scores' whose formula the vendor won't publish, because they're not auditable and can't be reproduced. And prompted brand recall, where you ask the model about your brand by name and it obligingly describes it. That last one measures nothing at all.
How often should AI visibility be reported to leadership? +
Monthly to the CMO, weekly to the team that owns the work. Weekly data is the right cadence for detecting real movement, but exec reporting at that frequency turns sampling noise into fire drills. Give leadership the monthly trendline and keep the weekly detail for the people who can act on it.
How do I show ROI on AI visibility work? +
Pair visibility with the AI traffic that does convert. Semrush found an AI-search visitor is 4.4x as valuable as an organic search visitor by conversion rate, and Adobe measured AI-referred retail traffic converting 54% better than non-AI traffic. Show Share of Voice as the leading indicator and revenue per AI session as the lagging one.
Should I report AI visibility per engine or as one blended number? +
Per engine, with a blended headline only if you state the weights. Engines disagree substantially, and a blended average hides the case where one engine carries your entire result. If a CMO only has room for one number, give them Share of Voice on the engine where their buyers actually are, and footnote the others.
Keep reading
AI Share of Voice: how to actually calculate it
Most AI Share of Voice numbers are wrong because they count raw mentions. Here's the correct formula, a worked example with real arithmetic, and the four errors that inflate it.
How to measure AI search traffic in GA4
A copy-pasteable regex for AI referrals, the exact GA4 exploration setup, and an honest account of why the traffic you can see is a fraction of the visibility you're getting.
How to build a prompt set that reflects real buyers
Your AI visibility data is only as good as the questions you track. Here's how to build a 25-prompt set from sales calls and support tickets, with five archetypes and examples.