THE SHORT ANSWER
Use UTM conventions as a shared naming contract for external campaign links.
For the broader picture of how target customers, channels and sales handoffs work together, read the pillar guide B2B demand generation: from attention to qualified pipeline.
UTMs as a naming contract
Use UTM conventions as a shared naming contract for external campaign links. Consistent values make reporting understandable; they do not establish a complete buyer journey. The objective is for teams to recognise the same sources, media and campaigns without manually assembling a collection of inconsistent spellings.
Separate stable campaign identity from a readable action name. A title may change with language while its ID connects the same initiative. Using names simultaneously for audience, month and artwork creates variants whose meaning only the original author may later understand.
Source, medium and campaign ID
Define allowed source, medium and campaign values together with a stable campaign identifier. Agree case, separators and ownership. Google Analytics distinguishes manual and automatically collected traffic dimensions. Check their interaction in your actual integration rather than treating manual parameters as a universal replacement for auto-tagging.
Use a separate content field for creative variants rather than declaring every motif a new campaign. Give channels and partners explicitly defined values too. Include valid examples and common mistakes so new colleagues can build links without relying on unspoken interpretations. Explore this further in the guide Partner leads: clarify origin, influence and double counting.
Build and test controlled links
Build links through a controlled table or generator with approved choices. Test redirects, destination and CRM handoff. Never place personal information in campaign parameters. Avoid tagging internal navigation as external acquisition: it does not describe a new origin and makes subsequent interpretation unnecessarily difficult. Explore this further in the guide B2B attribution: use models as perspectives.
Test existing URL parameters and redirects. Inspect the address that actually reaches the browser and the value stored in CRM. A correct-looking generated link is insufficient if an intermediate service removes parameters or the form does not retain them after submission.
Three spellings of one source
A hypothetical webinar uses linkedin, LinkedIn and li as source values. Reporting displays three rows for the same origin. The team standardises new links on linkedin and documents the historical mapping. Old records are not silently rewritten; reports apply an explicit normalisation while preserving the original collected value.
The mapping records each original value and its approved reporting value. Historical reporting stays consistent and auditable. Replacing raw values removes the ability to determine whether a later discrepancy originated during collection or was introduced by the normalisation process.
Link context is not buyer identity
Missing tags do not automatically mean organic traffic. Applications, redirects and copied links can change or remove parameters. Conversely, a shared campaign link may retain its tags even when another person distributes it. Treat UTM values as link context rather than proof of an uninterrupted identity-level journey.
A LinkedIn link forwarded by email may still carry linkedin. That describes the original link label, not necessarily the immediate sender. Add buyer reports or partner context separately instead of rewriting collected technical values according to an analyst’s assumption.
Unknown values and lost parameters
Check new campaigns before publication and regularly inspect unknown media, uncontrolled spellings and missing identifiers. Sample the destination, analytics record and CRM result together. If systems disagree, establish the dimension and collection time first rather than immediately blaming the naming convention for every difference.
Maintain an issue list with link, observed value, expected value and campaign owner. Prevent recurring free-text variants during creation. Explainable legacy values may remain mapped provided their meaning is verified and they do not silently appear as additional acquisition channels.
Maintain the approved dictionary
Give one person ownership of the approved value dictionary while campaign teams build links from it. Assign documented values to new channels instead of inventing abbreviations independently. Record retired campaigns and their successors so reporting across several quarters retains a consistent and explainable campaign identity.
Give new values a definition, owner and start date. Before retiring a value, inspect active adverts and automated links. A naming convention should not repeatedly require historical repairs because a changed dropdown unexpectedly invalidated existing campaign links.
INTERACTIVE / FROM READING TO ACTION
Three checkpoints for your implementation
Choose a checkpoint and track your reading progress. Checks are neither saved nor sent and do not score your business.
CHECKPOINT 01
Build and test controlled links
Build links through a controlled table or generator with approved choices.
Explore in the article ↗CHECKPOINT 02
Three spellings of one source
A hypothetical webinar uses linkedin, LinkedIn and li as source values.
Explore in the article ↗CHECKPOINT 03
Link context is not buyer identity
Missing tags do not automatically mean organic traffic.
Explore in the article ↗Frequently asked questions
Must everything be lowercase?
Consistency matters more than a particular convention. Lowercase values can simplify maintenance, provided every campaign team applies the same documented naming rules.
Should internal links be tagged?
Not as external campaign origin; use appropriate events for internal navigation.
Should old values be overwritten?
Preserve originally collected values. Apply a documented mapping in reporting so historical spellings become comparable without hiding what was actually recorded.
How can I put “UTMs as a naming contract” into practice?
Use UTM conventions as a shared naming contract for external campaign links. Consistent values make reporting understandable; they do not establish a complete buyer journey. The objective is for teams to recognise the same sources, media and campaigns without manually assembling a collection of inconsistent spellings.
What matters when working on “Source, medium and campaign ID”?
Define allowed source, medium and campaign values together with a stable campaign identifier. Agree case, separators and ownership. Google Analytics distinguishes manual and automatically collected traffic dimensions.
