See what your Google tags report before a choice, after “Reject” and after “Accept”, and whether ad_user_data is sent.
Google tags report consent in the gcs parameter of each request. Before a choice and after “Reject” you want G100, both storage signals denied. After “Accept” you want G111. We read those signals for you in all three moments, each as a new visitor, and flag tags that send data before they’re allowed to.
We record every Google request before anyone touches the banner.
gcs, gcd and the v2 fields ad_user_data and ad_personalization.
The signals should stay denied and nothing should be stored.
Now they should switch to granted, and tags should fire.
A table of what each Google tag reported in each moment, and what to change if it’s wrong.
| Moment | Google tag | gcs |
|---|---|---|
| Before | Google Analytics 4 | G101 |
| Before | Google Ads | G100 |
| Reject | Google Analytics 4 | G100 |
| Reject | Google Ads | G100 |
| Accept | Google Ads | G111 |
Prefer to look by hand? Four steps in any browser.
If you use Analytics data in Google Ads and have visitors from the EEA, yes. Without the v2 signals, those visitors drop out of audiences and conversions. UK law still needs consent before non-essential cookies either way.
No. It passes your visitor’s choice to Google tags. Your banner and the rest of your tags still need to respect that choice.
Basic waits to load Google tags until consent. Advanced loads them right away with consent “denied” and sends cookieless pings before a choice.
Yes. The check runs as part of the free homepage scan, with no signup.
