A UTM Naming Convention Your Team Will Actually Follow

Your report has Facebook and facebook as two separate rows. It also has FB, and fb, and one called facebook_ad that somebody made in March.

That is not a tooling problem and buying something will not fix it. It is a convention problem, and the convention that fixes it is the one people can follow without thinking, which means it has to be short.

A note on who writes about this. Search this question and almost every result is published by a company that sells a UTM management tool. Those pages are not wrong and they all arrive at the same conclusion, which is that you need the product. This site sells nothing and names no tool, and the position below is that the convention is the thing that matters and the storage is a detail.

Why the duplicates happen

Two facts, and between them they account for nearly all of it.

The values are case sensitive. Facebook and facebook are two different values as far as the reporting is concerned, and there is no correction applied for you. This single behavior is responsible for the majority of split rows in the average account.

Nobody knows what the previous person did. A link built in a hurry, six months after the last one, by somebody who was not there when the last one was built. There is no autocomplete, no validation and no list, so each link is a fresh guess.

Add the fact that a mistake is permanent, because historical data is not retroactively renamed, and you get a report that fragments a little more every quarter.

The convention

Six rules. Not sixteen, because a convention nobody remembers is not a convention.

1. Everything is lower case, always

The single highest-return rule on this page. No exceptions, no proper nouns, no capitalized campaign names.

If you adopt only one thing from this article, this is it, and it alone will remove most of your duplicate rows going forward.

2. Hyphens between words, never spaces

Spaces get encoded and produce values with strange characters in them. Pick one separator and use it everywhere. Hyphens or underscores both work; mixing them does not.

3. Fixed values for source and medium

These two parameters are the ones that break reports, because they are the ones the reporting groups by.

Write down the permitted values for each. Ten or fifteen of them, not fifty. That list is the convention, and it is the artifact that has to exist somewhere findable.

Medium especially should be a very short list. It describes the type of traffic rather than the specific placement, and if it is growing past a handful of values it is being used as a campaign name.

4. Campaign describes the campaign, not the ad

The campaign parameter should tell you which initiative this was, and it should be the same across every link belonging to that initiative, whatever channel they are on. That is what makes it possible to see one campaign's total performance across channels, which is most of why the parameter exists.

A date in the value is worth considering if you run the same initiative repeatedly.

5. Content and term have specific jobs, and empty is a valid answer

These two are the ones nobody has ever had explained. They are for distinguishing between variants and for recording a keyword, and if you are not doing either, leaving them out is correct rather than lazy. That has enough detail to be its own subject on this site.

6. Never tag internal links

Putting campaign parameters on a link from one page of your site to another page of your site starts a new session and overwrites the original source. The visit that arrived from a paid ad becomes a visit from your own tagged link, and the acquisition data is gone.

This is the most damaging single mistake in this territory and it happens most often on internal banners and email links that point at another page of the same site. Our article on what direct traffic actually is covers where those overwritten sessions end up, and this is the version of the problem that is entirely self-inflicted.

Making it survive contact with a team

The convention is easy. Getting three people to follow it for a year is the actual problem, and it is a process problem rather than a technical one.

One place where links are built. A shared document, a shared sheet, a shared form. It does not matter what it is; it matters that there is one and that everybody knows where.

The permitted values are in that same place, visible while somebody is building a link rather than in a separate document nobody opens.

Every link that gets built gets logged, with the date and who built it. This is the part that gets dropped and it is the part that makes the next person's job possible.

And one person owns the list. Not to approve every link, but to be the person who decides when a new permitted value is added. A list anybody can extend is a list, not a convention.

Whether you use a tool for this is a genuine choice and not the point. A tool enforces the list, which is real value. A shared sheet with a strict list and a person who owns it produces the same reports. What does not work is a tool with no agreed list, which is what most accounts with a tool actually have.

What to do about the mess you already have

Do not rename historical values. Renaming does not reach back into data already collected, and attempting it produces a third variant of the same value rather than a corrected one.

Start the convention from a dated line. From this date, these are the values. Everything before that date is read as it is.

Group the old variants at the reporting layer rather than in the data, using whatever grouping or filtering your reporting supports. That is the correct place to reconcile history and it does not touch what was collected.

Cleaning up a year of inconsistent parameters without losing the history has enough detail to be its own article on this site.

What this fixes, and what it does not

It fixes: split rows, channels that appear twice, campaigns that cannot be totaled, and the specific frustration of not being able to answer how a campaign performed overall.

It does not fix anything about whether your conversions are recorded correctly, whether attribution is reaching your site at all, or whether the numbers you report mean what you think. Those are separate problems and they are usually larger. Our article on choosing what a conversion should actually measure is the one to read if the reporting problem is about the numbers rather than about the labels.

The one-line version

Everything lower case, a short fixed list of sources and mediums, one place where links get built, one person who owns the list, and never tag an internal link.

That is the whole convention, it fits on a card, and it is the version people actually follow.

Similar Posts