Chamko

Websites & tools

Build a Marketing UTM Naming Convention That Teams Can Maintain

This guide establishes a consistent way to label campaign links so traffic sources remain interpretable across people, platforms, and reporting periods. It covers…

By Chamko Research Team Updated 4 min read

Quick answer

This guide establishes a consistent way to label campaign links so traffic sources remain interpretable across people, platforms, and reporting periods. It covers…

Related topics: campaign tracking parameters; UTM governance; marketing analytics consistency

Overview

This guide establishes a consistent way to label campaign links so traffic sources remain interpretable across people, platforms, and reporting periods. It covers parameter definitions, controlled values, preflight testing, and legacy reporting.

Why campaign naming needs a shared rule

Campaign tracking breaks down when each person invents names independently. One campaign may appear as “Diwali Sale,” “diwali_sale,” and “festival-promo” in analytics, making reports harder to compare. UTM parameters help identify where a tagged visit came from, but inconsistent values create fragmented reporting and false confidence in channel comparisons.

A naming convention is a small data-governance system. It defines allowed values, separators, casing, abbreviations, and who approves new campaign names. The aim is not to make every tag long or complicated. It is to make each value understandable to the people who will use the reports months later. Keep the convention simple enough that a busy colleague can follow it without asking the original campaign owner.

Define each parameter and its purpose

Use source to identify the referring platform or publisher, medium to classify the channel type, campaign to name the initiative, and optional content or term parameters to distinguish creative variants or paid-search terms. Choose definitions before tagging begins and document examples. For example, use a consistent source value for a social platform and a separate medium value for paid social, rather than putting both concepts into one field.

Avoid changing a parameter’s meaning to suit a particular campaign. If “medium” sometimes means channel type and sometimes means placement, the resulting reports will be difficult to interpret. Use optional parameters only when the team will actually analyse them. Excessive tagging can create maintenance overhead and accidental disclosure if personal or confidential information is placed in a URL.

Create a controlled vocabulary

Write a short vocabulary list for recurring sources, media, campaign types, and creative variants. Decide whether values use lowercase letters, hyphens, or underscores, and apply that rule consistently. Prefer readable words over private abbreviations that only one team understands. Include examples of valid and invalid tags, plus a process for requesting a new value when a new platform or partner appears.

A shared spreadsheet can work for a small team if it has a named owner, protected definitions, and a visible update history. A form or URL builder can reduce typing errors, but the tool should enforce the same rules rather than becoming a second source of truth. Never place email addresses, phone numbers, customer names, or other personal details in campaign parameters. URLs may be shared, stored, and exposed in logs.

Handle legacy names and reporting changes

Do not silently rename a campaign while it is active unless the reporting implications are understood. Historical data may retain the original value, and a new value can split the campaign into two rows. For a new naming rule, choose an effective date, explain the change, and apply the standard to new campaigns first. Create a mapping table for legacy values if reports need a consolidated view.

Review the most common “other,” “unknown,” or unexpectedly fragmented campaign values monthly. Investigate the cause before correcting the data. Some errors can be fixed in the source workflow; others may require report-level grouping. Keep the original raw values available for audit and avoid rewriting historical data without a clear reason. The goal is to improve future consistency while preserving the meaning of existing records.

Example naming scheme and operating checklist

A small retailer might use source values such as google, instagram, or newsletter; medium values such as paid_search, paid_social, or email; and a campaign value that combines an initiative with a period, such as monsoon_service_2026. The exact vocabulary matters less than consistent definitions and repeatable use. Keep creative variants in a separate field rather than embedding every detail in the campaign name.

Before launch, confirm the destination, required parameters, spelling, privacy, redirect behaviour, and analytics capture. After launch, inspect the first recorded visits and correct problems early. Assign one owner to maintain the vocabulary and one campaign owner to verify each tagged link. This modest discipline makes performance reports easier to compare and reduces the time spent guessing which rows represent the same initiative.

Key takeaways and next steps

A maintainable UTM system depends on clear definitions, a controlled vocabulary, and checks at the moment links are created. Start with the channels and campaign types the business actually uses, publish a one-page standard, and remove optional complexity that nobody analyses. Review recurring errors and keep legacy mappings documented.

For the next campaign, create the tagged URL from the shared builder, test it in the live journey, and save it in the campaign record. After a month, check whether the report is easier to read and whether staff still invent unapproved values. Improve the rule where real use reveals friction, but keep the core definitions stable. The purpose is trustworthy measurement, not tracking parameters for their own sake.

Key takeaways

  • Define source, medium, and campaign consistently before creating links.
  • Keep a controlled vocabulary with a named owner and readable values.
  • Never put personal or confidential information in tracking parameters.
  • Test redirects and analytics capture on the live destination.
  • Map legacy names instead of silently rewriting historical reporting.

Conclusion and next steps

Publish a one-page naming standard and use it for the next campaign rather than trying to clean every historical tag at once. Review the first month of reports, fix recurring sources of inconsistency, and keep the rule stable enough that trends remain comparable.

Keep reading