Consent Mode v2 for online stores - what you need to know
A practical explanation of what Consent Mode v2 is, why it's required, and how to implement it in a store without losing analytics data.
Consent Mode v2 isn’t just another cookie add-on - it’s how Google expects tags to behave depending on a user’s consent. Without it, Google Ads conversions and GA4 data become incomplete, and campaigns lose effectiveness.
What Consent Mode v2 is
It’s a mechanism that passes a user’s consent state to Google tags across four signals:
ad_storage- advertising cookies,ad_user_data- sending user data for advertising purposes,ad_personalization- ad personalization,analytics_storage- analytics cookies.
When a user does not consent, tags don’t write cookies but still send consentless pings. Google uses these to model conversions.
Why it matters
Without a correct Consent Mode v2 setup:
- Google Ads conversions are under-reported,
- conversion modelling in GA4 doesn’t work,
- you risk non-compliance with consent requirements.
How to implement it - in short
- Deploy a Consent Mode v2-compatible CMP (e.g. Cookiebot).
- Set the default consent state to “denied” before tags load.
- Update the consent state after the user’s choice in the banner.
- Configure GA4 and Google Ads tags in GTM to respect consent.
- Verify everything in GTM preview mode and Google Tag Assistant.
The most common mistake: the consent banner is there, but tags fire before the user decides anyway. Formally you have a CMP - but data is still collected non-compliantly.
Summary
Consent Mode v2 is now a standard, not an option. Done right, it protects you from data loss and lets campaigns run at full strength while staying compliant. If you’re unsure whether your store collects data correctly, start with a tracking audit.