UTM Naming Conventions
A maintainable naming policy for solo marketers, teams, and agencies, including a worked campaign register.
By UTMCraft / Axellier · Updated · Examples use fictional campaigns.
Build a small vocabulary before a large spreadsheet
A useful convention removes decisions people otherwise remake for every link. Start with approved sources, approved mediums, and one campaign template. Avoid a long template that asks people to invent values for dimensions they do not actually report on.
For a studio, objective_offer_month is enough: bookings_introclass_202610. The creative field can hold reel_demo_a or email_header. The destination carries the product path; there is no need to repeat every path segment in the campaign name.
Use a campaign register as the source of truth
Keep one row per initiative with the agreed campaign name, owner, start date, destination, and notes. Before making a new link, search the register. An extra five seconds prevents the same launch becoming intro_class, introclass, and pottery_launch in three channels.
A client-facing agency should keep each client’s vocabulary separate. Add a client prefix only when campaigns truly share one reporting property and the reporting owner needs it. Do not include confidential project names in public link labels.
Campaign: bookings_introclass_202610 Owner: studio marketing Source options: weekly_digest, instagram, partner_directory Medium options: email, social, referral Content options: header_button, reel_demo_a, listing_card
Normalize labels, never the entire URL
Lowercase campaign values and one separator are practical conventions. They are not a reason to lowercase the destination path or a signed token: those can be case-sensitive. Review each changed value, especially platform macros or IDs supplied by another system.
UTMCraft’s naming warning is a prompt to review. It does not prove that a value is wrong or enforce an organization-wide policy. The Taxonomy tool stores a local vocabulary; export it to share with colleagues. Each browser has its own copy.
Roll out changes without losing accountability
Test a convention with a real small campaign before distributing it widely. Record any exceptions, such as an ad platform’s fixed macro syntax. Once links are published, do not rename campaign values merely to make an old report look tidier.
For handoff, include two correct examples and one incorrect example with the reason it fails your policy. A short decision rule such as “content identifies placement, never an individual recipient” is easier to apply than a list of unexplained abbreviations.
Before you publish
- Choose only dimensions your reporting needs.
- Assign a campaign owner and maintain a register.
- Keep destination paths, IDs, and macros unchanged during normalization.
- Export local taxonomy deliberately; it is not team synchronization.
References and further reading
Our worked examples explain a workflow; platform behavior can change. Report a correction with a synthetic example.