Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Digital Marketing › Marketing Strategy

Building a Measurement Plan

What a measurement plan records before launch: events per objective, the source of truth per number, naming conventions, attribution stance and reporting.
Guideintermediate7 min readUpdated

Why it is a strategy document

It is tempting to treat measurement as a technical task to be done after the campaign is built. The order is wrong in two ways. First, tracking set up after launch cannot recover the baseline or the early results, so the campaign cannot be judged. Second, and more important, the questions a measurement plan answers are strategic: what the business counts as success, what evidence will be accepted, how credit is shared between channels. Those are decisions for the people who set the objectives, made before the people who build the tracking start. The objectives and KPIs guide produces the inputs; this plan turns each KPI into something that can actually be captured.

What the plan contains

The objective-to-event map

For every objective, the KPI, the event or events that make up the KPI, where each event happens and what qualifies it.

ObjectiveKPIEvent(s)Where it happensQualification
More qualified leadsSales-accepted leads per monthForm submitted; lead marked acceptedWebsite form; CRMAccepted by sales within the period
Higher first-purchase conversionPurchase conversion rate (CVR)Purchase completedCheckoutExcludes refunds within the return window
Reach the launch segmentUnique reach in segmentImpressionAd platformsAudience defined per platform

The map exposes vague objectives immediately — an objective with no event cannot be measured — and it exposes events that cannot be captured with the current set-up, which is the tracking work that must be done before launch.

The source-of-truth table

Every number will be available from more than one tool, and the tools will disagree. The plan names the reference for each kind of number and says why the others differ.

NumberReference sourceAlso reported byExpected differences
Spend, impressions, clicksAd platform—None; the platform is the only source
Sessions, on-site behaviourAnalytics (GA4 or similar)—Clicks exceed sessions (bots, blocked tracking, abandoned loads)
Platform conversionsAd platformAnalyticsPlatform counts view-through and modelled conversions within its own window; analytics counts on-site events with its own attribution
Revenue, orders, customersOrder system or CRMAnalytics, platformsAnalytics misses refunds and offline; platforms double-count across channels

The point is not to crown a winner but to stop the recurring meeting in which two reports are compared and neither is believed. When a report cites a number, the plan says which source it came from.

Naming conventions

Campaigns, ad sets, ads, content and links need names that a report can group by without a human translating. A convention fixes the fields and their order — for example market, channel, objective, segment, campaign, creative, date — and the UTM parameters that carry them into analytics. The convention is boring and the single highest-return decision in the plan: without it, every analysis starts with a cleanup.

Attribution settings

Which model and which windows the reference reports use for crediting conversions to channels, and the acknowledgement that platform attribution and analytics attribution will differ. At the strategy level the plan decides the stance: for example, last-click in analytics for operational optimisation, platform-reported figures for in-platform bidding, and periodic incrementality tests for budget decisions on creation channels. The attribution page covers the models; the plan records the choice.

Reporting cadence and audience

Who sees what, how often, in what form. A weekly operational view for the people running channels (diagnostic metrics, by channel); a monthly management view (KPIs against targets, by objective); a quarterly strategy review (programme-level numbers, mix decisions). Each report draws on the same plan, so the numbers agree across levels.

Ownership and verification

Who owns the plan, who owns each tracking implementation, and the check that must pass before any campaign spends: a test event visible in each reference source, named correctly, attributed correctly. The campaign brief references this check rather than redefining it.

Illustrative example — not a real result

A measurement plan preventing a familiar argument

A retailer's paid-social agency reports a strong return for the quarter; the finance team's order data shows revenue flat. The measurement plan already states that platform-reported conversions include view-through within a seven-day window and are the reference for in-platform optimisation only, that the order system is the reference for revenue, and that creation channels are judged on reach and on incrementality tests rather than attributed revenue. The meeting is short: the platform figure is what it was always going to be, the revenue figure is the one the business reports, and the open question — whether the social spend is incremental — has a scheduled test rather than an argument.

A minimal plan for a small business

Illustrative example — not a real result

One page for a local service business

Objective: more booked consultations from the service area. KPI: consultations booked, reference source the booking system. Events: booking form submitted (website, tracked through the tag manager to analytics and to the ad platforms), phone call from the site's tracked number (call tracking), booking confirmed (booking system). Qualification: a booking counts when confirmed, not when the form is sent. Diagnostics: sessions by source, form starts, form completions, calls, cost per booking by channel. Source of truth: booking system for bookings; analytics for site behaviour; ad platforms for spend and clicks only. Naming: every campaign named market, channel, service, month; every link tagged with matching UTM values. Attribution: last-click in analytics for channel comparison; platform figures used only to optimise inside each platform; disagreements expected and explained in the monthly note. Reporting: a weekly check of bookings and cost by channel by the owner; a monthly summary with the three KPIs. Verification: a test booking from each channel before any spend, visible in all three systems with the right name. The whole plan fits on one page, and it answers every question the owner would otherwise ask the agency.

A business with no accounts yet can write this plan as one step of the tutorial on setting up the marketing basics for a new business, once ownership, analytics, consent and naming are in place.

Pre-launch verification checklist

0/8

Reporting layers

AudienceCadenceContentsSource
Channel ownersWeeklyDiagnostic metrics by channel and campaign; pacing; tracking healthPlatforms and analytics, per the source-of-truth table
Marketing lead and managementMonthlyKPIs against targets by objective; allocation changes; notable diagnosticsReference sources only
Leadership and financeQuarterlyProgramme-level outcomes: customers, revenue, blended cost, brand trend; mix decisionsOrder system or CRM; brand tracking; incrementality results

Building it

  1. Start from the KPI tree in the objectives guide; list the KPIs and their diagnostic metrics.
  2. For each, write the event, the place and the qualification.
  3. Inventory the tools that exist (analytics, tag manager — GTM or similar — ad platforms, CRM, order system, email platform) and assign each number its reference source.
  4. Write or adopt the naming convention and the UTM scheme.
  5. Record attribution settings and the stance on platform-versus-analytics figures.
  6. Define the reports: audience, cadence, contents, source for every number.
  7. Hand the plan to whoever builds the tracking; the analytics cluster covers that implementation, including server-side signals such as the Conversions API where browser tracking is incomplete.
  8. Run the verification check before the first campaign spends; repeat it after every site or tool change.

When tools change

Platforms change attribution defaults, consent rules reduce what browsers report, and sites get rebuilt. Each of these breaks a measurement plan silently: numbers keep arriving and mean something different. The plan therefore records the date and version of each tool's settings, and the verification check is re-run after any platform notice, consent change or site release. A visible break in a trend with no change in activity is treated as a measurement question first and a performance question second; most sudden drops in reported conversions turn out to be a tag that stopped firing or a window that changed.

Common mistakes

  • Measurement after launch. No baseline, no early data, a campaign that cannot be judged.
  • No source of truth. Every report is contested and the loudest number wins.
  • No naming convention. Analysis becomes archaeology.
  • Platform figures as revenue. View-through and modelled conversions presented as sales.
  • One attribution model for every decision. Last-click for budget decisions starves demand creation.
  • Reports with no owner. Dashboards that nobody checks and nobody trusts.

The core metrics guide explains the numbers the plan captures; the analytics hub covers the tools and the tracking plan that implements this one.

Frequently asked questions

What is the difference between a measurement plan and a tracking plan?

The measurement plan decides what will be measured and why, at the strategy level; the tracking plan specifies how each event is implemented — tag names, parameters, triggers. The analytics cluster covers the tracking plan; this page covers the decisions that come before it.

Which should be the source of truth, the ad platform or analytics?

Neither universally. The plan names a reference per metric: platform data for spend, impressions and clicks; analytics for on-site behaviour and cross-channel comparison; the CRM or order system for revenue and customers. Disagreements are expected and explained, not resolved by picking a winner.

How detailed should a measurement plan be?

Detailed enough that someone could build the tracking from it and someone else could build the report. Usually a few pages: an objective-to-event table, a source-of-truth table, naming conventions, attribution settings and the reporting cadence.

Terms used on this page

Tools to try

Frameworks

Where this page is used

Also related

Related