Google Consent Mode v2 for WooCommerce
Quick answer: The wizard's checkbox sets one GA4 tag parameter (restricted_data_processing). It does not set up the default consent state or connect to a consent banner - the part that actually determines whether tags fire before a visitor responds to a cookie prompt. You still need to add that yourself, typically through a consent management platform (CMP).
Google Consent Mode v2 lets Google's tags adjust their behavior based on a visitor's cookie consent choices, rather than firing at full capacity regardless of consent. It became effectively required for advertisers using Google Ads or Analytics audiences in the EEA and UK starting March 2024.
What the checkbox actually sets
Enabling it adds a restricted_data_processing parameter to the GA4 Configuration tag. That's a real, valid Consent Mode setting - but it's a small piece of a larger requirement.
What's missing, and why it matters
The part that actually implements consent-based behavior is the "default consent state" - a snippet that must run before GTM loads, setting analytics_storage and ad_storage to "denied" by default, then updating to "granted" only after a visitor consents. This wizard does not generate that snippet. Without it, your tags behave as if consent were already granted, which defeats the purpose of Consent Mode.
What you need to add yourself
- A consent banner / cookie notice for your visitors
- A default consent state snippet firing before GTM loads (many consent management platforms, including several Google-certified CMPs, add this automatically)
- Consent update calls wired to your banner's accept/reject actions
Frequently asked questions
Does checking this box make my store GDPR compliant?
No. It sets one tag parameter. Compliance depends on your consent banner, default consent state, and how consent updates are wired - none of which this wizard generates. Treat this as one small piece of a larger setup, not a complete solution.
Do I need a consent management platform (CMP)?
For most stores serving EEA/UK visitors, yes - a CMP is the practical way to get the default consent state and banner logic in place correctly, since building it by hand is easy to get subtly wrong.
Will this be more automated in the future?
It's a reasonable direction for the wizard to grow toward, but as of today the default consent state setup is explicitly out of scope and documented as a known limitation - this page will be updated if that changes.