Consent missing for EEA users
Google found data from EEA visitors that is not labeled with a consent state, so it cannot confirm that the tags are blocked for visitors who refused. Check that the consent banner passes the visitor's choice to the Google tags. Then confirm the data is labeled with consent in Tag Assistant's Consent tab. The message stays open until the labels appear.
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. Google cannot confirm the tags are blocked for EEA visitors who have not consented, so the message stays open.
- How serious
- Medium. This is a consent and data-quality gap, not an ad stop. Data from a visitor who refused must not reach Google as if it were consented.
What it means
The European Economic Area has consent rules for data about visitors. Google's diagnostic reads the consent labels that travel with each tag request. When EEA data arrives with no label, Google cannot confirm that the tags were blocked for visitors who did not agree, so it flags the setup.
The message is about the consent setup, not one missing tag. The fix is a consent setup on the site that labels the data, checked in Tag Assistant, not a change inside the ad account.
What actually triggers it
A consent banner that is not wired to the tags
Not on Google's help page
The banner shows a choice to the visitor but does not pass that choice to the Google tags, so each request leaves unlabeled.
Tags that fire before the consent default is written
The Google tag fires before the default consent state is written, so the first requests carry no label. Google's Consent Mode troubleshooting page names this order problem as a cause.
Fix it in this order
- Open the Diagnostics tab in the Google tag settings and read the consent message and its link.
- Check the consent setup on the site. The banner or the consent tool should write the visitor's choice to the consent state before the Google tags load.
- Open Tag Assistant on an EEA page and read the Consent tab. Confirm the consent states appear before the first tag.
- Publish any change, then check the Diagnostics tab again after new EEA visits have arrived.
Often confused with
Some pages missing consent for EEA users
The same consent rule, on fewer pages. Only some pages send the data unlabeled, so check those pages before the consent setup as a whole.
Website/App missing EEA consent for ads personalization
A narrower gap. The consent is there, but the personalization label is absent. The fix is an upgrade to consent mode v2, not a new banner.