UTM Naming Checklist for Consistent Campaign Tracking

A UTM naming convention checklist helps your team create tracking links that are consistent, readable, and easier to compare in analytics reports. Set rules for capitalization, separators, campaign names, and parameter use before launching links, then apply those rules every time.

UTM parameters are short values added to a URL so analytics tools can identify details about a visit, such as its traffic source or campaign. A simple standard prevents small differences—like “Email,” “email,” and “e-mail”—from splitting related traffic into separate labels.

UTM naming convention checklist

Use this checklist when you create a campaign tracking link or review one prepared by a teammate:

• Choose one format: Decide whether values use lowercase, hyphens, underscores, or another consistent style.
• Define each parameter: Write down what your team means by source, medium, campaign, content, and term.
• Name the source precisely: Use the platform, publication, partner, or other origin that sent the visit.
• Use a controlled medium list: Agree on a small set of channel labels, such as email, paid_social, or referral.
• Use a repeatable campaign pattern: Include the details your reporting needs, in a predictable order.
• Reserve content for variations: Use it to distinguish specific links, placements, or creative versions.
• Skip parameters that add no value: Leave optional fields blank when you do not have a clear reporting use for them.
• Check the destination: Confirm the link opens the intended page and retains all required parameters.
• Record the link: Add the final URL and its naming details to a shared campaign log.

What each UTM parameter is for

UTM parameters are added to the end of a destination URL after a question mark. If the URL already contains a query string, additional parameters are joined with an ampersand. The values are labels you choose; they are not a complete campaign strategy on their own.

For most manually tagged links, source, medium, and campaign are the core fields to define. Content and term are optional. Their usefulness depends on your campaign and analytics setup, so do not fill them just to make every link look complete.

How to create a consistent UTM naming system

1. Pick a case and separator rule

Choose one style and document it. Lowercase values with underscores or hyphens are easy to scan, for example paid_social or product-launch. The particular separator matters less than applying the same one across your links.

UTM values can appear as distinct labels in analytics reporting when their spelling or capitalization differs. If one person uses LinkedIn and another uses linkedin, the results may be harder to compare. Agree on the canonical spelling, then use it everywhere.

2. Set definitions for source and medium

Source and medium answer different questions. Source identifies where a visit came from; medium describes the channel or method. For example, a company newsletter could be the source and email the medium. A social platform might be the source and paid_social the medium for a paid placement.

Create an approved list for common sources and mediums. Include examples and explain how to handle edge cases, such as partner newsletters or organic social posts. Avoid changing labels based on personal preference or the wording used in a campaign brief.

3. Build a predictable campaign name

A campaign value should identify the initiative clearly without becoming a long, unstructured sentence. Your team might combine a product or offer, an audience, and a time period—if those details are useful for reporting. Choose a fixed order so campaign labels are easier to scan and sort.

For instance, a team might use a pattern like product-audience-period. Treat the pattern as a rule rather than a one-off example. If a date or region is not important to your reporting, leave it out instead of adding detail that nobody will maintain.

4. Use optional fields only for useful comparisons

Use utm_content when you need to compare two or more links within the same campaign, such as a header link and a footer link. Pick a concise naming rule that makes the difference obvious. Avoid changing the value to describe details that are already captured elsewhere.

Use utm_term when it has a defined purpose in your reporting, such as identifying a paid search term. Do not assume every channel needs a term value. Consistent blanks are better than invented labels that create noise.

5. Generate, inspect, and log the URL

1. Copy the destination page’s full URL and verify that it is correct.
2. Choose the parameters you actually need for the campaign.
3. Apply your approved source, medium, and campaign values, plus any useful optional values.
4. Review the completed link for spelling, separators, and duplicate or missing parameters.
5. Open the link to check that it loads the intended destination.
6. Save the final URL and its purpose in your shared campaign log.

You can create a tagged URL with the UTM Builder. Before sharing the result, compare its values with your team’s naming guide and check that the destination page is correct.

Common UTM naming mistakes to avoid

• Mixing capitalization: Inconsistent case can create separate-looking labels in reports. Standardize values before a campaign goes live.
• Using source and medium interchangeably: Decide which value identifies the origin and which identifies the channel.
• Creating new labels for familiar channels: Several spellings for the same platform or channel make comparisons less clear.
• Putting changing details into every field: Too many unique values can make summaries difficult to interpret.
• Tagging internal links casually: UTM parameters are designed to label campaign traffic. Adding them to links between pages on your own site can affect how visits are attributed, depending on your analytics setup. Follow your analytics team’s guidance.
• Sharing URLs with typos or the wrong destination: A tracking label cannot compensate for a broken or incorrect landing page.
• Including sensitive information: Query parameters may be visible in the URL, browser history, and logs. Never put personal or confidential data in UTM values.

Keep the convention useful as your team grows

Put your naming rules somewhere everyone who creates campaign links can find them. Include approved values, examples for common channels, and a simple process for proposing a new label. Review the guide when your marketing channels or reporting needs change, not every time someone prefers a different word.

A central campaign log is also useful. Record the destination, final tagged URL, campaign owner, and the meaning of any nonstandard values. This makes it easier to check an old link, reuse a pattern, or understand a report without guessing what a label meant.

The goal is not to make every UTM link complicated. It is to make similar campaigns use similar labels, so your analytics are easier to interpret. A short convention that people follow is more practical than a detailed system that is difficult to maintain.

Frequently asked questions

Which UTM parameters should I use every time?

For many manually tagged campaign links, source, medium, and campaign provide the essential context. Use content and term only when they answer a specific reporting question.

Should UTM values be lowercase?

Lowercase is a practical choice because it reduces accidental variations. The important rule is to choose one style and use it consistently.

Do UTM parameters change the destination page?

They are added to the URL, and many sites still load the same page with those parameters attached. Test the link to confirm your destination handles it as expected.

Can I put a person’s name or email address in a UTM value?

No. URLs can be exposed in browser history and server or analytics logs. Keep personal and confidential information out of tracking parameters.

How can I keep campaign names consistent across a team?

Publish a short naming guide with approved source and medium values, a campaign-name pattern, and examples. Use a shared campaign log and review links before launch.