Basic vs Advanced Consent Mode: what modelling recovers

Short answer: run Advanced if you advertise, because it earns you an advertiser-specific model instead of a generic one. But know what you're buying: Google's behavioural modelling only switches on once a property clears hard volume thresholds, and most small and mid-sized sites never clear them. Advanced on a low-traffic site gives you the cookieless pings and none of the modelling. It's still the right choice — just not for the reason it's usually sold.

The actual difference

Both versions set a consent default before any tag fires. What differs is whether Google's tags load at all while consent is denied.

Basic blocks the tags outright. Nothing loads until the visitor interacts with the banner. In Google's words, this "transmits no data to Google prior to user interaction with the consent banner", and if the visitor declines, "no data is transferred to Google at all – not even the consent status."

Advanced loads the tags on page open. While consent is denied they send cookieless pings — no identifiers, no cookies, just the signal that an event happened and that consent was refused.

That difference in what Google receives is the difference in what Google can model. Basic gets you conversion modelling "based on a general model." Advanced gets you "an advertiser-specific model."

The thresholds nobody mentions

Here's the part that changes the decision, and it comes straight from Google's own documentation. Behavioural modelling in GA4 activates only when a property meets all of the following:

• Advanced implementation — "Google tags load in all cases, not only if the user consents."
• "At least 1,000 events per day with analytics_storage='denied' for at least 7 days."
• "At least 1,000 daily users sending events with analytics_storage='granted' for at least 7 of the previous 28 days."

Read the second one again. You need a thousand events a day from people who refused, sustained for a week. A site with 2,000 sessions a month does not produce that. Neither does most UK professional services, most single-location retail, and a large share of the SMB market generally.

And clearing the bar isn't a guarantee. Google states that modelling "follows a set of eligibility criteria and data thresholds" beyond the published numbers, weighing things like the ratio of new to returning users.

So why run Advanced anyway

Three reasons that survive the above.

You might qualify later. Modelling activates automatically once a property qualifies, and the thresholds are rolling. Basic guarantees you never will.

The ad platforms use the signals directly. Consent Mode isn't only about GA4 modelling. ad_user_data and ad_personalization govern what Google Ads may do with the data you are allowed to collect. Getting them wired correctly affects remarketing eligibility and Smart Bidding regardless of whether behavioural modelling ever switches on.

Basic is harder to get right than it looks. Blocking tags until interaction means something must un-block them reliably on consent, across page navigations and single-page routes. In practice we see more sites broken by half-finished Basic setups than by Advanced ones.

The questions people actually ask

Is Advanced mandatory? No. Neither version is mandatory. What is required, for EEA and UK traffic, is that you obtain consent before using personal data for ads personalisation and that you pass ad_user_data and ad_personalization to Google. You can satisfy that with Basic.

Does it apply outside the EEA and UK? The consent requirements target EEA, UK and Swiss traffic. Nothing stops you running Consent Mode globally, and if you serve mixed traffic it's usually simpler than maintaining two behaviours.

Does it cover Meta and TikTok? No. Consent Mode is a Google mechanism governing Google tags. Meta, TikTok and everyone else need their own consent handling. This is the single most common misunderstanding we correct: the banner said no, the Google tags obeyed, and the Meta pixel fired anyway.

Do I still need a CMP alongside GA4? Yes, if you serve EEA or UK visitors. GA4 consumes a consent state; it doesn't collect consent or store the record.

All Pages or the consent-update trigger? Under Advanced, tags should fire on All Pages — that's the entire point, since built-in consent checks handle the denied case with cookieless pings. Under Basic, they wait for the update. Setting Advanced and then gating tags on a consent-update trigger is a common half-migration that produces the worst of both: no pings while denied, and no data after.

What to do

Set Advanced. Wire the default before the container. Include ad_user_data and ad_personalization. Fire tags on All Pages and let the built-in consent checks do their job. Then verify on the live site rather than in the CMP's admin panel — because as our piece on CMP certification covers, nothing about buying a good product tests your installation of it.

And set expectations honestly with whoever reads the reports: if you're under the thresholds, modelling isn't coming, and the numbers will be lower than last year because last year's were counting things they shouldn't have. That's the work we do — and the conversation is a lot easier before the drop than after it.

Sources

1. 1.Google — Consent mode overview (basic vs advanced implementation) · Checked 2026-07-26
2. 2.Analytics Help — [GA4] Behavioural modelling for consent mode, including the eligibility thresholds · Checked 2026-07-26
3. 3.Google Ads Help — About consent mode · Checked 2026-07-26
4. 4.Tag Manager Help — Updates to consent mode for traffic in the European Economic Area · Checked 2026-07-26
5. 5.Google — Set up consent mode on websites (default and update commands) · Checked 2026-07-26
6. 6.Perfmetrix — UK private clinic consent benchmark (our own scan data) · 2026-07-08