0% consent rate detected in some regions
Google sees a consent rate of 0% in some regions, which means denied ad user data signals are sent outside the EEA. That suggests an EEA-only consent setup was applied to every visitor. Limit the denied default to EEA regions, leave other regions on their normal setup, then confirm the signal from a visitor outside the EEA.
At a glance
- Where it shows
- The Diagnostics tab in the Google tag settings, among the consent messages.
- What stops
- Measurement and remarketing for visitors outside the EEA, since their data is sent as denied.
- How serious
- Medium. Google says this can cause measurement loss and break remarketing in the regions named.
What it means
Consent mode can tell Google that a visitor denied ad user data. Google's message says the site always sends that denied signal in regions outside the EEA, where consent is not required, so the consent rate there reads zero. Google warns this can cause measurement loss and break remarketing outside the EEA.
Google's page gives a general version of this message, which says the denied signal is sent regardless of geography. This one names the regions, and the region is the clue: the setup is right for one region and wrong for the rest.
What actually triggers it
A denied default written without a region list
Not on Google's help page
The denied default is written without a list of regions, so it applies everywhere, including the regions the message names.
An EEA example copied into a site that serves everyone
Not on Google's help page
A consent snippet copied from an EEA-only example is placed on a site or theme that serves every visitor. Nothing errors on the page.
A denied default in regions where no banner shows
The consent tool shows its banner only in some regions but writes a denied default everywhere, so visitors elsewhere never get a choice and stay denied. Google's Consent Mode troubleshooting guide names this case and says to target the banner and the default at the same regions.
Fix it in this order
- Open the Diagnostics tab in the Google tag settings and note the regions the message names.
- Find the consent default on the site: the code or the consent tool that writes the denied state.
- Limit the denied default to the regions where the banner shows, so the banner and the default target the same regions and other visitors do not receive a denied ad user data state.
- Publish the change, then test from a visitor outside the EEA, such as a page loaded through a VPN, and confirm the state is not denied.
Often confused with
EEA data with no consent label. Here the labels are present, but denied labels are sent where they should not be.
Website/App missing EEA consent for ads personalization
A missing personalization label, not a denied signal. The region in this message is what separates the two.