1. Observed Wire Symptom
Multi-national storefronts intend to default EEA/UK visitors to 'denied' and US/APAC visitors to 'granted', yet German or British visitors transmit gcs=G111 (BROKEN_DEFAULT_GRANTED) on Cold Load before interacting with the banner.
2. Technical Root Cause
gtag('consent', 'default', { region: [...] }) strictly requires valid ISO 3166-1 alpha-2 two-letter country codes (or ISO 3166-2 subdivision codes like 'US-CA'). Passing non-ISO shorthands like 'EU', 'EEA', or 'UK' (instead of 'GB' and all 30 EEA member codes + 'CH') causes gtag.js to ignore the regional rule and fall through to your global 'granted' default!
<script>
// FATAL BUG: 'EU' and 'UK' are NOT valid ISO 3166-1 alpha-2 codes!
// German & British visitors fall through to global 'granted' below!
gtag('consent', 'default', {
ad_storage: 'denied', analytics_storage: 'denied',
ad_user_data: 'denied', ad_personalization: 'denied',
region: ['EU', 'UK']
});
gtag('consent', 'default', {
ad_storage: 'granted', analytics_storage: 'granted',
ad_user_data: 'granted', ad_personalization: 'granted'
});
</script><script>
// 1. Explicit 30 EEA + GB + CH ISO 3166-1 alpha-2 country codes -> denied
gtag('consent', 'default', {
ad_storage: 'denied', analytics_storage: 'denied',
ad_user_data: 'denied', ad_personalization: 'denied',
wait_for_update: 500,
region: [
'AT','BE','BG','HR','CY','CZ','DK','EE','FI','FR','DE','GR',
'HU','IS','IE','IT','LV','LI','LT','LU','MT','NL','NO','PL',
'PT','RO','SK','SI','ES','SE','GB','CH'
]
});
// 2. Unscoped Rest-of-World fallback (evaluated when outside region list)
gtag('consent', 'default', {
ad_storage: 'granted', analytics_storage: 'granted',
ad_user_data: 'granted', ad_personalization: 'granted'
});
</script>3. Post-Publish Verification Checklist
- ✓Replace any 'EU', 'EEA', or 'UK' strings in region arrays with all 30 EEA ISO country codes plus 'GB' and 'CH'.
- ✓Verify from an EEA exit node (e.g., Frankfurt DE) that Cold Load /g/collect emits gcs=G100 & gcd=13p3p3p2p5 despite the global granted fallback.
- ✓Honor Sec-GPC: 1 / navigator.globalPrivacyControl in US states (e.g., US-CA, US-CO, US-CT) before granting ad_user_data and ad_personalization.
4. Practitioner Edge-Case FAQ
- Does declaration order matter between a region-scoped consent default and an unscoped global consent default?
- In Google's gtag runtime, a matching region-specific default rule takes precedence over an unscoped global default regardless of which push appeared first—provided both execute synchronously before gtm.js. Declaring the strict EEA rule first followed by the unscoped fallback is canonical.
- Can we target specific US states like California inside gtag region arrays?
- Yes. ISO 3166-2 subdivision codes such as 'US-CA', 'US-CO', 'US-CT', 'US-VA', and 'US-TX' are supported by Google's edge geolocation in gtag('consent', 'default', { region: ['US-CA', ...] }).
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 PRE_CONSENT_MARKETING_LEAK
Paste any storefront URL to inspect live Frankfurt gcs/gcd beacons and exact GTM Tag IDs.