A UTM naming system is useful when several people can create campaign links that tell the same reporting story. Without agreed rules, one team might use Email, another email and another newsletter as the medium. The links still work for visitors, but the reporting becomes harder to interpret.
The solution is more than a long naming convention. Your team needs clear definitions, a small set of approved values, an easy way to build links and a process for checking them before publication. The system should reduce the decisions made under pressure when an email or advert is about to go live.
Start with the questions your reporting needs to answer. Then design a convention that preserves those distinctions without turning every link into a coded description of the entire campaign. Consistency is valuable when it supports a decision the business actually makes.
Define the reporting questions first
List the comparisons that matter. You may need to compare partner referrals with email campaigns, distinguish a paid placement from an unpaid post or assess several versions of a creative. Give each distinction a reason and an intended reporting view.
A campaign manager might ask which launch activity produced useful enquiries, while a content manager wants to compare links within a newsletter. Those questions need different levels of detail. The campaign name can connect the overall effort, while another field distinguishes the placement or creative.
Decide how this information relates to later business outcomes. A website visit, a submitted enquiry and a qualified opportunity are different events. UTM consistency can help organise acquisition information, but it cannot by itself prove that a campaign caused a sale.
Write the questions in ordinary language before assigning field values. This gives a new colleague a way to understand the convention without memorising unexplained abbreviations. It also helps identify fields that nobody uses and therefore need not complicate the process.
Give each parameter one agreed purpose
For manually tagged campaigns, define source, medium and campaign consistently, with additional parameters where useful. Google Analytics parameter values are case-sensitive. Agree conventions the team can apply and test the actual published links. Our analytics campaign tagging guide provides the related checks.
For an illustrative convention, source could identify the referring platform or named publisher, medium could identify the channel category, and campaign could identify the coordinated activity. A content value could distinguish a particular creative or placement when that comparison is required.
Keep those roles separate. If one person uses campaign to describe a channel while another uses it to describe an offer, the same column contains two different concepts. A shorter list of well-defined fields is more useful than a detailed list with unstable meanings.
Agree how identifiers are used where required by your reporting setup. A stable campaign identifier can support a registry even when the human-facing campaign description changes. Do not introduce extra identifiers unless someone can explain how they will be maintained and used.
Create a small controlled vocabulary
Choose a consistent case convention, such as lower case, and a simple separator for multi-word values. Then define approved source and medium values with examples. The important feature is that colleagues make the same choice for the same situation.
Check medium values against your analytics channel definitions before adopting them. A team can invent a perfectly consistent label that does not map as expected in its reporting tool. Confirm the intended classification using the platform's current rules and your own configuration.
Make the vocabulary accessible in the link builder. A dropdown or validated field reduces avoidable variation more effectively than expecting everyone to consult a separate document. Include a route for requesting a new value when a genuinely new activity appears.
Keep aliases out of new links once a value has been agreed. If the approved source is a full platform name, a colleague should not shorten it for convenience. Record historical variants separately, so older reporting can be interpreted without allowing the inconsistency to continue.
Design campaign names around stable distinctions
Imagine a business promoting an autumn service review through email, a partner article and a paid placement. The campaign can share one agreed name across those activities, while source and medium identify how each visitor arrived. Creative variations belong in their designated field rather than becoming separate campaigns accidentally.
Choose which details belong in the campaign name. A period, offer and audience may be useful, but avoid including every internal team label. A name should remain understandable when someone reads the report several months later.
Maintain a registry with the campaign name, identifier where used, purpose, owner, dates and approved destination. This provides context for the encoded values. It also helps prevent two different activities from receiving the same name or one activity from acquiring several names.
Be careful when naming reflects people or confidential activity. Use non-personal campaign labels and avoid embedding customer names, email addresses or sensitive details in URLs. Campaign parameters are unsuitable as a private customer record.
Give the team a reliable link-building workflow
Provide a builder that combines an approved destination with validated values. It can be a simple internal tool or a controlled spreadsheet, provided it prevents obvious omissions and generates a usable URL. The team should not need to type a long tagged address manually every time.
Include examples for the activities colleagues actually run. A partner newsletter, an organic social post and a display advert should each have a clear example. Explain which parts change for a new placement and which remain tied to the campaign.
Account for advertising platforms that use automatic tagging or dynamic parameters. Check the relevant integration rather than assuming manual UTMs replace it. Assign someone to approve the interaction between platform-generated information and the team's convention.
Version the rules when a meaningful change is made. Record when the new convention starts and how older values should be interpreted. Renaming everything without an effective date can make a trend report look as though performance changed when only the labelling changed.
Test the destination and the reporting result
Before publication, open the generated link and confirm that it reaches the intended page. Check any redirect, shortened link or external handover involved in the journey. A correctly constructed parameter string is not useful if the customer reaches the wrong offer.
Test the reporting result in an appropriate way for your analytics setup and visitor choices. Confirm the expected fields appear without collecting unnecessary personal data. Record the test conditions, because consent settings and other collection limits can affect what is observable.
Inspect how the page behaves with parameters present. Forms, navigation and campaign-specific content should still work. If the destination system changes the URL, establish whether the required information reaches the point where it is collected.
Use a brief pre-publication check with an owner. Verify the campaign, source, medium, optional detail and destination. This turns quality assurance into a repeatable step rather than a last-minute request to inspect a link nobody understands.
Review exceptions without confusing attribution with certainty
Check reports for unexpected values and missing classifications. Investigate a sample of the original links and publication routes before rewriting a reporting rule. The fault may be in the naming, the destination journey or the collection setup.
Explain limits when discussing results. A tagged link can be forwarded, revisited or encountered through an unexpected route. Collection can be incomplete, and later customer decisions involve other interactions. Use UTMs as organised evidence about recorded acquisition, supported by broader enquiry and CRM information.
Giraffe Digital's digital strategy service connects campaigns, customer journeys and measurement. A manageable UTM system helps those conversations begin with consistent labels and clear assumptions.
The best convention is one that colleagues can follow repeatedly. Keep definitions stable, make the builder easy to use, check real journeys and maintain the context behind the values. That makes campaign reporting easier to explain and easier to act on.
Frequently asked questions
How should we define the reporting questions first?
List the comparisons that matter. You may need to compare partner referrals with email campaigns, distinguish a paid placement from an unpaid post or assess several versions of a creative. Give each distinction a reason and an intended reporting view. A campaign manager might ask which launch activity produced useful enquiries, while a content manager wants to compare links within a newsletter. Those questions need different levels of detail. The campaign name can connect the overall effort, while another field distinguishes the placement or creative. Decide how this information relates to later business outcomes. A website visit, a submitted enquiry and a qualified opportunity are different events. UTM consistency can help organise acquisition information, but it cannot by itself prove that a campaign caused a sale.
How should we create a small controlled vocabulary?
Choose a consistent case convention, such as lower case, and a simple separator for multi-word values. Then define approved source and medium values with examples. The important feature is that colleagues make the same choice for the same situation. Check medium values against your analytics channel definitions before adopting them. A team can invent a perfectly consistent label that does not map as expected in its reporting tool. Confirm the intended classification using the platform's current rules and your own configuration. Make the vocabulary accessible in the link builder. A dropdown or validated field reduces avoidable variation more effectively than expecting everyone to consult a separate document. Include a route for requesting a new value when a genuinely new activity appears.
How should we design campaign names around stable distinctions?
Imagine a business promoting an autumn service review through email, a partner article and a paid placement. The campaign can share one agreed name across those activities, while source and medium identify how each visitor arrived. Creative variations belong in their designated field rather than becoming separate campaigns accidentally. Choose which details belong in the campaign name. A period, offer and audience may be useful, but avoid including every internal team label. A name should remain understandable when someone reads the report several months later. Maintain a registry with the campaign name, identifier where used, purpose, owner, dates and approved destination. This provides context for the encoded values. It also helps prevent two different activities from receiving the same name or one activity from acquiring several names.
How should we give the team a reliable link-building workflow?
Provide a builder that combines an approved destination with validated values. It can be a simple internal tool or a controlled spreadsheet, provided it prevents obvious omissions and generates a usable URL. The team should not need to type a long tagged address manually every time. Include examples for the activities colleagues actually run. A partner newsletter, an organic social post and a display advert should each have a clear example. Explain which parts change for a new placement and which remain tied to the campaign. Account for advertising platforms that use automatic tagging or dynamic parameters. Check the relevant integration rather than assuming manual UTMs replace it. Assign someone to approve the interaction between platform-generated information and the team's convention.
How should we review exceptions without confusing attribution with certainty?
Check reports for unexpected values and missing classifications. Investigate a sample of the original links and publication routes before rewriting a reporting rule. The fault may be in the naming, the destination journey or the collection setup. Explain limits when discussing results. A tagged link can be forwarded, revisited or encountered through an unexpected route. Collection can be incomplete, and later customer decisions involve other interactions. Use UTMs as organised evidence about recorded acquisition, supported by broader enquiry and CRM information. Giraffe Digital's digital strategy service connects campaigns, customer journeys and measurement. A manageable UTM system helps those conversations begin with consistent labels and clear assumptions. The best convention is one that colleagues can follow repeatedly.
