Consent Mode v2

Consent Mode v2 is Google's consent-signalling framework for GA4 and Google Ads. With it enabled, your tags can fire in a privacy-respecting state before the user has accepted cookies — Google modulates what data they receive based on the consent signals. Without it, GA4 in many EU regions either underreports or won't fire at all.

When to enable it

• You have visitors in the EEA, UK, or Switzerland.
• Your Google Ads campaigns are flagged for "consent signals not detected" in the Ads UI.
• Your CMP (cookie banner) supports the IAB TCF or Google's consent v2 mode (Cookiebot, OneTrust, Iubenda, Borlabs, Klaro, CookieYes — all support this).

What TrackingCoder generates

Tick the Consent Mode v2 opt-in during the wizard (+1 credit) and the generated container includes the consent annotations the GA4 / Google Ads tags need:

• consent_required: ad_storage + analytics_storage on each affected tag.
• The right consent_status shape (uppercase NEEDED, parameter type LIST, items wrapped as TEMPLATE with the consent signal) — the exact shape GTM's import expects.

What it doesn't do

TrackingCoder doesn't install a consent banner or modify your existing CMP. The banner is the thing that sets the consent state in the dataLayer (gtag('consent', 'update', {...})); TC's output is the thing that reads those consent flags on the tag side. You need both halves working — TC handles the second half, your CMP handles the first.

Common questions

I have a banner, do I still need the +1 credit? Yes — having a banner doesn't automatically mean your tags respect its signals. The annotations TrackingCoder adds are the bridge. Without them, your tags ignore the consent state.

I don't have EU traffic. Skip Consent Mode v2. The standard generated container fires on every page load in jurisdictions that don't require consent.