Consent mode v2 in GTM comes down to four choices passed to Google tags: ad_storage, analytics_storage, ad_user_data and ad_personalization. The banner’s template runs on Consent Initialization - All Pages and sets defaults, the banner updates them, and each tag’s consent settings decide whether it waits. Basic mode blocks Google tags until consent; advanced mode loads them and sends measurements without cookies while consent is denied.
- Defaults must be set before any other tag fires.
- Google tags have built-in consent checks; Custom HTML pixels need Require additional consent.
- Turn on the consent overview to see every tag’s status in one screen.
- Prove it in Tag Assistant’s Consent tab: On-page Default, then On-page Update.
Consent mode guides are mostly written by banner vendors, so they explain their banner. What a paid-media owner needs is the GTM side: where the defaults are set, what happens to Meta, TikTok and Snap tags, and how to check it on the live site. Which defaults apply in which country is a legal decision; this post covers how to implement the one your legal team makes.
The four signals in plain terms
What each signal controls
| Controls | If denied | |
|---|---|---|
| ad_storage | Advertising cookies and identifiers | Ads tags don’t read or write ad cookies |
| analytics_storage | Analytics cookies, such as visit duration | GA4 doesn’t use analytics cookies |
| ad_user_data | Sending user data to Google for advertising | User data isn’t sent for ads |
| ad_personalization | Personalized advertising, such as remarketing | No personalized ads from this data |
The last two were added in November 2023, which is what "v2" refers to. If you advertise to users in the European Economic Area, Google’s EU user consent policy applies. For example, Google Ads Help says that from March 2024, Customer Match lists used in the EEA need both ad_user_data and ad_personalization granted.
Basic or advanced?
Basic vs advanced consent mode
| Basic | Advanced | |
|---|---|---|
| Google tags before a choice | Don’t load | Load with your default states |
| While consent is denied | Nothing is sent to Google | Measurements are sent without cookies |
| Modeling in Google Ads | Based on a general model | An advertiser-specific model |
| Pick it when | Your policy says no requests before consent | Your legal team accepts cookieless pings before consent |
Set it up in GTM
1. Install the banner template
Google’s Featured CMPs have templates in the Community Template Gallery. Add yours, configure it, and fire it on the Consent Initialization - All Pages trigger, which every web container has by default and which runs before other triggers. That tag sets the default state of each signal and updates it when the visitor chooses. If the banner needs a moment to load, wait_for_update tells Google tags how many milliseconds to wait for the update.
2. Turn on the consent overview
Admin, Container Settings, Additional Settings, Enable consent overview. The Consent Overview then lists every tag as Consent Not Configured or Consent Configured, which is the fastest way to see what nobody has looked at.
3. Set consent per tag
Each tag’s Advanced Settings has Consent Settings. Built-In Consent Checks show what the tag already respects: Google’s own tags adjust their behaviour based on consent state. Additional Consent Checks has three options: Not set, No additional consent required, and Require additional consent for tag to fire, which fires the tag only when every listed signal is granted.
This is where Meta, TikTok and Snap come in. A Custom HTML pixel has no built-in checks, so with Not set it fires regardless of the banner. If your policy says marketing pixels wait for consent, set Require additional consent with ad_storage on each one. The Meta template also has its own consent field you can map to your banner.
Consent mode v2 in GTM: setup checklist
Consent mode v2 in GTM
- Legal has decided the default state per region and whether you run basic or advanced mode.
- The banner template fires on Consent Initialization - All Pages, nowhere else.
- Defaults set for all four signals: ad_storage, analytics_storage, ad_user_data, ad_personalization.
- wait_for_update set if the banner loads late.
- Enable consent overview is on, and no tag is left in Consent Not Configured by accident.
- Google tags reviewed under Built-In Consent Checks.
- Every non-Google pixel set to Require additional consent, or documented as exempt.
- Tags that don’t manage consent use Initialization or later triggers, not Consent Initialization.
- Tested denied: Tag Assistant’s Consent tab shows denied in On-page Default and no pixel fires.
- Tested granted: On-page Update shows granted and the pixels fire once.
- Tested on mobile and in a fresh browser, not just your usual session.
- Version published with a note naming the policy it implements.
How to check it works
- Open Preview in a fresh browser profile and don’t touch the banner.
- In Tag Assistant’s Summary, select the earliest Consent event. In your tag’s Output, open the Consent tab and read the On-page Default column.
- Check that marketing pixels did not fire before the choice.
- Accept the banner, select the most recent Consent event and read On-page Update.
- Repeat with reject, then confirm what fires matches your policy.
Note what this does to testing elsewhere: Google says events don’t appear in GA4 DebugView when consent mode is set and analytics consent wasn’t granted. Accept the banner when you test the GA4 setup.
Where this goes wrong
- The banner tag on All Pages. Defaults then arrive after other tags have already fired. Use Consent Initialization.
- Pixels left on Not set. The consent overview shows them, but nobody opens it. Meta, TikTok and Snap fire before consent.
- The whole container waits for the banner. Some sites only load GTM after consent. Nothing fires before consent, but advanced mode is impossible and your consent settings never see a denied state. Know which setup you inherited.
- Testing only with consent granted. Your browser remembers your choice. Test in a fresh profile.
- Server events ignore the choice. If a server sends the same events, it needs the visitor’s consent too.
For pixel setups that respect the banner, see Meta Pixel in GTM and TikTok and Snap pixels in GTM. Consent is also a section of the GTM audit checklist.
Do it faster with Whathead
Whathead’s Google Tag Manager MCP can read the consent settings on every tag and set them in a workspace. Choosing the banner and deciding which tags wait for consent stay with you. Whathead is our product.
- “List every tag in GTM-XXXXXXX with its type, firing trigger and Additional Consent Checks setting. Group them by platform and flag non-Google pixels set to Not set.”
- “Set Require additional consent for tag to fire, with ad_storage, on every Meta, TikTok and Snap tag. Show me the list before changing anything, and don’t publish.”
Before anything changes, Claude asks you to approve each write. GTM writes have no dry-run preview, so the workspace is the draft; run the Tag Assistant test above before you publish. Whathead’s server-side tracking, in private pilot, supports Consent Mode v2 or a custom CMP for the server leg.
Consent mode v2 in GTM: common questions
What is consent mode v2?
Google’s consent mode with two signals added in November 2023, ad_user_data and ad_personalization, next to ad_storage and analytics_storage. Google tags adjust their behaviour based on these four states.
What is the difference between basic and advanced consent mode?
Basic blocks Google tags until the visitor chooses. Advanced loads them with default states and sends measurements without cookies while consent is denied.
Do I need a consent management platform?
Google recommends a CMP to collect consent, and its Featured CMPs have GTM templates. Consent mode itself only passes the choice to tags.
Does consent mode control the Meta, TikTok or Snap pixel?
Not by itself. In GTM, set Require additional consent for tag to fire on those tags so they wait for the signal you choose.
How do I check that consent mode v2 works?
In Tag Assistant, select the earliest Consent event and read On-page Default in the tag’s Consent tab, then the most recent one and read On-page Update.
Sources
- Google Tag Manager Help: Consent mode in Tag Manager, Initialization triggers. Checked 19 Nov 2026.
- Google developers: Set up consent mode, Consent mode concepts, Verify consent mode. Checked 19 Nov 2026.
- Google Ads Help: EU user consent policy for Customer Match. GA4 Help: DebugView. Checked 19 Nov 2026.
Written by Ahmed Shahin, founder of Whathead. Last reviewed 19 November 2026.
See every tag’s consent setting
List consent settings across your GTM container from Claude, then fix the gaps in a workspace you test before publishing.



