Marketing · Free implementation template
Campaign Measurement Plan
Define how campaign activity connects to qualified pipeline and revenue before launch.
Introduction
What the Campaign Measurement Plan is for.
Define how campaign activity connects to qualified pipeline and revenue before launch.
A completed marketing template defines what counts as a qualified signal and what must happen inside the window where that signal is still true. This one covers objective, funnel, attribution, decision rules, and it is written for marketing leaders, growth teams, agencies. Each section is a decision that has to exist before the workflow can be built or automated — the prompts are there to force the decision, not to be filled in for their own sake.
A completed template is also a structured brief. ARIA can read it as the objective, the systems involved, and the constraints that apply, which is what turns the specification into something that runs rather than something that gets filed.
- Category
- Marketing
- Sections
- 4
- Format
- Markdown, no signup
- Best for
- Marketing leaders, Growth teams, Agencies
The problem
Specifications fail on the decisions nobody wrote down.
Marketing systems produce a continuous stream of intent signal that loses most of its value within hours. The common failure is not missing the signal; it is routing it days later to a team that no longer has context for it.
The second failure is quieter and more expensive: consent and suppression state gets treated as ordinary data, and an automation modifies it as a side effect of doing something else. That is a compliance problem rather than a data problem.
Specifying the qualification rule, the time window, and the consent boundary before building anything is what separates a program that can be measured from a campaign that can only be described.
You're likely here because
- Campaign results are reported differently each time
- Attribution is argued about after the campaign ends
- Nobody agreed what success meant before launch
How it works
From a blank Campaign Measurement Plan to a running workflow.
Each stage is a decision that has to be made once. Making them in this order is what keeps the later ones answerable — you cannot set an automation boundary before you know who owns the record.
Step 01
Define the qualifying signal
State which behaviour counts, at what threshold, and over what period. A threshold without a window produces handoffs the receiving team will reject.
Step 02
Locate consent state
Record where subscription and suppression state lives and which system is authoritative for it. A workflow reads it before acting and never writes it incidentally.
Step 03
Set the segment rule
Membership is computed at decision time from a stated rule rather than cached as a list that silently goes stale.
Step 04
Specify the handoff
Name the receiving team, the context that travels with the record, and what the team is expected to do within what timeframe.
Step 05
Fix the attribution model
Campaign, source, and medium travel with the record downstream, or revenue can never be traced back to the program that produced it.
The template
Every section, with the prompts that force the decision.
Section 01
Objective
Section 02
Funnel
Section 03
Attribution
Section 04
Decision rules
After it is filled in
What the completed specification is actually consumed by.
Filling in the Campaign Measurement Plan produces an artifact, and an artifact on its own changes nothing. What matters is what consumes it afterwards.
Handed to the runtime, the qualification rules in a completed marketing specification become the filter that decides which signals are acted on, and the window becomes a deadline rather than an intention. That is the difference that matters: a signal routed inside its window reaches someone who still has the context, and the same signal routed two days later reaches someone who has to reconstruct it.
What the specification cannot do is create the signal quality it assumes. If the definition of qualified is wide enough to admit anything, the workflow will faithfully act on noise at speed. The first review after go-live should be about the definition rather than the routing, because the routing is rarely the part that is broken.
Implementation path
How to actually fill it in.
- 01
Agree the qualification threshold with the team that receives the handoff, not just the team that generates it.
- 02
Confirm where consent state is authoritative before any workflow is permitted to act on an audience.
- 03
Instrument the signal-to-action latency from day one; it is the number that determines whether the program works.
- 04
Run the rule against historical data to see how many records it would have qualified before enabling it live.
- 05
Review rejected handoffs weekly for the first month — rejection rate is the fastest signal that the threshold is wrong.
Controls this specification sets
Controls that matter.
Control 01
Subscription and suppression state is read-only to the workflow.
Control 02
Sending windows, throttles, and per-account quotas are respected; work queues rather than failing the batch.
Control 03
Personal data moves only into systems named in this specification.
Control 04
Every qualified handoff carries the campaign context that produced it.
Worked examples
When teams reach for this one.
Before a campaign launches
Agreeing the measurement plan in advance is the only reliable defence against post-hoc attribution disputes.
Comparing two channels
Comparison is only valid when both are measured over the same population and window — which this plan fixes explicitly.
Reporting to a board
A plan that states its denominators survives scrutiny; one that reports rates alone does not.
Limitations
What this template does not do.
- A measurement plan cannot retroactively fix instrumentation that was not in place.
- Multi-touch attribution remains a modelling choice, not a measurement — state which model you chose.
- Analytics data is reprocessed and can move after the fact; declare the refresh window.
- Offline and word-of-mouth influence stay largely unmeasured regardless of the plan.
FAQ
Questions about the Campaign Measurement Plan.
Who should fill in the Campaign Measurement Plan?
The people who own the outcome, together. This template is written for marketing leaders, growth teams, agencies, and the value comes from surfacing disagreement between them rather than from one person completing it alone.
How long does it take?
A focused session, usually one to two hours for a first pass. Sections that take much longer are normally pointing at a real disagreement, which is the template doing its job rather than failing.
Is it free, and is there a signup?
Free, with no gate. The Markdown download link at the top of this page returns the full template immediately.
What happens after it is filled in?
The completed template becomes the specification the build works from. You can hand it to ARIA to resolve into an objective and an execution path, hand it to an internal team, or use it to brief a vendor — the artifact is the same in each case.
Does this replace the tooling?
No. It specifies what the tooling has to do. Marketing tools differ in how much of this they can enforce, which is itself useful information when you are comparing them.
How often should it be revisited?
When the process it describes changes, and on a scheduled review otherwise. A specification that no longer matches what runs is worse than none, because people still trust it.
More marketing templates
Other marketing specifications.
AI Website Build Brief
Turn a business objective into a clear website build brief covering audience, message, proof, conversion, analytics, and connected follow-up.
Open the template →
Landing Page Conversion Checklist
Review a landing page against message clarity, proof, friction, analytics, and connected follow-up before sending paid or organic traffic.
Open the template →
Content Operations Workflow
Create a repeatable system for briefs, drafting, review, approval, publishing, distribution, and performance learning.
Open the template →
Keep exploring
Related reading and next steps.
Start with ARIA
Hand the brief to ARIA.
A completed template is a structured brief. Tell ARIA the objective and it resolves the systems involved and the execution path — so the specification becomes a running workflow, not another document.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Fill it in, then hand it to ARIA.
A completed template is a structured brief. ARIA can resolve it into the objective, the systems involved, and the execution path — so the specification becomes a running workflow rather than another document.