Measurement
Part of B2B demand generation measurement should start with the decision, not the data
Build a B2B demand generation reporting dashboard without vanity metrics
A practical how-to for building a B2B demand generation reporting dashboard that answers decisions, with a worked example in pounds and UK source checks.
What to take away
- If a Monday meeting opens with a team arguing over 4,000 clicks and no one can say which campaign produced pipeline, the dashboard is the problem, not the data.
- A B2B demand generation reporting dashboard should answer three decisions: where to spend next month, which campaigns to stop, and which accounts sales should call.
- Build one page per decision, and keep raw channel metrics in a second layer for analysts.
- Every number needs a named source, a date and a definition, otherwise the meeting re-litigates it.
Start from the decision, not the chart
Write down the decisions the dashboard must support before you open a reporting tool. For most B2B teams these are budget shifts, campaign stop or continue, and sales follow-up priority.
Each decision becomes one dashboard page. If a chart cannot change a decision, it belongs in an analyst view, not the front page.
This keeps the build small. Even a modest reporting licence, say £400 a month, can cover three decision pages, and the rest is discipline. If you are still choosing software, compare demand generation tools against those three pages first.
Define each metric in one sentence
Every metric needs a plain definition, an owner and a refresh date. "Qualified pipeline" is useless until you say who qualifies it and when.
Write definitions in a shared document, not inside the tool. Tools change; definitions should survive the migration. Mapping CRM stages to demand stages also forces you to name the owner of each stage.
Where a dashboard figure turns into an advertising claim, the CAP Code requires marketers to hold documentary evidence for objective claims before publication. Keep the source file next to the number.
Choose a model for connecting spend to revenue
Attribution is the hardest part and the part most often fudged. Pick one primary model, state it on the page, and do not switch it mid-quarter.
Single-touch models are simple but flatter whichever channel touches the form. Multi-touch models spread credit and need clean data. Compare the trade-offs in the attribution methods comparison before you commit, because the choice changes what your dashboard can defend.
Label the model in the page title. "Pipeline by first touch" and "pipeline by even split" should never share a chart. The wider strategy framework shows where the model choice sits in the annual plan.
Build the three pages
Each decision gets one page, and each page gets a small set of metrics.
| Page | Decision it supports | Main metrics |
|---|---|---|
| Spend efficiency | Where to spend next month | Cost per qualified opportunity by channel, month on month |
| Campaign health | Which campaigns to stop | Pipeline created, velocity and stall rate by campaign |
| Account priority | Which accounts sales should call | Accounts with rising engagement and no open opportunity |
Keep filters consistent across pages. If page one uses UK only and page three uses global, the meeting will find the gap and lose the thread. For the cost lines on page one, use the same definitions as your return on investment calculation.
A worked example in pounds
Take an agency with a £6,000 monthly budget, where the numbers are illustrative. It splits £2,500 on paid search, £2,000 on events and £1,500 on content.
Spend vs pipeline by channel
Paid search
- Monthly spend
- £2,500
- Qualified pipeline
- £9,000
- Cost per opportunity
- £0.28
Events
- Monthly spend
- £2,000
- Qualified pipeline
- £14,000
- Cost per opportunity
- £0.14
Content
- Monthly spend
- £1,500
- Qualified pipeline
- £4,000
- Cost per opportunity
- £0.38
| Channel | Spend | Qualified pipeline | Pipeline per £1 spent |
|---|---|---|---|
| Paid search | £2,500 | £9,000 | £3.60 |
| Events | £2,000 | £14,000 | £7.00 |
| Content | £1,500 | £4,000 | £2.67 |
Events lead on total pipeline and on pipeline per pound, and content trails. That single comparison drives the next month's shift, with the rule that one month of data moves a fraction of the budget. Plan the split in a monthly budget template so every change has a recorded reason.
Set a refresh and review rhythm
Data should refresh automatically where possible, weekly at minimum. Someone must own the refresh and confirm it landed before the meeting.
Refresh and review rhythm
- WeeklyAutomatic data refresh
- Before meetingOwner confirms refresh landed
- MonthlyReview for budget decisions
- QuarterlyReview for attribution model changes
Review monthly for budget decisions and quarterly for model changes. Changing attribution monthly destroys comparability.
Retention needs a separate rule. The GOV.UK company records guidance says a limited company must keep records for 6 years from the end of the last company financial year they relate to, but that covers accounting records. Dashboard exports that hold personal data fall under the UK GDPR storage limitation principle: identifiable data should be kept no longer than necessary.
Keep the dashboard honest
Add a small data quality panel: missing values, late CRM updates, campaigns with spend and no pipeline. Visible gaps stop quiet guessing.
Retire metrics that nobody has used for two quarters. A dashboard with thirty charts gets skimmed; one with nine gets read.
Finally, write the meeting agenda into the dashboard itself. If the first page answers the first question asked, the argument about clicks tends to disappear.
Common questions
How many metrics should a demand generation dashboard show?
Aim for three decision pages with roughly three metrics each. More than that and the review becomes a reading exercise rather than a decision.
Should the dashboard use first touch or multi-touch attribution?
Pick one primary model and label it clearly. First touch suits simple sales cycles, multi-touch suits longer ones with several stakeholders, and the choice must stay fixed for at least a quarter.
Who should own the reporting dashboard?
One named person owns definitions and refresh, even if several people build charts. Without a single owner, definitions drift and the meeting reopens old arguments.
How often should the numbers refresh?
Weekly is enough for most B2B teams, with a monthly review for budget shifts. Daily refreshes rarely change a decision and add maintenance cost.
