Consent Mode decoder: what do gcs and gcd mean?
Nothing is sent or stored: decoding happens in your browser.
In short
gcs and gcd are two parameters that Google tags add to their requests to pass on the consent state. gcs gives ad_storage and analytics_storage at the moment of the request; gcd describes all four signals, with their default state and their update. This TAGBRUT decoder translates those values: paste a request URL, or just a value, to see whether the default state was set in time and whether the visitor's choice was actually sent.
On this page
Where to find gcs and gcd
- Open your site in a private window, from a country where your Consent Mode applies.
- Open the browser's developer tools, Network tab, and filter on
collect. - Reload the page without answering the banner, then copy the URL of the first GA4 or Google Ads request.
- Paste it into the decoder. Repeat after "Accept all", then in a new private window after "Reject all".
Tag Assistant shows the same states without going through the Network tab.
How to read gcs
gcs is G1 followed by two characters: the first for ad_storage, the second for analytics_storage. It gives the state at the moment the request leaves.
| Value | ad_storage | analytics_storage | Typical situation |
|---|---|---|---|
G100 | denied | denied | Full denial, or no choice yet |
G101 | denied | granted | Analytics accepted, advertising denied |
G110 | granted | denied | Advertising accepted, analytics denied |
G111 | granted | granted | Everything accepted |
G1-- | not set | not set | No state sent |
A G100 request leaving before any choice is the mark of advanced mode: the tag loads and sends a cookieless request. In basic mode, nothing leaves before the visitor chooses.
How to read gcd
In gcd, there is one letter per signal, always in the same order: ad_storage, analytics_storage, ad_user_data, ad_personalization. In 13p3r3p3p5l1, they are the letters in third, fifth, seventh and ninth position: p, r, p, p. Each letter combines the default state and the update.
| Letter | Default | After the choice |
|---|---|---|
l | not set | no update |
p | denied | no update |
q | denied | denied |
r | denied | granted |
t | granted | no update |
u | granted | denied |
v | granted | granted |
m | not set | denied |
n | not set | granted |
Google states what these parameters carry, but we did not find an official table of the letters: this one comes from an open source parser, and we cross-checked it against our own captures. Google also notes that these fields may change.
Example captured on tagbrut.com, from France, after "Accept all": gcs=G101 and gcd=13p3r3p3p5l1. Analytics is granted (r), the advertising signals stay denied (p). That is intentional: our banner offers no advertising.
Typical results, and what to do
| What you read | What it means | What to do |
|---|---|---|
p everywhere, before the choice | Default state set in time | Nothing, then check after the choice |
p everywhere, after the choice | The banner is not pushing the update | Review the link between the banner and Consent Mode |
r or q everywhere | The visitor's choice is sent | Nothing |
m or n | No default state when the request left | Set the default state before tags load |
t, u or v | Signal granted by default | Check the regional setup for EEA visitors |
l everywhere | No signal sent | Check the banner, or test from a covered region |
l on ad_user_data or ad_personalization | Incomplete Consent Mode | Add the two version 2 signals |
What we found at one client
An e-voting SaaS vendor thought they were compliant: the banner was there, and so was Consent Mode. Yet 64% of Google Ads clicks opened no GA4 session, and bidding was learning from a fraction of the traffic. Switch to advanced Consent Mode, default state set before GTM loads, 14 tags rewired to fire from the landing page: modeling of declined conversions is possible again for Google Ads and GA4.
What the decoder cannot see
- Only one request at a time. The loading order between GTM and the banner shows across the whole page, not on one request. Our Consent Mode v2 guide covers the full test.
- Where you test from. If your Consent Mode only targets the EEA, a test run elsewhere shows misleading states.
- Non-Google tags. Meta, LinkedIn or TikTok do not carry these parameters: whether they respect the choice is checked separately.
- Compliance. The decoder reads a technical state; it does not say whether your banner meets the applicable law.
Frequently asked questions
What does gcs=G100 mean?
G100 means ad_storage and analytics_storage are denied at the moment of the request. That is normal before the visitor chooses, or after a denial. Such a request only exists in advanced mode, because in basic mode Google tags do not load before the choice.
What does gcs=G111 mean?
G111 means ad_storage and analytics_storage are granted at the moment of the request. If this value appears before any click on the banner for a visitor in the EEA, consent is granted by default or an earlier choice was kept: run the test again in a private window.
Why does gcd appear when I do not use Consent Mode?
Because Google sends it either way, whether Consent Mode is on or not. The presence of gcd proves nothing: its letters are what matters. l everywhere means no state was sent.
What does the letter n mean in gcd?
That a signal was granted by an update while no default state existed when the request left. Most often, the default state arrives too late, or only applies to a different region from the one tested.
Does the decoder keep what I paste?
No. Decoding happens in your browser, and the pasted value is neither sent to TAGBRUT nor stored. A request URL can contain identifiers: you can paste just the gcs or gcd value.
When to call in an expert
- The decoder shows red or amber, and you do not know why.
- Your conversions dropped after a banner change.
- Google Ads and GA4 no longer count the same visits.
- You do not know whether your site runs basic or advanced mode.
The diagnosis is free: the five findings that cost the most, quantified, and what we would do first, in writing within 2 business days of read access to your account.
Sources (4)
- Google for Developers, "Consent mode overview": `gcs` and `gcd` HTTP parameters, `gcd` always sent, fields subject to change, basic and advanced modes, the four consent types. developers.google.com/tag-platform/security/concepts/consent-mode
- Google Ads Help, "About consent mode".
- Analytics Debugger, open source GTM template "Google Consent Parser": `gcd` decoding (default state and update of each signal). github.com/analytics-debugger/gtm-template-server-side-google-consent-parser
- TAGBRUT, request captures on tagbrut.com on 24/10/2026 (
G100and13p3p3p3p5l1before the choice,G101and13p3r3p3p5l1after acceptance,G100and13p3q3p3p5l1after denial).
More guides
- Consent Mode v2: basic or advanced, and how do you fix tracking after a cookie banner change?Read the guide
- How do you send CRM sales back to Google Ads?Read the guide
- How do you check that your Google Ads conversions are accurate?Read the guide
- Server-side tagging or Google Tag Gateway: which one do you need?Read the guide
- What is a tracking plan, and how do you build one?Read the guide