Google Consent Mode v2

Consent Mode v2 lets Google tags (gtag.js, GTM, Google Ads, GA4) adjust their own behavior based on the visitor's consent state, instead of you having to block or unblock each tag manually. Cookie Munch implements it natively — no separate GTM template required.

Enable it

In the banner settings editor, go to Consent → Consent Mode and toggle Enable Consent Mode. Two fields become available:

What gets signaled

Cookie Munch's three visitor-controlled categories map to the full Consent Mode v2 signal set:

Before any vendor script loads, the banner pushes a default-denied block for every signal except security_storage. As soon as the visitor decides (or a stored decision is restored), an update signal reflects their actual choices — Google tags that respect Consent Mode adjust their behavior (e.g. cookieless pings instead of full tracking) automatically.

Basic vs. advanced mode

• Basic — pings are either fully blocked or fully allowed based on consent; no additional signals are set.

• Advanced — in addition to the signals above, the default block also sets ads_data_redaction: true and url_passthrough: true, which tell Google Ads to redact ad-click data and preserve click IDs via URL passthrough until consent is granted — enabling conversion modeling for visitors who haven't yet decided or who declined, instead of losing that data entirely.

Note: wait_for_update only delays tag firing — it does not change the default (denied) state. If the visitor hasn't decided within that window, tags fire with consent still denied, and update the moment a decision arrives.

Interaction with other frameworks

Consent Mode signals are derived from the same three-category consent state that drives IAB TCF and US State Privacy — you don't configure them separately. If your site also runs TCF, granting purposes 2, 3, 4, or 7 (ad selection/delivery/measurement) sets marketing = true, which in turn grants the Consent Mode ad signals.

See also: Banner settings · Geo-targeting & regional rules