Consent Mode v2 in GA4: What Changed on June 15, 2026 (and How to Stop Losing Conversions)

Since June 15, 2026, Consent Mode v2 in GA4 is no longer just a GDPR compliance checkbox: it is now the only switch that decides whether your conversions reach Google Ads. Google has stripped the Google Signals setting of its safety-net role. In practice, the ad_storage parameter alone governs the flow of advertising data between GA4 and your linked Ads accounts. If your consent banner sends the signal incorrectly, your conversions, your remarketing audiences, and your Smart Bidding signals can vanish with no fallback whatsoever. This guide explains how Consent Mode v2 works, spells out exactly what flips on June 15, and gives you a full audit checklist, from the banner all the way down to the tag.

What changed on June 15, 2026

Until now, two settings jointly decided whether Google Ads received advertising cookies and user identifiers from your site: the Google Signals setting inside GA4, and the ad_storage parameter in Consent Mode. Both had to permit collection for the full signal to flow. That dual control acted as a safeguard: if your CMP or Consent Mode was misconfigured, turning Google Signals off still kept data from leaking into Google Ads.

Since June 15, 2026, that logic is gone. Here is what matters:

• ad_storage becomes the sole authority. The Consent Mode ad_storage parameter alone governs what gets collected and passed to linked Google Ads accounts. There is no second control anymore.
• Google Signals is confined to GA4 reporting. The setting no longer governs the flow to Google Ads. It now serves only to associate sessions with signed-in users for GA4’s internal behavioral reports (cross-device journeys, demographics, interests).
• No more safety net. Switching Google Signals off no longer stops data from reaching Google Ads. If ad_storage is granted, the data goes, full stop.

Put plainly: every interaction with your banner now routes data in just two ways. Consent granted on ad_storage, and Google Ads receives everything. Consent denied, and Google Ads is blocked. There is no longer a grey zone managed by Google Signals.

That is exactly what makes the audit urgent: a banner error that went unnoticed yesterday can now cut off your conversions with no alert at all.

Consent Mode v2 in GA4: the 4 parameters to know

Consent Mode v2 relies on four signals that your site sends to Google through gtag or GTM. Understanding which does what is the foundation of any serious audit.

• ad_storage: permits advertising-related storage (ad cookies, identifiers). This is the parameter that became central on June 15.
• analytics_storage: permits analytics-related storage (GA4 measurement cookies, _ga).
• ad_user_data: permits sending user data to Google for advertising purposes.
• ad_personalization: permits using data for personalized advertising and remarketing.

One technical distinction is worth stating clearly. ad_storage and analytics_storage are upstream qualifiers: they decide which identifiers travel with the pings being sent. ad_user_data and ad_personalization are downstream instructions: they tell Google’s services how to process the data once received. The first two (introduced with Consent Mode v1) gate collection; the last two (added by v2 in March 2024 for the EU’s DMA) gate usage.

Since March 2024, these four signals have been mandatory to serve ads and use remarketing in the European Economic Area. The June 15 change does not touch that requirement: it changes who, between Google Signals and ad_storage, holds the controls for the flow to Ads.

Basic vs advanced mode: the real difference

Consent Mode ships in two flavors, and the choice has a direct impact on how much data you keep.

In basic mode, Google pixels and tags do not fire until consent is given. Visitors who reject the banner are completely invisible to Google Ads and GA4. In advanced mode, tags load immediately in a “denied” state, send anonymized cookieless pings, and if consent is later granted, hits collected on the same page get reprocessed with “granted” status. Advanced mode is also what unlocks conversion modeling: Google estimates the conversions lost from users who refused.

For reference, advanced mode delivers a modeling uplift in the range of 15 to 25%, provided you meet the minimum thresholds (roughly 700 ad clicks per country over 7 days and around a 20% consent rate). For most European sites investing in Google Ads, advanced mode is the sensible choice: it maximizes retained signal while respecting the user’s refusal.

Why this change breaks your conversions silently

The danger is not the change itself, it is that it turns a tolerated error into an invisible outage. Before June 15, a banner that failed to send ad_storage correctly could be rescued if Google Signals was on: the flow went through anyway. That leniency is gone.

From now on, three typical symptoms show up when ad_storage is not transmitted correctly:

• Missing conversions in Google Ads. Conversions imported from GA4 stop coming through, or drop sharply. Your campaigns look weaker even though nothing changed on the business side.
• Remarketing audiences draining out. Without ad_storage granted, audience lists stop filling and eventually fall below the minimum activation thresholds.
• Blind Smart Bidding. Automated bidding algorithms lose their conversion signal and degrade their decisions, often with no explicit warning.

A large share of GA4 implementations are believed to carry silent Consent Mode misconfigurations. As long as Google Signals acted as a net, those errors had no consequence on Ads. That is no longer true. Hence the audit below.

Audit checklist: banner, CMP, signal, tag

Here is the sequence to run in order, from the interface the user sees down to the signal actually sent. The idea is to follow the consent through each link in the chain to spot where it gets lost.

1. The banner (CMP)

First, confirm that your consent management platform actually fires all four parameters. Open your site in a private window, reject everything, then accept everything, and watch both scenarios.

• Does the banner offer a genuine refusal as accessible as acceptance? (DMA requirement)
• On refusal, do all four signals correctly switch to “denied”?
• On acceptance, do they correctly switch to “granted”?
• Is the default declared before any Google tag, with wait_for_update to give the CMP time to respond?

2. The Consent Mode signal (gtag / dataLayer)

Inspect the real signal, not just what the CMP claims to send. The default should look like this, declared as early as possible:

gtag('consent', 'default', {
  'ad_storage': 'denied',
  'analytics_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'wait_for_update': 500
});

Then, on the user’s decision, an update revises the relevant parameters:

gtag('consent', 'update', {
  'ad_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted'
});

In Chrome, the Google Tag Assistant extension or the Network tab (filter on google-analytics and googleads) show you the gcs parameter sent with each hit. A gcs=G111 means consent granted on storage; G100 means refused. That is the irrefutable proof of what actually leaves the browser.

3. The Google Signals setting in GA4

Go to Admin → Data collection and modification → Data collection. Check the Google Signals state and remember its new scope: this setting no longer drives the flow to Google Ads. If you turn it off thinking you are blocking Ads, you are pulling the wrong lever as of June 15. Keep it on only if you want signed-in user association for GA4 reports.

4. The tag and the GA4 to Google Ads link

Finally, verify that the link between your GA4 property and your Google Ads account is active (Admin → Product links → Google Ads links), and that your imported conversions are flagged as active. On the GTM side, check that your conversion and remarketing tags respect the consent state (consent settings filled in correctly).

To transmit consent robustly, beyond the browser, moving server-side is the natural complement to this audit. See the guide GTM Server-Side: why and how to migrate, which details how to relay consent signals server-side without depending on browser restrictions. And if your GA4 property is new or shaky, fix the foundations first with Set Up GA4 From Scratch.

Measuring the impact before and after

An audit without measurement stays a hypothesis. Set a baseline before any fix, then compare.

• ad_storage consent rate. Track the share of sessions with gcs=G111. It is your number-one health metric.
• Imported conversions in Google Ads. Record the daily volume before the fix, then watch the recovery after. A clear rebound confirms the signal is flowing again.
• Remarketing audience size. Check that your lists climb back above the activation thresholds.

Document the exact date of each change so you can isolate its effect in the charts. If you have the BigQuery export wired up, you can query the gcs parameter directly at the event level to measure the real consent rate, without relying on interface sampling. This kind of analysis follows the same fine-grained measurement logic described in the guide on tracking AI traffic in GA4, where you also go and find the signal where it actually hides.

In summary

The June 15, 2026 change does not reinvent Consent Mode v2, it removes its safety net. From now on, ad_storage alone decides the fate of your conversions toward Google Ads, while Google Signals is limited to GA4-internal reporting. To lose nothing:

1. Audit the full chain: banner, CMP, gcs signal, Google Signals setting, tag and Ads link.
2. Confirm ad_storage switches to “granted” when the user accepts, by inspecting the real gcs parameter.
3. Measure before and after on consent rate, imported conversions, and audience size.

Sites that treat consent as a simple GDPR checkbox will watch their conversions erode without understanding why. Those who audit the banner-to-tag chain now will keep accurate numbers and campaigns steered on real signal.