KPI reporting for agencies: the client metrics worth surfacing automatically

Most KPI reporting guides are written for boardrooms: pick SMART metrics, add charts, avoid data dumps. Correct, generic, and useless at an agency on the last Friday of the month, where the real questions are which numbers each client should see, which source computes each one, and how any of this happens without eating a day per client.

This is the agency cut: the client KPIs worth surfacing automatically, the spec card that stops the same metric meaning two things, the weekly-versus-monthly split, the vanity metrics to drop, and where thresholds turn reporting into an early-warning system.

What is KPI reporting, for an agency?

KPI reporting is the regular delivery of a small set of measures that tell a client whether the work is working: chosen against the client's goal, computed the same way every period, and paired with what you will do next. For an agency the operative words are small, same way, and every period; volume is not the point, consistency is.

The generic advice caps a report at five to seven indicators, and it is right. What it never says is which seven for an agency client, and who computes them. That is the rest of this guide.

The client KPIs worth surfacing automatically

The base set for a retained marketing client, chosen because each repeats monthly, maps to a goal, and can be computed from a source your agency already controls:

Two notes on the table. The last row is the one agencies omit and clients remember: a line for your own delivery (what was shipped against the plan) reads as confidence, not risk. And every row above it is computable from the ad platforms, Search Console and analytics accounts you already run, which is what makes automatic surfacing possible at all.

How figures get from those sources into a report without a human copy-pasting, and without a model inventing them, is the architecture question, covered in full in our guide to automated client reporting. This piece stays on the selection question: which numbers deserve the pipeline.

The KPI spec card: one metric, one meaning

The quiet killer of client trust is the same KPI computed two ways: conversions from the ad platform in one section and from analytics in another, disagreeing by design. The fix is a spec card per KPI, written once, applied every month:

One maintenance rule: the spec card changes when the client's goal changes, and only then. Not quarterly by calendar, not because a number looks bad this month. A KPI redefined mid-quarter to look better is the fastest way to lose the trust the card exists to build.

Seven rows, one page, and it ends three recurring arguments at once: which number is right (the owning source's), why it changed (the formula is fixed), and who does something about it (the named owner). A client who has seen your spec cards stops second-guessing your numbers, because the numbers stopped moving between reports.

Leading and lagging: the lens that assigns cadence

One distinction from the wider KPI literature earns its place here: leading indicators signal what is about to happen (engagement, click-through, lead volume), lagging indicators confirm what did (revenue, conversions, cost per result). Agencies argue about which matters; the useful answer is that they belong to different cadences. Leading metrics carry thresholds and live in the weekly recap, where there is still time to act; lagging metrics carry commentary and live in the monthly, where the story gets told.

The weekly-monthly split

Cadence is a decision per KPI, not per client. The split that works:

• Weekly (the Slack recap): pacing, conversion counts, anything with a threshold. Five figures, no commentary, posted by the system. Its job is no surprises.
• Monthly (the report): trends, cost per result, organic movement, and the commentary that explains why and what next. Its job is the renewal conversation.
• Quarterly (the review): strategy-level KPIs only, against the client's business goals. Its job is the bigger retainer.

The same pipeline feeds all three; only the template and the audience change. Sending the monthly depth weekly trains clients to skim; sending only monthlies means bad news arrives late. The split is what makes both cadences trusted.

Per-service additions, briefly

• SEO retainers: add indexation coverage (pages indexed vs published) and one content KPI tied to output, not just rankings. Position movement belongs in the monthly, never the weekly.
• Paid-media retainers: add impression share on the priority campaigns; it answers 'could we have bought more of what worked' in one figure.
• Full-service retainers: resist the urge to merge everything into one blended number. One page per channel, then a single blended cost-per-result on top; clients read the top line, auditors read the pages.

The client-goal test, before any of it

The selection rule that overrides every list, including this one: start from the client's stated business goal and walk backwards. A lead-gen client's set centres on cost per qualified lead; an e-commerce client's on blended return and repeat rate; a brand client is the honest hard case, where you agree proxies in writing before the retainer starts, or fight about them after.

Vanity metrics: what to drop

Every metric you report is a promise to keep reporting it. Drop the ones that cannot survive the question so what:

• Impressions without clicks or cost context: reach that neither cost nor earned anything is weather, not performance.
• Follower counts: they go up almost regardless of anything, which is exactly why they reassure and inform nobody.
• Sessions without a conversion column next to them: traffic alone rewards the wrong work.
• Average position without click data: rankings are an input; the click is the event. Report movement only where it moved results.

The test is not whether a metric can look good. It is whether a bad month in that metric would change what you do next week. If not, it is decoration, and decoration erodes the trust your real numbers need.

Thresholds: where reporting becomes an early-warning system

A KPI with a threshold is more than a report line; it is a tripwire. Pacing past plan, CPA through the amber band, conversions at zero for two days: each becomes an alert to your team the day it happens, not a paragraph three weeks later. The mechanics of those checks (and the other agency workflows worth systemising) are in the agency workflow automation guide; the reporting insight is simpler: every threshold you define is a promise the client never finds out from their own dashboard first.

The commentary rule that keeps trust

One habit turns a KPI table into a report worth paying for: every off-target figure gets one sentence of why and one of what next, written by a human who read the numbers. A red cell with no sentence reads as either you did not notice or you hoped we would not; both are worse than the bad number itself. Automate the figures precisely so someone has time to write those two sentences.

Putting it in place

• Pick the base set above, subtract what your service mix does not cover, add at most two client-specific KPIs. Seven is the ceiling, not the target.
• Write a spec card per KPI. One afternoon, and it outlives every account manager transition.
• Split the cadence: five figures weekly, the story monthly. Automate the figures first; keep the story human.
• If you want the map before the build (which KPIs, which sources, what a system would replace), that is what our free 30-minute mapping call is for. You leave with the KPI map either way.