hello@datascale.de+49 89 921 35 623DEEN

Search services, integrations and blog posts.

HomeBlogConsent Mode V2 in Practice: Basic, Advanced and QA

GDPR

Consent Mode V2 in Practice: Basic, Advanced and QA

Audit Consent Mode V2: distinguish Basic and Advanced, inspect defaults and updates with Tag Assistant, and verify each destination.

The CMP captures the choice; Consent Mode communicates it. analytics_storage and ad_storage govern storage, ad_user_data covers sending user data for advertising, and ad_personalization covers personalized advertising. These signals replace neither the banner nor checks for other destinations such as Meta or LinkedIn.

Basic and Advanced compared

QuestionBasicAdvanced
Before consentGoogle tags blocked; no data to GoogleGoogle tags load with defaults; restricted measurements possible
On rejectionNo data to GoogleCookieless measurements; no storage prohibited by denied signals
Ads conversion modelingGeneral modelAdvertiser-specific model, subject to eligibility

Basic does not eliminate all conversion modeling. Advanced does not guarantee a fixed number of recovered conversions. Google describes the distinction in its Consent Mode documentation.

Cookieless does not automatically mean anonymous or legally permitted. Document the chosen mode and assess the actual data flows.

Five errors to test directly

  1. Late default. Check whether dependent tags run first. CMP templates and manual integrations have different initialization paths.
  2. Missing update. Test acceptance, rejection and partial choices separately.
  3. Competing defaults. A manual snippet must not overwrite the CMP decision.
  4. Incorrect mapping. Analytics consent must not accidentally enable advertising use.
  5. Unchecked destination. A correct Google signal does not establish how third-party tags or server templates behave.

The Usercentrics guide follows the chain into the server. The GA4 audit guide covers other measurement failures.

Debug with Tag Assistant instead of a fixed gcd format

Open Tag Assistant and inspect the earliest consent state and the update following the banner choice. Then compare network activity and server preview against expectations for the selected mode.

gcs and gcd carry consent information. Google notes that encoding may change. An eight-character pattern is not a reliable decoder, and the presence of gcd alone does not establish that Consent Mode is active.

QA before the next release

Test first visit, stored choice, acceptance, rejection, partial consent and withdrawal. Repeat relevant cases after SPA navigation. Record expected cookies, requests and states per destination in the CMP/GTM QA template.

The June 2026 change concerns controls in linked GA4/Google Ads setups. Keep it separate from the choice between Basic and Advanced.

Is Consent Mode a cookie banner?

No. The CMP captures the choice; Consent Mode communicates it to supporting tags. Both parts need to work together.

Does Basic mode eliminate conversion modeling?

No. Google distinguishes a general model with Basic from an advertiser-specific model with Advanced. Availability depends on other eligibility requirements.

Does a gcd parameter prove correct implementation?

No. Inspect defaults, updates and actual tag behavior with Tag Assistant and, where applicable, server preview.

Do we also need server-side tracking?

That depends on data flows and operational needs. Consent Mode and server-side tracking serve different purposes. The hosting guide helps with the architecture decision.

Alex Grieskamp

Author

Alex Grieskamp

Moved from finance into digital analytics, builds technically demanding tracking setups and explains them clearly.

Ask a question →

From practice

What you read here, we test against your setup.

Prioritised findings with effort estimates and next steps. From €1,490 net, no follow-up obligation.