What Consent Mode is and is not
Consent Mode carries a decision to Google’s tags through named consent types. The four primary advertising and analytics signals are analytics storage, ad storage, ad user data and ad personalisation; Google’s API also defines additional consent types for other storage and functionality. It is a transport, not a consent mechanism: something still has to present the choice, record it and be able to demonstrate it.
There are two shapes. In a basic implementation the tags are not loaded until consent exists. In an advanced implementation they load with denied defaults and send cookieless pings from which Google models the gap. Which one you are running is a decision with legal implications, and it should be deliberate.
The ordering rule
Denied defaults set after the container are defaults nothing saw
The default state has to be established before the container loads. If it is set afterwards, Consent Mode code and a working banner may both be present even though tags already ran under their prior assumptions.
The tag manager adapter handles this: the container is loaded with denied defaults established before any tag runs, consent updates are sent as selections change, and updated denied states are sent on withdrawal.
Consent Mode does not cover the whole container
Google tags read Consent Mode signals. A Meta pixel, a LinkedIn tag or a chat widget in the same container does not. Those need their own trigger conditions or their own consent checks, which means a container with denied Consent Mode defaults can still be firing three non-Google trackers before consent.
Verifying it
- GTM Preview to see the consent state each tag observed at the moment it fired
- The network panel to see what left that browser during the tested journey; preserve the capture as evidence, without treating one run as proof of every visitor state
- Every tag individually, not just the container
- Each state: before consent, after rejection, after approval, after withdrawal
- A check for duplicate installations, which produce contradictory behaviour that looks like a Consent Mode bug
Common questions
Is advanced Consent Mode compliant in the EEA?
It sends cookieless pings before consent, which is a processing activity in its own right. Whether that is acceptable for your site is a question for your advisers. The product does not assume an answer.
Do I still need a consent record if I use Consent Mode?
Yes. Consent Mode transmits a state; it does not store evidence of a decision you can produce months later.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- Google: set up consent mode on websites
Vendor documentation
Checked
- Google: consent mode reference and consent types
Vendor documentation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.