Google Tag Manager Is Set Up but Nobody Can Explain What Each Tag Does

A Container Nobody Wants to Touch

Open the tag manager and there are forty, sixty, sometimes over a hundred tags sitting in the container, with names like Tag Copy 2, Untitled Tag, and cryptic abbreviations that meant something to whoever created them years ago and mean nothing now. Every person who has managed the account since then added something without removing anything, because removing a tag feels risky when nobody can confirm what depends on it.

This creates a strange kind of organizational paralysis. The team knows the setup is messy, everyone agrees it should be cleaned up, and yet nobody actually does it because the fear of breaking a critical piece of tracking outweighs the discomfort of leaving the mess in place. So the container keeps growing, each new agency or employee adding their own layer on top of the last one's leftovers.

Why This Happens So Consistently

Tag sprawl is almost always a symptom of transitions, a new agency takes over and instead of auditing what exists, they simply add their own tracking on top to be safe. A new employee inherits the account with zero documentation and has no way to know what is load bearing and what is dead weight. A platform migration adds a new tracking requirement and the old one never gets removed because nobody wants to be the person who deletes something and causes a problem.

Each individual decision to just add rather than clean up seems reasonable in isolation, but the cumulative effect over several years is a container that actively slows down the site, creates duplicate or conflicting data, and makes every future change more dangerous because the blast radius of any edit is completely unknown.

The Only Safe Way Forward

Cleaning this up correctly means auditing every single tag, confirming what it fires on, whether it is still connected to an active destination, and whether removing it changes any reported number before actually removing anything. That process takes real time and a methodical approach, testing each change in a controlled way rather than deleting in bulk and hoping nothing important breaks.

This is unglamorous, detail heavy work that most internal teams do not have the bandwidth to do properly while also running daily campaigns. BSC has cleaned up exactly this kind of tangled container many times, bringing a container back to something one person can actually understand and maintain going forward.