Consent Mode

Complianz GTM & Didomi Mobile Apps: Complete Consent Mode v2 Implementation Guide

Managing EU, UK, and EEA consent banners breaks silently at the boundary between your Consent Management Platform (CMP) and Google Tag Manager / Mobile SDKs.

Two setups cause constant troubleshooting tickets across Europe right now:

  1. Complianz + GTM on WordPress: Enabling Complianz without syncing cmplz_event_* DataLayer triggers and Consent Mode v2 initialization leaves tags permanently blocked after “Accept All”—or worse, firing analytics_storage='denied' tags out of order.
  2. Didomi CMP on Web & Mobile Apps: Didomi is the standard enterprise CMP across France (CNIL), Switzerland, and large European publishers, yet connecting Didomi mobile app SDKs (iOS/Android) cleanly into Firebase Analytics / GA4 Consent Mode is rarely documented end-to-end.

Here is the clean, verified setup for both Complianz GTM and Didomi Web + Mobile Apps. Need expert verification? Explore our Consent Mode v2 GTM Master Guide or book a tracking audit.


Most broken WordPress Complianz installations stem from running script blocking inside Complianz simultaneously with GTM Consent Mode (creating double blocking).

Clean 4-Step Complianz GTM Architecture

  1. Configure Complianz Script Center:
    • Inside WordPress Complianz → Wizard → Consent → Statistics: choose “Yes, with Google Tag Manager” and paste your GTM-XXXXXX container ID only if your theme/GTM4WP doesn’t already load GTM. Never duplicate the container script.
    • Check “Enable Google Consent Mode v2” inside Complianz Settings (Pro/Standard versions supporting GCM v2), OR deploy the official Simo Ahava Consent Mode template at Consent Initialization in GTM with Complianz sending updates via cmplz_event_marketing and cmplz_event_statistics.
  2. Use GTM Built-in Consent Checks (Do NOT Double-Gate with Trigger Exceptions Unless Strict Basic Mode): In Advanced Consent Mode, configure Google Tags (GA4 Config, Google Ads Remarketing/Conversion, Conversion Linker) to trigger on normal Initialization / All Pages / Custom Events (purchase, generate_lead), not blocked manually by cmplz_event_marketing triggers. Why? Google tags need to fire in a cookieless ping state when denied so Google Consent Mode behavioral & conversion modeling works! Conversely, Meta Pixel, TikTok, Pinterest, and LinkedIn should carry Require additional consent: ad_storage / ad_user_data or custom triggers tied strictly to cmplz_event_marketing (wait until explicit opt-in).
  3. Critical Fix for Complianz Cached Banners: When a returning visitor already clicked “Accept All”, Complianz pushes cmplz_event_0 (or cmplz_event_statistics / cmplz_event_marketing) dynamically after GTM Container Loaded. Set Trigger Group or listen for custom event cmplz_event_marketing in addition to pageview triggers for marketing pixels so returning opted-in users don’t miss page-1 conversion firing!

Quick Verification in Tag Assistant

Load your site in GTM Preview, reject cookies first, and confirm:

  • Consent Tab → On-page Default: ad_storage, analytics_storage, ad_user_data, ad_personalization all = Denied.
  • Click Accept All, confirm Update sets all four to Granted, and non-Google pixels fire immediately without waiting for a page reload.

Part 2: Didomi Web + Didomi Mobile Apps (iOS / Android + Firebase GA4)

Unlike WordPress-only CMPs, Didomi spans web domains, CTV, and native mobile applications under strict French CNIL and EU IAB TCF v2.2 frameworks.

Didomi on Web (GTM + sGTM)

  • Official Didomi GTM Template / Integration: Enable “Google Consent Mode v2” inside the Didomi Console for your web notice.
  • Didomi injects the gtag('consent', 'default', ...) state before your GTM script executes (ensure Didomi <script> sits above <script>...gtm.js in <head>!), then automatically dispatches gtag('consent', 'update', ...) and pushes didomi-consent-changed into dataLayer.
  • Server-Side GTM Forwarding: The GA4 Client in sGTM automatically parses Google’s gcs (G111 / G100) and gcd consent signals from every web event—so Server-Side Meta CAPI and LinkedIn CAPI tags must inspect consent status before forwarding user parameters (em, ph, _fbp).

Didomi Mobile Apps (iOS Swift & Android Kotlin → Firebase GA4)

In mobile apps, web GTM consent signals don’t exist. You must bridge Didomi’s Native Mobile SDK directly to the Firebase Analytics SDK (setConsent):

  1. Android (Didomi + FirebaseAnalytics): Register a Didomi.getInstance().addEventListener inside Application.onCreate(). Map Didomi purpose IDs (e.g., Google Advertising / Analytics purposes configured in your Didomi Notice) directly into FirebaseAnalytics.ConsentStatus:
    • AD_STORAGE (GRANTED / DENIED)
    • ANALYTICS_STORAGE (GRANTED / DENIED)
    • AD_USER_DATA (GRANTED / DENIED)
    • AD_PERSONALIZATION (GRANTED / DENIED) Call firebaseAnalytics.setConsent(consentMap) immediately when SDK becomes ready and whenever onConsentChanged fires!
  2. iOS (Swift + Apple App Tracking Transparency ATT): In iOS, Google Ad Personalization and IDFA additionally depend on Apple’s ATT prompt (ATTrackingManager.requestTrackingAuthorization). Configure Didomi’s ATT + Consent Combined Notice so ATT refusal automatically leaves AD_PERSONALIZATION = .denied in Analytics.setConsent([...]) while still respecting granular analytics consent where legally permitted.
  3. Unify Web & Mobile GA4 Reporting: Validate screen_view and in_app_purchase parameters in GA4 DebugView with both granted and denied consent profiles so cross-platform Web + App attribution doesn’t fracture. See also our Firebase Analytics to GA4 Guide.

Struggling with Complianz, Didomi, Cookiebot, or Iubenda Consent Mode diagnostics? Request a free tracking audit or review our Germany TDDDG Consent Guide.


Frequently Asked Questions

Should I use Complianz’s built-in GA4 integration or manage Google tags inside GTM?

Manage all GA4, Google Ads, and Meta tags inside Google Tag Manager while letting Complianz act strictly as your Consent Management Platform (driving Consent Mode v2 updates and DataLayer consent events). Mixing Complianz hard script-blocking with GTM tags causes misfires and drops returning opted-in visitors.

Yes. Didomi provides native Google Consent Mode v2 mapping inside its Console for web notices (dispatching default and update signals to GTM) and exposes consent status callbacks in its iOS and Android SDKs so developers can update FirebaseAnalytics.setConsent(...) cleanly on every consent change.

Check two culprits: (1) GA4 tags in GTM are mistakenly gated by an “All Consent Given” blocking trigger instead of using Advanced Consent Mode (Ad Storage / Analytics Storage built-in checks), or (2) Complianz fires its update event after GTM initialization without re-triggering pageviews or conversion tags.

Direct Implementation White-Label for Agencies

Need this implemented, audited, or white-labeled?

Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.

✓ 24–48h Emergency SLA ✓ Strict Non-Solicitation & NDA ✓ 8.5+ Event Match Quality
Jobair Mahmud

Jobair Mahmud

AI-Driven Performance Marketing & Web Analytics Consultant

Helping eCommerce brands and marketing agencies trust their ads data, scale Smart Bidding, and eliminate wasted ad spend through bulletproof server-side tracking and PPC management.