1. Observed Wire Symptom
Outbound /g/collect and /pagead/conversion/ beacons carry opaque query strings such as gcs=G111 alongside gcd=13r3r3l2l5 or gcd=11l1l1l1l5, masking missing Consent Mode v2 signals (ad_user_data and ad_personalization) behind an apparently healthy gcs=G111 value.
2. Technical Root Cause
The legacy gcs parameter (G1<ad_storage><analytics_storage>) only encodes two Consent Mode v1 storage flags. Google Ads audience population and EEA conversion modeling inspect the four sequential letter slots inside gcd: 11/13<ad_storage><sep><analytics_storage><sep><ad_user_data><sep><ad_personalization>5. When slots 3 and 4 emit 'l' (uninitialized), your CMP or GTM template is still running legacy Consent Mode v1.
GET /g/collect?v=2&tid=G-XXXX&gcs=G111&gcd=13r3r3l2l5
# Slot 1 (ad_storage): 'r' (denied -> granted)
# Slot 2 (analytics_storage): 'r' (denied -> granted)
# Slot 3 (ad_user_data): 'l' (NOT INITIALIZED -> v1 legacy!)
# Slot 4 (ad_personalization):'l' (NOT INITIALIZED -> v1 legacy!)# Compliant Advanced Consent Mode v2 Wire Transitions:
# 1. EEA Cold Load: gcs=G100 & gcd=13p3p3p2p5
# ('p' = default denied, no update yet across all 4 signals)
# 2. EEA Reject All: gcs=G100 & gcd=13q3q3q2q5
# ('q' = default denied -> explicit update denied)
# 3. EEA Accept All: gcs=G111 & gcd=13r3r3r2r5
# ('r' = default denied -> explicit update granted)
# Race / Error Letters:
# 't'/'v' = default granted | 'u' = granted->denied race
# 'm'/'n' = update fired without prior consent default3. Post-Publish Verification Checklist
- ✓Filter Chrome DevTools Network by '/g/collect' or 'pagead' and inspect gcd rather than relying solely on gcs.
- ✓Verify EEA Cold Load emits 'p' across all four gcd letter slots (e.g., gcd=13p3p3p2p5), never 'l', 't', or 'v'.
- ✓Verify clicking Accept All transitions granted signals from 'p' to 'r' across slots 3 and 4 (ad_user_data and ad_personalization).
4. Practitioner Edge-Case FAQ
- What do the digits 11, 13, 2, 3, and trailing 5 inside gcd=13p3p3p2p5 mean?
- The leading two digits ('11' or '13') denote Google's internal gcd schema version, the single digits between letters are field delimiters encoding signal metadata, and '5' marks the end terminator. Always extract the four lowercase letter slots in order: ad_storage, analytics_storage, ad_user_data, and ad_personalization.
- What does letter 'u' or 'n' inside gcd indicate during an audit?
- Letter 'u' means a signal defaulted to 'granted' and was later updated to 'denied' (a <head> race leak). Letter 'n' means a CMP pushed consent 'update: granted' without any prior gtag('consent', 'default', ...) declaration—acceptable in strict Basic Blocking only if zero Google tags fired prior to 'n'.
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 MISSING_V2_PARAMETERS
Paste any storefront URL to inspect live Frankfurt gcs/gcd beacons and exact GTM Tag IDs.