Some pages missing consent for EEA users
Google found that some pages on the site send data from EEA visitors without a consent label, while others are labeled. Google's Consent Mode troubleshooting guide describes one way consent goes missing on a page: it is set after the tags have fired. Test the suspect pages in Tag Assistant, move the consent default ahead of the tags, then confirm each page.
At a glance
- Where it shows
- The Diagnostics tab in the Google tag settings, among the consent messages.
- What stops
- Nothing stops by itself. The data from the affected pages reaches Google without a consent label.
- How serious
- Medium. Only some pages are affected, but a visitor who refused consent on one of them is still measured.
What it means
This is the EEA consent rule of the whole-site message, limited to some pages. It means the consent setup works on some pages and not on others, so a site can pass on its home page and still be flagged on a landing page.
Google's Consent Mode troubleshooting guide describes one way a page ends up without consent: the consent state is written after the Google tags have fired. When only some pages are affected, the cause sits in what those pages do differently, such as the template they use, which is why the check is page by page.
What actually triggers it
A landing page built on another template
Not on Google's help page
A landing page from a page builder or a separate template can carry its own head code and skip the site's consent setup.
Consent written after the tags fire on some pages
The consent default sits in a template that loads after the Google tags on those pages. Google's guide says consent must be set before any tag reads it.
A Tag Manager consent tag on a late trigger
In Tag Manager, a consent tag on a trigger that fires after the conversion linker leaves the state unset on the first load. Google's guide recommends the Consent Initialization trigger for consent-writing tags.
Fix it in this order
- Test the pages you suspect in Tag Assistant, and read the Consent tab on each one for the consent states.
- Find the template each failing page uses, including landing pages from a builder, and locate where its consent default is written.
- Move the consent default so it runs before any Google tag. In Tag Manager, use the Consent Initialization trigger for consent-writing tags. In gtag code, run the consent default or update before any config call.
- Publish the change, then reload each affected page in Tag Assistant and confirm the consent states appear before the first tag.
Often confused with
The whole-site version. The fix is the same check, applied to every template on the site rather than to the pages the message names.
Consent Mode is not detected on some of your pages.
That message is about detection: whether consent mode is found on a page at all. This one is about the data labels on pages where the setup is found.