Operations and diagnostics
Organise UTM parameters and identifiers for readable reporting
Create a campaign dictionary, separate analytics and affiliate attribution, test redirects and preserve historical mappings.
Before you begin
One campaign often receives several names, fragmenting reports and creating manual reconciliation. Shared conventions identify operation, origin and placement. UTMs do not replace affiliate programme identifiers. Manual and automatic tagging priorities depend on the tool; this guide provides a method and hypothetical values.
Start with reporting questions
Define decisions about channels, editions, creatives or markets. Each required distinction needs a stable field. Avoid unused segmentation. Define units and scope too: sessions, users, clicks or orders. Systems can credit the same sale differently. Naming conventions support reconciliation without making attribution models identical.
Write a value dictionary
Record field definition, accepted values, owner and example. Keep case and separators consistent rather than creating values for punctuation changes. Preserve identifiers when public titles change. Examples such as october-guide-2026, editorial-newsletter, email and comparison-block describe hypothetical operations, not mandatory provider conventions.
Separate analysis and remuneration
Analytics tools interpret UTMs as campaign tags. Affiliation may require its own partner identifier or sub-identifier. Preserve mappings without assuming analytics tagging creates commission. Confirm accepted parameters and encoding. Query strings added at the wrong level of wrapped links can alter redirects. Test destinations and journeys, not merely syntax.
Inspect automatic rewriting
Inventory advertising, sending, shortener and redirect tools. Consult tagging precedence rules. Google Analytics documents interactions; do not generalise them to every system. Keep published URLs, landing URLs and received reporting values. Locate the first affected redirect when fields disappear instead of changing the whole taxonomy.
Exclude personal information
Names should describe operations rather than people. Do not put emails, telephone numbers, customer names or sensitive references into URLs, which can appear in history, logs and other tools. Segment codes should fit data policies rather than become disguised individual identifiers. Review flows when granularity or recipients change.
Validate published links
Check expected fields, dictionary values, destination and absence of personal data. Test the final channel because sending or publishing can still transform URLs. Compare controlled events against exports, documenting dimensions and filters. Renaming a current link may not repair historical events. Preserve separate, evidence-based normalisation mappings.
Version changes
Record important changes and effective dates. Retain mappings when old values become one reporting category. Do not turn unknown origins into certain ones just to tidy tables. Measure out-of-convention values, unclassified events and reconciliation effort. Fix causes in link-generating tools. Quality is demonstrated by received values rather than a rule document alone.
A working record to adapt
| Field | Hypothetical value | Purpose |
|---|---|---|
| Campaign | october-guide-2026 | Identify a stable operation |
| Source | editorial-newsletter | Name the origin |
| Medium | Group the channel | |
| Content | comparison-block | Distinguish placement |
| Partner | Programme-supplied value | Preserve affiliation function |
Practical answers
Questions to settle before signing
Do UTMs establish commission?
No. Programmes define the identifiers and approval rules.
Can names change?
Yes, with documented mappings and effective dates; historical events may remain unchanged.
Which convention is mandatory?
Accepted parameters depend on tools. Internal values should be consistent and documented.
How should unknown origins be treated?
Keep them unknown, investigate causes and record only justified normalisation.
Sources and further reading
This guide is designed to help you ask better questions and organise a practical plan. It is educational and does not constitute legal, tax or financial advice. Platform rules, market conditions, technical capabilities and eligibility requirements can change, sometimes with little notice. Confirm material decisions with current official sources and, where the consequences matter, with qualified professionals who understand your market and organisation.