A campaign can have one objective, one audience and one offer, yet appear in analytics as several unrelated records. An email link uses utm_campaign=autumn_launch, a paid advert uses Autumn-Launch, and a partner link shortens it to launch. The campaign is coherent to the people running it, but the reporting labels say otherwise.

This usually happens because links are built at different times by different people or platforms. Each value seems reasonable in isolation. The problem only becomes visible when someone tries to compare performance across the whole campaign.

A UTM naming convention prevents that fragmentation. It defines how campaign URL tracking values will be written, who controls them and where approved names are recorded. For a UK SME, the convention does not need to be elaborate. It needs to be clear enough that a colleague, agency or supplier can build a link without inventing another version of the campaign name.

Why One Campaign Becomes Several Conflicting Records

UTM parameters pass campaign information through a destination URL. When someone clicks the link, those values can appear in analytics as dimensions such as source, medium and campaign. Google Analytics campaign URL guidance identifies utm_source, utm_medium and utm_campaign as the parameters that should always be used when adding campaign parameters.

Those three fields answer different questions. The source identifies where the traffic originated, the medium describes how it arrived, and the campaign connects the visit to a particular marketing effort. If the distinction between those fields is not agreed in advance, values begin to overlap.

For example, one person might enter linkedin as the source and paid-social as the medium. Another might enter linkedin-ads as the source and social as the medium. Both links refer to paid activity on the same platform, but the resulting records cannot be compared cleanly without further interpretation.

Case and formatting create quieter versions of the same problem. Spring_Sale, spring-sale and spring_sale are three labels, even if everyone intended them to represent one campaign. Spaces, abbreviations and date formats introduce further variations. Analytics receives the value in the URL, not the explanation behind it.

A naming convention therefore has two jobs. It defines what each parameter means and controls the vocabulary permitted within it. Both are necessary. Agreeing that utm_medium describes the traffic type is not enough if team members can still choose among paid-social, paidsocial, social-paid and cpc-social.

Define The Campaign Identity Before Building Links

Start with the campaign itself rather than with the URL builder. A campaign name should represent the shared marketing effort across its different placements. If email, paid media and partner activity all support the same launch, they should use the same utm_campaign value.

This is where the tagging convention connects to the wider marketing strategy. The campaign needs a defined objective, audience and set of activities before its tracking labels can be consistent. UTM parameters can describe an agreed structure, but they cannot resolve a campaign that different stakeholders understand differently.

Choose a repeatable structure for utm_campaign. A useful value might combine a stable campaign name with a period or market where those distinctions genuinely matter. For example, service_launch_2026_q3 identifies an initiative and its operating period. If the same campaign is not being reused across periods, adding a date may create unnecessary detail. Include a component because it separates records that the business will need to compare, not because every possible field must be filled.

The same restraint applies to internal terminology. A code such as sl26q3 may be quick for the person who created it, but opaque to a colleague reviewing the report six months later. Full descriptive names are usually easier to govern, provided they stay concise and follow one format.

Record the approved campaign value before anybody creates a live link. This turns the name into a shared identifier rather than a suggestion. The campaign register should also show the plain-English campaign title, owner, destination page and active period. Those details help a reviewer establish whether a proposed value belongs to an existing campaign or requires a new entry.

Set Controlled Values For Source And Medium

Once the campaign identity is fixed, define a controlled vocabulary for utm_source and utm_medium. These fields should remain distinct even when a platform name feels as though it could fit into either one.

Use utm_source for the specific referrer or origin. Depending on the activity, values could include a platform, publication, partner or named mailing stream. Use utm_medium for the broader method by which the visit arrives, such as email, cpc or banner. These examples reflect the source and medium distinctions used in Google Analytics guidance, but your register should contain only the values your campaigns actually use.

The practical test is whether the fields support two levels of comparison. A team may want to review all email traffic together through the medium, then distinguish one mailing source from another. If source and medium both contain improvised combinations of platform, placement and campaign name, that comparison becomes harder.

Set formatting rules alongside the vocabulary. A compact convention for an SME could require:

• lowercase values throughout
• underscores between words
• no spaces or unexplained abbreviations
• one approved term for each source and medium
• the exact registered campaign value in every campaign link

This is the only part of the convention that needs to feel rigid. Consistent formatting keeps equivalent values together and makes errors easier to spot. It also removes small decisions from link building. The person creating a URL should select an approved value, not debate whether paid_social or social_paid looks better.

Avoid putting information into more than one parameter. If the source is linkedin, the medium does not also need to be linkedin_paid_social. A value that repeats other fields becomes harder to maintain and produces longer URLs without adding a useful reporting distinction.

Use Content And Term Fields Only For Meaningful Distinctions

The optional fields should answer specific questions that the core three fields cannot answer. utm_content can distinguish creatives or links within the same source, medium and campaign. Google’s guidance gives the example of using it to tell apart two calls to action in one email.

That does not mean every design detail needs its own value. If the business will not review performance by button position, image treatment or message variation, recording all of those elements creates administrative work without improving the eventual decision. Use utm_content when there is a real comparison to preserve.

A controlled content value might identify a recognised creative or placement, such as testimonial_ad_a or email_header_cta. The exact pattern matters less than its stability. If one person records the asset name, another records its visual colour and a third records its position, the values will not support a consistent comparison.

utm_term is intended for paid keyword information. It should not become a spare field for audience names, internal notes or campaign dates. Overloading it may make the immediate URL convenient, but it weakens the meaning of the resulting dimension.

For many links, utm_source, utm_medium and utm_campaign will provide the necessary structure. Add utm_content or utm_term only when the distinction has been defined and somebody expects to use it. A smaller, well-governed dataset is more useful than a detailed one whose values mean different things from campaign to campaign.

Manage Manual Tagging Alongside Platform Auto-Tagging

Manual tagging and platform auto-tagging can exist within the same marketing operation. Google Analytics explains that integrations with advertising platforms may use auto-tagging, while destination URLs can be manually tagged with UTM parameters to collect traffic-source information.

That makes ownership important. A team managing email, partner links and pay-per-click management should not assume that every platform handles campaign information in the same way. Before adding manual parameters to an advert, check whether the platform integration already supplies traffic-source data and how analytics will treat the two methods together.

Google states that when manual and auto-tagging are used together, traffic-classification dimensions use auto-tagged values. It also notes that if an advertising click identifier cannot be used as intended and any UTM parameter is present, Google Analytics can derive cross-channel traffic-source values exclusively from the UTM parameters. This is a strong reason not to add one casual parameter to an otherwise auto-tagged link.

Where manual parameters are required, apply the complete relevant set using the approved register. Do not append a lone campaign label as a fallback and leave source or medium undefined. The convention should identify which links are manually tagged, which rely on integrations and who checks the final URL.

UTM parameters also have a defined scope. They label campaign traffic reaching the destination and make those labels available for reporting. They do not replace consent management, website tag configuration or customer relationship management governance. Keeping those responsibilities separate prevents a tidy URL scheme from being mistaken for a complete measurement setup.

Run Naming QA And Maintain The Register

The best time to find a tagging error is before the link is distributed. Once an email has been sent or an advert has started receiving clicks, correcting the URL may not repair the inconsistent records already collected.

Pre-launch QA should begin with the destination. Confirm that the untagged page loads correctly, then inspect the complete URL. Check that the question mark and parameter separators are in the right places, the destination has not been altered, and the registered values have been copied exactly. Open the final link rather than approving it from a spreadsheet alone.

Next, compare the values with the campaign register. The campaign name should match every other route supporting the same initiative. The source should identify the actual origin, and the medium should use an approved category. Optional content and term values should describe only the distinctions assigned to those fields.

The register should remain a working control document. Give one person or role responsibility for approving new values and resolving duplicates. If a genuinely new medium is required, add it once with a short definition and use it consistently thereafter. Do not let each campaign team expand the vocabulary independently.

Regular reporting can also reveal governance problems. Near-identical labels, unexplained values and campaigns split by capitalisation indicate that the convention is not being followed or is difficult to use. Correct the process that produced the variation, then update future links. Rewriting historical labels outside the collection process is a separate data-management decision and should not be treated as a substitute for better link control.

For most SMEs, the practical answer is a small campaign register and a short pre-launch check. Define the utm_campaign value first, select utm_source and utm_medium from controlled lists, and use optional parameters only for comparisons the team intends to make. Assign an owner, test the finished links and retain the approved values for the next campaign.

We plan and deliver measurable multi-channel campaigns with implementation and performance reporting. When URL governance forms part of that work, the useful starting point is not a more complicated attribution framework. It is an agreed naming register that everybody building campaign links can follow before those links go live.