Google’s June 2026 Consent Mode Overhaul: What Changed for WooCommerce Stores

What changed in Google Consent Mode on June 15 2026?#

Google made ad_storage the sole control that determines what advertising data reaches your Google Ads account, removing the separate gates that ad_user_data and ad_personalization previously provided. Before June 15, each of the four Consent Mode signals independently controlled a specific slice of advertising functionality — ad_user_data gated whether Google could use visitor data for ads, ad_personalization controlled remarketing eligibility, and ad_storage managed cookie-based tracking. That’s no longer how it works.

The consolidation means ad_storage is now the single control for all advertising data flow to Google Ads as of June 15, 2026 (OneTrust, 2026). When a visitor grants ad_storage, all four advertising functions activate. When they deny it, everything stops — regardless of how the other three signals are set.

The ad_storage signal now controls all advertising data flow to Google Ads, overriding ad_user_data and ad_personalization for advertising purposes (OneTrust, 2026).

For WooCommerce store owners running Google Ads, this isn’t a cosmetic API cleanup. A consent banner that correctly set ad_user_data and ad_personalization but left ad_storage ambiguous was fine before June 15. After it, that same configuration sends Google nothing.

How does the ad_storage change affect WooCommerce conversion tracking?#

When a visitor denies ad_storage consent, no advertising cookies are set, no conversion events pass to Google Ads, and remarketing audiences stop growing from that visitor — Google fills gaps with less precise conversion modelling. The impact is severe: sites without proper Consent Mode v2 signals saw remarketing audience drops of 40–60% (Plainly, 2026). That’s not a theoretical risk — it’s measured audience shrinkage on live campaigns.

Here’s the thing: your WooCommerce store might be tracking purchases in GA4 while sending Google Ads absolutely nothing. Analytics tracking (analytics_storage) and advertising tracking (ad_storage) are independent signals. A visitor who grants analytics consent but denies ad consent still shows up in your GA4 reports. But Google Ads never sees that purchase. Your ROAS calculations, Smart Bidding inputs, and audience signals all have a hole where that conversion should be.

Related: GDPR Consent Mode V2 Is Breaking WooCommerce Tracking — Here’s the Math

What are the four Google Consent Mode signals?#

The four signals are analytics_storage (controls GA4 cookies), ad_storage (controls advertising cookies and conversions), ad_user_data (controls whether user data reaches Google for ads), and ad_personalization (controls remarketing and personalised ads). Understanding how they interact after June 2026 is essential for configuring your consent banner correctly.

Since June 2026, ad_storage overrides the other three signals for advertising data purposes (Didomi, 2026). The hierarchy now works like this:

Signal	Pre-June 2026 Role	Post-June 2026 Role
analytics_storage	Controls GA4 cookies	Unchanged — still controls GA4 cookies independently
ad_storage	Controls advertising cookies	Now sole gate for ALL advertising data to Google Ads
ad_user_data	Independent gate for user data in ads	Subordinate to ad_storage for advertising purposes
ad_personalization	Independent gate for remarketing	Subordinate to ad_storage for advertising purposes

The practical takeaway: if your consent banner doesn’t explicitly grant ad_storage, the other advertising signals are irrelevant. Without ad_storage, Google Ads receives nothing — even if ad_user_data and ad_personalization are both set to granted.

What happened to Google Signals after the June 2026 update?#

Google Signals no longer gates advertising data — it now only affects Analytics reporting features like cross-device audiences, while ad_storage alone controls what conversion and advertising data reaches Google Ads. This is a significant shift that many store owners haven’t caught. If you enabled Google Signals in GA4 thinking it was helping your advertising data reach Google Ads, that assumption is now wrong.

Google Signals’ role reduced from dual advertising-and-analytics gate to Analytics-only reporting control (OneTrust, 2026). Before the June update, Google Signals sat in the chain between your GA4 data and Google Ads. It contributed demographic and cross-device data that fed into advertising audiences. That dual role ended on June 15. Google Signals still powers cross-device reporting within GA4 — things like Users by Age or the cross-device segment in Explore — but it no longer contributes to the advertising data that reaches your Google Ads account.

Sites without proper Consent Mode v2 signals saw remarketing audience drops of 40–60% after Google’s June 2026 ad_storage consolidation (Plainly, 2026).

The question isn’t whether Google Signals matters. The question is whether your consent banner correctly grants ad_storage — because that’s the only signal Google Ads is listening to now.

Related: Google’s June 2026 Consent Mode Change Silently Broke WooCommerce Conversion Attribution

How much conversion data do EU WooCommerce stores lose without proper consent?#

EU WooCommerce stores lose 40 to 70 percent of advertising conversion data because that proportion of EU visitors reject cookie consent banners, and without ad_storage granted, Google Ads receives no user-level advertising data from those sessions. 40–70% of EU visitors reject cookie consent banners (Didomi / GDPR studies, 2023) — and under the new rules, every one of those rejections means zero conversion data reaches your Google Ads account.

That number isn’t theoretical. If your WooCommerce store shows 100 purchases in GA4 but Google Ads reports 40 conversions, you’re seeing the consent gap in action. Those missing 60 purchases happened — your payment gateway confirms that — but Google Ads never knew about them because the visitors denied ad_storage and no server-side fallback was in place.

The downstream effects compound. Smart Bidding receives fewer signals and optimises less accurately. Remarketing audiences grow slower because denied-consent visitors are invisible. Lookalike audiences narrow. Each percentage point of consent rejection ripples through every automated campaign you run.

Does Google’s conversion modelling replace the lost consent-blocked data?#

Google’s behavioural modelling estimates conversions from unconsented sessions but produces less precise data than observed conversions, and is only available to accounts meeting minimum traffic thresholds that many small WooCommerce stores fall below. Translation: if your store doesn’t generate enough traffic, Google can’t model what it can’t see, and you’re left with a raw gap in your conversion data.

Even for stores that qualify, modelled conversions carry less weight than observed ones. Google Ads’ Smart Bidding treats modelled data as a lower-confidence input than directly observed conversions (Google Analytics Help, 2026). Your Target ROAS or Maximise Conversions bidding strategy will make more cautious decisions when a large proportion of its conversion data comes from modelling rather than direct observation.

There’s a structural problem modelling can’t solve: 30–40% of conversion data lost to tracking blockers industry-wide (Industry consensus, 2024). Consent rejection is just one channel of data loss. Ad blockers, Safari ITP, and Firefox ETP strip tracking parameters before your consent banner even loads. The more data you lose at the source, the less reliable the model becomes.

Related: Your WordPress Consent Banner Looks Fine But Google Sees Zero Consent

Can server-side tracking fix the Consent Mode data gap for WooCommerce?#

Server-side tracking sends consented first-party conversion data directly from your server to Google Ads, reducing dependency on client-side ad_storage cookies and recovering data that browser-side consent rejection otherwise blocks. Server-side tracking recovers 30–40% of conversion data typically lost to tracking blockers (OneTrust, 2026) — not by circumventing consent, but by sending the consented data through a channel that ad blockers and browser privacy features don’t intercept.

When a customer completes a WooCommerce purchase, the order data — transaction ID, value, products — exists on your server regardless of what happened in their browser. Server-side tracking pairs that order data with the consent status you’ve collected and sends the consented conversion event directly to the Google Ads API. The browser, the ad blocker, and the cookie expiry are all out of the loop.

Tools like Transmute Engine handle this consent signal routing server-side for WordPress and WooCommerce stores specifically, so conversion data reaches Google Ads correctly regardless of what the visitor’s browser does to client-side tags. The result is the same first-party data, routed through your own server endpoint instead of through the browser’s increasingly hostile tracking environment.

What is the most common Consent Mode misconfiguration on WordPress sites?#

The most common error is setting analytics_storage to granted while leaving ad_storage denied or unset, which lets GA4 collect browsing data but blocks all conversion events and remarketing signals from reaching Google Ads. With 43.5% of websites running WordPress (W3Techs, 2024), this misconfiguration affects the largest platform surface on the web — and it’s almost always invisible to the store owner because GA4 keeps working normally.

The misconfiguration happens because most WordPress consent banner plugins treat analytics and advertising consent as a single category. They ask visitors one question — “Accept cookies?” — and map the answer to all four Consent Mode signals simultaneously. A properly configured setup sets analytics_storage default to denied with a path to granted through the banner, and independently sets ad_storage default to denied with its own consent path.

40–70% of EU visitors reject cookie consent banners, blocking all conversion events from reaching Google Ads under the new Consent Mode rules (Didomi, 2026).

The diagnostic is straightforward: open your browser’s developer console, navigate to your WooCommerce store, reject the consent banner, and check what gtag(‘consent’, ‘default’, ...) fires. If ad_storage shows denied or doesn’t appear at all, your Google Ads is receiving nothing from visitors who decline — which, in the EU, is the majority.

Key Takeaways#

• ad_storage is now the master switch: since June 15, 2026, it’s the sole control for all advertising data reaching Google Ads — the other signals are subordinate for advertising purposes.
• WooCommerce stores face 40–60% audience drops: sites without proper Consent Mode v2 signals saw remarketing audiences shrink by 40–60% after the consolidation.
• GA4 data doesn’t mean Google Ads data: analytics_storage and ad_storage are independent signals, so your GA4 reports can look healthy while Google Ads receives nothing.
• Server-side tracking recovers the gap: routing consented first-party conversion data server-to-server recovers 30–40% of data lost to browser-side blocking.
• Check your ad_storage default now: the most common WordPress misconfiguration leaves ad_storage denied or unset while analytics_storage works fine.

References#

1. OneTrust (2026). What Google’s June 2026 Consent Mode Changes Mean for Google Ads. Source
2. Didomi (2026). Google Consent Mode 2026 Changes. Source
3. Plainly (2026). What’s New in GA4 2026. Source
4. Google Analytics Help (2026). Consent Mode and Modelling. Source
5. W3Techs (2024). Usage of Content Management Systems. Source