A Consent Mode v2 rollout wiped 70% of events — 83% recovered in two days

The situation

A German home decor brand selling across DACH markets rolled out a new CMP (Consent Management Platform) in January 2024 to comply with updated GDPR requirements. Within 48 hours, GA4 sessions dropped 70%, Meta reported a 65% drop in pixel events, and Google Ads conversions went to near zero.

The problem

The CMP was blocking all GTM tags by default until consent was given. But the Consent Mode V2 integration between the CMP and GTM was not configured — GTM was not receiving consent signals in the format Google requires. As a result, Google's consent mode modeling couldn't fill in the gaps. The result was 70% event loss with no modeling fallback.

What we did

1. Diagnosed CMP-GTM integration gap — CMP was setting cookies but not calling gtag("consent", "update") in the format GTM requires
2. Configured proper Consent Mode V2 implementation: default consent state set to "denied" for ad_storage, analytics_storage, ad_user_data, ad_personalization
3. Mapped CMP consent categories to Google consent parameters so GTM receives correct signals when users accept or decline
4. Implemented Meta CAPI with server-side deduplication to recover iOS and cookie-blocked purchase signals independently of consent

Why it worked

Consent Mode V2 requires a specific handshake between the CMP and GTM: the CMP must fire gtag consent update calls with the exact parameter names Google requires. Most CMP platforms have a GTM integration guide but the defaults are often misconfigured. Without modeling working, Google and Meta can't recover any signal from non-consenting users. Properly implemented, Consent Mode V2 recovers 75-90% of conversion signal even when most users decline.