UTM naming conventions: keep campaign links readable and reporting consistent

Agree on meanings

Decide how the team names a traffic source and marketing medium. Keep spelling and capitalization consistent so equivalent links do not appear as unrelated categories. Campaign names should identify a meaningful initiative or buying situation.

Use content values when they answer a real creative or placement question. Do not encode every production detail if nobody will use it in a decision.

Create the convention

1. Write a small approved vocabulary for sources and media.
2. Choose a campaign format that includes only useful identifiers.
3. Define when content or term values are needed.
4. Store the final destination and tagged link in a shared record.
5. Test the link and verify how the visit appears in the reporting system.

Avoid putting names, email addresses or other personal information into URL parameters. Links can be copied, logged and shared beyond the intended audience.

Working convention table

Worked example: consistent classification

Illustrative example: one team uses “newsletter,” another uses “email” and a third uses a differently capitalized value for the same intended medium. Reports can split the activity in confusing ways. A shared convention defines the classification and updates future links consistently.

The repair should not pretend historical records automatically become comparable. Annotate the change and account for the old vocabulary during analysis.

Keep internal navigation separate

Campaign tags are intended to describe acquisition context. Adding them indiscriminately to internal website links can complicate interpretation in analytics tools. Use an appropriate internal interaction event when the question is about navigation inside the site.

Do UTMs guarantee perfect attribution?

No. Consent, browser behavior, redirects and reporting rules still affect what can be observed. They improve classification when implemented consistently.

Should every link include every parameter?

Use the parameters required for the reporting question and the tool's current guidance. Extra detail without a decision purpose adds maintenance work.