# Consent mode not detected in Google Ads: what it means

Google Ads shows no consent mode tick, or a consent alert in Diagnostics. Every message decoded, the usual cause behind each, and what to check first.

_Shaun Brown · October 9, 2026 · https://tagsentry.ai/blog/consent-mode-not-detected-google-ads_

> **The short answer:** "Not detected" means Google Ads hasn't seen your tags set a Consent Mode default before they ran, or hasn't had time to look. Wait 48 hours after any change (Google says it can take up to two weeks). If it's still missing, open Diagnostics and match the alert to the table below: most point to one cause, and the commonest is a Google tag that runs before your consent code.

Consent Mode is Google's way of letting your cookie banner tell Google's tags what a visitor agreed to. If that's new to you, [Consent Mode v2, explained without the jargon](/blog/google-consent-mode-v2-explained) covers it in five minutes.

## Where "not detected" shows up

There are three places, and people often mean different ones.

1. **The conversion status in Google Ads.** Go to Goals, Conversions, Summary, open a website conversion action and click **Diagnostics**. A working setup shows a green tick with "Consent mode is implemented". "Not detected" here usually means the tick simply isn't there.
2. **Tag Diagnostics alerts** in the same area. These are named warnings, like "Consent mode installation out of order".
3. **Google Analytics.** Under Admin, Data collection and modification, **Consent settings**, each web stream shows whether ads measurement and ads personalization signals are arriving. Analytics reads the first from `ad_user_data` and the second from `ad_personalization`.

## Give it 48 hours first

Google says the status can take 48 hours to appear, and in some cases up to two weeks. Analytics says its consent notices can take 48 to 72 hours to update after signals start arriving.

So if you changed your banner yesterday, the missing tick probably means nothing yet. Check the page itself in [Tag Assistant](https://tagassistant.google.com/) now, and look at Ads again in a few days. If Tag Assistant shows the defaults and updates working, Google says a missing status during that window may be down to the delay.

## Every consent message, decoded

Google spreads these across several help pages. Here they are in one place, with the cause we'd check first.

| Message | Where | What Google saw | Check first |
|---|---|---|---|
| No green tick, no consent status | Ads, Diagnostics | No `ad_storage` default before the Ads tags ran, or not enough time | Tag Assistant's Consent tab on your landing page |
| "Consent mode is implemented" | Ads, Diagnostics | It works. Modelling hasn't started | Nothing. See the last section |
| "Consent mode is implemented and modeling is active" | Ads, Diagnostics | It works, and Google is modelling missed conversions | Nothing |
| "Consent mode installation out of order" | Tag Diagnostics | On some pages, consent commands ran in the wrong order | A Google tag above your consent code |
| "Verify consent mode set up as 0% consent rate detected" | Tag Diagnostics | `ad_user_data` is always denied, everywhere | The update after Accept never fires |
| "0% consent rate detected in some regions" | Tag Diagnostics | Denied `ad_user_data` outside the EEA | EU rules applied to every country |
| "Website/App missing EEA consent for ads personalization" | Tag Diagnostics | EEA data has no `ad_personalization` signal | Your banner still sends Consent Mode v1 |
| "Some pages missing consent for EEA users" | Tag Diagnostics | Some pages send EEA data with no consent label | Pages your banner doesn't load on |
| "Consent missing for EEA users" | Tag Diagnostics | EEA data has no consent label, and tags aren't held | No Consent Mode at all |
| "Update your consent settings" | Tag Diagnostics | No consent label, but tags are held site-wide | You use basic mode: attest to it in your default consent settings |
| A notice that ads measurement consent isn't detected | Analytics, Consent settings | No `ad_user_data` from EEA traffic | Signals missing from default and update |
| A notice that ads personalization consent isn't detected | Analytics, Consent settings | No `ad_personalization` from EEA traffic | Same, for the fourth signal |

The two "0%" alerts are worth reading closely. The second one means visitors in places that don't need a banner are being treated like EU visitors. Google warns that this "can lead to loss in measurement and can break remarketing outside of the EEA". It's also the usual reason [conversions drop after a banner goes up](/blog/why-analytics-dropped-after-cookie-banner).

## The checks, in order

Five causes sit behind nearly every message above. Work through them top to bottom.

**1. A Google tag runs before your consent code.** Google's rule is that the default must be set before any tag uses consent. A Google Ads tag pasted into your theme header, or added by a plugin, above your banner's script fires with no default. Tag Assistant shows "A tag read consent state before a default was set".

The fix: move the consent code to the very top of the head, above Tag Manager and any other Google tag. In Tag Manager, put consent tags on the **Consent Initialization** trigger.

**2. An old conversion tag.** The first cause Tag Assistant's help lists is a page with no Google tag or conversion linker, or one with a legacy AdWords conversion tag (AWCT). Replace old tags with the Google tag.

**3. The default is incomplete.** Google asks for defaults on at least four signals: `ad_storage`, `analytics_storage`, `ad_user_data` and `ad_personalization`. An empty Consent tab in Tag Assistant means `ad_storage` was never set. Older Consent Mode v1 setups send only the first two.

**4. The update never fires.** The default looks right, but clicking Accept changes nothing in Tag Assistant's latest Consent event. A banner tool should send the update by itself. If yours doesn't, that's a question for its support team.

**5. The Google tag is blocked.** If Tag Assistant says "Could not connect", Google says your tag or Tag Manager container may be blocked from loading. An ad blocker in your own browser can do it too, so test in a clean private window.

For the full walkthrough of each check, with the `gcs` and `gcd` codes you'll see in the network panel, use our [10-minute Consent Mode test](/blog/check-consent-mode-v2-working). If Meta or TikTok tags still fire after a Reject, that's a different setting: [Tag Manager's consent settings](/blog/gtm-consent-settings-not-configured).

## "Implemented" without modelling is fine

"Consent mode is implemented" with a green tick isn't an error. Modelling (Google's estimate of the conversions it couldn't see) needs 700 ad clicks over 7 days for a domain and country. Below that, Ads reports what it measured and stops there.

Impact results also need at least 7 full days of Consent Mode running, and they show for 4 weeks after modelling starts. After that the table goes away and the status stays.

## Where TagSentry fits

TagSentry is one line of code above Google Tag Manager. Before any tag runs, it sets every Consent Mode signal to denied, all four included. Where visitors can opt out, it switches tracking on moments after the page loads, unless they opted out.

With our banner in charge and the line first in the head, above Tag Manager and any other Google tag, checks 1 and 3 are covered.

Google's tags run cookieless by default (Google calls this advanced mode), and basic mode, which holds them entirely, is one switch. [See how the banner works](/consent), or run the [free scan](https://app.tagsentry.ai/scan) to see whether your site has a banner and whether it stops trackers.

## Sources

- [Google Ads Help: Verify consent mode implementation](https://support.google.com/google-ads/answer/14218557?hl=en)
- [Google Ads Help: Troubleshoot tag issues with Tag Diagnostics](https://support.google.com/google-ads/answer/14681508?hl=en)
- [Google Ads Help: Troubleshoot consent mode](https://support.google.com/google-ads/answer/14522438?hl=en)
- [Tag Assistant Help: Consent Mode troubleshooting for Google Ads](https://support.google.com/tagassistant/answer/12005833)
- [Analytics Help: Verify and update consent settings in Google Analytics](https://support.google.com/analytics/answer/14275483?hl=en)
- [Google for Developers: Consent mode overview (basic and advanced)](https://developers.google.com/tag-platform/security/concepts/consent-mode)