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

Marketing Data & Analytics Library

Measurement Templates

Three documents carry most of the weight in marketing measurement: a plan that connects objectives to tracking, a naming convention that keeps campaign data readable, and a dictionary that fixes what each metric means. This hub introduces the template for each, explains how they depend on one another, and shows how to keep them in use after the first month.
SectionbeginnerUpdated

In this section

What measurement templates do

A template is a set of questions arranged so that the answers form a working document. The value is not in the headings but in the questions a team is forced to answer in order, and in the gaps that appear when an answer is missing. A measurement plan that has an objective with no question beneath it has found a vanity objective. A naming convention with a medium nobody can map to a channel has found a reporting hole before the first click arrives. A dictionary row with two candidate formulas has found the argument that would otherwise have surfaced in a board meeting.

The templates here are deliberately plain. They are tables with a field column and a what-to-write column, followed by guidance on each field and a filled example for an invented business. They are meant to be pasted into whatever the team already uses, a spreadsheet, a wiki, a planning tool, and adapted. What should survive the adaptation is the logic: every objective has questions, every question has a metric, every metric has an event or a source, every event has an owner. The measurement cluster teaches the reasoning behind that chain; the templates are the chain written down. The parent data library explains the labelling rules that apply to every filled example in this section, which are illustrative and never evidence.

The three templates

Each template answers a different question, and they are used in a fixed order because each one's output is the next one's input.

TemplateQuestion it answersProducesUse it when
Measurement planWhat do we need to know, and what must be collected to know it?Objectives, questions, KPIs and targets, segments, an events and parameters table, owners and cadenceA new objective, a new site or app, a new quarter, or an inherited setup nobody can explain
UTM and naming conventionsHow will campaign traffic be labelled so reports can read it?Parameter rules, controlled vocabularies for source and medium, a campaign name pattern, an ad account naming patternBefore the first tagged link goes out, and whenever channel reports fill with unassigned traffic
KPI dictionaryWhat exactly does each number mean, and who owns the definition?One row per metric with definition, formula, grain, source, owner, direction and caveatsWhen two reports disagree, when a dashboard is being built, or when a metric is being added to a target

The measurement plan names the KPIs; the dictionary defines them; the naming convention ensures the data that feeds them arrives with the right labels in GA4 and the ad platforms. A team can start with any of the three, and often starts with the one whose absence is hurting most, but a plan without a dictionary will drift and a convention without a plan will label traffic nobody is measuring.

Keeping templates alive

A template is filled once and then either maintained or forgotten, and most are forgotten. Three habits prevent it. The first is an owner per document rather than per team: a named person who is asked, on a cadence, whether the document still matches reality. The second is a change log inside the document, so that a renamed event or a new UTM medium is recorded where the next reader will find it rather than in a chat thread. The third is a review trigger tied to events the team already notices: a new campaign type, a site release, a platform change, a quarter end. Each trigger is a prompt to open the document and compare it with what the tools now show.

The cheapest check is a reconciliation. Once a month, take the list of events the plan says exist and compare it with the events the analytics property is actually receiving; take the list of mediums the convention allows and compare it with the mediums in the traffic report; take the dictionary's definitions and compare the figure each produces with the figure on the dashboard. Discrepancies are either tracking faults or documentation drift, and both are cheaper to fix in the month they appear than a year later when the history has to be restated.

Illustrative example — not a real result

A language school's templates after six months

A language school fills all three templates in January: a plan with two objectives (enrolments and trial lesson bookings), a naming convention with seven allowed mediums, and a dictionary of eleven metrics. By June the plan still lists trial_booked as the key event, but a site rebuild in April renamed it to trial_lesson_booked, so the enrolment dashboard shows a drop to zero that nobody investigated for three weeks. The traffic report contains fourteen mediums, including Email, email and e-mail, because two new agencies were never sent the convention. The dictionary is intact, because its owner reviews it at each month end, and it is the dictionary that exposes the other two failures: the "trial booking rate" row names the event the plan expects, which is the event the property no longer receives. The school adds a monthly reconciliation to the owner's calendar and sends the convention to every new supplier as part of onboarding.

Common template problems

Most trouble with these documents shows up as one of a few symptoms. The table maps each to the resource that addresses it and, where the fix is a method rather than a template, to the guide that teaches it.

SymptomLikely causeResource
The plan lists KPIs but nobody can say why a number movedNo questions or KPI tree beneath the objectivesMeasurement plan template
Events in the plan do not match events in the propertyThe plan was never reconciled after a release; no owner per eventMeasurement plan template, measurement cluster
Channel reports show a large unassigned bucketMediums outside the controlled list; case and separator variantsUTM and naming conventions
Platform campaign names and analytics campaign names cannot be joinedTwo naming patterns, or noneUTM and naming conventions
Two dashboards report different values for the same metricDifferent formulas, grains or sources with no single definitionKPI dictionary
A target was set on a metric nobody definedMetric added to a plan without a dictionary rowKPI dictionary
The documents exist but are a year out of dateNo owner, no change log, no review triggerThe habits above; the measurement cluster for the operating rhythm

If the symptom is a figure that looks wrong rather than a document that is missing, the problem is more likely tracking or definitions than templates, and the measurement cluster has guides on data quality and platform discrepancies for that case.

Terms used on this page

Frameworks

Related