The Measurement Plan to Agree Before You Spend
Four things should be agreed before a single dollar of new ad spend goes out: which attribution model governs routine reporting, what an incrementality test will look like and when it runs, a minimum spend threshold below which testing isn't reliable, and what happens if the results come back disappointing. Skipping this conversation until after the numbers arrive is how measurement disputes become relationship disputes.
What this looks like in a real account
Why this conversation is easier before spend starts than after
Before any money has been spent, everyone in the room is reasoning abstractly — nobody has a stake in defending a specific number yet, because no number exists. That's precisely the window in which a genuinely honest measurement plan gets agreed. Once spend starts and early results come in, every subsequent conversation about methodology carries the shadow of whoever's position it currently favours. The plan agreed in week one, before results exist, is a fundamentally more trustworthy document than one negotiated in week eight, after a disappointing number has already made someone defensive.
What the plan actually needs to specify
Name the default attribution model for routine reporting, and the reporting window for each ad product involved — Sponsored Products, Sponsored Brands, Sponsored Display and DSP each run different windows, and DSP itself splits by whether inventory is in-store or offsite. Name the incrementality test design specifically: holdout or geo-lift, on which channel or audience, over what minimum duration — with an explicit note that the learning window shouldn't be cut short before audience models settle, typically past the three-week mark where premature test-pulling is most common. Name a minimum spend threshold below which a formal incrementality test isn't statistically reliable, so nobody demands a definitive causal answer from a budget too small to produce one.
The clause that matters most: what happens if it's bad news
This is the part most measurement plans skip, and it's the one that actually earns the document its value. State explicitly, in advance: if the incrementality test shows minimal or no lift, what happens next — does the channel get cut, does budget move, does a second test run at a different scale before a final call. Agreeing this before the result exists means a disappointing test doesn't turn into a negotiation about whether the test itself was valid; the response was already decided when nobody had a reason to fight about it.
A worked version of what this looks like in practice
Say a brand is launching a new DSP prospecting line at $15,000 a month. The agreed plan: last-touch attribution for weekly reporting, a geo-lift incrementality test starting in week 5 (after the initial learning period) running 6 weeks, a $10,000 monthly minimum before treating any single-market read as reliable, and a bad-news clause stating that if the geo-lift shows under 5% lift after the full 6 weeks, budget reallocates to retargeting for the following quarter with a re-test scheduled in 6 months. When the test comes back at 3% lift in month three, there's no debate — the plan already said what happens, and the conversation moves straight to execution rather than relitigating whether 3% counts as "good enough."
The common mistake, including ours
The mistake is treating the measurement plan as a formality to draft after the media plan is already locked, rather than as part of the media plan itself. We've launched DSP spend for a client before the incrementality test design was fully agreed, planning to finalise it "once things were running" — and by the time we circled back, three weeks of spend had already happened without a clean test window, meaning the earliest reliable read was pushed back by the exact amount of time we'd spent not finishing the plan. We now treat the measurement plan as a launch blocker, not a follow-up task.
What to do if a plan wasn't agreed and spend is already running
If spend is already underway without a written plan, the honest fix isn't to pretend one existed retroactively — it's to build the plan now, dating it clearly as starting from today, and accepting that any test window measured against the period before the plan existed is weaker evidence than one measured cleanly after it. A late plan is still meaningfully better than none, and the sooner it's written, the sooner a genuinely clean test window can begin.
Who should design the test, and why that's part of the plan too
"Is this incremental, or would they have bought anyway" is the single most common objection we hear in DSP conversations, and it's fundamentally a trust question, not a technical one. The honest answer is naming, in the plan itself, who designs and computes the test — a holdout or geo-lift run entirely by the party being paid on the result, with no agreed design written down in advance, isn't a test a skeptical stakeholder should fully trust, including from us. Writing the test design, the holdout definition and the reporting cadence into the plan before spend starts is what makes that objection answerable rather than just reassuring.
| Plan element | Agree before spend starts | Risk if skipped |
|---|---|---|
| Default attribution model | Which model, which windows per ad product | Retroactive methodology disputes |
| Incrementality test design | Holdout vs geo-lift, duration, who designs it | A test built on the fly, mid-flight, poorly powered |
| Minimum spend threshold | Below which testing isn't reliable | Demanding a causal answer from an underpowered budget |
| Bad-news clause | What happens if lift is minimal or absent | A disappointing result becomes a negotiation, not a decision |
Which one you should actually pick
Any brand and agency relationship can build this plan themselves as a short, specific document agreed before launch — it requires discipline, not proprietary tooling. reMKTR treats it as a non-negotiable launch step, having lost clean test-window time to a delayed version of exactly this plan before, as part of the discipline behind Full Circle's $500M+ in managed Amazon spend across 100+ brands.
Shortlist on the job, not the feature grid. Pull your search-term report for the last 90 days and total the spend against terms that produced no orders — 33.6% on the account above. Then ask each vendor on your list what they would do about it in week one, and see who answers with a process rather than a screenshot.
Common questions
When should a measurement plan be finalised relative to a media launch?
Before spend starts — treating it as a launch blocker rather than a follow-up task avoids losing clean test-window time to a plan that's still being finalised after spend is already running.
What's a reasonable minimum spend threshold for a reliable incrementality test?
It depends on baseline conversion volume and expected lift size, but the plan should name a specific number rather than leaving it open — testing below that threshold should be understood as directional, not definitive.
Why does the plan need a 'bad news' clause specifically?
Because agreeing the response to a disappointing result before that result exists removes the incentive to relitigate the test's validity after the fact, when someone has a stake in the outcome.
Who should be responsible for designing the incrementality test?
The design, the holdout definition and the reporting cadence should be agreed and written into the plan by all parties before spend starts — regardless of who ultimately executes it, which is a fair question to ask of any vendor, including us.
We show the method before the number.
Claim the free auditRead next
- Tinuiti Pricing: How the Quote Gets BuiltPricing · tinuiti pricing
- Skai Review: A Media Buyer's Honest ReadReview · skai review
- Pacvue Pricing: No Public Number — What to AskPricing · pacvue pricing
- Skai vs Pacvue: Contracts, Not Feature GridsHead to head · skai vs pacvue