An agency report with twenty headline numbers tells the client you have data. One with four tells them you know which numbers matter to their business. The difference is a short conversation at the start of the engagement, and a definition for each KPI written down where the whole team can find it.
The test for a client KPI
Ask one question of every candidate: “If this moved 20% next month, what would we change?” A KPI has a fast, specific answer, such as moving budget, pausing a campaign or fixing a landing page. A metric that only gets a nod is context.
Then ask a second: “Would the client’s leadership care?” The KPIs that go in the headline should connect to what the client reports upward, such as revenue, qualified pipeline or bookings, not just to what the agency optimizes.
KPIs by client type
The right set depends on how the client makes money. These are starting points, not a fixed list:
| Client type | Headline KPIs | The decision they drive |
|---|---|---|
| Lead generation (B2B) | Qualified leads, cost per qualified lead, pipeline from paid | Move budget to campaigns that produce pipeline, not form fills |
| Ecommerce | Revenue from paid, blended ROAS, new-customer share | Scale, hold or cut channels on real revenue, not platform claims |
| Local services | Booked calls or appointments, cost per booking | Shift spend by location and fix call handling |
| Financial services | Applications or funded accounts, cost per funded account | Fund products and regions that produce accounts |
| Multi-location brands | Leads or bookings by location, spend vs budget by location | Rebalance budget across locations |
Two numbers belong in almost every report even when they are not KPIs: spend against budget, and whether the tracking behind the KPIs is working. A KPI that dropped because a tag broke is not a performance problem, and the report should say so.
Write the definition down
Most KPI disputes are definition disputes. “Leads” can mean form submissions in GA4, new contacts in the CRM or contacts that reached a qualified stage. Write each KPI down with enough detail that two people would get the same number:
| Field | Example |
|---|---|
| KPI | Cost per qualified lead |
| Source of record | HubSpot, with ad spend from Google Ads and LinkedIn Ads |
| Counts | Contacts that reached the Sales Qualified stage |
| Excludes | Test records, existing customers, internal domains |
| Date field and time zone | Date entered SQL stage, client’s local time |
| Target | Under $85 for the quarter |
| Owner | Account manager, reviewed with the client’s head of marketing |
Review the definitions with the client once, at the start, and again when their sales process or tracking changes. The agency client reporting QA checklist includes a metric definitions template you can copy.
Move these out of the headline
They can explain why a KPI moved, but they don’t drive decisions on their own:
- Impressions with no outcome attached.
- Follower counts.
- Total pageviews with no key event behind them.
- Email open rate, which privacy features have made unreliable.
- Keyword rankings with no traffic or conversions behind them.
- Clicks and CTR, unless the decision is about creative.
Never show a KPI on its own
“318 qualified leads” is neither good nor bad. Show each KPI against its target and the previous period, and against the same period last year when the client is seasonal. Mark it on track, at risk or off track, so the client can read the page in a few seconds before the discussion starts.
How Maven fits
In Maven, each client is a workspace with their own connected sources. Record the client’s KPIs, how each is defined and the targets in the workspace’s agent context. Maven keeps your words exactly and maintains a read-only list of the client’s priority KPIs, so reports and answers in Claude or ChatGPT use the client’s definitions instead of platform defaults. Monthly media budget targets drive pacing, and alerts can watch a KPI and post to Slack or email when it crosses a line you set.
The weekly client brief turns those KPIs into a Monday email to the client. The monthly client performance review covers the deeper monthly read. Both are published only after you approve them.
A KPI checklist for each new client
- Three to five headline KPIs, each tied to a goal the client cares about.
- A written definition for each: source, what counts, exclusions, date field, target and owner.
- The definitions reviewed with the client.
- Every KPI shown against target and previous period.
- Spend against budget and tracking status on every report.
- Context metrics moved below the headline or to an appendix.
Part of: Agency client reporting
Also in Set up the report: Agency client reporting QA checklist and metric definitions template, Looker Studio vs HubSpot vs Google Sheets for marketing reporting
Frequently asked questions
How many KPIs should a client report have?
Three to five headline KPIs per client, each tied to a goal and a decision. Everything else belongs in breakdowns or an appendix. More headline numbers make it harder to see what changed.
How do agencies choose KPIs for a new client?
Start from the client’s business model and what they are paying you to change, such as qualified leads, revenue or bookings. For each candidate KPI, ask what you would do differently if it moved 20%. Keep the ones with a clear answer.
What should a KPI definition include?
The metric name, the source of record, the exact event or CRM stage, filters and exclusions, the date field and time zone, the target and the owner. “Leads” on its own is not a definition.
Which marketing metrics should agencies stop reporting as KPIs?
Impressions, follower counts, total pageviews, email open rate and keyword rankings on their own. They can explain movement, but none of them tells the client what to do next.
How should KPIs be shown in a client report?
Always against something: the target, the previous period and, where seasonality matters, the same period last year. A number on its own is neither good nor bad.
