The metrics on most client reports are the ones the client asked for, and they’re nearly all lagging. Revenue, sessions, conversions, rankings — every one of them measures something that has already finished happening, which means every report becomes an explanation of the past rather than a case for what to do next.
This covers what to stop reporting, what to report instead, and how to make the swap visible in a Data Studio report rather than just agreeing it’s a good idea.
Lagging KPIs measure results you can’t act on
A lagging KPI measures a result. Organic revenue, transactions, sessions, conversions, average order value. They’re the numbers the client cares about, and they belong on the report — that isn’t in question.
The problem is what happens when they’re the only thing on it, and it’s structural rather than aesthetic:
You can’t flip a switch to skyrocket performance in any of these metrics. There is no single action that you can do to improve organic traffic or to reduce bounce rates. It’s a combination of things.
So a report made entirely of lagging KPIs asks a question nobody can answer in the meeting. Worse, it puts you in what’s fairly called explaining mode — the first two or three months of any engagement spent saying “we haven’t seen changes yet, but we did this and this and this”. The dashboard has forced you into a defensive posture before the work has had time to land.
Leading KPIs measure the work you control
A leading KPI measures the work that produces the result. Pages published, issues fixed, links earned, pages submitted for indexing, load speed. They’re current rather than historical, and — this is the point — they’re yours.
Six reasons they belong on a client report, and only the first is obvious:
- You can show progress before results exist. Month one has no revenue story. It does have a work story.
- They’re directly controllable, so they’re honestly measurable. Nobody argues about whether a page was published.
- They aren’t sitting in GA4 waiting for you. You have to think about how to measure them — which sounds like a drawback and is actually the mechanism. A metric you had to construct is one both sides have agreed matters.
- They demonstrate expertise. Reporting the inputs shows you know what produces the outcome, rather than trying things and hoping traffic rises.
- They let you signpost what’s outside your control — clearly, in advance, rather than defensively afterwards.
- They let you pivot with evidence. Halfway through an initiative that isn’t moving the outcome, leading KPIs give you a data-backed way to say so and change course, instead of finishing it because it was in the plan.
You’ll also see these called input and output metrics, which is arguably the clearer pair — inputs are what you do, outputs are what happens. Same distinction either way.
Mapping input metrics to the output metrics they drive
The practical artefact is a sheet, per client, mapping each output metric to the inputs that actually drive it — with an owning team on both sides, yours and theirs.
| Input metrics (what we do) | Output metric (what happens) |
|---|---|
| Pages crawled · new pages created · pages submitted for indexing | Number of indexed pages |
| Load speed · number of HTTPS pages | Bounce rate |
| Mobile usability issues resolved | Engagement time for mobile users |
| Content published · digital PR placements · social amplification | Organic sessions |
Put the expected lag on the map as well as the pairing. An input that takes twelve weeks to show up in an output isn’t a failing input in week four, and writing that down at kick-off is what stops it being relitigated every month.
Build the map once per client, at the start. It becomes the spine of the reporting, the basis of the conversation about who owns what, and — when something doesn’t move — the map you use to work out why.
A vanity metric isn’t a category of metric, it is a missing comparison
The usual framing is a list: impressions are vanity, followers are vanity, page views are vanity. That framing is wrong, and it’s why the advice never changes anyone’s report.
A vanity metric is any metric reported without context. That’s a deliberately harsher claim than the conventional one — Nielsen Norman Group define a vanity metric as one that appears impressive without giving insight into true performance, which is closer to the list-based framing. Our version puts the fault in the reporting rather than in the metric. Impressions with a comparison, a denominator and a related metric beside them are useful. Revenue reported as a single number with nothing around it is a vanity metric, however serious it sounds.
The useful part is that Nielsen Norman Group’s three fixes for a context-free metric are each a Data Studio setting rather than a philosophy.
Context 1: a timeframe on every number
Every number gets a comparison. Set the Comparison date range on the chart’s Setup tab — previous period, or previous year for anything seasonal.
This is off by default, which is why so many reports ship without it. A number with no previous period is a fact, not information.
Context 2: a per-user or per-visit denominator
Totals grow because the audience grew. Rates tell you whether anything improved.
Build the rate as a calculated field rather than reporting the total: revenue per user rather than revenue, pages per session rather than pageviews, conversions per thousand sessions rather than conversions. It takes a minute and it changes what the number means.
Context 3: a ratio against a related metric
The strongest context is another metric. Spend beside conversions. Sessions beside conversion rate. Impressions beside clicks.
A combo chart with the second metric on the right axis does this — with the caveat that dual axes mislead easily, so label both and don’t read meaning into where the lines cross. choosing between a combo chart and the alternatives goes into when a second axis earns its place.
Seven metric swaps, and what changes in the Data Studio report
Concretely, what to report instead — and what changes in the report to make it visible.
| Instead of | Report | What you change |
|---|---|---|
| Impressions | Impressions with CTR beside them | Add CTR to the same chart; combo with a second axis |
| Total sessions | Sessions by channel, with a previous-period comparison | Comparison date range + a breakdown dimension |
| Pageviews | Pages per session, and engagement time | Calculated field for the rate |
| Total conversions | Conversion rate, and cost per conversion | Calculated field; add cost from the ads source |
| Follower count | Referral sessions from social, and their conversion rate | Swap the source — this one isn’t a chart change |
| Number of links earned | Links earned, plus referring domains to target pages | Filter to the pages the programme is actually about |
| Average position | Clicks and CTR for the same queries | Search Console, with position as a secondary metric |
Rankings aren’t a vanity metric, they’re a mis-audienced one
Position tracking gets called a vanity metric constantly, and that’s lazy. It’s genuinely useful — it’s a leading indicator of visibility and it’s the thing an SEO team works on daily.
The problem isn’t that it’s vain, it’s that it’s mis-audienced. It belongs on the specialist page, where somebody can act on it. On an executive summary it steers a conversation about revenue into a conversation about position four versus position six, which is a worse conversation and not one the executive can do anything about.
The general rule underneath: match the granularity to the reporting cycle. Daily-granularity data in a monthly report is noise wearing a chart.
Diagnosing a drop by walking back up the input/output chain
The real use of an input/output map is diagnosis. When an output metric drops, you don’t guess — you walk the chain.
Organic revenue is down. In order:
- Did the number of transactions fall, or did average order value fall?
- If transactions fell — did conversion rate change?
- If conversion rate held — did sessions change?
- If sessions fell — which channels caused it?
- Then the ones people forget: any change in stock? Any key products missing in the period? Any site errors while it was happening?
Repeat until you reach the input metric that explains it. That last step matters more than it looks — an e-commerce revenue drop caused by a stock-out isn’t a marketing failure, and a report that can’t distinguish the two will have you defending work that was fine.
The fix for that specific case is a reporting one: put stock on hand next to items sold, and the conversation resolves itself before it starts.
Interrogating a client goal before it becomes a reporting brief
The same thinking runs forwards. A client says they want a 20% increase in organic traffic. That’s fine as a starting point and useless as a brief.
Twenty per cent from where? Traffic from one market isn’t worth the same as traffic from another, and mobile traffic doesn’t behave like desktop. The refined version — “a 20% increase in organic traffic from the US, on mobile” — is a different project with different inputs: mobile usability fixes, a mobile UX pass, content aimed at that market, and possibly digital PR on the platforms that audience actually uses.
Do this at kick-off and the report almost writes itself, because you’ve already agreed what the inputs are.
Which metrics belong on an executive, channel or specialist page
Most disagreements about vanity metrics are actually disagreements about audience.
| Report | Leading KPIs | Lagging KPIs |
|---|---|---|
| Executive summary | One or two, framed as progress | Three or four, with comparisons |
| Channel or project page | The main event — this is where the work lives | The outcome that page is accountable for |
| Specialist page | Everything, at whatever granularity is useful | Secondary |
An executive doesn’t want your input metrics in detail, but they do want to know work is happening and what it’s aimed at. One line does that. The specialist wants all of it.
Do not scope a dashboard to your contract when the client owns a whole KPI
One trap worth naming, because it looks like discipline and isn’t.
If you’re contracted for technical SEO, it’s tempting to build a technical dashboard: crawl errors, index coverage, Core Web Vitals. All input metrics, all controllable, all correct — and it reports on a fragment of an outcome nobody is accountable for.
Scope the dashboard to the whole KPI even when your contract is a slice of it. Show the outcome the client cares about, then show your slice’s contribution to it. That’s a more honest report, it’s more useful to them, and it makes the case for expanding the engagement without you having to make the case.
Five metric-reporting mistakes that make a report harder to act on
Reporting only outputs. The default, and the one that produces explaining mode.
Reporting only inputs. The overcorrection. A report full of work completed and no outcome reads as activity for its own sake, and eventually somebody asks what it bought.
Reporting a total where a rate belongs. Growth in a total can be entirely audience growth.
Reporting a metric nobody owns. If neither side is accountable for moving it, it’s context at best. Say so, or take it off.
Changing the metric when it stops flattering you. The one that costs credibility fastest. There are two legitimate reasons to evolve a metric — the work moved on, or you found a better measure of the same thing — and both should be announced before the number turns, not after.
Frequently asked questions
What is the difference between leading and lagging KPIs?
A lagging KPI measures a result that has already happened — revenue, sessions, conversions. A leading KPI measures the work that produces it — pages published, issues fixed, links earned. Lagging KPIs are what the client cares about; leading KPIs are what you control, which is why a report needs both.
What is a vanity metric?
Any metric reported without context, rather than a fixed list of bad metrics. Impressions with a comparison, a denominator and a related metric beside them are useful. Revenue as a bare number with nothing around it is a vanity metric, however serious it sounds.
Are rankings a vanity metric?
No — they are mis-audienced. Position tracking is genuinely useful on a specialist page where somebody can act on it. On an executive summary it redirects a revenue conversation into one about position four versus six, which nobody in the room can do anything about.