The short answer
Google Consent Mode is a set of signals that tell Google's tags what a visitor agreed to, so the tags change what they store and send. In Advanced mode the tags load straight away, without cookies; in Basic mode they wait for a yes. In our test with Google's own tag, Advanced sent 3 cookieless requests before anyone clicked, and Basic sent none.
What it is
Consent Mode is how a website tells its Google tags (Analytics, Ads, Floodlight) what a visitor has agreed to. Your cookie banner collects the answer. Consent Mode passes it to Google's tags as named signals, each granted or denied, and the tags read them.
It doesn't show a banner or keep a record of consent, and it won't make a site follow any law. It only covers Google's tags, too. A Meta Pixel or Hotjar script ignores it, so those need holding some other way.
The signals
Version 2 added two signals, ad_user_data and ad_personalization. Google requires them for measuring and advertising to people in the European Economic Area.
| Signal | What it controls |
|---|---|
ad_storage | Whether ad cookies can be read or written |
analytics_storage | Whether analytics cookies can be read or written |
ad_user_data | Whether data about the user can be sent to Google for advertising (new in v2) |
ad_personalization | Whether that data can be used for personalised ads and remarketing (new in v2) |
functionality_storage | Cookies the site needs for features like language |
personalization_storage | Cookies for personal touches, like recommendations |
security_storage | Cookies for security, like fraud prevention |
The first four decide what Google Analytics and Google Ads do. They're also the four that travel with every request, in the gcs and gcd values you can read in the network panel.
Defaults and updates
Each page load has two moments.
- The default. Before any Google tag runs, the page says what the signals are for someone who hasn't answered yet. In the EU, UK and similar places, that should be
denied. In most US states the law lets people opt out instead, so it usually ends upgranted. - The update. When the visitor answers the banner, the page sends the new state, and Google's tags follow it from then on.
Order is where setups often go wrong. If the default arrives after a Google tag has run, that tag fired with no instructions. In our Google Ads conversion test, a default that landed after the tag let the conversion go out with no consent state at all and a _gcl_au cookie written first.
Site builders make this easy to get wrong: Webflow writes its own Google tag above your head code, and in Next.js the way you load the default decides whether it runs first.
Basic and Advanced
Google offers two ways to run Consent Mode.
Advanced mode lets Google's tags load as soon as the page does, with the signals denied. Until the visitor agrees, they send what Google calls cookieless pings: a request saying a page was viewed or a conversion happened, with the consent state attached and no cookies. Google uses these to estimate the conversions it can't see.
Basic mode keeps Google's tags off the page until the visitor agrees. Before that, nothing from Google loads. If someone never answers, or says no, Google hears nothing about that visit.
Google Analytics' modelling needs Advanced: its rules ask for Google's tags to load whether or not the visitor consents.
What each mode sent in our test
On 22 October 2026 we built a test page that loads Google's live tag with a Google Analytics 4 ID and a Google Ads ID, both made up. Every signal starts denied. The "visitor" answers after 3 seconds, then the page sends a generate_lead event.
We recorded every request to Google and blocked it, so nothing reached Google. We ran it twice. The second run waited 12 seconds so one late request could arrive, and the table shows that run.
| Setup | Sent before the answer | Sent after the answer | Cookies set |
|---|---|---|---|
| Advanced, no answer | 3 cookieless page views (gcs=G100) | nothing | none |
| Advanced, Accept all | the same 3 | 12, including the lead and the Ads conversion (G111), and remarketing | _ga, _gcl_au |
| Advanced, Reject all | the same 3 | 3: the lead, sent cookieless to Analytics and Ads (G100) | none |
| Basic, no answer | nothing (Google's tag never loaded) | nothing | none |
| Basic, Accept all | nothing | 12: a page view, then the same lead, conversion and remarketing requests as Advanced | _ga, _gcl_au |
| Basic, Reject all | nothing | nothing | none |
No cookie was set in either mode until the visitor pressed Accept.
The difference is what happens to a refused visit. With Advanced, the lead still went to Google after Reject, by the cookieless route and with no remarketing, and that's what Google models from. With Basic, Google got nothing after Reject or no answer. After Accept, both modes sent the same conversion and remarketing requests and set the same cookies.
The gcd value records the history of each signal. It read 13p3p3p3p5l1 before the answer (denied by default), 13r3r3r3r5l1 after Accept (denied, then granted) and 13q3q3q3q5l1 after Reject (denied, then denied again). Our Consent Mode checklist decodes every letter.
| Basic | Advanced | |
|---|---|---|
| Google's tags before a choice | Don't load | Load, no cookies |
| Requests before a choice | None | Cookieless pings |
| Conversion modelling in Ads | General model | Advertiser-specific model, with enough traffic |
The right mode depends on how much risk you'll accept and where your visitors are. Advanced gets you Google's more detailed, advertiser-specific modelling.
What changed in June 2026
On 15 June 2026, Google changed how Analytics data reaches Google Ads. Since then, ad_storage alone decides whether ad data collected by Google Analytics is shared with Ads. Before that, the Google Signals setting also had a say.
So a wrong ad_storage value now shows up directly as missing conversions in Google Ads. If your Ads numbers moved in late June, check that signal first, then ad_user_data.
What changed in October 2026
On 8 October 2026, Google changed how Tag Manager containers start. Every container now starts as soon as it loads, and each gtag('config') command appears in the dataLayer as a gtag.config event. We saw it in our test: the Ads remarketing requests after Accept carried the event name gtag.config.
Google warns that tags on a wildcard custom event trigger may now fire on these events. These events fire as the page loads, usually before the visitor has answered, so check that every tag on such a trigger has consent settings.
What usually goes wrong
- The default is set too late. Google's tags run before the default arrives. Check the order in Tag Manager's preview, on the very first event on the page.
- The strictest rules are applied to everyone. A banner that denies everything for US visitors throws away data those visitors never asked you to drop. This is a common reason analytics falls after a banner goes up.
- Tags have no consent settings. In Tag Manager, a tag whose consent settings are "Not set" waits for nothing beyond Google's built-in checks. Non-Google tags in that state fire regardless.
- The update never fires. The banner records the answer, but nothing tells Google's tags, so they stay on the default for good.
- The two new signals are missing. An older setup may only send
ad_storageandanalytics_storage. Withoutad_user_data, an Accept still sends Ads conversions by the cookieless route.
How to check yours in five minutes
- Open your site in a private window, from the region you care about.
- Open Tag Manager's preview mode, or your browser's network panel filtered to
google. - Find the first Google request and its
gcsvalue.G100means both storage signals were denied.G111means both were granted. - Answer the banner, reload, and check that the value changed.
- Repeat from a US connection. If you see
G100there too, you're applying EU rules to American visitors.
For a fuller test, work through our Consent Mode v2 checklist. If Google Ads says consent mode isn't detected, here's what each status and alert means.
Where TagSentry fits
TagSentry sets Consent Mode defaults from one line of code above Google Tag Manager. Before any tag runs, it sets every signal to denied. Where visitors can opt out, it switches tracking on moments after the page loads, unless they opted out. If their browser sends Global Privacy Control, advertising stays off and analytics still runs.
Google's tags run cookieless until a visitor agrees (Advanced is the default), so Google can still model conversions. The same line watches which events are sent to Google and emails you once when one that matters stops, and once when it's back.
Sources
- Google for Developers: Consent mode overview (Basic and Advanced)
- Google Tag Manager Help: Consent mode overview (ad_user_data and ad_personalization)
- Simo Ahava: Consent Mode V2 for Google tags (gcd decoding)
- Google Analytics Help: Behavioral modeling for consent mode
- Google Ads Help: About consent mode conversion modeling
- OneTrust: What Google's June 2026 Consent Mode changes mean for Google Ads
- Usercentrics: Google Signals and Consent Mode changes in 2026
- Google Tag Manager Help: Release notes (8 October 2026, gtag('config') behaviour)
- iubenda: Google Tag Manager and GDPR after the German court decision