ConsentPulse
<- All Guides/Consent Mode v2/MISSING_V2_PARAMETERS

Basic vs. Advanced Consent Mode v2: Auditing Zero-Beacon Containers

Distinguishing compliant Basic Consent Mode blocking (0 Cold/Reject hits -> G111 on Accept) from broken containers.

1. Observed Wire Symptom

On EEA Cold Load and after clicking Reject All, zero /g/collect or Google Ads network requests fire—causing naive single-pass Consent Mode checkers to falsely report 'Consent Mode Not Implemented' on a strictly compliant Basic Consent Mode v2 site.

2. Technical Root Cause

Google supports two compliant Consent Mode v2 architectures: Advanced Mode loads Google tags immediately so they send cookieless gcs=G100 pings prior to consent, whereas Basic Mode suppresses Google tags completely until consent is granted (via CMP script blocking in CookieYes/Complianz/Borlabs or GTM Additional Consent Checks). You can only validate Basic Mode by executing an Accept All pass and inspecting slots 3 and 4 of gcd.

BROKEN PATTERN
# Broken "Pseudo-Basic" Setup (Legacy v1 after unblocking):
Cold Load:  0 Google beacons (tags blocked until consent)
Reject All: 0 Google beacons
Accept All: /g/collect fires with gcs=G111 & gcd=13t3t3l2l5
# Slots 3 & 4 ('l') prove ad_user_data & ad_personalization were never set!
REMEDIATED PATTERN
# Compliant Basic Consent Mode v2 Wire Signature:
Cold Load:  0 Google beacons (strictly blocked before consent)
Reject All: 0 Google beacons (strictly blocked after opt-out)
Accept All: /g/collect fires with gcs=G111 (or GA4-only G101)
            AND gcd=13r3r3r2r5 (or 13t3t3t2t5 / 13n3n3n2n5)
            where slots 3 & 4 (ad_user_data, ad_personalization) != 'l'.

3. Post-Publish Verification Checklist

  • ✓Never judge Consent Mode v2 from a Cold Load pass alone—always test Cold Load, Reject All, AND Accept All.
  • ✓To enforce Basic Mode inside GTM, set Additional Consent Checks -> Require 'analytics_storage' on GA4 and 'ad_storage' on Google Ads tags, plus trigger on your CMP's consent-update event.
  • ✓To switch to Advanced Mode for Google Ads behavioral modeling, keep synchronous default 'denied' in <head> and set Google tags to 'No additional consent required' (relying on Built-In Consent Checks).

4. Practitioner Edge-Case FAQ

When should a DACH / German agency choose Basic Consent Mode v2 over Advanced?
Strict DPO interpretations under Germany's TDDDG (§ 25) and certain EU DPAs prefer zero outbound pings to Google endpoints prior to opt-in (Basic Consent Mode v2). Trade-off: Basic Mode loses unconsented behavioural modeling in GA4 and uses coarser conversion modeling in Google Ads.
Why does a Basic Mode container become 'Stuck in Denied' when Google Tag uses only Initialization - All Pages?
If you add 'Require additional consent: analytics_storage' to your Google Tag (__googtag) and leave its only trigger as 'Initialization - All Pages', GTM blocks it on Cold Load and never re-evaluates Initialization when the visitor clicks Accept All on Page 1. Add your CMP consent-update trigger alongside Initialization.

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.

Audit URL Free ->
View 2,328-Site Study ->