Team naming standard

UTM naming conventions for marketing teams

Use one readable naming pattern for every campaign row so reports stay clean when multiple people build links across email, paid, affiliate, and creator workflows.

Use the formula Go deeper
One pattern

Keep order, casing, and separators fixed across every campaign row.

One reading style

Names should still make sense when someone audits the row weeks later.

One release path

Lock the naming shape first, then move into build and release.

The naming formula

Pick one pattern and keep it stable. The exact labels can vary by team, but the written shape should not drift once it is set.

date_or_cycle – brand – initiative – audience_or_channel

Use lowercase, keep separators consistent, and make the row readable without forcing someone to guess what the campaign was meant to mean.

Keep one order. Do not move the date to the end on one launch and to the front on the next.
Keep one separator style. Pick hyphens or underscores and apply them the same way every time.
Keep the row readable. Avoid vague short forms that only make sense in a launch chat.
Keep approved values separate. The naming standard controls shape; taxonomy design controls allowed labels.

Bad vs good naming patterns

Show the team what drift looks like and what repeatable naming looks like before the next campaign row gets built.

Bad naming

  • Sale-Apr1
  • Facebook_cpc
  • Black-friday-email
  • black-Friday-Email-10-OFF
Casing, separators, and meaning all drift at once.
Rows stop grouping cleanly in filters and exports.

Good naming

  • 2026-03-shortlinkfix-spring_sale-email
  • 2026-03-shortlinkfix-spring_sale-paid_social
  • 2026-03-shortlinkfix-black_friday-affiliate
  • 2026-03-shortlinkfix-newsletter-prospects
The shape stays readable and repeatable.
Different people can create the same style without inventing new variants.

Fix the naming problem you already have

Use the jump that matches the failure so the next step is obvious without turning this page into a tool directory.

Values are approved, but rows are written inconsistently

Lock the shape and examples first.

Use the naming template

The team keeps confusing naming with allowed values

Separate formatting rules from the approved dictionary.

Use taxonomy design

The team needs faster naming without freestyle input

Normalize the row before it reaches the builder.

Open the naming generator

The name is ready and the URL needs to be assembled

Move the approved row into the build step.

Build the link

The row is built and now needs release control

Use the human release gate before launch.

Run the checklist

Go deeper in naming control

UTM taxonomy design

Use this when the team needs the approved source, medium, content, and term vocabulary behind the naming standard.

Open taxonomy design

UTM taxonomy vs naming conventions

Use this when people keep mixing up allowed values and written format.

Compare the two layers

UTM naming template

Use a shared template when the team needs the same row structure every time.

Use the template

UTM naming generator

Normalize campaign rows before they move into the final URL builder.

Open naming generator

UTM builder

Move the approved naming row into the final tracked URL.

Build approved URLs

UTM QA checklist

Use the release gate when the campaign needs human signoff before it goes live.

Run the checklist