Your cookie banner may be breaking your advertising: what Consent Mode is and why an EU business needs it
That little "Accept cookies" window decides how much data reaches Google and Meta - and therefore how smart your advertising is and how accurate your reporting is. Set up wrong, tracking quietly breaks: numbers understated, optimization blind, and you don't even know why.
The little "Accept cookies" window that pops up on a website seems like a formality. But in reality it's exactly what decides how much data reaches Google and Meta - and therefore how smartly your advertising works and how accurate your reporting is. If this is set up incorrectly, tracking "quietly breaks": the numbers in your account are understated, optimization goes blind, and you don't even understand why. Let's break down what Consent Mode is, who needs it, how it's set up, how its versions differ, and what to watch out for.
First, the context: what the EU requires
In Europe there's a rule: before placing "non-essential" cookies on a user (and that's precisely analytics and advertising pixels), you have to obtain their consent. This follows from the pairing of two laws - the ePrivacy Directive and the GDPR. Consent must be freely given and informed: no pre-ticked boxes, with a "Reject" button as prominent as "Accept," and without "walls" that block the site.
And this isn't just theory. Regulators are fining violations ever more harshly: for example, the French regulator CNIL in September 2025 fined Google €325 million and Shein €150 million specifically for cookie violations. So the topic is at once about your advertising budget and about compliance with the law.
A conflict arises: the law requires asking for consent (and some people don't give it), while ad systems need data. Consent Mode is the bridge between these two worlds.
What Consent Mode is
Consent Mode is a Google mechanism that passes information about what exactly a user consented to into its services (Google Ads, GA4). Simply put, your cookie banner "tells" Google: this person allowed advertising cookies, and this one didn't. And the tags behave accordingly.
In the current version (Consent Mode v2), four consent signals are passed: for storing advertising data, for analytics, for transferring user data to Google, and for ad personalization. The last two were added precisely in version v2 - and without them Google no longer allows using Europeans' data for remarketing and personalized advertising.
Who it's mandatory for
If you have traffic from the EU or the UK and you use Google Ads or Google Analytics - this is about you. Since March 2024, Consent Mode v2 has effectively been mandatory: without it, Google simply won't collect data about new users from Europe for advertising. In practice, this means remarketing lists stop growing, audiences "shrink," and conversions in reports are understated. The size of the business doesn't matter - there are no exemptions for small businesses.
Separately about Meta: it doesn't have "Consent Mode" as a separate technology, but the principle is the same - the Meta pixel and Conversions API in the EU must only fire after consent. So a correct banner and passing consent are equally important for both Google and Meta: without consent the pixel won't fire, and you'll lose the data.
The difference: basic and advanced mode
Here's the key nuance that many people miss. Consent Mode has two setup options, and the difference between them is fundamental.
Basic mode. The tags don't load at all until the person has given consent. If they agree - data is collected in full; if they refuse - Google gets nothing. Simple, maximally "clean" from a privacy standpoint, but everyone who refused is completely "invisible" to you.
Advanced mode. The tags always load, but if the person refused, instead of the usual data Google receives anonymous, cookieless "pings" - without personal data. Based on these anonymized signals, conversion modeling kicks in: Google uses machine learning to fill in the picture and estimate the conversions you otherwise wouldn't have seen. In essence, part of the data "lost" to refusals comes back in the form of a statistical model.
What conversion modeling is, in plain words: the system looks at the behavior of those who consented and, based on those patterns, estimates how many conversions were brought by those who refused cookies. It's not an exact count per person, but a well-founded estimate - and it's noticeably more accurate than simply "zero."
The practical takeaway: advanced mode usually provides more data and feeds the algorithm better. But it has a legal nuance - the anonymous pings are sent even without explicit consent, so with this setup it's worth checking with a lawyer and your privacy requirements.
How it's set up
The good news: you don't have to program anything, it's all done through a combination of tools.
- A consent management platform (CMP) - that very banner that asks for permission and remembers the choice. Popular ones are Cookiebot, OneTrust, CookieYes, iubenda. It's important that the banner blocks advertising and analytics scripts before consent, not after.
- Google Tag Manager - in it you configure the tags to "listen" to the user's decision from the CMP and fire only for the permitted categories. Many CMPs integrate with GTM in just a couple of clicks.
- Tags that respect consent - make sure GA4, Google Ads, and the Meta pixel don't collect data if the person refused. And don't forget about offline conversions: if you upload them via API, consent signals need to be passed there too.
Other important nuances
- Banner design isn't a trifle. It's precisely for "dark patterns" (a bright "Accept" button while "Reject" is hidden) that fines are issued. "Reject" must be as easy as "Accept."
- Don't block what's necessary. Technically required cookies (cart, login) don't require consent - there's no need to disable them.
- Modeling needs volume. For conversion estimates to be adequate, you need enough traffic and conversions; on very small volumes the effect is more modest.
- Check that it actually works. A common mistake is a banner that's there "for show," while in reality the tags fire before consent (both a fine and skewed data) or, conversely, cut data from those who consented. The setup needs to be tested.
The key points in brief
In the EU, you can't place advertising and analytics cookies without the user's consent - and some people don't give it. Google's Consent Mode is a mechanism that passes the user's choice into ad systems, so that you both comply with the law and don't lose data needlessly. Since March 2024 it's effectively mandatory for everyone with European traffic and Google Ads/Analytics; for Meta, the same consent principle applies. The key choice is between basic mode (no data on refusal) and advanced mode (anonymous signals plus conversion modeling, but with an eye on lawyers). It's set up via a CMP banner and Google Tag Manager. Do it right and your advertising sees more data, optimizes better, and the business is at ease about compliance.
Privacy and advertising in the EU are increasingly intertwined, and one wrong setting can quietly cut both your data and your results. To keep this under control and avoid losing money on "broken" tracking - subscribe to my newsletter. I explain important mechanics and rules from Meta, Google, and regulators in plain language and always with a concrete takeaway: what exactly you should do about it.
Subscribe to the newsletter