Open a Google Tag Manager container that has been running for three years and you will find tags nobody recognises, triggers that fire on pages that no longer exist, and at least one variable called test.

This is normal. Containers accumulate. The problem is that a messy container is not just untidy, it actively slows your site and produces wrong numbers.

Before you delete anything

Two rules that will save you.

First, export the container. Admin, then export, and keep the file. If you break something you can restore it in minutes rather than rebuilding from memory.

Second, work in a new workspace rather than the live one. Nothing publishes until you decide it does.

Step one: find what is actually firing

Start with facts rather than assumptions.

1. Open preview mode and browse your site the way a customer would. Homepage, product page, cart, checkout, thank you page.

2. At each step, note which tags fired.

3. Anything that never fires during a normal journey is a candidate for removal.

Also check the versions screen. It shows what changed, when, and by whom. Tags added six months ago by someone who no longer works there are worth questioning.

Step two: hunt for duplicates

Duplicates are the most damaging thing in a messy container because they inflate your numbers rather than breaking them visibly.

Look for:

• Two GA4 configuration tags, which doubles absolutely everything.

• The same conversion tag appearing twice under slightly different names.

• A tag in GTM that is also hardcoded in the site theme.

• Multiple tools measuring the same event, all still active.

Search your live page source for your measurement and conversion IDs. If an ID appears both in the theme and in a GTM tag, you have found a duplicate that preview mode alone would never reveal. There is more detail in the duplicate purchase event guide.

Step three: check the triggers

Triggers rot faster than tags because they depend on URLs and page structure, both of which change.

• URL based triggers pointing at pages that were renamed during a redesign.

• Click triggers using CSS selectors that a theme update quietly invalidated.

• Form triggers built for a form that has since been replaced by an embedded one.

• Triggers with no tag attached, which are harmless but add noise.

Step four: clean up safely

Do not delete in bulk on day one. Pause first.

Rename anything suspicious with a clear prefix, then pause it and publish. Wait a week. If nothing breaks and nobody complains, delete it.

This feels slow and it is far faster than explaining why conversion tracking disappeared on a Friday afternoon.

Step five: leave it better than you found it

Rename everything to a consistent convention. Platform, then type, then purpose, so anyone can read the list and understand it.

Use folders. Group by platform or by area of the site.

Write real version notes when you publish. Fixed tracking is not a version note. Removed duplicate GA4 config that was doubling all events is.

How often

Every six months for most businesses, and always after a site redesign, a platform migration, or an agency handover. Those three events are where the majority of tracking damage originates.

If you want the debugging side rather than the housekeeping side, see how to debug GTM tags properly.

Need this fixed properly?

If your container has become something nobody wants to touch, an audit will usually find several things quietly costing you money. I set up and repair tracking for ecommerce stores and lead generation businesses, so the numbers in your ad accounts match the money in your bank account.

Have a look at what I do, or book a call and we can go through your setup together.