Boundary page

UTM taxonomy vs naming conventions

Taxonomy decides which values are allowed. Naming conventions decide how approved values are written. Keeping those jobs separate is what stops drift, duplicate rows, and endless QA arguments.

Use this page to settle the boundary fast, assign each field to the right control layer, and move back into the correct owner page before a row reaches the builder.

Compare the layers Check field ownership Fix the right layer
Taxonomy owns meaning

Approved dictionaries, aliases, and the reporting rollups that need to stay stable.

Naming owns expression

Case, separators, ordering, and the readable formula used when approved values become campaign names.

QA enforces both

The split only works when launch review checks approved values and written format together.

The boundary board

Use this split to stop teams solving vocabulary problems with formatting rules or formatting problems with dictionary changes.

Taxonomy owns

Approved valuesSource, medium, and any other labels that must roll up into one clean reporting meaning.
Field meaningWhich field should carry creator, offer, platform, or audience detail in the first place.
Alias controlLegacy mappings, synonym cleanup, and value retirement without fragmenting reports.
Ask taxonomy first

If the decision changes how rows group in reporting, it belongs here.

Ask naming next

If the decision is about readability, separators, date order, or format, naming owns it.

Use QA to police both

Neither layer matters if unchecked rows still reach live campaigns.

Naming conventions own

Formatting rulesCase, separators, date placement, and the formula used to write campaign names cleanly.
Pattern consistencyHow approved values get assembled so teams stop producing near-duplicate rows.
Builder-ready outputThe written shape that templates, generators, and builders are expected to reproduce every time.

Field-by-field ownership matrix

Use this when teams keep bouncing decisions between the dictionary and the formula instead of assigning them properly.

utm_source
Taxonomy
One approved dictionary

Source values need one stable reporting meaning. Alias cleanup belongs in taxonomy, not the naming guide.

utm_medium
Taxonomy
Classification before expression

Medium is a classification field. Decide the approved values first, then write them consistently everywhere.

utm_campaign
Naming
Formula matters most

Campaign names usually fail because people write the same idea in different orders with different separators.

utm_content
Naming
Only tighten when needed

Keep this in the naming layer unless reporting genuinely needs a strict dictionary for placements or variants.

utm_term
Use-case
Govern only when search logic depends on it

If search, partner, or audience analysis relies on stable values, tax it more like taxonomy. Otherwise keep it light.

Same problem, different layer

Most repeated QA arguments happen because the symptom is real but the team is fixing it from the wrong layer.

Source drift

People use facebook, fb, and meta interchangeably, then wonder why source rows fragment.

Wrong fixChange separators or casing and hope the duplicates merge.
Right fixFreeze one approved source value and keep alias notes in taxonomy.

Campaign readability

Everyone understands the promotion, but each team writes it in a different order with different separators.

Wrong fixTreat it as a taxonomy debate and keep inventing more campaign variants.
Right fixLock one naming formula and enforce it in the template, generator, and builder.

Creator or partner detail

The team knows the detail matters, but keeps arguing whether it belongs in source, content, or campaign.

Wrong fixLet each channel decide field placement ad hoc.
Right fixUse taxonomy to assign the field, then naming to define how the chosen value is written.

Paid social medium sprawl

The same traffic ends up tagged as paid-social, paid_social, social_paid, and cpc.

Wrong fixTeach better formatting and ignore the medium dictionary problem.
Right fixFreeze the approved medium first, then enforce its written form through naming and QA.

Go deeper in naming and taxonomy

UTM Naming Conventions

Use this when the team needs the written formula, separators, and campaign structure locked down.

UTM Taxonomy Design

Use this when the issue is approved values, alias control, field meaning, or reporting rollups.

UTM Naming Template

Use the template when the rules need a governed operating sheet before rows reach the builder.

UTM Builder

Use the builder when approved values and the naming formula are already set and the team needs final URLs assembled cleanly.

UTM QA Checklist

Use the checklist when a launch needs human release discipline after the naming and taxonomy layers are already controlled.