A Google Tag Manager container is a one-way door. Tags get added for a campaign, a tool trial, a contractor's experiment, and nobody comes back to remove them. Three years on, a container that should hold a dozen tags holds forty, and a third of them do nothing useful. Some do active harm.
The kinds of dead tag
- Universal Analytics. Any tag of type Universal Analytics, or any Custom HTML with a UA- ID. The property no longer processes data.
- Tools you no longer pay for. A heatmap tool from 2023, an A/B testing platform, a chat widget that was replaced. The tag still loads the vendor script on every page.
- Campaign tags with expired triggers. A conversion pixel for a landing page that was deleted. It never fires, but it still has to be evaluated on every page load and it clutters every audit.
- Duplicates. Two GA4 configuration tags for the same measurement ID, or two Meta Pixel tags with the same ID, usually one from a template and one from pasted script. These are not dead; they are double counting.
- Paused tags that were never unpaused. Paused "for a test" six months ago.
Why remove them
Each live tag that loads a vendor script costs the visitor a request and a few milliseconds of main-thread time, and marketing scripts are already the heaviest thing on most pages. Each dead tag also costs you clarity: every audit, every debug session and every handover has to wade through it. And a container with obvious cruft is one nobody trusts, which is how teams end up building a second container alongside it.
Finding them
- Read the container. Sort tags by type. Anything Universal Analytics is dead. Anything Custom HTML deserves a second look: what vendor, is there a template for it, is the vendor still used.
- Compare with what fires. A tag inventory scan that watches a sample of real pages tells you which tags actually fire in the last 30 days. A tag that has not fired in a month is either dead or has a broken trigger.
- Compare with the stack. List the tools the business pays for. Any vendor in the container that is not on the list is a candidate.
- Check for duplicates. Group tags by the ID they carry. More than one live tag per ID is a duplicate unless it is a deliberate migration.
Removing them safely
- Pause first, delete later. Pause the tag, publish, wait two weeks, and confirm nothing changed in the reports that matter. Then delete.
- Delete the trigger and variables that only that tag used. Orphaned variables are the next generation of cruft.
- Write the reason in the version description. The next person to open the container will thank you.
- Keep a container version from before the cleanup. GTM versions are free rollbacks.
Keeping it clean
A quarterly review of the container against the tool list is enough for most teams. For agencies managing many containers, a scheduled scan that flags tags not seen firing in 30 days turns the quarterly review into a weekly email.
FAQ
Do unused GTM tags slow down my site?
A tag that never fires costs almost nothing at runtime. A tag that fires and loads a vendor script you no longer use costs a request on every page, and marketing scripts are typically the largest part of a page's JavaScript.
Is it safe to delete Universal Analytics tags?
Yes. Universal Analytics stopped processing data in 2023 for standard properties and 2024 for 360 properties. The tags send requests that are discarded. Pause, publish, verify, delete.
How do I know a tag is really dead?
Watch it over a period. A tag inventory that records which tags fire on real page loads, or a GTM sync history, shows which tags have fired recently. Thirty days without a fire is a strong signal, as long as the tag is not seasonal.
The free audit at tageasy.io/check reads your published container and lists every tag type inside it, including any that reference dead properties.