1. Observed Wire Symptom
Installing Cookiebot with data-blockingmode='auto' suppresses gtm.js completely before consent (killing Advanced Consent Mode v2 cookieless modeling pings), or causes third-party tags inside GTM to fire erratically on cookie_consent_update.
2. Technical Root Cause
Cookiebot's DOM MutationObserver (data-blockingmode='auto') rewrites <script> tags lacking data-cookieconsent='ignore' to type='text/plain'—blocking gtm.js from loading at all until consent. When teams try to run Advanced Consent Mode v2 while Auto-Blocking intercepts gtm.js, Google tags cannot transmit gcs=G100 pings on EEA Cold Load.
<!-- Broken for Advanced Consent Mode v2: uc.js blocks gtm.js -->
<script id="Cookiebot" src="https://consent.cookiebot.com/uc.js"
data-cbid="00000000-0000-0000-0000-000000000000"
data-blockingmode="auto"></script>
<!-- Missing data-cookieconsent="ignore" -> GTM is rewritten to text/plain! -->
<script>(function(w,d,s,l,i){...})(window,document,'script','dataLayer','GTM-XXXX');</script><!-- Fixed: Deploy Cookiebot CMP (__cvt) on Consent Initialization -->
<!-- Or mark GTM snippet data-cookieconsent="ignore" with manual gating: -->
<script data-cookieconsent="ignore">
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('consent', 'default', {
ad_storage: 'denied', ad_user_data: 'denied',
ad_personalization: 'denied', analytics_storage: 'denied',
wait_for_update: 500
});
</script>
<script data-cookieconsent="ignore">(function(w,d,s,l,i){...})(window,document,'script','dataLayer','GTM-XXXX');</script>3. Post-Publish Verification Checklist
- ✓If using Advanced Consent Mode v2, add data-cookieconsent='ignore' to your inline consent default snippet and GTM container script.
- ✓Configure GTM Additional Consent Checks on every non-Google tag inside GTM before turning off Cookiebot Auto-Blocking!
- ✓Bind non-Google marketing tags to Custom Event 'cookie_consent_update' with Additional Consent 'ad_storage' required.
4. Practitioner Edge-Case FAQ
- Is Cookiebot Auto-Blocking blocking gtm.js illegal or non-compliant?
- No—blocking gtm.js completely until consent implements Google Basic Consent Mode v2 (0 pre-consent beacons, G111 after Accept All), which is strictly GDPR compliant. However, it forfeits Advanced Consent Mode v2 cookieless behavioral and conversion modeling for unconsented EEA traffic.
- Why does Cookiebot sometimes trigger a full page reload when a user clicks Decline?
- When a visitor revokes previously granted consent (or when Auto-Blocking detects active cookies it must purge), Cookiebot invokes window.location.reload() so server/client scripts re-initialize cleanly in a denied state.
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 CONSENT_SETTINGS_NOT_SET
Paste any storefront URL to inspect live Frankfurt gcs/gcd beacons and exact GTM Tag IDs.