The measurement plan: one tracking spec for every market

A measurement plan is the written contract for your tracking. It defines which business questions you answer, which events and parameters answer them, which consent each one needs and which platform receives what.

What a measurement plan is.

Most tracking is built tag by tag: a campaign needs a pixel, someone adds it. A measurement plan turns that around. It starts with the decisions marketing has to make, works back to the data those decisions need, and only then says what gets implemented. Developers build from it, agencies configure from it, legal reviews it, and anyone can check the live setup against it.

What goes into it.

goalsthe decisions the data must support, e.g. budget split by market and channel
KPIsone definition per metric, e.g. what counts as revenue: gross, net, after returns
eventsevery event with its name, trigger and parameters
data layerthe spec your developers implement on the website
consentwhich consent category each tag and event needs
platformswhat goes to GA4, Google Ads, Meta, TikTok and the warehouse
ownershipwho maintains what, and how changes are tested before release

Why it matters more with five or more markets.

When every market built its own tracking, "purchase" means five slightly different things. One market counts orders before payment, another after; one sends net revenue, another gross. The dashboards look comparable and are not, so budget decisions between markets are made on numbers that cannot be compared.

A shared measurement plan fixes this once: one global spec, with local exceptions written down instead of hidden in a container. New markets are rolled out from the same document, so the tenth market costs a fraction of the first.

What a good one looks like.

Readable: A marketing manager understands the goals and KPIs part without help; the technical part is precise enough that developers build without follow-up questions.

Testable: Every event can be checked in the live setup. If you cannot test it, it is a wish list.

Owned: It has an owner and a change process. A plan that is not updated when the website changes is wrong within a quarter.

How Web Wombats builds it.

The measurement plan is the core of our blueprint, the second step after the audit. We write it with marketing, the market teams, IT and legal, then implement it in the pilot market and roll every further market out from it. Your agencies get one spec to work from instead of a dozen different ones.

A useful first step: the free tracking score shows in 30 seconds how consistent your markets are today.

Questions about measurement plans.

Is a measurement plan the same as a tracking concept or tagging plan?

Mostly yes. A tagging plan often covers only the events; a full measurement plan also covers goals, KPI definitions, consent and ownership.

What format is it in?

Usually a shared spreadsheet for the event and platform mapping, plus a data layer specification for developers. The format matters less than whether people actually use it.

How long does it take?

That depends on the number of markets, shops and platforms. The audit before it gives you a reliable estimate.

We already have GA4. Do we still need one?

GA4 is a tool, not a plan. If your markets cannot answer "how much did we sell, by channel, by market" with the same numbers finance sees, a plan is what is missing.

Keep reading