UTM deprecation and cleanup
Over time a UTM taxonomy accumulates abandoned sources, one-off mediums, and inconsistent campaign names. Cleaning it up improves reporting, but you cannot edit links already in the wild — they will keep arriving with old values. Deprecation is therefore about steering new links to the clean taxonomy while mapping legacy values forward in reporting. This page covers a safe cleanup process.
You cannot recall published links
A link printed on a flyer, posted in a forum, or saved in someone's bookmarks will keep sending its original UTM forever. So cleanup cannot mean rewriting the past — it means governing the future.
Deprecate a value by removing it from the builder's approved list and documenting its replacement, so no new links use it. Old links keep working; their values simply stop growing.
- Published links keep their original UTMs indefinitely
- Deprecate = remove from the builder, document the replacement
- Old values taper as new links adopt the clean set
Mapping legacy values forward
To preserve comparability, maintain a mapping from deprecated values to their replacements and apply it in your reporting layer (a lookup or calculated field) so a campaign's history reads as one series.
Because there is no vendor-published standard for a deprecation process, this is an operational convention documented in your governance, which is why it is marked not yet verified against a primary source. Record what changed and when, so historical reports remain explainable.
How it appears in analytics and logs
A long tail of low-volume, near-duplicate sources and mediums signals taxonomy drift that cleanup addresses. After deprecation, residual hits on old values mean previously published links are still circulating — expected, not an error.
Diagnostic use case
Retire stale or inconsistent UTM values and consolidate a sprawling taxonomy without losing historical comparability or breaking links already published.
What WebmasterID can help detect
WebmasterID keeps recording whatever UTM values arrive, so a cleanup is reflected as new links adopt the clean taxonomy while old values taper off; the server-side history stays intact for comparison.
Common mistakes
- Assuming you can stop old UTMs from arriving — published links persist.
- Deleting old values from reports instead of mapping them forward.
- Cleaning the taxonomy without updating the builder's approved list.
- Not recording the deprecation date, making historical shifts unexplainable.
Privacy and accuracy notes
Cleanup operates on campaign taxonomy — the labels on links — not on visitor data. Deprecating a value changes how future links are tagged and reported, with no effect on any individual's data.
Related pages
- UTM governance and templates
UTM data degrades when everyone builds links by hand. This page covers the governance that prevents it: a shared builder or spreadsheet, documented allow-lists for source and medium, and a review step so new values are deliberate rather than ad-hoc.
- How to audit your UTM parameters
Over time, UTM values drift — Facebook and facebook, email and Email, newsletter and news — and split one channel into several report lines. A periodic UTM audit finds and consolidates that drift. This page describes a repeatable audit method you can run from your analytics export.
- UTM builder tools and workflows
A UTM builder is a tool that assembles a tagged URL from your source, medium, campaign, and optional content/term values, so people do not hand-edit query strings and introduce typos. Builders range from Google's free Campaign URL Builder to spreadsheet templates and governed internal tools that lock taxonomy. This page covers the builder spectrum and how a builder enforces consistency at the point of creation.
- Campaign links docs
Retire stale UTM values while preserving history.
Sources and verification notes
- Google Analytics Help — Collect campaign data with custom URLsUTM parameter reference the deprecated and replacement values sit on.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.