Video Hub / How to Set Up Consent Mode V2 in Google Tag Manager

How to Set Up Consent Mode V2 in Google Tag Manager

Please accept marketing cookies to view this video

Accept cookies

Frequently asked questions

No, but it makes the setup far easier to control and verify. GTM gives you a single place to see which tags require which consent categories, and a preview mode for confirming the signals are firing. Without it you are configuring consent inside each tool individually, with no consolidated view of what fires when.

Any tag that tracks behavior or sends data to a third-party platform. That covers advertising pixels, but also session recording and heatmap tools, and CRM tracking codes loaded through your container. A useful test is whether the tool has its own privacy policy and sets its own cookies. If so, it should not be on an all pages trigger.

Your consent platform's own tag, your container configuration tags, and Google tags such as GA4 and Google Ads. The consent tag has to fire first to display the banner at all. Google tags have consent logic built in and adjust their own behavior, which is what allows them to send cookieless pings when consent is denied.

Because it has to communicate the consent state before anything else evaluates. Tags fire in sequence when a page loads, and consent initialization is the earliest point available. Firing the banner later leaves a window in which other tags evaluate against no consent state at all, which is where pre-consent tracking comes from.

No. A single global default of denied covers the GDPR requirement across every EU country, so listing Germany, France and Italy individually is unnecessary. Region-specific rules are for exceptions, such as adding a US state that operates on an opt-out basis while the rest of your traffic defaults to denied.

Use preview mode and inspect the consent state parameter on a page view event before and after interacting with the banner. Before consent, Google tags should be firing while third-party pixels stay blocked. After accepting, the consent state should change and the previously blocked tags should fire. If the state never changes, the signal chain is broken.

No. The cookieless pings sent when someone declines contain no personal data, no cookies and no user identifiers. They record only that a visit or conversion happened. Advanced mode was designed specifically to satisfy privacy requirements and measurement needs at the same time, which is why it is not a tradeoff between the two.

Yes, if you want your consent data to feed Google's advertising products properly. Google maintains a published list of certified partners, and a homemade banner or an uncertified tool may not deliver signals in the form Google accepts. The certification is what guarantees the technical handshake works rather than appearing to.