Markdown Editor

Marketing Measurement Plan Template (Attribution, MMM, Incrementality)

Decisions, KPI tree, metric definitions, data sources, attribution, incrementality experiments with worked readout, MMM, UTM convention, privacy, decision rules

MarketingVollständigCommon practice; privacy checks cite ePrivacy Art. 5(3), UK PECR, CCPA (GPC)measurementplan

Anleitung: Use it when marketing and finance need one agreed way to judge spend. Fill the decisions and the KPI tree first, then plan experiments before trusting platform conversions. The main pitfall is treating platform-reported conversions as incremental.

Vorschau

Marketing Measurement Plan: [Organisation or product], [Period]

The agreed way a marketing team measures what its spend and work achieve: the KPI tree from business outcome down to channel metrics, metric definitions, the data sources, how credit is assigned (attribution), how true causal lift is tested (incrementality experiments), how budgets are modelled across channels (marketing mix modelling), the UTM naming convention, privacy and consent rules, reporting and the decisions each number drives. Based on common marketing analytics practice, with privacy checks that cite EU, UK and US rules as dated examples. Replace every [bracketed] value and every row marked Example. This is a documentation format, not legal advice: check the current official text and ask a qualified professional.

Document control

FieldValue
Document ID[MMP-YYYY-01]
Organisation or product[Name]
Planning period[YYYY or YYYY-H1]
Version[0.1]
Status[Draft / Approved / Superseded]
Owner[@marketing-analytics-lead]
Approvers[@cmo], [@finance-partner], [@privacy-lead]
Reviewers[@growth-lead], [@data-engineering]
Last updatedYYYY-MM-DD
Next reviewYYYY-MM-DD
Classification[Internal]
Related plansmarketing/marketing-plan, data/analytics-tracking-plan

Approvals

RoleNameDecisionDate
Plan owner[@owner][Approved]YYYY-MM-DD
Finance partner (budget and ROI method)[@finance][Approved / Changes]YYYY-MM-DD
Privacy lead (section 9)[@privacy][Approved / Changes]YYYY-MM-DD

Revision history

VersionDateAuthorChange
0.1YYYY-MM-DD[@owner]First draft
[0.2] (Example)YYYY-MM-DD[@owner]Added geo holdout EXP-02 and changed MQL definition (see CHG-001)

Contents

  1. Decisions this plan supports
  2. KPI tree
  3. Metric definitions
  4. Data sources and ownership
  5. Measurement methods and how they fit
  6. Incrementality experiments
  7. Marketing mix modelling
  8. Attribution and UTM conventions
  9. Privacy, consent and data minimisation
  10. Reporting cadence and audiences
  11. Decision rules and guardrails
  12. Change control and data quality
  13. Glossary and references

1. Decisions this plan supports

Decision IDDecisionOwnerFrequencyEvidence usedMethod (section 5)
DEC-01 (Example)Split next year's paid budget across channels[@cmo] with [@finance]Annual, revisited each quarterChannel ROI and saturation curvesMMM, calibrated by experiments
DEC-02 (Example)Pause, keep or scale a campaign in flight[@growth-lead]WeeklyCost per qualified pipeline, trend against targetAttribution, with incrementality factor
DEC-03 (Example)Decide whether a channel adds sales we would not otherwise get[@growth-lead]Twice a year per major channelLift and incremental cost per acquisitionHoldout or geo experiment
DEC-04 (Example)Choose between two landing page or email variants[@lifecycle]Per testConversion rate difference with confidence intervalA/B test (product/ab-test-plan)
[DEC-05][decision][@owner][frequency][evidence][method]

Out of scope: [Example: sales rep performance measurement, which is covered by the sales operations plan; product analytics for retention, covered by data/analytics-tracking-plan].

2. KPI tree

The top of the tree is a business outcome finance already reports. Each level below explains the level above as a product or sum, so a change at the top can be traced to a cause lower down.

KPI IDKPILevelOwnerTarget for periodLinked decision
KPI-01 (Example)Marketing-sourced new ARROutcome[@cmo]$2.4MDEC-01
KPI-02 (Example)Sales-qualified opportunities (SQOs) from marketingPipeline[@demand-gen]480DEC-01, DEC-02
KPI-03 (Example)Cost per SQO, paid channelsEfficiency[@growth-lead]Under $1,100DEC-02
KPI-04 (Example)Incremental cost per acquisition, paid socialCausal efficiency[@growth-lead]Under $180 per incremental demo requestDEC-03
KPI-05 (Example)Branded search volumeBrand health[@brand]Up 15% on prior yearDEC-01
[KPI-06][KPI][level][@owner][target][DEC-ID]

Keep the tree to roughly ten nodes. If the team needs more, the extra metrics are diagnostics: they live on a dashboard tab, not in targets.

3. Metric definitions

MetricFormulaIncludesExcludesWindowSource of truth
MQL (Example)Count of contacts reaching lead score 60 or a hand-raise actionDemo requests, pricing contact forms, score 60 or aboveStudents, competitors, existing customers, personal email domainsCalendar month of qualificationCRM
SQO (Example)Count of opportunities accepted by sales at stage 1 with a sourced-by-marketing flagFirst-touch or self-reported marketing sourcePartner-sourced, expansion dealsMonth of acceptanceCRM
Cost per SQO (Example)Paid media spend / SQOs from paid channelsMedia spend, agency fees on mediaSalaries, toolingMonth, with 60-day lag viewFinance ledger, CRM
Incremental CPA (Example)Test spend / incremental conversions from a controlled experimentConversions above the control group rateConversions the control would also have madeTest periodExperiment readout
Pipeline velocity (Example)(SQOs x win rate x average contract value) / sales cycle daysMarketing-sourced SQOsExpansionRolling 90 daysCRM
[metric][formula][includes][excludes][window][source]

Lag matters in business-to-business sales. Example: Larkspan's median time from first click to closed deal is 74 days, so a month's spend is judged on SQOs at 60 days and on ARR at 120 days, never on the same month's revenue.

4. Data sources and ownership

Source IDSystemDataOwnerFreshnessJoin keyNotes
SRC-01 (Example)CRMLeads, opportunities, revenue[@revops]HourlyOpportunity ID, account IDSource of truth for pipeline and ARR
SRC-02 (Example)Ad platforms (search, social)Spend, impressions, clicks, platform conversions[@growth]DailyCampaign ID via UTMPlatform conversions are not incremental
SRC-03 (Example)Web analyticsSessions, landing pages, form starts[@analytics]DailySession UTMConsent-dependent coverage (section 9)
SRC-04 (Example)Finance ledgerInvoiced media and agency costs[@finance]Monthly closeCost centre, campaign codeSource of truth for spend
SRC-05 (Example)Self-reported attribution field"How did you hear about us?" on demo form[@demand-gen]Real timeLead IDCaptures podcasts, word of mouth, communities
[SRC-06][system][data][@owner][freshness][key][notes]

Event naming, properties and consent flags for the website follow data/analytics-tracking-plan. Shared business terms (MQL, SQO, ARR) are recorded once in the data team's data/business-glossary.

5. Measurement methods and how they fit

MethodQuestion it answersSpeedStrengthWeaknessUsed for
Attribution (rules-based or data-driven)Which touchpoints were on the path to conversion?DailyGranular, fast, campaign-levelCorrelational; misses offline and non-clickable media; reduced by consent gapsDEC-02
Incrementality experiment (holdout, geo, A/B)How many conversions did this cause?Weeks per testCausal; the ground truth for calibrationOne channel at a time; needs volume; costs some sales in the holdoutDEC-03, DEC-04
Marketing mix modelling (MMM)How should the total budget be split across channels?Quarterly refreshCovers all channels and offline factors; no user-level data neededNeeds two or more years of weekly data; wide uncertainty; correlational unless calibratedDEC-01
Self-reported attributionWhere do buyers say they heard of us?Real timeCaptures dark social and word of mouthRecall bias; free text needs codingSense-check for all three

How they fit, in one loop: experiments measure true lift for a channel, the lift calibrates both the attribution model (as an incrementality factor) and the MMM (as a prior or a constraint), and the calibrated MMM sets next quarter's budget, which attribution then steers week by week.

6. Incrementality experiments

6.1 Experiment register

Exp IDChannelHypothesisDesignPrimary metricDurationDecision ruleStatus
EXP-01 (Example)Paid social prospectingPaid social causes demo requests beyond those that would happen without itAudience holdout: 10% of the eligible audience randomly excluded from adsDemo request rate6 weeksKeep spend if incremental CPA is under $180 and the 95% interval excludes zero liftComplete
EXP-02 (Example)Branded searchBranded search ads add clicks beyond organic resultsGeo test: ads off in matched regionsDemo requests per region4 weeksCut branded bids by half if incremental demos are under 10% of paid clicksPlanned
[EXP-03][channel][hypothesis][design][metric][weeks][rule][status]

6.2 Worked readout: EXP-01 (Example)

GroupAudienceDemo requestsRate
Exposed (treatment)180,0002,1601.20%
Holdout (control)20,0002001.00%
  • Absolute lift: 1.20% minus 1.00% = 0.20 percentage points.
  • Relative lift: 0.20 / 1.00 = 20%.
  • Incremental demo requests: 0.20% x 180,000 = 360.
  • Uncertainty: the 95% confidence interval for the absolute lift is about 0.05 to 0.35 percentage points (unpooled standard error, z about 2.67), so incremental demos lie between about 96 and 624.
  • Spend in the test window: 54,000,soincrementalCPAis54,000, so incremental CPA is 54,000 / 360 = **150∗∗,insidethe150**, inside the 180 rule. Decision: keep spend.
  • Platform comparison: the ad platform reported 900 conversions, a platform CPA of $60. The incrementality factor is 360 / 900 = 0.40: for steering in section 8, multiply platform-reported paid social conversions by 0.40 until the next test.

Design checks before launch:

  • Randomisation unit fixed (user, account or region) and the holdout cannot see the ads through other campaigns.
  • Minimum detectable effect and sample size computed from the baseline rate.
  • No other major change (pricing, launch) planned for the test window, or it affects both groups equally.
  • Primary metric and decision rule frozen in this register before launch.
  • Cost of the holdout (lost sales) agreed with the budget owner.

7. Marketing mix modelling

ItemChoice
Outcome variable[Example: weekly marketing-sourced SQOs, also run on new ARR]
Granularity and history[Example: weekly, 156 weeks (three years)]
Channels modelled[Example: paid search, paid social, display, email, events, organic as baseline]
Control variables[Example: seasonality, price change in week 88, competitor launch, sales headcount]
Carry-over and saturation[Example: geometric adstock per channel; Hill saturation curve]
Calibration[Example: EXP-01 lift used as a prior for paid social]
Tool[Example: open-source Bayesian MMM library, version pinned in the repository]
Refresh[Example: quarterly, before DEC-01 review]
Validation[Example: holdout of the last 12 weeks, error reported; coefficients sense-checked against experiments]

Channel results (Example, last 12 months):

ChannelSpendModelled incremental revenueROI (revenue / spend)Read
Paid search$120,000$300,0002.5Near saturation above $12,000 per week
Paid social$80,000$136,0001.7Room to grow; consistent with EXP-01
Display$40,000$36,0000.9Returns less than spend; test before cutting
Email$10,000$65,0006.5Limited by list size, not budget
Total$250,000$537,0002.1

Report each ROI with its interval from the model, and act on a difference only when intervals do not overlap or an experiment confirms it. Marginal ROI (the return on the next dollar) guides reallocation, not average ROI: paid search has the higher average but is near saturation, so the next dollar may earn more in paid social.

8. Attribution and UTM conventions

8.1 Attribution model

  • Model used for steering: [Example: position-based (40% first touch, 40% lead creation touch, 20% spread across the middle) for pipeline, last non-direct click for web conversion rate tests].
  • Lookback window: [Example: 90 days before lead creation].
  • Adjustments: [Example: paid social conversions multiplied by the EXP-01 incrementality factor of 0.40 in the weekly report].
  • Known gaps: [Example: users who decline analytics cookies are not in path data; podcast and community influence is only visible in self-reported attribution].

8.2 UTM convention

ParameterRuleAllowed values (Example)
utm_sourcePlatform or publisher, lower casegoogle, linkedin, newsletter, partner-name
utm_mediumChannel type from a fixed listcpc, paid-social, email, display, referral, event
utm_campaignCampaign code from the campaign register: year, quarter, short name2026q4-ap-automation-launch
utm_contentCreative or link variantvideo-a, cta-footer
utm_termPaid search keyword group onlyap-automation

Rules: lower case only, hyphens not spaces, no personal data (never an email address or user ID in a URL), one campaign code per campaign brief (marketing/campaign-brief), and a link builder or spreadsheet that validates values against the lists above.

Example link (Example): https://example.com/demo?utm_source=linkedin&utm_medium=paid-social&utm_campaign=2026q4-ap-automation-launch&utm_content=video-a

9. Privacy, consent and data minimisation

QuestionExample rules to check (as of October 2026)Answer
Do analytics or ad tags store or read information on the device before the visitor consents?EU Directive 2002/58/EC Article 5(3); UK PECR regulation 6 (ICO guidance; the Data (Use and Access) Act 2025 amends PECR, so check which changes are in force)[answer]
Do we honour browser opt-out preference signals such as Global Privacy Control for sale or sharing of personal information?California CCPA and its regulations (the California Attorney General states GPC must be honoured as a valid opt-out request)[answer]
Is the lawful basis for each processing purpose recorded, including uploading customer lists to ad platforms?EU and UK GDPR Article 6; record in compliance/gdpr-ropa[answer]
Do measurement reports use aggregated data wherever user-level data is not needed?Data minimisation, GDPR Article 5(1)(c)[answer]
How long are raw event and click-level data kept?Retention schedule in data/data-retention-deletion-standard[answer]

Design for consent gaps: [Example: report the consent rate weekly, present web conversion metrics as "consented sessions only", and rely on CRM outcomes, experiments and MMM, which do not need cookie-level data, for budget decisions].

Last checked: [YYYY-MM-DD], by [@privacy-lead].

10. Reporting cadence and audiences

ReportAudienceCadenceContentsFeeds decisionOwner
Weekly channel pulse (Example)Growth teamWeeklySpend, cost per SQO, factor-adjusted conversions, anomaliesDEC-02[@growth-analyst]
Monthly marketing review (Example)CMO, sales leadershipMonthlyKPI tree status, pipeline at 60 days, experiment resultsDEC-02, DEC-03[@analytics-lead]
Quarterly budget review (Example)CMO, financeQuarterlyMMM refresh, ROI intervals, reallocation proposalDEC-01[@analytics-lead]
[report][audience][cadence][contents][DEC-ID][@owner]

Dashboard specifications follow data/dashboard-specification.

11. Decision rules and guardrails

Rule IDTriggerActionApprover
RULE-01 (Example)Cost per SQO above target for 3 consecutive weeks on a channelCut that channel's weekly budget by 20% and review creative[@growth-lead]
RULE-02 (Example)Experiment shows incremental CPA above the threshold with interval excluding the thresholdReduce channel to maintenance spend; retest in 6 months[@cmo]
RULE-03 (Example)MMM marginal ROI for a channel exceeds another by more than its interval widthMove up to 10% of budget per quarter toward it[@cmo], [@finance]
RULE-04 (Example)Consent rate drops more than 10 points week on weekCheck the consent banner and tags before reading web metrics[@analytics-lead]
[RULE-05][trigger][action][@approver]

Guardrail metrics that must not get worse while optimising for the target: [Example: SQO-to-win rate, unsubscribe rate, brand search volume].

12. Change control and data quality

Change IDDateChangeReasonEffect on historyApproved by
CHG-001 (Example)YYYY-MM-DDMQL score threshold changed from 50 to 60Sales rejected 38% of MQLs at 50Prior months restated at 60 for trend charts[@cmo], [@sales-lead]
[CHG-002]YYYY-MM-DD[change][reason][effect][@approver]

Data quality checks before publication:

  • Spend in ad platforms reconciles with the finance ledger within [Example: 2%].
  • Share of sessions and leads with a valid UTM campaign code above [Example: 95%].
  • No duplicate leads per contact within the window.
  • Opportunity source field populated for all new SQOs.

13. Glossary and references

  • Adstock: the carry-over effect of advertising into later weeks.
  • Attribution: assigning credit for a conversion to touchpoints on the path to it.
  • Incrementality: the conversions caused by marketing that would not have happened without it.
  • Incrementality factor: incremental conversions divided by platform-reported conversions, used to adjust attribution.
  • MMM: marketing mix modelling, a regression of outcomes on spend and other factors over time.
  • MQL / SQO: marketing-qualified lead / sales-qualified opportunity, as defined in section 3.
  • Saturation: diminishing returns as spend on a channel rises.

References (checked 2026-10-30):

Standard and licence note

Based on common marketing analytics practice (KPI trees, attribution, holdout and geo experiments, marketing mix modelling with adstock and saturation, UTM tagging), with privacy questions that cite public law and regulator guidance as dated examples (EU Directive 2002/58/EC, UK PECR and ICO guidance, EU and UK GDPR, California CCPA). The text, structure and the fictional Larkspan figures are original. Check the current official version of each source before relying on it; this is not legal or financial advice. Template licence: MIT.

Ähnliche Vorlagen