Making Google Consent Mode v2 readable for non-technical teams
Why the gcs and gcd values in a Google tag request confuse almost everyone, what they actually mean and why I built a small checker that explains them in plain English.
The question nobody can answer quickly
"Is consent mode working?" sounds like a yes or no question. In practice it usually turns into a screen share, a browser's network tab and someone squinting at a request URL full of short, cryptic parameters.
Marketing, editorial and analytics colleagues are often the people who need the answer, but the evidence is written for developers. That gap is what the Consent Mode Checker is for: paste in the values, get a plain-English explanation back.
Where the answer lives
When a page using the Google tag sends a hit, the request carries two parameters that describe consent:
- gcs – the current state of the two original storage signals.
- gcd – a longer value that describes all four Consent Mode v2 signals and how each one reached its current state.
You can find both in your browser's developer tools by filtering the network tab for
collectReading gcs
gcsG1| Value | ad_storage | analytics_storage |
|---|---|---|
| G100 | denied | denied |
| G101 | denied | granted |
| G110 | granted | denied |
| G111 | granted | granted |
That is useful, but it only covers two of the four signals Consent Mode v2 cares about and it says nothing about whether the banner actually updated anything.
Reading gcd
gcd11p1p1p1p5- Code
ad_storage - Code
analytics_storage - Code
ad_user_data - Code
ad_personalization
Each letter tells you both the default state and whether an update changed it:
| Letter | Meaning |
|---|---|
| l | Signal not set at all |
| p | Denied by default, no update |
| q | Denied by default, denied by update |
| t | Granted by default, no update |
| r | Denied by default, granted by update |
| m | No default, denied by update |
| n | No default, granted by update |
| u | Granted by default, denied by update |
| v | Granted by default, granted by update |
So
11p1p1p1p5pThe mistakes this catches
Most problems fall into a handful of patterns:
- for the v2 signals.Code
landCodead_user_datawere never set, often because the consent platform or template predates v2.Codead_personalization - after accepting. Defaults are in place but the update never fires, so consent is effectively always denied.Code
p - before any choice. Signals are granted by default, which is rarely what a privacy policy intends.Code
t - Mismatched signals. Analytics updates correctly while the ad signals stay at their default, which usually points to a partial mapping in the consent platform.
Why I built a checker instead of a guide
A table like the one above is accurate, but asking someone to decode a ten-character string under pressure is not a good experience. The checker takes the
gcsgcdWho it is for
The point is to change who can answer the question. Instead of every consent check routing through an engineer, an analyst or marketer can confirm the behaviour themselves and bring a specific finding when something is wrong: "ad_user_data is never set" is a far quicker conversation than "consent looks broken".
That is a pattern I come back to often as a technical leader: the most valuable tools are frequently the small ones that turn specialist knowledge into something the wider team can use on their own.
Quick checklist
- Filter the network tab for and open a Google request.Code
collect - Check for the two storage signals.Code
gcs - Check for all four signals and whether they were updated.Code
gcd - Test three journeys: no interaction, accept all and reject all.
- Expect the letters to change between those journeys. If they don't, the banner is not updating the tag.