Does Google Tag Manager itself need consent?
This confuses a lot of people. Google Tag Manager itself is a container that loads other tags; on its own it does not set tracking cookies. So GTM usually does not need consent, but the tags it fires absolutely do.
The container vs the tags
Google Tag Manager is plumbing: it decides which tags fire and when. Loading the container does not, by itself, track the user or set analytics or marketing cookies. What tracks the user is the tags inside it, GA4, the Meta pixel, and so on, and those need consent.
So what do you actually need to do
You do not block GTM; you use GTM to block the tags. With Consent Mode and consent checks on your tags, the container can load, but the tracking tags only fire once the visitor agrees. That is the correct, compliant pattern.
The nuance
- GTM can be configured to set its own cookies or load before consent in ways that raise questions, so keep it clean.
- Some strict interpretations prefer to delay even GTM; most guidance treats the container as acceptable as long as the tags are gated.
The practical takeaway: do not panic about GTM, do make sure every tracking tag inside it respects consent via a CMP.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · What is a CMP?