UTM tags are useful only when your team can interpret them consistently later. A simple naming convention for a small business can keep campaign reports readable without turning every link into a naming project. This guide gives you a reusable template and examples for email, paid social, and partner campaigns.
Key Takeaways
- Agree on a small vocabulary for
utm_source,utm_medium, andutm_campaign; useutm_contentonly when you need to tell links or creative apart. - Pick one casing style and one separator, then keep both consistent.
- Treat the examples below as starting points, not universal standards. Choose names that fit your own reporting.
- Keep a shared list of approved values so teammates do not invent near-duplicates.
A practical UTM naming template
Use this pattern for each campaign URL:
utm_source=[publisher_or_platform]
utm_medium=[channel_type]
utm_campaign=[period]_[initiative]
utm_content=[creative_or_link_label]
For example:
utm_source=customer_newsletter&utm_medium=email&utm_campaign=2025_spring_sale&utm_content=hero_cta
The fields answer different questions:
| Parameter | What to record | Example |
|---|---|---|
utm_source | The platform, publication, or partner that sent the visitor | customer_newsletter |
utm_medium | The broad channel type | email |
utm_campaign | The shared promotion or initiative, optionally with a period | 2025_spring_sale |
utm_content | A specific creative, placement, or link when comparison is useful | hero_cta |
Start with the first three fields. Add utm_content when you need to distinguish, for example, two buttons in one email or two creative versions in one campaign. If you do not plan to use the distinction in reporting, leave it out.
Choose one format and stick with it
This template uses lowercase values and underscores between words. Your team could instead choose hyphens; the important part is to choose one approach and document it. Avoid mixing SpringSale, spring-sale, and spring_sale for the same initiative.
In analytics reports, spelling and capitalization differences can split what your team considers one source or campaign into separate values. A shared separator and vocabulary also make names easier to search and compare. Use plain, descriptive words, and do not put sensitive information such as customer names or email addresses in a URL.
Examples for common small-team campaigns
These examples show one possible convention. They are not prescribed values: choose terms that match your channels and the way your team wants to report.
utm_source=customer_newsletter
utm_medium=email
utm_campaign=2025_spring_sale
utm_content=hero_cta
Here, customer_newsletter identifies the particular sender or publication, while email describes the channel. If you send several newsletters, you might use a stable source name and distinguish each send in the campaign name, such as 2025_spring_sale_april.
Paid social
utm_source=linkedin
utm_medium=paid_social
utm_campaign=2025_spring_sale
utm_content=carousel_testimonial
Use a medium label your team applies consistently to paid social traffic. If you use platform-specific campaign names, keep the platform in utm_source and the shared promotion in utm_campaign so you can compare results for the same promotion across channels.
Partner campaign
utm_source=acme_partner
utm_medium=partner
utm_campaign=2025_spring_sale
utm_content=partner_blog_link
A team that groups partner referrals under a different medium could choose that label instead. Decide once, record the choice, and use it consistently. Do not assume that another business’s vocabulary will match your reports.
Put the convention into a lightweight workflow
- Create a short naming guide. Record the approved source and medium values, casing, separator, and campaign format in a shared document or spreadsheet.
- Name the campaign once. Agree on the
utm_campaignvalue before creating links for different channels. Reuse it where the links belong to the same initiative. - Add only useful distinctions. Use
utm_contentfor a comparison you intend to review, not as a place to store every detail about an ad. - Build and inspect the URL. Add the parameters to the landing-page URL, then check that the destination and parameter values are correct. A URL-building tool can help assemble a link, but it cannot decide your team’s vocabulary for you.
- Test the reporting path. Open a tagged link in a controlled test and confirm that your analytics setup records the campaign as expected. Reporting behavior can depend on the analytics product and implementation.
- Review names periodically. Add legitimate new sources when needed, but avoid creating spelling variants for existing ones.
Google Analytics uses campaign URL parameters to collect campaign information. The precise reporting details and available fields can change, and I could not consult current Google Analytics documentation while preparing this article. Before standardizing a workflow around a specific Analytics report or parameter, verify the current Google guidance and check it against your own property and reporting needs.
Common Mistakes
- Changing case between links:
LinkedInandlinkedinmay show up as different values in reports. Choose a case style and apply it everywhere. - Using inconsistent synonyms: Mixing
paid-social,paid_social, andsocial_paidmakes a shared channel harder to analyze. Keep an approved list. - Putting different concepts in one field: Keep the platform or sender in
utm_source, the channel type inutm_medium, and the initiative inutm_campaign. - Making campaign names too specific: If every channel gets a completely different campaign label, it becomes harder to compare channels for one promotion. Reuse the campaign name when the effort is shared.
- Adding tags without a reporting purpose: More parameters and more elaborate names create more opportunities for inconsistent data. Add a distinction only when someone will use it.
- Assuming the example vocabulary is mandatory: Labels such as
email,paid_social, andpartnerare practical choices, not universal standards for every team or analytics setup.
Best Practices
- Keep a single source of truth for approved values and have one person or role maintain it.
- Use lowercase and a single separator throughout your UTM values.
- Keep names short enough to scan, but descriptive enough to recognize later.
- Agree on the campaign name before teammates publish links through different channels.
- Avoid changing a value midway through a campaign unless there is a clear reporting reason; document any change.
- Remember that UTM values are visible in the URL and may be shared or logged. Never place confidential or personally identifying information in them.
Conclusion
A maintainable UTM naming convention does not need many rules: define what each field means, choose a consistent format, and keep an approved vocabulary. Start with the template, adapt its labels to your reporting needs, and check that the resulting campaign data is useful in your analytics setup.
