Common UTM Tracking Mistakes
Diagnose duplicate parameters, lost destination values, inconsistent names, and misleading validation results.
By UTMCraft / Axellier · Updated · Examples use fictional campaigns.
Two campaign values in one link
A URL such as ?utm_campaign=old&utm_campaign=new is ambiguous to downstream consumers. Some systems read the first value, others the last. Inspect all values in the Parser before choosing which is correct; never assume the displayed last value is the complete input.
In the Builder, import an existing URL and set the intended campaign field. The builder replaces that named field with one value. Other query parameters remain intact. Validate the result and compare it with the original before publishing.
Before: https://example.com/class?variant=blue&utm_campaign=old&utm_campaign=new After: https://example.com/class?variant=blue&utm_campaign=class_oct26
Cleaning away the product selection
A short URL is not necessarily a correct URL. A query parameter might select a product size, language, search result, or signed resource. Removing every query value can change the destination’s behavior.
The recommended Cleaner mode removes UTM fields and recognized click IDs while leaving unknown keys. Even then, inspect the result. The tool does not know the business meaning of your destination and cannot guarantee that the page still behaves the same.
Changing capitalization in the wrong place
SummerLaunch and summerlaunch can fragment a naming convention. That does not mean all uppercase characters in a URL are errors. Paths, product IDs, and signed values may depend on case.
Normalize the campaign labels you own, not the entire destination. The validator’s naming suggestions apply to campaign fields. A clean validation result is still only a structural check, not a test of whether the website loads.
Treating “ready” as proof of tracking
The final check must match the claim. A generated QR image is not proof that a phone can scan the printed version. A valid URL is not proof that Analytics recorded a visit. A copied link is not proof that an email provider preserved it.
Use a release checklist: inspect parameters, visit your own landing page, test the distributed asset, and verify reporting independently. Keep the results together so the next person can reproduce your checks.
Before you publish
- Resolve duplicate campaign keys explicitly.
- Preserve functional query values.
- Normalize campaign labels only.
- Test the real distribution path and reporting, not just URL syntax.
References and further reading
Our worked examples explain a workflow; platform behavior can change. Report a correction with a synthetic example.