Does Zest work with Google Consent Mode v2? I need to pass consent signals to GTM/GA4.

[zapalblizh]

I'm setting up analytics on a new site and need proper consent signals for Google's March 2024 requirements. Does Zest handle Consent Mode v2 out of the box, or do I need extra config? Specifically I need analytics_storage, ad_storage, and ad_user_data defaults set before GTM loads.

[reatlat]

Yes, Zest supports Google Consent Mode v2 out of the box. Just flip one flag:

window.ZestConfig = {
  consentModeGoogle: true
};

Or use a data attribute on the script tag:

<script
  src="https://cdn.jsdelivr.net/npm/@freshjuice/zest"
  data-consent-mode-google
></script>

When enabled, Zest automatically pushes a 'default' denied state for all consent types (analytics_storage, ad_storage, ad_user_data, etc.) on initialization — this is the critical GDPR requirement: signals are set before GTM or gtag loads. Then, on every consent change (accept/reject/modify), Zest sends 'update' signals reflecting the visitor's actual choices.

How to wire it

1. Set consentModeGoogle: true in your Zest config (as above)
2. Load Zest before your GTM/gtag snippet — Zest's script blocking handles this automatically in safe mode (the default), which blocks googletagmanager.com until consent is granted
3. Once the visitor accepts analytics, Zest replays the blocked GTM script, and the 'update' signal fires with the granted categories

What Zest pushes

Signal	Trigger	Values set
default	Page load (before GTM)	All denied
update	Consent change	Matches actual consent state

The full reference is on the Configuration page under Consent Mode Integrations, with usage examples at cookiezest.com/docs/examples/#google-consent-mode-v2.

💡 Zest blocks googletagmanager.com in safe mode (the default). If you've disabled blocking or switched to manual mode, make sure Zest still loads before GTM — otherwise the default signal fires too late.