Consent Mode v2, configured correctly

Consent Mode v2 tells Google tags whether a visitor has granted consent for analytics and advertising storage, and adds two signals, ad_user_data and ad_personalization, that Google requires for audiences and measurement in the EEA.

Most problems come from defaults that are too broad or updates that fire too late. Markitech reads your container, shows the default and update sequence, and proposes region-specific settings you approve before publishing.

How to do it

1. Set consent defaults before any Google tag fires, ideally with a consent initialization trigger.
2. Use region-specific defaults: denied in the EEA and UK, and what your policy allows elsewhere.
3. Update consent from your consent platform when the visitor chooses.
4. Include ad_user_data and ad_personalization alongside ad_storage and analytics_storage.
5. Pass consent state to the server container if you use server-side tagging.
6. Verify with Tag Assistant that defaults and updates fire in the right order.

Common mistakes

• Setting a global denied default that suppresses measurement in regions that do not require it.
• Firing tags before the consent default is set.
• Forgetting ad_user_data and ad_personalization in v2.
• Not passing consent to server-side tags.

Ask Markitech

Related questions

• Does Markitech support server-side tagging?
• Does Markitech work with the Meta Conversions API?
• Does Markitech support Consent Mode v2?

Key terms

Approved by you, every time

Markitech proposes each change in chat and holds it until you approve. Nothing is published, created or changed in your accounts without that approval.

Part of the Server-Side Tracking guide.