Skip to content

Guide

Consent Mode v2: How to Test What Your Site Sends Before and After Reject

  • consent mode v2
  • consent mode v2 checker
  • google consent mode
  • gcs parameter
  • gcd parameter
  • ad_user_data
  • ad_personalization
  • cookie banner test

Your consent banner looks right. It appears on the first visit, it has Accept and Reject buttons, and your consent platform’s dashboard says Consent Mode v2 is enabled. What none of that tells you is what your site actually sends to Google, Meta and TikTok before the visitor decides, and after they click Reject.

This guide shows how to test that yourself in about ten minutes with the browser you already have, how to read the gcs and gcd parameters that Google tags attach to every request, and the most common reasons a correctly configured banner still leaks requests. If you would rather have the test run for you, our free Consent Mode v2 checker automates both scenarios.

A note before we start: this is a technical guide to what your site sends. It is not legal advice, and a clean test result is not a compliance certificate.

Consent Mode is Google’s way of telling its tags (GA4, Google Ads, Floodlight) what the visitor agreed to. The original version had two signals:

  • ad_storage: may advertising cookies be read and written?
  • analytics_storage: may analytics cookies be read and written?

Version 2 added two more, and made them a requirement for advertisers who want to use data from visitors in the European Economic Area for measurement, remarketing and audiences:

  • ad_user_data: may user data be sent to Google for advertising?
  • ad_personalization: may the data be used for personalised advertising, such as remarketing?

When the two new signals are missing for EEA visitors, Google Ads loses conversions and audience data it would otherwise be allowed to use, which adds to the signal loss your campaigns already face.

Each signal is either granted or denied. Your site sets a default state before any Google tag runs, and then an update when the visitor makes a choice:

gtag('consent', 'default', {
  ad_storage: 'denied',
  analytics_storage: 'denied',
  ad_user_data: 'denied',
  ad_personalization: 'denied',
  wait_for_update: 500,
});

// Later, after the visitor accepts:
gtag('consent', 'update', {
  ad_storage: 'granted',
  analytics_storage: 'granted',
  ad_user_data: 'granted',
  ad_personalization: 'granted',
});

Most consent platforms write these calls for you. The test below checks that they happen, in the right order, with all four signals.

Basic and advanced mode

There are two ways to run Consent Mode, and they produce different test results:

  • Basic mode: Google tags do not load at all until the visitor consents. Before consent you should see no Google requests.
  • Advanced mode: Google tags load immediately with the default state denied and send cookieless pings that Google uses for modelling. Before consent you should see Google requests, and they must carry the denied state.

Both are valid setups. Know which one you chose before you read the results, or a correct advanced setup will look like a leak.

Reading gcs and gcd in the Network tab

Every request a Google tag sends carries the consent state in two parameters.

gcs is the short one. It starts with G1 and then has one digit for ad_storage and one for analytics_storage, where 1 means granted and 0 means denied:

gcs ad_storage analytics_storage
G100 denied denied
G110 granted denied
G101 denied granted
G111 granted granted

If a Google request has no gcs parameter, the tag ran without any Consent Mode state. That usually means the default was never set, or it was set after the tag had already fired.

gcd is the longer one, for example 13p3p3p3p5. It encodes all four v2 signals, and each one is a letter that records both the default and the update. You do not need to decode every character. The letters worth knowing:

Letter Meaning
l Signal not set at all
p Denied by default, no update yet
q Denied by default, denied again by the update
r Denied by default, granted by the update
t Granted by default, no update
u Granted by default, denied by the update
v Granted by default, granted by the update
m / n No default, then denied (m) or granted (n) by an update

The letters appear in a fixed order: ad_storage, analytics_storage, ad_user_data, ad_personalization. So 13p3p3p3p5 means all four signals denied by default and no choice made yet, which is exactly what you want to see before the visitor touches the banner. An l in the third or fourth position means ad_user_data or ad_personalization is missing: your setup is still on Consent Mode v1. Newer tag versions sometimes add a few more characters after the last digit; the four letters are what matters.

Test 1: before any interaction

  1. Open a private window so no earlier consent choice is stored.
  2. Open DevTools (right click, Inspect) and go to the Network tab. Tick “Preserve log”.
  3. Load your home page and do not touch the banner.
  4. Filter by collect to see GA4 and Google Ads requests. Then filter by facebook.com/tr, analytics.tiktok.com, ct.pinterest.com and any other vendor you use.

What you are looking for:

  • Google requests should either be absent (basic mode) or carry gcs=G100 and a gcd with p in all four positions (advanced mode, all denied by default). If you have chosen to grant some signals by default for visitors outside the EEA, you will see that here too.
  • Meta, TikTok, Pinterest and other non-Google requests should be absent if your banner is meant to ask first. These vendors do not read Google’s consent signals. Consent Mode does nothing for them; only your consent platform or your tag manager can hold them back.
  • Cookies: in the Application tab, check whether _ga, _gcl_au, _fbp or _ttp were already written. In advanced mode with everything denied, Google should not set its cookies.

Test 2: after Reject

  1. In the same private window, click Reject (or “Reject all”, or save the settings with every optional category off).
  2. Clear the Network log, then reload and browse to a second page, for example a product page.
  3. Repeat the same filters.

After Reject:

  • Google requests should carry gcs=G100, and the gcd letters should change from p to q (denied by default, denied again by the update). If you still see p, the update was never sent: your banner recorded the choice but did not tell the Google tags.
  • No Meta, TikTok, Pinterest or Reddit requests should appear at all. This is where most leaks are found.

For completeness, run a third pass with Accept: you should see gcs=G111, r letters in gcd, and the other vendors’ requests appearing. If nothing changes after Accept, your tags are blocked permanently, which costs you data you are allowed to collect.

Common causes when the test fails

Tags installed outside the tag manager. A pixel pasted into the theme, or injected by a platform app, does not pass through your consent platform’s rules. It fires on every page regardless of the banner. This is the single most common cause of requests after Reject.

The default is set too late. The gtag('consent', 'default', ...) call must run before any Google tag. If your consent platform’s script loads asynchronously after GTM, the first hits go out with no consent state at all. Look for Google requests without gcs.

Only two of the four signals are set. Older consent platform versions and hand-written snippets often set only ad_storage and analytics_storage. The gcd shows l for the other two. Update the platform or add the two missing keys.

Tags in GTM have no consent check. In Google Tag Manager, non-Google tags (Meta, TikTok, custom HTML) need a consent requirement or a trigger condition tied to your consent categories. Without one, they fire on page load.

Consent is read only on the first page. Some setups apply the choice on the page where it was made, but on the next page tags fire again before the stored choice is read. That is why Test 2 loads a second page.

Run both tests automatically

The manual test is worth doing once so you understand what you are looking at. After that, it is repetitive, and it has to be repeated after every new app, theme update or tag change.

Our free Consent Mode v2 checker runs both scenarios in a real browser:

  1. It loads your page and records every tracking request sent before any interaction, with the time it was sent.
  2. It detects your consent banner, clicks Reject using the open source DuckDuckGo autoconsent rules, and records everything sent after the refusal.
  3. It decodes gcs and gcd on every Google request and reports whether ad_user_data and ad_personalization are present.
  4. It stops every tracking request before it leaves the scanner, so nothing reaches your ad or analytics accounts.

The result lists observations, for example “3 requests were sent before any banner interaction”, with the vendor and timing of each request and the steps to fix it. The same checks are part of the full website tracking checker.

Frequently asked questions

Not by itself. In advanced mode, Google tags send cookieless pings with the denied state, and that is how the mode is designed. What matters is that those requests carry gcs=G100 and all four signals in gcd, and that no cookies are set.

No. Consent Mode is read only by Google tags. Meta, TikTok, Pinterest and other pixels have to be blocked or allowed by your consent platform or by consent conditions in your tag manager. Meta has its own consent call (fbq('consent', 'revoke') and fbq('consent', 'grant')), which your consent platform may or may not use.

What does “G100” mean?

G100 means both ad_storage and analytics_storage are denied. G111 means both are granted. The last two digits are ad storage and analytics storage, in that order.

Does a clean test mean my site is compliant?

No. The test shows what your site sends in one browser session. Compliance also depends on the wording of your banner, your legal basis, your records of consent and the jurisdictions you serve. Ask a privacy professional for that assessment.

Written by

Chris Gaudy

Founder & CEO

Building accurate conversion tracking for e-commerce teams.

Get tracking insights in your inbox

Tips on server-side tracking, conversion optimization, and product updates. Delivered weekly.

No spam. Unsubscribe anytime.