UTM Naming Convention Template for Small Teams

Campaign links are easier to compare when everyone uses the same names for source, medium, and campaign. This UTM naming convention template gives small marketing teams a shared format, practical examples for email, paid social, and partner campaigns, and rules for avoiding inconsistent reporting values.

Key Takeaways

• Agree on a short list of approved values for utm_source and utm_medium before launching campaigns.
• Use lowercase letters and one separator consistently; the examples below use underscores.
• Give each campaign a stable, descriptive name, and use utm_content to distinguish creative or link placements when needed.
• Never put personal, confidential, or sensitive information in UTM values.

A reusable UTM naming convention template

Use this as a starting point, then record your team’s approved source and medium values in a shared document:

A compact naming pattern to copy is:

utm_source={platform_or_partner}
utm_medium={approved_channel}
utm_campaign={initiative_audience_or_offer_period}
utm_content={creative_or_placement}

Treat the words in braces as placeholders, not literal values. Keep names descriptive enough for your team to recognize later, but avoid turning them into long sentences. Choose one format for dates or periods—such as q2—and use it consistently. If you do not need to distinguish a creative or placement, leave utm_content out rather than inventing a value.

Why lowercase and consistent separators help

Campaign reports group visits using the values they receive. If the same source is tagged as Instagram, instagram, and ig, those labels can show up as separate values, depending on the analytics platform and report. That makes totals harder to compare and may require cleanup or mapping later.

Lowercase names reduce accidental capitalization differences. A consistent separator makes multiword values easier to read and copy. This template uses underscores, but hyphens can work too: the important part is to choose one convention and stick to it. Do not mix spring-launch, spring_launch, and spring launch for the same campaign.

Examples for common campaign types

The examples use example.com as a stand-in domain. Replace it with your own landing page, preserving any existing query parameters when you build the final URL.

Email campaign

https://example.com/pricing?utm_source=monthly_newsletter&utm_medium=email&utm_campaign=spring_launch_new_customers_q2&utm_content=hero_cta

Use a stable source name for the newsletter and email as the medium. If the team sends several newsletters, name each source according to an agreed rule—for example, monthly_newsletter—rather than alternating between a publication name, an email tool name, and newsletter without a distinction.

Paid social campaign

https://example.com/product?utm_source=instagram&utm_medium=paid_social&utm_campaign=spring_launch_new_customers_q2&utm_content=video_a

Here, instagram identifies the source and paid_social identifies the medium. Use utm_content to distinguish ads or placements when that distinction is useful in your reporting. If the campaign runs on multiple platforms, keep the campaign name consistent and change the source for each platform.

Partner campaign

https://example.com/guide?utm_source=acme_partner&utm_medium=partner&utm_campaign=spring_launch_new_customers_q2&utm_content=partner_newsletter

Use the partner’s agreed name as the source. If your team classifies partner referrals differently, choose one medium—such as partner or referral—and document when to use it. The example is a convention, not a universal channel taxonomy.

You can assemble tagged links with the UTM Builder, then check that the resulting parameter values match your team’s naming rules. A builder can help create a URL; it cannot decide which names your team should standardize on.

How inconsistent names create reporting rows

These links may represent the same campaign to your team, but their values are not identical:

?utm_source=Instagram&utm_medium=paid-social&utm_campaign=SpringLaunch
?utm_source=instagram&utm_medium=paid_social&utm_campaign=spring_launch
?utm_source=ig&utm_medium=paid_social&utm_campaign=spring_launch

They vary in capitalization, separators, and source abbreviation. An analytics report may list these as different values rather than combine them. Before launch, compare a proposed link with the shared naming list. When cleaning up existing reports, define a deliberate mapping for old values; changing future tags alone does not necessarily combine historical data.

Keep personal and sensitive information out of UTM values

Do not include a person’s name, email address, phone number, account ID, customer ID, or other information that identifies or could be linked to an individual in any UTM parameter. Avoid sensitive information such as health details, financial data, private offer eligibility, or confidential internal project names as well.

UTM values are part of a URL. URLs can be stored in browser history, analytics systems, server logs, shared messages, and other systems. Encoding a value or making it hard to read does not make sensitive information safe to put in a link. Use non-identifying labels such as new_customers or segment_a only when your organization permits them and they cannot reveal private information about a person.

A simple team workflow

1. Agree on the vocabulary. List approved sources and mediums, including how to name new platforms and partners.
2. Set the format. Choose lowercase and a separator, then define a campaign pattern and date or period style.
3. Make a link. Add the required values and optional content value to the landing-page URL. Preserve existing query parameters; a URL with a query string already uses & to add another parameter.
4. Review before sharing. Check spelling, capitalization, separators, destination, and privacy. Compare each value with the shared list.
5. Keep the list current. Assign someone to add new platforms and partners, and note when older labels should be mapped or retired.

Common Mistakes

• Changing names between links: email, newsletter, and e-mail may be treated as different medium values. Choose one approved label for the intended channel.
• Using a new campaign name for every creative: Keep utm_campaign stable across the campaign; use utm_content for the creative or placement difference you want to compare.
• Putting everything in the source: The source identifies where the visit came from; the medium describes the channel. Avoid values such as instagram_paid_video in source if your reporting convention separates those concepts.
• Adding unnecessary parameters: More tags do not automatically make reports more useful. Include optional content only when you plan to use the distinction.
• Putting private information in the URL: UTM parameters are not a secure storage method, even if the URL is only sent to a targeted audience.
• Replacing an existing query string carelessly: If the destination already has parameters, append UTMs with & rather than adding a second ?, and verify that the destination still works.

Best Practices

• Keep a short, shared naming guide with examples and an owner.
• Prefer stable, readable labels over team-specific shorthand.
• Use the same campaign value across channels when you want to compare those channels as part of one initiative.
• Decide what utm_content is meant to distinguish before using it; avoid mixing creative names, audience names, and placement labels without a rule.
• Review campaign links before launch and periodically check reports for unexpected spelling or casing variants.
• Keep personal, confidential, and sensitive information out of every URL parameter.

Conclusion

A useful UTM convention is one your whole team can apply consistently. Start with approved source and medium values, a repeatable campaign pattern, and optional content labels for meaningful differences. Document the rules, check links before sharing, and keep private information out of URLs.