Choose a language

Person testing a consent banner on a phone in front of a laptop

How to Verify Google Consent Mode v2 Without Losing Data

Published November 5, 2026 · Mis à jour le November 16, 2026 · 16 min read

Consent Mode v2 adds two signals on top of the original two: ad_user_data and ad_personalization now sit alongside ad_storage and analytics_storage. The version arrived with Google's November 2023 update, and on sites that serve EEA visitors it is now part of keeping Google Ads measurement and personalization working. The practical question is not whether you installed it, but whether it is actually firing.

This guide walks through verification in order. You will learn what each signal controls, how the default state differs from the update that fires when someone clicks your banner, where to see the state in Tag Assistant and GTM Preview, and how to read the gcs parameter in a network request. It closes with a monitoring routine and a grace period so you do not panic over normal latency.

The path in 6 steps

The steps of this page, in order.

  1. 01 Know the signals Understand what each of the four consent signals controls before you test anything.
  2. 02 Set your default Know what state the page should be in before the visitor touches the banner.
  3. 03 Confirm in tools Use Tag Assistant and GTM Preview to see the state the page reports.
  4. 04 Read the request Inspect the gcs value in network requests to prove signals leave the browser.
  5. 05 Debug failures Match common symptoms to causes before blaming Google.
  6. 06 Monitor after launch Watch the signals weekly and give yourself a grace period before calling it data loss.

02 / 10

What is the difference between the default and update consent state?

The default state applies before the visitor makes a choice; the update state applies the moment their choice changes, and the two must be verified separately.

No consent values exist until a page explicitly pushes a default state, the set of yes/no values the page assumes before the visitor makes any choice. That push belongs on every page load, first thing, with consent signals denied for any region where your banner is shown.

The update state is the new set of values sent when the visitor clicks the banner; only then does that session change. Test the two separately, because a correct default can hide a broken update, and a working update can mask a default that never fired.

Default pushed on every page load

Confirm the default consent command runs before any tag and on every template, not just the homepage. A single page that loads tags first will send data before consent.

Region scoping matches your banner

Scope the default to the regions where your banner actually appears. If your banner shows only to EEA visitors, your default should name those regions; a global default would deny consent for visitors who never saw a banner.

Update wired to the banner callback

Check that the update command fires from the banner's accept or reject callback, not on a timer. Verify it runs once per choice, since a repeated update can overwrite a later decision.

05 / 10

How do I read the gcs parameter in a network request?

Open the browser network tab, filter for requests to Google endpoints, and read the gcs value, which encodes the ad_storage and analytics_storage state.

The gcs parameter, a short code attached to Google requests that encodes the current consent state, appears on hits sent to Google endpoints from your tags. Open DevTools, filter the request list to those domains, and check whether the value matches what you selected before and after a consent change.

That comparison proves the state set in Tag Assistant is transmitted on the wire, not merely stored locally. If the code does not flip when consent is granted or denied, the tag is not propagating consent.

  1. Open the network panel

    In Chrome DevTools, go to the Network tab and reload the page with your consent banner reset.

  2. Filter for Google requests

    Type a Google collection endpoint in the filter box so only tag hits remain in the list.

  3. Read the gcs value

    Click a request, open the query string parameters, and find the gcs key.

  4. Compare before and after

    Grant consent in the banner, trigger a new hit, and confirm the gcs value changed.

Going further

Decode the gcs value

06 / 10

What actually happens to GA4 and Google Ads data when consent is denied?

In advanced mode, tags still load and send cookieless pings that Google can use for modeling; in basic mode, tags are blocked and no data flows until consent is granted.

In advanced mode, a denied analytics_storage signal does not blank out GA4. Tags still fire and send cookieless pings containing no identifiers; Google can use those pings to feed conversion modeling, its estimation of conversions it cannot observe directly when consent is missing. So you lose identifiers, not the event itself, expect lower counts, with modeling filling part of the gap.

When the ad signals (ad_user_data, ad_personalization) are denied, Google Ads keeps the cookieless ping but cannot build remarketing audiences or serve personalized ads from that traffic. In basic mode, nothing fires at all until consent is granted, so there is no estimate to model. Hits collected while consent was denied on the same page do not need to be resent once consent is granted.

09 / 10

Frequently asked questions

Frequently asked questions

10 / 10

Sources, data and disclaimer

The Web Insider editorial team
About the author The Web Insider editorial team

Web Insider is a practical magazine for people who build, run or grow a website. Every fact is checked against its official source, and every test shows its proof.

Your feedback

Was this page helpful?

Share

Could this page help someone?

Explore the topicData & Analytics

Audience measurement, Google Analytics 4 and Google Tag Manager: set them up, check them and keep your data reliable.

Explore the topicWebsites & Platforms

WordPress, Shopify, PrestaShop and WooCommerce: run, integrate and maintain a site without making it fragile.

Explore the topicGuides & How-Tos

Methods, training and practical benchmarks to scope a web project, test a site and make better decisions.

Explore the topicSecurity & Compliance

Backups, updates, GDPR, cookies and audience measurement: keep a site safe and compliant.