Skip to main content
Measurement planReference

Tracking measurement plan template

A measurement plan is the document that says what you're measuring and why, agreed before anyone writes a tag. It's short — business objectives, the conversions that indicate them, where each one's truth lives, and who owns the answer — and it exists to prevent the most expensive failure in this field, which is a technically flawless implementation of the wrong thing. Most tracking rebuilds we're asked to do are re-implementations, not repairs.

Free30 minutesNo obligation

Measurement plan · what breaks

Where teams get this wrong — Measurement plan

  1. 01

    Starting with tags

    Then you get a correct implementation of whatever someone assumed you wanted.

  2. 02

    No named source of truth per conversion

    Which guarantees a later argument about whose number is right.

  3. 03

    A plan nobody signed off

    If marketing and finance never agreed, the numbers will be disputed the first time they matter.

Measurement plan · the fix

What a correct implementation looks like — Measurement plan

  • Business objectives written first

    In plain language, before any event names.

  • One conversion per objective

    The thing that indicates the objective happened.

  • A source of truth per conversion

    Named system, named owner.

  • Signed off by whoever will quote the numbers

    Usually marketing and finance together.

Measurement plan · architecture

What the plan contains

Six sections. It should fit on two pages — a measurement plan nobody reads has failed at its only job.

  1. 1

    Business objectives

    What the business is trying to achieve, in plain language.

  2. 2

    Indicating conversions

    One per objective. What it looks like when the objective happened.

  3. 3

    Source of truth

    The system whose record decides. Named, with an owner.

  4. 4

    Value definition

    What a conversion is worth and how that figure is derived.

  5. 5

    Supporting events

    Funnel steps that give bidding volume. Explicitly secondary.

  6. 6

    Sign-off

    Who agreed, and when. This is what prevents the argument later.

Measurement plan · diagnose

Common mistakes and how to validate each — Measurement plan

Ordered by how often we find them. Each one has a specific check rather than a general instruction to be careful.

  1. 01

    Objectives written as event names

    Read the plan. If it starts with purchase rather than with revenue, it's a tag spec, not a measurement plan.

  2. 02

    Several conversions per objective

    Count them. More than one and bidding won't know what to chase.

  3. 03

    Source of truth left as a dashboard

    GA4 isn't a source of truth. Name the system that holds the records.

  4. 04

    No value definition

    Ask what a lead is worth. If nobody can answer, value-based bidding is off the table.

  5. 05

    No sign-off

    Ask who agreed the plan. If nobody, expect the numbers to be disputed the first time they matter.

Measurement plan · prove

How to prove your implementation is right — Measurement plan

Against your own records and a live payload, not against a preview screen.

Source of truth

the systems named in the plan itself

  • A written plan signed off before implementation started.
  • One indicating conversion per objective.
  • A named source-of-truth system and owner for each.
  • A value definition with a documented derivation.
  • Checked on a live conversion, not in preview mode.
  • Reconciled over a fully closed window, matched per record.
  • Re-checked 30 days later.

Measurement plan · free audit

What we check in the free audit

  • Objectives written as event names
  • Several conversions per objective
  • Source of truth left as a dashboard
  • No value definition
  • No sign-off

Checked against

the systems named in the plan itself

Get my free conversion tracking audit

Free30 minutesNo obligation

Measurement plan · when not to buy

What this reference deliberately leaves out — Measurement plan

Stated openly, because a reference that's silent about its own gaps is the dangerous kind.

  • This is the plan, not the data layer specification. The spec is the technical contract that follows from it.
  • Reporting design — dashboards, cadence, audience — is a separate document.
  • Attribution model choice belongs in the plan as a stated decision, but the reasoning is covered separately.
  • Vendor documentation is the authority, not this page. Where the two disagree, the vendor is right and we'd like to know so we can correct it.
  • Parameter names and behaviour change. Anything here is accurate as we last verified it; verify against the current documentation before you rely on it for a build.

Measurement plan · what we deliver

The checklist — Measurement plan

  • Objectives stated in business language

    Not in event names.

  • Each objective has one indicating conversion

    Not four.

  • Each conversion has a named source of truth

    A system, not a dashboard.

  • Value definition agreed

    What a conversion is worth, and who decided.

  • Signed off before implementation

    By the people who'll quote the numbers.

Pricing

Pick the package that fits your ad spend

Browser-side starter

$400One-time fee · lifetime ownership

Repairs and verifies your existing browser-side setup against this reference, on a live conversion.

  • Implementation checked against the spec
  • Verified on a live conversion
  • Reconciled against your own records
  • Written handover
Have mine checked

1st-party server-side

Recommended

$800One-time fee · most popular

Money events sent from your own records through a first-party container on your subdomain, built to this specification.

  • First-party server container on your own subdomain
  • Events from your records, not the browser
  • Deduplicated on a shared event ID at every destination
  • First-party cookies beyond Safari's 7-day cap
  • 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Have it built properly

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid channel server-side plus the offline loop, documented to this standard.

  • Everything in 1st-party server-side
  • Pinterest, Snapchat, Reddit and LinkedIn CAPI
  • CRM and offline conversion loop
  • Refunds and cancellations corrected wherever each platform allows it
  • Monitoring so the next break surfaces in days
Get the full stack

FAQ

Measurement plan questions, answered

Because the most expensive failure in tracking is a flawless implementation of the wrong thing, and it's only visible months later.

Free · 30 min

Agree what you're measuring before building it

Free30 minutesNo obligation