What is Consent Mode, in plain terms?
When a visitor answers your cookie banner, something has to tell Google's scripts what the answer was. Consent Mode is that messenger. It passes a set of yes/no signals from your consent banner to gtag.js, GA4, and Google Ads tags, and those tags then adjust their behaviour -- full cookies when consent was granted, restricted behaviour when it was denied.
Version 2, which Google made mandatory in March 2024 for anyone using its advertising features in the European Economic Area, added two new signals on top of the original storage ones:
- ad_user_data -- may data about this user be sent to Google for advertising purposes?
- ad_personalization -- may that data be used for remarketing and personalised ads?
The pressure behind it is regulatory: the Digital Markets Act requires Google, as a designated gatekeeper, to have provable consent for combining user data across services. Without these signals arriving, Google Ads simply degrades -- no remarketing audiences from EEA traffic, reduced conversion measurement.
What is the difference between basic and advanced mode?
This is the part most explanations skip, and it is the part worth understanding.
Basic mode does what you would expect: Google tags do not load at all until the visitor consents. Declined consent means nothing is sent to Google. Clean, but Google gets no data about decliners, so your reports show the familiar consent-shaped hole.
Advanced mode is the interesting one. Google's tags load before consent and, when the visitor declines, they still send "cookieless pings" -- signals stripped of cookies but carrying information like page URL, rough timestamp, and browser context. Google then uses these pings to feed behavioural modelling: machine-learning estimates of the sessions and conversions the declining visitors probably generated. Those modelled numbers are blended into your GA4 reports, often without any visible marker.
Is Consent Mode data accurate?
Modelled data is an educated guess. Google trains on the behaviour of consenting visitors and extrapolates to the non-consenting -- but as we covered in why your GA numbers are wrong, people who decline tracking do not behave like people who accept it. The model fills the gap with a statistical portrait of the wrong population. You get numbers that look complete, with no way to tell which portion was measured and which was inferred.
There is also a legal wrinkle worth knowing: whether "cookieless pings" sent after an explicit refusal are truly consent-free is a live debate among European privacy lawyers and regulators. Advanced mode sits in a grey zone -- you declined tracking, and something was transmitted anyway.
Do you actually need Consent Mode v2?
Work through this honestly:
You run Google Ads and want conversion measurement and remarketing from EEA traffic. Then yes -- Consent Mode v2 is effectively compulsory, and you will need a certified consent management platform (CMP) wired to it. That is the deal Google offers: its ad ecosystem in exchange for the integration work.
You use GA4 but no Google advertising features. Consent Mode v2 is not required. You still need the consent banner itself for GA4's cookies -- Consent Mode never replaces the banner, it only communicates with it.
You mainly want to understand your traffic. Then notice what this whole apparatus is for: a mechanism to partially reconstruct, by machine learning, data you were not permitted to collect. The alternative is to not collect personal data in the first place -- at which point the banner, the CMP, the consent signals, and the modelling all become unnecessary.
The cookieless route: no consent machinery at all
A privacy-first analytics tool sets no cookies and processes no personal data, so the ePrivacy consent requirement never triggers. Nothing needs to be gated, signalled, or modelled -- every visitor is simply counted, with real measurements rather than estimates. That is the approach TrackTrendy takes: a 1.4KB script, anonymous aggregated statistics, full reports on visitors, sources, campaigns, goals and revenue, from €4/month. No CMP subscription, no consent-rate anxiety, no modelled gap-filling.
A perfectly reasonable setup for many businesses is both: TrackTrendy as the always-on, complete source of truth for traffic and conversions, and Google's consent stack kept only if and where you actively run Google Ads.