1. Observed Wire Symptom
Clicking 'Reject All' stops GA4 cookies (gcs=G100), while facebook.com/tr, analytics.tiktok.com, px.ads.linkedin.com, and clarity.ms continue firing full marketing beacons on every page view.
2. Technical Root Cause
CMP plugins emit signals (gtag('consent', ...)), they do not rewrite GTM's execution engine. Native GA4 and Google Ads tags have Built-In Consent Checks, whereas Custom HTML tags (__html) and many third-party community templates ignore Consent Mode completely when bound to Trigger #2 (All Pages) with Additional Consent Checks left unset.
GTM Tag #14: "Meta Pixel - Base Code" (Type: Custom HTML)
Firing Trigger: All Pages (gtm.js)
Consent Settings -> Additional Consent Checks: Not set
Result: Fires unconditionally on EEA Cold Load AND Reject All.GTM Tag #14: "Meta Pixel - Base Code" (Type: Custom HTML)
1. GTM Admin -> Container Settings -> Enable Consent Overview.
2. Tag -> Advanced Settings -> Consent Settings:
"Require additional consent for tag to fire" -> ad_storage.
3. Replace "All Pages" with your CMP post-consent event trigger
(e.g., Custom Event "cookie_consent_update") so Page-1
Accept clicks fire Meta immediately without a page reload.3. Post-Publish Verification Checklist
- ✓Enable 'Consent Overview' in GTM Container Settings and audit every tag under 'Consent Not Configured'.
- ✓Add ad_storage under Additional Consent Checks on Meta, TikTok, LinkedIn, Bing UET, Pinterest, Snap, and Criteo tags.
- ✓Add analytics_storage on Microsoft Clarity and Hotjar tags, and re-test Cold Load + Reject All from an EEA exit node.
4. Practitioner Edge-Case FAQ
- Why did adding 'Require additional consent: ad_storage' stop Meta Pixel from firing on Page 1 after clicking Accept All?
- Additional Consent Checks act as a blocking gate at the moment the tag's Firing Trigger evaluates—they do not retroactively re-fire an 'All Pages (gtm.js)' trigger that was suppressed at 0ms. Pair Additional Consent Checks with your CMP's consent-ready custom event trigger (e.g., cookie_consent_update or OneTrustGroupsUpdated) so Page-1 accepts fire the pixel immediately.
- Do paused GTM Custom HTML tags still trigger Consent Mode audit failures?
- Paused tags carry "paused": true in the compiled gtm.js resource AST and do not execute at runtime. However, leaving unguarded legacy tags paused creates publish drift risk if a marketer unpauses them without reviewing Consent Overview.
Did this GTM remediation playbook help resolve your issue?
1-click practitioner feedback — shapes which CMP & GTM edge cases we document next.
Verify If Your Container Suffers From CUSTOM_HTML_BYPASSES_CONSENT
Paste any storefront URL to inspect live Frankfurt gcs/gcd beacons and exact GTM Tag IDs.