Website/App missing EEA consent for ads personalization
Google found EEA data with no ads personalization consent label. The message names two causes: consent mode v1 with auto-delegation, and consent mode v2 set up without a personalization choice. Google's fix is to upgrade to consent mode v2 with the personalization choice set. Then confirm the consent states in Tag Assistant on an EEA page.
At a glance
- Where it shows
- The Diagnostics tab in the Google tag settings, among the consent messages.
- What stops
- Nothing on the site stops. EEA data reaches Google without the label that says whether the visitor allowed ads personalization.
- How serious
- Medium. The message stays open until the setup is upgraded, and the personalization data for EEA visitors stays unlabeled.
What it means
Google's consent rules for EEA visitors cover two separate choices: consent to store data for ads, and consent to use it for personalized ads. Consent mode v2 carries the second choice as its own signal. The message says that signal is missing from EEA data.
The message names two causes. One is consent mode v1 with auto-delegation. The other is consent mode v2 without a personalization choice. Both are fixed by the same step, the upgrade to v2 with the personalization choice set.
What actually triggers it
A v1 setup still running on the site
The site still runs the older consent mode from a plugin, a template or an old tag. The v1 setup cannot carry the personalization label.
A v2 setup that sets only the storage choice
The consent setup is on v2 but writes the ad storage choice and leaves out the personalization choice, so EEA data carries no personalization label. Google's message names this case.
Fix it in this order
- Open the Diagnostics tab in the Google tag settings and read the consent message.
- Find the consent setup on the site: the consent mode code, or the consent tool that writes the default states.
- Upgrade to consent mode v2, following Google's developer documentation, and set the personalization choice alongside the others.
- Publish the change, then open Tag Assistant on an EEA page and read the Consent tab for the personalization state.
Often confused with
EEA data with no consent label at all. This one is narrower: the other consent choices are present, and only the personalization label is absent.
0% consent rate detected in some regions
A denied signal sent outside the EEA. That one is a region problem, not a missing personalization label.