How to Create a UTM Naming Convention Your Team Can Maintain

A UTM naming convention is a small set of shared rules for labeling campaign links. Without one, the same channel can appear under several spellings in reports, making results harder to compare. This guide gives you a practical template for utm_source, utm_medium, and utm_campaign, plus examples and a lightweight way to manage exceptions as a team.

Key Takeaways

• Use lowercase values and one separator consistently; agree on the rules before creating links.
• Keep source for the platform or partner, medium for the channel type, and campaign for the specific initiative.
• Treat the examples below as starting points, not universal naming rules.
• Write down exceptions and review the convention when your team, channels, or reporting needs change.

A simple UTM naming template

Start with three fields. They cover many everyday campaign links without requiring a long taxonomy:

A useful starting pattern is:

utm_source=<platform-or-partner>
utm_medium=<channel-type>
utm_campaign=<initiative>

For example, a link in a newsletter promoting a spring product launch might be:

https://example.com/product?utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch

The labels are decisions your team makes, not values that should be copied blindly from this article. The important part is applying your chosen meanings consistently. Keep the campaign value identifiable without turning it into a sentence or packing every detail into it.

Why capitalization and separators matter

Reporting tools may treat Email, email, and EMAIL as different values. In systems that distinguish capitalization, inconsistent spellings can split what your team intended to measure as one source or medium. Other tools may normalize values differently, so check how your own reporting setup handles them.

Choose a rule that is easy to follow. For example:

• Use lowercase ASCII letters and numbers.
• Use underscores between words: paid_social.
• Avoid spaces, which may be encoded in URLs and can be harder to scan.
• Avoid switching between separators, such as paid-social, paid_social, and paid social.

The separator itself is less important than agreeing on one. If your analytics reports or other systems already rely on a particular format, follow that format and document it.

Examples for common campaign types

These examples show one possible convention. Adjust the values to match your channels, reporting platform, and existing data.

Email

utm_source=monthly_newsletter
utm_medium=email
utm_campaign=2025_summer_sale

Here, the source identifies the specific newsletter, while the medium stays at the channel level. A team that sends several email types might choose newsletter, product_update, or another source naming pattern instead.

Paid social

utm_source=instagram
utm_medium=paid_social
utm_campaign=2025_summer_sale

This separates the platform from the paid channel type. If your team needs to distinguish creative versions, consider using utm_content for that detail rather than creating a new medium for each ad format.

Partner campaign

utm_source=partner_acme
utm_medium=referral
utm_campaign=2025_summer_sale

A team might instead use a medium such as partnership if that better fits its reporting. Choose one definition, record it, and use it consistently; do not assume that referral or any other label is the right choice for every organization.

Keep the convention maintainable

A naming scheme becomes difficult to use when it tries to encode every possible detail. Start with a short shared standard and add fields only when they answer a real reporting question.

A one-page reference or shared spreadsheet can include:

1. Definitions: What your team means by source, medium, and campaign.
2. Formatting rules: Capitalization, separators, and how to handle abbreviations.
3. Approved values: A short list of common sources and mediums—not a list so long that nobody can find the right option.
4. Examples: A correct example for each channel your team uses.
5. An owner: Who can approve changes and update the document.

If an exception is necessary, record the value, why it differs from the convention, who approved it, and whether it is temporary or permanent. For example, a partner may require a particular source label. Note that requirement rather than silently changing the label for one link and leaving the next person to guess.

Review the document periodically and when a new channel, platform, or reporting need appears. Check a sample of recently created links for inconsistent capitalization, separators, or meanings. When changing a convention, consider how old and new values will appear side by side in historical reports; renaming future links does not automatically rewrite past campaign data.

Common Mistakes

• Changing case or separators from link to link: PaidSocial, paid-social, and paid_social may not group together in reports.
• Using source and medium interchangeably: Decide which field names the platform or partner and which names the channel type.
• Putting every detail in the campaign value: Long, inconsistent campaign names are harder to create and compare. Use an optional field such as utm_content for distinctions like creative versions when that fits your reporting setup.
• Treating example values as universal standards: A label is useful only if it has a clear, shared meaning in your organization.
• Leaving exceptions undocumented: One-off values can become accidental conventions if nobody records why they exist.
• Putting personal or confidential information in a URL: Query parameters can be exposed in browser history, logs, analytics systems, and shared links. Use campaign labels, not names, email addresses, or other sensitive data.

Best Practices

• Keep the initial convention small enough that people will actually use it.
• Use a shared document or link-building workflow as the source of truth; avoid relying on memory or old links.
• Check the final URL before publishing, especially if a destination already has query parameters.
• Test how your analytics reports group the chosen values before standardizing a large campaign.
• If a value must differ, document the reason and decide whether it is an exception or a change to the convention.

Conclusion

A maintainable UTM naming convention is one your whole team can apply without guessing. Agree on the meaning and format of source, medium, and campaign; use consistent capitalization and separators; and keep a short, updated record of approved values and exceptions. Start simple, then add complexity only when it improves a real reporting decision.