← Back to blog

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

Code
collect
and opening a request to Google Analytics or Google Ads.

Reading gcs

Code
gcs
is short and follows a fixed pattern:
Code
G1
followed by two digits.

Valuead_storageanalytics_storage
G100denieddenied
G101deniedgranted
G110granteddenied
G111grantedgranted

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

Code
gcd
is where most of the confusion comes from. It looks something like
Code
11p1p1p1p5
. Ignore the digits; they are separators. The four letters, in order, describe:

  1. Code
    ad_storage
  2. Code
    analytics_storage
  3. Code
    ad_user_data
  4. Code
    ad_personalization

Each letter tells you both the default state and whether an update changed it:

LetterMeaning
lSignal not set at all
pDenied by default, no update
qDenied by default, denied by update
tGranted by default, no update
rDenied by default, granted by update
mNo default, denied by update
nNo default, granted by update
uGranted by default, denied by update
vGranted by default, granted by update

So

Code
11p1p1p1p5
means every signal was denied by default and nothing ever updated it. If a visitor clicked "Accept all" and you still see
Code
p
, the banner is not talking to the tag.

The mistakes this catches

Most problems fall into a handful of patterns:

  • Code
    l
    for the v2 signals.
    Code
    ad_user_data
    and
    Code
    ad_personalization
    were never set, often because the consent platform or template predates v2.
  • Code
    p
    after accepting.
    Defaults are in place but the update never fires, so consent is effectively always denied.
  • Code
    t
    before any choice.
    Signals are granted by default, which is rarely what a privacy policy intends.
  • 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

Code
gcs
and
Code
gcd
values, decodes each signal and explains the result in clear, jargon-free language.

Who 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
    Code
    collect
    and open a Google request.
  • Check
    Code
    gcs
    for the two storage signals.
  • Check
    Code
    gcd
    for all four signals and whether they were updated.
  • 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.