Consent Mode is not detected on some of your pages.
Google Ads cannot detect Consent Mode on some pages of the site. Three causes are named: a page with no Google tag or conversion linker, a page that never sets an ad_storage consent state, and a page where consent is set after the tags have fired. Open Tag Assistant on each page and read the Consent tab, which shows which cause applies.
At a glance
- Where it shows
- The Google Ads message for the affected site. The Consent tab in Tag Assistant shows the cause on each page.
- What stops
- Consent signals on the named pages, so conversions from those pages are reported without one.
- How serious
- Medium. The conversions from those pages are reported without the consent signal Google Ads looks for.
What it means
Consent Mode lets a site tell Google what a visitor agreed to, through consent states such as ad_storage, so Google's tags can adjust what they send. This message says Google Ads cannot find that setup on some pages. It is a check on pages, not on the whole site.
The message does not say which of the three causes applies. Google's guide lists all three, and the Consent tab in Tag Assistant is where a page shows which one it has, so read it before changing anything.
What actually triggers it
No Google tag or conversion linker on the page
The page has no Google tag or conversion linker, or it still carries a legacy AdWords Conversion Tracking tag. Google's guide says to check Tag Assistant for legacy tags.
No ad_storage state set on the page
The page never sets a consent state for ad_storage. In Tag Assistant the Consent tab is blank, or it lists other states but none for ad_storage.
Consent set after the Ads tags fire
Consent is set after the Ads tags have fired. The Consent tab shows the error A tag read consent state before a default was set.
Fix it in this order
- Open Tag Assistant on the affected page and read the Consent tab. Note which of the three causes it shows.
- If the page has no Google tag or conversion linker, add them. If it has a legacy AdWords Conversion Tracking tag, replace it.
- If no ad_storage state is set, deploy Consent Mode on the page, following the developer documentation's implementation example.
- If consent is set too late, make sure consent-writing tags fire before the conversion linker. In Tag Manager, use the Consent Initialization trigger for them, then confirm the states appear in the Container Loaded event. In gtag code, run the consent default or update before any config call.
- Reload the page in Tag Assistant to confirm the Consent tab shows the states, then check the message again.
Often confused with
Some pages missing consent for EEA users
Also about pages and consent, but about the data labels for EEA visitors on those pages. This message is about whether consent mode is found at all.
The Diagnostics message for EEA data labels across the site. Consent Mode not detected means the setup is missing from some pages.