Skip to main content
Tracking is two separate systems that have to agree: UTM parameters tag the inbound link, event tracking records what happens after the click. Both are defined once in setup stage 6 of get started.

Before you start

Naming conventions have to be decided first. UTM values are drawn from the same closed lists as campaign names, and event names come from event naming conventions.

The path

1

1. Understand what a UTM does

Read UTM parameters once. It covers what each parameter is for and why the values have to be consistent rather than descriptive.
2

2. Fill in your UTM standard

Fill in UTM standards: a closed list of allowed values per parameter, the case rule, and the separator.Rule that matters most: the utm_campaign value has to match the campaign name field it corresponds to. If they diverge, spend and conversions cannot be joined.
3

3. Name your events

Decide the event pattern in event naming conventions. Do this before anything is implemented, because renaming an event splits its history in two.
4

4. Build the event tracking plan

Fill in the event tracking plan: every event, its properties, where it fires, and who owns it.Then: save it to the event library so there’s one version rather than one per implementation ticket.
5

5. Connect it to reporting

The marketing reporting data dictionary defines what each metric means. The flat file is where tagged clicks and recorded events meet as rows. Check that the dictionary’s grain matches what your events actually produce.
6

6. Apply it per campaign

From then on, every campaign tags its links from the standard at build time. See step 3 of make a campaign.

The join that has to hold

If any one of these drifts, the row splits and every report downstream is wrong in a way that’s hard to spot, because both halves still look plausible.
Type: setup
Domains: tracking, setup
Provides: task:set-up-tracking
Uses: data-dictionary, flat-file, library:event, naming-convention, utm-rules
Hands off to: task:make-a-campaign
Triggers: “Set up UTMs” · “Build our tracking plan” · “Define our events” · “Why don’t our numbers join?”Asks, in order:
  1. Are naming conventions decided yet? Options: yes or no. Skip when: naming conventions exist.
  2. Which events matter (e.g. signup, purchase, lead)? Options: your answer. Skip when: tracking plan exists.
Output: Filled UTM standard, event naming pattern, event tracking plan saved to event library, grain check against data dictionary.

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on November 2, 2026