Measurement planning

Measurement brief intake checklist

Published June 1, 2026. Status: evergreen source page.

A measurement brief is the moment to prevent the wrong dashboard from becoming the accepted answer.

Use this intake before a campaign launches, before a vendor scopes a study, or before an analyst starts a readout. The goal is to define the decision, counterfactual, primary outcome, evidence limits, and language standard while the team can still change the plan.

What the brief must answer

Intake field	Write this before work begins	Why it matters
Decision owner	The person or team that will act on the result, plus the date the decision is due.	Prevents a measurement project from becoming an interesting report with no owner.
Decision question	The exact choice in front of the team: renew, scale, pause, shift budget, change creative, change audience, or run a stronger test.	Separates operational decisions from broad curiosity.
Counterfactual	What would plausibly happen without the campaign, package, offer, creative, or channel being measured.	Keeps the team from treating observed activity as caused activity.
Primary outcome	One outcome that matches the decision, with a fixed source, definition, and window.	Stops a weaker proxy from replacing the metric that matters.
Eligible population	The audience, geography, placement set, customer status, device scope, or time window that can fairly enter the analysis.	Makes the denominator visible before results are filtered.
Comparison design	The best available comparison: randomized holdout, geo control, matched baseline, prior period, model baseline, or no valid comparison.	Sets the strongest claim the work can support.
Data readiness	Required IDs, placement fields, creative fields, dates, outcomes, exclusions, match rules, and known missing fields.	Finds tracking problems before the report is already late.
Claim boundary	The strongest wording allowed if the evidence is clean, mixed, weak, or incomplete.	Prevents descriptive reporting from being promoted into causal language.

Pick the measurement lane

The intake should not force a single method. It should make the tradeoff visible enough that the team chooses a method on purpose.

If the decision asks...	Start with...	Do not let it become...
Did this media create incremental outcomes?	A randomized, geo, store, or matched-market design with a protected comparison.	An attributed outcome report presented as lift.
How should budget move across channels?	MMM with controls, uncertainty, sensitivity checks, and credible calibration evidence where available.	A ranking of channels based only on predictive fit.
Did people notice or remember the message?	A brand or attention study with sample quality, field dates, and outcome meaning visible.	A proxy metric treated as proof of profitable demand.
Which creative, context, or page deserves iteration?	A diagnostic readout with delivery, audience, placement, destination, and outcome quality separated.	A winner claim from small or confounded slices.
Was the campaign delivered cleanly?	Delivery QA with placement, context, device, viewability, invalid traffic, frequency, and pacing fields.	A performance claim when only exposure quality was measured.
Which path or touchpoint appeared before conversion?	Attribution or path reporting labeled as descriptive and checked for window and lag rules.	Causal credit for the last observable touch.

Red flags at intake

The decision is "show impact."

Impact is not a decision. Rewrite the brief around the action the team will take if the evidence is strong, weak, mixed, or missing.

The primary metric is still open.

If the team can choose the winning metric after the campaign, the readout will reward search rather than measurement discipline.

The comparison is described as "before launch."

Before-and-after can be useful context, but it is weak causal evidence when seasonality, pricing, distribution, promotions, news, and other campaigns are moving too.

The data source is only a summary deck.

A serious brief should name the source tables, fields, owner, exclusions, match rules, and change log that will support the final claim.

The readout language is decided by the result.

Agree on language tiers before results are visible: delivered, observed, associated with, directionally consistent with, or estimated incremental lift.

Minimum handoff packet

Campaign or study brief with objective, dates, eligible inventory, audience, creative, destination, geography, and budget scope.
Measurement plan with decision question, counterfactual, primary outcome, method, comparison, exclusions, and readout rule.
Data map with placement IDs, creative IDs, destination URLs, audience fields, exposure fields, outcome fields, and source owners.
Quality-control plan for viewability, invalid traffic, frequency, deduplication, match rates, conversion lag, and missing data.
Claim-language ladder that states what wording is allowed for descriptive, directional, modeled, experimental, and inconclusive evidence.

Meeting prompts

Ask this	What a useful answer includes
What decision will be different if this measurement is credible?	A budget, creative, audience, vendor, package, or testing action with an owner.
What result would make us do nothing?	A pre-stated inconclusive or no-action condition, not only a hoped-for win condition.
Who is excluded from the analysis, and why?	Named exclusion rules with counts or expected counts wherever possible.
What is the best comparison we can protect before results are visible?	A feasible holdout, market control, matched baseline, model baseline, or an honest statement that the work is descriptive.
Which fields must exist on day one?	Placement, creative, context, audience, destination, outcome, test-cell, and timestamp fields.
What is the strongest sentence this design can support?	A sentence that names the evidence type, population, window, and uncertainty or limitation.

Pair with

Use this intake before the measurement method selector when a team is choosing between methods, the incrementality test plan template when the decision needs causal evidence, the campaign data-layer spec when the source fields must be fixed before launch, the campaign readout QA checklist when the report arrives, and the evidence-to-claim language matrix when the final wording needs to match the evidence.

Takeaway

A good measurement brief narrows the room for convenient interpretation. Decide the question, comparison, outcome, data fields, and language before the result exists. Then the readout can help the next decision instead of decorating a decision already made.