What is Tag Manager?

Before tag managers, every new pixel meant a code deployment. A tag manager replaces that with a single container script on the site; marketers then add, configure, and sequence tags inside the tool, publishing changes instantly. Triggers control when tags fire (page load, click, purchase), and variables pass data like order values into each tag. Google Tag Manager dominates the category, with Adobe Launch and Tealium iQ as the main enterprise alternatives.

That convenience is a double-edged sword for privacy. A tag manager makes it trivial for anyone with access to add trackers — which is how sites accumulate dozens of tags nobody remembers installing, each collecting visitor data. The container fires on page load by default, so an ungoverned setup ships every tracker to every visitor before any consent question is asked.

It is also the natural enforcement point. Modern consent management platforms integrate with tag managers so that tags fire only after the visitor's consent state allows them: Google Tag Manager's consent mode and built-in consent checks let each tag declare what consent it requires, and the CMP's signal gates it. Combined with regular audits of what is in the container, this turns the tag manager from the leak into the valve.

Governance matters as much as configuration: restrict publish access, review new tags for what data they collect and where it goes, document each tag's vendor in your cookie policy, and re-scan the site after container changes — a single misconfigured trigger can silently reintroduce pre-consent tracking.