Almost every argument about a marketing report is really an argument about a definition nobody wrote down. At Growth Bully, a Malta performance marketing agency, the measurement plan is the first document on a new account, because the alternative is discovering in month three that the agency and the client have been counting different things since week one.
It is not a dashboard and it is not a tracking spec. It is one page, written in plain language, and it takes about an hour. What follows is the structure we use, a worked example for a business that sells by quote, and the test that tells you whether the plan is real or decorative.
What is a marketing measurement plan?
A measurement plan is a written agreement, made before spend starts, about what will be counted and who decides. It names the business decision the data exists to serve, the small set of outcomes that answer it, the definition of each outcome in words, the owner of each number, and the review date.
The reason it goes first is that measurement is not neutral. Whichever outcome you choose to count becomes the thing the campaign optimises towards, and that choice is made either deliberately on one page at the start or accidentally by whoever builds the dashboard. Reading a report sceptically, covered in how to read a marketing report, is the downstream skill. This is the upstream one.
What should a measurement plan actually contain?
Six items, nothing more: the decision, the outcomes, the definitions, the sources, the owners and the review date. Anything longer stops being a plan and becomes a specification nobody reads. Write them in that order, because each line constrains the one after it.
- The decision. One sentence naming what you will do differently depending on the numbers. If no decision changes, the measurement is reporting for its own sake.
- The outcomes. Two or three, never more. An outcome is something the business gets, not something a platform records.
- The definitions. Each outcome written in words precise enough that two people counting separately get the same answer.
- The sources. Where each number comes from, which is one named system per outcome, not two.
- The owners. A person for each number. Shared ownership means nobody chases it when it stops arriving.
- The review date. When the plan itself gets challenged, separate from the monthly reporting date.
Notice what is absent. No channel list, no platform metrics, no targets. Channels are how you pursue an outcome and they can change mid quarter without the plan changing, which is exactly the point.
What does a finished measurement plan look like?
Here is the full worked example for a business selling a considered service by quote, written the way it would actually be handed over. It fits on one page and every line is a sentence somebody can be held to.
- Decision: whether to keep, cut or double the paid budget at the end of each quarter.
- Outcome one: qualified enquiries. Defined as an enquiry with a stated need we serve, a site or project in our service area, and a named person who can approve the work. Source: the CRM, one record per enquiry. Owner: the sales lead.
- Outcome two: cost per qualified enquiry. Defined as total media spend plus fees divided by outcome one, in the month the spend occurred. Source: the ad accounts for spend, the CRM for the count. Owner: the account manager.
- Outcome three: quotes issued and quotes won from those enquiries, tracked against the month the enquiry arrived rather than the month it closed. Source: the CRM. Owner: the sales lead.
- Review: the plan is reread on the first working day of each quarter and the definitions can be changed then, not mid quarter.
Outcome three is the one most plans omit, and it is the one that keeps the other two honest. Without it the account optimises towards enquiry volume, and a year later it is excellent at producing enquiries the sales team does not want. The arithmetic for setting a target against it sits in what a lead is worth.
How do you define a qualified enquiry before reporting starts?
By writing the three or four conditions that must all be true, then testing the definition against twenty real enquiries from the last quarter. If two people classify those twenty differently, the definition is not finished. Most useful versions name a real need, a budget in range and the authority to decide.
Define it yourself rather than accepting an agency version, because the party counting the outcome should not also be the party setting the bar. Our full working definition, and the conditions that tend to survive contact with a real pipeline, is in what a qualified lead actually is.
One practical rule: the definition must be checkable from the record itself. A condition like genuinely interested cannot be audited, so it will quietly be interpreted differently every month by whoever is in a hurry.
How do you test measurement before trusting the dashboard?
Submit real enquiries yourself and follow each one through every system, end to end. One form fill, one phone call and one message, then check that each appears exactly once in the CRM, once in analytics and once in the ad platform, with the right source attached. Most plans fail here.
The common failures are dull and expensive. A form that fires a conversion on page load rather than on submit, a phone enquiry with no source at all, a thank you page reachable by refresh so one enquiry counts three times, and consent handling that drops a third of events before they are ever recorded. The durable setup is covered in conversion tracking that survives, and the consent side in tracking that still works after the consent banner.
Expect the systems to disagree even once they are correct. Platforms and analytics count in different windows and both will claim the same sale, which is why the plan names one source per outcome instead of averaging them. The mechanics are in why analytics and ad platform numbers never match and attribution windows.
How often should the measurement plan be reviewed?
Quarterly, and separately from the monthly report. Monthly meetings should argue about results inside the agreed definitions. Changing a definition in the same meeting where you discuss performance is how a target gets hit by redefining it, usually without anyone intending to.
A quarterly review has three questions. Did the decision named at the top actually get taken using these numbers, did any definition drift in practice, and is anything on the page now being collected and never used. Measurement that informs no decision is overhead, and cutting it is a win rather than a loss.
This is the layer underneath everything we run, from lead generation to the Decision-Maker Pipeline, and the enquiry to meeting gap it exposes is what the pipeline scorecard is built to read. Scale decisions in digital marketing are only as good as the definitions behind them.
