Consent Mode v2 in 2026: What It Is, How It Works, and What Changes on June 15
8 min read · AstraLoop Studio
If you run Google Ads campaigns or check your GA4 reports, June 15, 2026 is a date that concerns you. That's when Google quietly but fundamentally changed how Analytics and Google Ads exchange data: the old Google Signals switch no longer controls the flow of data to advertising. Now a single mechanism decides what gets through and what doesn't — Consent Mode v2.
For a small or midsize business, the consequence is concrete. If your cookie banner isn't sending consent signals correctly, conversions, remarketing audiences, and the signals that feed Smart Bidding can quietly switch off without anyone noticing — and this time, there's no safety net. In this guide, we'll cover what Consent Mode v2 actually is, how it really works, what changed on June 15, and how to stay compliant with GDPR and the DMA without throwing away half your data.
What Is Consent Mode v2, in Plain English
Consent Mode v2 isn't another tracking tool. It's a technical bridge between your cookie banner (the CMP, or Consent Management Platform) and Google's tags (GA4, Google Ads, Floodlight). Every time a user accepts or rejects cookies, the CMP translates that choice into signals the tags read to understand what they can and can't do.
Here's a practical example. A user rejects cookies on your e-commerce site: the CMP sends Google's tags a "denied" signal, and from there Google decides whether to collect anything in anonymized form, or nothing at all. That's the entire role of Consent Mode — but it's a role that decides how much data you see at the end of the month.
Version 2 arrived to comply with the Digital Markets Act (DMA, EU Regulation 2022/1925), the European law that treats Google as a "gatekeeper" and requires it to obtain explicit consent before using data for advertising. Since March 2024, Consent Mode v2 has effectively been mandatory for anyone running campaigns targeting users in the European Economic Area and the UK: without it, remarketing and audiences empty out. The GDPR (EU Regulation 2016/679) still governs how you collect and justify that consent, with the Italian Data Protection Authority's cookie guidelines serving as the operational reference in Italy.
Compared to the previous version, v2 added two consent parameters to the two that already existed. That's four signals, each with a precise job:
| Parameter | What It Authorizes |
|---|---|
| analytics_storage | Storage of analytics data: GA4 cookies, sessions, on-site behavior. |
| ad_storage | Storage of advertising data: cookies and identifiers used by Google Ads. |
| ad_user_data (new in v2) | Sending user data to Google for advertising purposes. |
| ad_personalization (new in v2) | Using data for personalized advertising and remarketing. |
Basic or Advanced Mode: The Choice That Decides How Much Data You Lose
Consent Mode v2 can be implemented in two ways, and the difference isn't so much technical as practical: it changes how much data you can recover from users who don't give consent.
Basic Mode
In basic mode, Google's tags don't fire until the user accepts. Anyone who rejects cookies becomes invisible: no data collected, no signal sent, not even anonymized. It's the most privacy-conscious setup, but also the one that costs you the most, because on average a significant share of visitors reject or ignore the banner.
Advanced Mode
In advanced mode, the tags load immediately, but in a denied-consent state. For users who haven't accepted, Google sends anonymous, cookieless pings — meaning without personal identifiers — that feed conversion modeling: a machine learning model estimates the missing conversions from non-consenting users based on the behavior of those who accepted. In practice, you recover part of the data that basic mode loses entirely.
There's a legal question you shouldn't ignore, though: sending pings, even anonymous ones, from users who haven't consented can count as data processing. Before choosing advanced mode, it's worth running the details past your DPO or a privacy consultant to evaluate it under the GDPR and the ePrivacy Directive for your specific case. This guide is informational and doesn't replace a legal assessment.
What Actually Changed on June 15, 2026
Until that day, two levers controlled the flow of data from GA4 to Google Ads: the Google Signals toggle in Analytics settings, and the Consent Mode's ad_storage parameter. As of June 15, 2026, there's only one lever left.
Here's a before-and-after summary:
| Aspect | Before June 15, 2026 | After June 15, 2026 |
|---|---|---|
| Who controls data flowing to Google Ads | Google Signals plus ad_storage | Only the Consent Mode parameters (ad_storage, ad_user_data, ad_personalization, analytics_storage) |
| Role of Google Signals | Also governs the advertising flow | Limited to GA4's behavioral reports on logged-in users |
| If you disable Google Signals | Blocks data from reaching Ads | No longer blocks anything: if ad_storage is granted, data flows anyway |
| Ad personalization | Multiple settings inside GA4 | Single ad_personalization parameter managed by Google Ads |
In plain terms: Google Signals is no longer your safety net. Before, even with a poorly configured Consent Mode, the Signals toggle could still hold up part of your tracking. Not anymore. If your banner doesn't correctly trigger ad_storage and the other parameters, the data simply never reaches Google Ads — and with it go your measured conversions, remarketing lists, and the signals that feed Smart Bidding.
Two more technical details are worth flagging. Ad personalization now moves to the single ad_personalization parameter, managed on the Google Ads side, and IP addresses collected by the Google tag are encrypted and routed to the linked Ads account. Advertising consent, moreover, now bundles in cross-device linking as well: accepting enables the entire package of advertising features, with no separate control over multi-device tracking.
Not sure if your Consent Mode is sending the right signals after June 15? Request a tracking check: we'll show you where you're losing data and how to close the gaps.
How to Stay Compliant Without Losing Data: The Checklist
The good news is the fix doesn't require overhauling your site. It does require verifying that the chain between consent and tags actually works — something many small and midsize businesses have never seriously tested. Here are the steps that matter.
- Use a Google-compatible CMP. Your banner needs to be a Consent Management Platform capable of transmitting all four Consent Mode signals. CMPs working with the TCF had until February 28, 2026 to migrate to TCF v2.3 — check that you're on the right version.
- Verify the parameters actually fire. Using Google Tag Manager's preview mode or a debugging extension, confirm that on consent, ad_storage, ad_user_data, and ad_personalization flip from "denied" to "granted." This is where most of the gaps hide.
- Consider advanced mode. If your DPO deems it compatible with your context, advanced mode recovers part of the conversions from non-consenting users through modeling. For many SMBs, it's the difference between usable data and half-empty data.
- Strengthen tracking upstream. Server-side tracking and enhanced conversions make measurement more resilient to cookie and consent loss, because they don't depend solely on the browser.
- Shift your center of gravity to your own data. The less you rely on third-party cookies, the less these changes hurt you. Building a foundation of first-party data and connecting offline conversions from your CRM gives you tracking that withstands Google's pivots.
- Test — don't assume. If you've never verified that GA4 is configured in line with consent, now's the time. A half-hour test today is worth more than three months of skewed data.
Three Mistakes We See Most Often
When we dig into a client's tracking setup, the same problems keep showing up. It's worth knowing them in advance.
- The "fake compliant" banner. It shows the user a choice but never actually connects consent to the tags. Visually everything looks fine, but the parameters stay locked and the data never flows.
- Consent collected but never transmitted. The user accepts, but the CMP doesn't update the status of Google's parameters. This is the trickiest case, because everything seems to work until you check the signals one by one.
- Zero testing after site changes. A theme update, a new plugin, a GTM tweak — it doesn't take much to break the chain. Anyone who skips retesting after changes discovers the gaps months later, when the data is already lost.
What You Risk If You Leave Things As They Are
Ignoring this change cuts two ways, and neither is comfortable. On the compliance side, consent that's collected or transmitted incorrectly exposes you to challenges under GDPR and the DMA. On the business side, the damage is sneakier: campaigns keep running, but on partial data. Smart Bidding optimizes against conversions it only half sees, remarketing audiences shrink, reports paint a distorted picture, and you make decisions on the wrong numbers. It's the kind of problem that stays quiet until you watch your cost per acquisition climb for no apparent reason.
That's why it's worth treating tracking not as a one-off technical compliance task, but as a system you keep in good health. If you want the full picture, from event configuration to end-to-end measurement, start with our complete guide to conversion tracking. Consent Mode v2 is just one piece: reliable tracking is the foundation any customer acquisition system needs to actually work, because without clean data, every euro you invest in advertising is spent in the dark.
Frequently asked questions
Is Consent Mode v2 mandatory?
Effectively yes, if you run Google Ads campaigns targeting users in the European Economic Area and the UK: since March 2024 it's required under the Digital Markets Act and Google's EU User Consent Policy. Without it, remarketing and audiences empty out.
What exactly changes as of June 15, 2026?
Google Signals no longer controls the flow of data from GA4 to Google Ads. Control shifts to the four Consent Mode parameters (ad_storage, ad_user_data, ad_personalization, analytics_storage), while Signals remains only for GA4's behavioral reports on logged-in users.
Do I still need to keep Google Signals active?
You can, but its role is now limited to reports on logged-in users within GA4. It's no longer an advertising lever or a safety net for tracking toward Google Ads — that job now belongs entirely to Consent Mode.
Basic or advanced mode — which is better?
Basic mode is more cautious but loses non-consenting users entirely. Advanced mode recovers part of the conversions through modeling, by sending anonymous pings. Evaluate advanced mode with your DPO in light of GDPR and the ePrivacy Directive before enabling it.
Will I lose conversions because of this change?
Only if consent isn't transmitted correctly. With a compatible CMP and verified parameters, you keep your measurement intact. The risk mainly concerns those with untested setups that previously relied on Google Signals.
Is Consent Mode v2 enough to be GDPR-compliant?
No. It's the technical layer that communicates consent to Google. Compliance depends on how you collect and document that consent under the GDPR and the Italian Data Protection Authority's cookie guidelines. This content is informational and not legal advice.
Want tracking that withstands Google's changes without surprises and stays compliant with GDPR and the DMA? Talk to us, and let's build a solid, future-proof setup together.