Google Consent Mode v2, implemented for you
For EEA traffic, Google requires consent choices to be passed to its tags to keep key advertising measurement, personalization and remarketing capabilities. Consent Mode v2 is that mechanism — and Cookie Craft implements it for you.
related: Tag Manager · GA4 & Google Ads
The four signals, set from the real choice
Cookie Craft starts the relevant signals as denied and updates them the moment the visitor decides. Google tags read these states via built-in consent checks.
| Signal | What it controls |
|---|---|
| analytics_storage | Access to the storage used for analytics (GA4). |
| ad_storage | Storage used for advertising. |
| ad_user_data | Whether user data may be sent to Google for advertising. |
| ad_personalization | Whether data may be used for personalised advertising. |
Basic or Advanced — decide it explicitly
Cookie Craft provides the order and states both models need. The choice must be reflected identically in your cookie policy and your commercial copy.
| Model | Before consent | Implication |
|---|---|---|
| Basic | Google tags are held until the visitor grants consent. | You may say Google measurement starts only after consent — if that is the published setup. |
| Advanced | Tags may fire with denied states, sending limited cookieless signals. | Don’t claim “nothing leaves before consent”; explain the limited signals. |
How it fits the rest of your stack
Consent Mode governs Google’s states; GTM and GA4 do the measurement.
Works with GTM
Your Google tags use built-in consent checks, so they respect the state without manual trigger surgery.
Helps GA4 & Ads data
Correct signals in the EEA help Google tags receive what they need for eligible measurement and modeling features.
Verifiable
Check denied/granted states in GTM Preview and Tag Assistant before you publish.
Required for Google in the EEA. Included here.
No higher tier, no add-on, no snippets to paste.