Google Consent Mode Decoder (gcs & gcd)
Every GA4 and Google Ads request carries your visitor's consent in two short codes, gcs and gcd. Paste a request and see, in plain words, what was granted or denied, whether a default was set, and whether Consent Mode v2 is complete.
In Chrome press F12, open the Network tab, filter by collect, click a request and copy its URL. You can also paste just values like G111 13r3r3r3r5l1.
Private by design: everything is decoded in your browser. Nothing you paste is uploaded or stored.
Consent Mode not passing?
I set up Consent Mode v2 with your cookie banner in GTM, test defaults and updates in every region, and keep conversion modelling working.
How to use the Consent Mode Decoder
Google tags add two consent codes to every request. gcs shows whether ad_storage and analytics_storage were granted for that hit. gcd is the detailed version: for each of the four Consent Mode v2 types it records the default state and any update from your cookie banner. Reading them is the fastest way to prove your banner and Consent Mode work together.
Step by step
- Open your site in a private window so no earlier consent is stored.
- Press F12, open the Network tab and filter by "collect" (GA4) or "googleadservices" (Google Ads).
- Before clicking the banner, copy a request URL and decode it: everything should be denied by default in the EEA/UK.
- Accept or reject in the banner, copy the next request and decode it again: the update should match the choice.
How to read your result
Defaults set, update received, v2 complete
All four consent types have a default and change when the visitor chooses. This is what Google expects for EEA and UK traffic.
No default consent
The banner sends an update but no default ran before the tags. Add the default command in a tag that fires on Consent Initialization.
ad_user_data / ad_personalization missing
Your setup is Consent Mode v1. Google Ads cannot build audiences or fully model conversions for EEA/UK users until both are sent.
Common mistakes
- Setting the default consent in a normal tag instead of the Consent Initialization trigger, so the first hits go out without it.
- Granting everything by default worldwide, including for EEA and UK visitors.
- A banner that saves the choice but never calls gtag('consent', 'update', …).
- Testing in a normal window where the banner choice from an earlier visit is already stored.
Questions
What do G100, G101, G110 and G111 mean?
After "G1", the first digit is ad_storage and the second is analytics_storage: 1 is granted, 0 is denied. G111 means both granted; G100 means both denied.
Does denied consent mean no data at all?
With advanced Consent Mode, tags still send cookieless pings when consent is denied, and Google uses them for behavioural and conversion modelling.
Is this tool an official Google tool?
No. It decodes the public parameters based on how Google tags behave today. Google can change the format, so confirm important findings in Tag Assistant.
Consent Mode not passing?
I set up Consent Mode v2 with your cookie banner in GTM, test defaults and updates in every region, and keep conversion modelling working.