A UTM naming convention should help the team answer a reporting question without requiring a meeting to decode each label. The strongest convention is usually small enough to remember, explicit enough to prevent accidental variations and flexible enough to describe a genuinely new campaign.
Use the campaign URL builder after agreeing on the labels. The tool can assemble a link, but it cannot decide whether two campaigns should share a name. That is an operating choice. This guide provides an original example register for a small business with newsletters, paid campaigns and partner promotions.
Start with the questions the report must answer
- Fit
- Explain the service scope.
- Trust
- Show supporting evidence.
- Next step
- Give a clear contact route.
Write three questions before designing the names. Which distribution source brought the visit? Which initiative was being promoted? Which placement or creative did the person use? If a field does not help answer a real question, consider whether the extra detail will be maintained consistently.
Avoid packing every characteristic into one campaign value. A label that combines source, city, audience, creative, device and date becomes difficult to reuse and easy to mistype. Put stable concepts in their intended fields, then keep a separate campaign register for descriptive details that do not belong in the URL.
Agree on a simple style
Choose a consistent case and separator. For the fictional system here, values use lowercase letters, numbers and underscores. That is our example convention, not a platform requirement. Google’s campaign parameter guide notes that values are case sensitive; inconsistent capitalization can therefore create separate reporting labels.
Decide how dates are used. A quarterly guide campaign could use 2026q4, while a recurring newsletter might use a specific issue identifier in the content field or register. Keep the same idea consistent rather than switching between quarter names, months and full dates without a reason.
Build a naming register with examples
| Field | Team rule | Example | Avoid |
|---|---|---|---|
| Source | Identify the distributor consistently | customer_newsletter | Renaming the same list every issue |
| Medium | Use the agreed channel vocabulary | email | Mixing email, Email and newsletter |
| Campaign | Name the shared initiative | project_planning_2026q4 | A label that says only campaign1 |
| Content | Describe the placement or creative | estimate_button | A customer’s name or email |
| Owner record | Keep outside the URL | Campaign owner and approval date | Personal details in tracking tags |
The register should also contain the full destination and a short campaign description. Someone reviewing the data months later needs to know what the visitor saw. A clean name without an archived creative or page reference can still leave the reporting question unresolved.
Separate a recurring program from an individual issue
Suppose a business sends a recurring educational newsletter. It might keep source and medium stable, use a campaign value for the current initiative and identify each placement in content. Another business may deliberately use one campaign per issue. Either approach can be workable if it matches the reporting question and remains consistent.
Choose once for a defined program and document the decision. Do not change naming halfway through an initiative simply because a different team member sends the next message. If a change is necessary, record its effective date so the reporting comparison can account for the new labels.
Give creative variants useful identities
Content values should distinguish variants without implying an outcome. For example, estimate_button and cost_guide_text describe placements. winner and high_conversion claim a result that may change or may never have been measured. A neutral label remains useful before and after a test.
Keep creative differences in the archived campaign record. A variant name cannot explain a changed headline, image and offer by itself. If several things change together, document them. Otherwise a later conversion difference can be incorrectly attributed to the button wording alone.
Make approval easy enough to happen
Assign one person to maintain the small vocabulary of sources and media. Let campaign owners propose new campaign and content values within the convention. Before launch, review the final destination, labels and any required query parameters together. This can be a short checklist rather than a separate administrative process.
Use the builder’s batch workflow for approved placements, then save the output with the campaign record. The campaign link testing checklist covers functional destinations and existing URL parameters. The builder field guide explains the complete path from destination choice to a testable link.
Keep the register connected to business outcomes
A campaign label identifies a measurement category. It does not establish that a visit caused a customer to buy. Connect the campaign review with your inquiry and sales process using the capabilities of your actual systems. Show the difference between visits, raw inquiries, qualified opportunities and customers.
The lead cost guide helps keep those stages separate. If your team needs an operating process that joins forms, assignments and customer records, explore AI automation services. A useful automation preserves meaning across systems instead of merely moving inconsistent labels faster.
Frequently asked questions
How many fields should a small team use?
Use the fields required by your measurement plan, starting with a clear source, medium and campaign. Add placement detail when it answers a question you intend to review. More fields are not automatically better if the team cannot maintain them reliably.
Should I rename old links when the convention changes?
Preserve the historical record and document the new convention’s start date. Changing labels on active placements can create a reporting break that needs explanation. Review the impact before editing links already distributed through email, print or partner content.
Can campaign names contain customer information?
Use campaign level descriptions instead. URLs can be copied and logged beyond the intended recipient, and Google prohibits sending personally identifiable information to Analytics. Read its data safeguards, and join the Trojan newsletter for more practical measurement workflows.
Questions, answered.
Should I rename old links when the convention changes?
Preserve the historical record and document the new convention’s start date. Changing labels on active placements can create a reporting break that needs explanation. Review the impact before editing links already distributed through email, print or partner content.
Can campaign names contain customer information?
Use campaign level descriptions instead. URLs can be copied and logged beyond the intended recipient, and Google prohibits sending personally identifiable information to Analytics. Read its data safeguards, and join the Trojan newsletter for more practical measurement workflows.
