A UTM naming convention that holds across clients.

A UTM tag is the only thing connecting a click the client paid for to what that person did afterwards. The ad platform knows the spend. Analytics knows the behaviour. The tag is what joins them.

The failure is quiet. Nothing errors. Someone writes Facebook instead of facebook, analytics creates a second source, one channel now reports as two, and every total that groups by source is wrong from that day on. Nobody notices for a quarter, and the rows already collected cannot be fixed after the fact.

Across a roster it multiplies. Each client's campaigns are tagged by different people, sometimes by the client's own team, and a convention that differs per client turns every question asked across clients into a list of exceptions.

Six of them. They are boring on purpose, because a convention only works if it is easy enough that a busy person follows it under pressure.

• Lower case, always

  Analytics tools treat Facebook and facebook as two different values. Lower case everything, with no exceptions, and you remove the most common cause of a split channel.

• Hyphens inside a value, never spaces

  A space becomes %20 in the URL and then appears in your reports as %20. Use hyphens inside a value and keep to one separator, so there is no decision to make while launching.

• Source is the platform, medium is the mechanism

  Source answers where the click came from, such as google or linkedin. Medium answers what kind of thing it was, such as cpc or paid-social or email. Swapping these two is the next most common mistake, and it makes channel grouping impossible.

• Put a date in the campaign name

  Campaigns repeat. A campaign called spring-sale run three years running collapses into one row. Lead with the year and the month and every run stays separate and sorts correctly.

• Content is the creative, term is the keyword

  Use content to tell two creatives apart inside the same campaign. Use term for the keyword on search. Leave either empty rather than inventing a value, because an empty field is honest and a guessed one is not.

• Never put anything private in a URL

  No names, no email addresses, and no client identifier you would not show in public. A tagged URL gets pasted into chats, forwarded and indexed. Treat it as public, because it is.

Source is the platform in lower case. Medium is one of a short fixed list you decide once, such as cpc, paid-social, email, affiliate or referral. Campaign is the year, the month, and then what is being sold and to whom, joined with hyphens. Content is the creative identifier. Term is the keyword.

The important part is not this exact shape. It is that the list of allowed medium values is short, fixed and written down, because medium is the field channel grouping depends on and the field people improvise in.

Most ad platforms can tag clicks automatically, and that tagging does not populate the UTM parameters. It adds a click identifier of its own instead.

If you use both automatic tagging and manual UTMs on the same campaign you can end up with two records for one click, or with the platform tag winning and your UTMs being ignored. Decide which one you rely on per platform, write that decision down beside the convention, and check it the moment a channel reports double.

A document is not enforcement. Nobody opens it at five on a Friday while launching a campaign. Give people a builder that only offers the allowed values, so the convention is the path of least resistance rather than a rule to remember. Agree it with each client at onboarding, including anybody on their side who launches campaigns, because a convention the client's team has never seen is one they will not follow.

Then audit. The useful query lists every source, medium and campaign value that appears on fewer rows than you would expect. A value appearing once is almost always a typo, and finding it in the first week is the difference between fixing it and living with it.

The connectors that carry UTM fields land them as their own tables, so the values each client's campaigns actually used are queryable next to the spend they came with rather than only inside an analytics interface.

That is what turns the audit above into a scheduled check instead of an afternoon of work. A source or medium value that appears once, for any client, can be flagged the week it appears.