1. Observed Wire Symptom
window.dataLayer shows gtm.js initializing at index 0 while ['consent', 'default', {...}] arrives 150–400ms later at index 3+, producing uninitialized gcd=11l1l1l1l5 (no_default) beacons on initial landing.
2. Technical Root Cause
When an agency loads a CMP via a GTM tag on 'Initialization' or 'All Pages', or places an async CMP <script> tag without a synchronous inline gtag('consent', 'default', ...) block above GTM in <head>, gtm.js evaluates tags before the CMP finishes downloading.
<head>
<!-- Broken: Async CMP + GTM download in parallel; gtm.js often wins -->
<script async src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js"></script>
<script>(function(w,d,s,l,i){...})(window,document,'script','dataLayer','GTM-XXXX');</script>
</head><head>
<!-- 1. Synchronous Consent Mode v2 default MUST execute first -->
<script>
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>
<!-- 2. Load CMP SDK + GTM container after default is locked in -->
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js"></script>
<script>(function(w,d,s,l,i){...})(window,document,'script','dataLayer','GTM-XXXX');</script>
</head>3. Post-Publish Verification Checklist
- ✓Place synchronous inline gtag('consent', 'default', ...) strictly above the GTM container snippet in <head>.
- ✓Inspect window.dataLayer in DevTools Console: ['consent', 'default', ...] must appear at index 0 before {'gtm.start': ..., event: 'gtm.js'}.
- ✓If deploying your CMP via a GTM Community Template, bind it strictly to 'Consent Initialization - All Pages'.
4. Practitioner Edge-Case FAQ
- Does GTM's 'Consent Initialization - All Pages' trigger run before 'Initialization - All Pages'?
- Yes. GTM's trigger lifecycle executes strictly in order: (1) Consent Initialization - All Pages, (2) Initialization - All Pages, (3) All Pages (gtm.js). Any GTM CMP template must fire on step 1 so default consent exists before Google Tags fire on step 2.
- Why do Next.js and Nuxt apps frequently trigger CONSENT_DEFAULT_AFTER_GTM?
- Framework <Script strategy='afterInteractive'> components hydrate asynchronously in unpredictable order. Render your gtag('consent', 'default', ...) inline script in the server HTML <head> (strategy='beforeInteractive' in Next.js) above the GTM snippet.
Did this GTM remediation playbook help resolve your issue?
1-click practitioner feedback — shapes which CMP & GTM edge cases we document next.
✓ Thanks — your feedback was logged to our diagnostic accuracy telemetry.
Verify If Your Container Suffers From CONSENT_DEFAULT_AFTER_GTM
Paste any storefront URL to inspect live Frankfurt gcs/gcd beacons and exact GTM Tag IDs.
Related Remediation Playbooks
View 2,328-Site Study ->Head Race Conditions
Read guide ->Fixing Missing wait_for_update: Why Returning Consented Users Send gcs=G100
Consent Mode v2
Read guide ->Multi-Region gtag('consent', 'default') Scoping: EEA Denied + US Granted
Head Race Conditions
Read guide ->