What the April 2026 GA4 Update Actually Changed

The April 2026 GA4 update touched every layer connecting analytics data to ad campaign optimization — from event definitions to attribution models to consent enforcement.

This wasn’t a cosmetic refresh. Google restructured default event definitions, modified how enhanced conversions pass data back to Google Ads, updated Consent Mode requirements, changed the reporting interface, and deprecated several features PPC teams relied on daily. If your Google Ads campaigns use GA4-imported conversions — and most WooCommerce stores do — every one of those changes affects how your conversions are counted, attributed, and reported.

The attribution model shift is the most visible change. Google pushed the default further toward data-driven attribution with updated logic that weights upper-funnel interactions differently than prior versions. That means conversion values and ROAS calculations may shift even if nothing in your campaigns changed.

But the audience-facing changes are more dangerous because they’re silent. GA4 audience definitions that use certain legacy parameters or custom dimensions may no longer export correctly to Google Ads. The result: audience lists stop populating, and nobody gets a notification. Your remarketing campaigns continue running, bidding on audiences that are quietly evaporating.

Google also fully removed first-click attribution as a selectable model in GA4 reporting, consolidated the Advertising section, and moved the model comparison tool. Teams that relied on specific report layouts for weekly reviews are finding their workflows broken alongside their data.

You may be interested in: Your WordPress Analytics Dropped 90% Overnight — Consent Mode V2 Enforcement Fix

Why Remarketing Audiences Are Showing “List Too Small”

Three separate failure modes from the April 2026 update converge on the same symptom: audience lists that silently drop below the minimum threshold.

Here’s the thing: Google actually lowered the minimum audience size from 1,000 to 100 active users across all networks in December 2025 (Search Engine Land). That was supposed to make remarketing more accessible for smaller stores. The fact that WooCommerce stores still can’t meet even the 100-user threshold after the April update tells you how severe the data flow disruption actually is.

The first failure mode is the broken GA4-Ads link. Several advertisers reported that the GA4-to-Google Ads product link broke or partially disconnected after the update. Symptoms include imported conversions showing zero volume despite GA4 recording events normally, audience lists showing “List too small to use,” or remarketing campaigns losing their audience targeting entirely.

The second is the audience schema change. GA4 audience definitions that reference certain legacy parameters or custom dimensions stopped exporting to Google Ads after the update. These audiences appear active in GA4 but never populate in Google Ads. There’s no error message — just a list that gradually shrinks as existing cookies expire and new users never enter.

Google lowered the minimum audience size from 1,000 to 100 users in December 2025, yet many WooCommerce stores still cannot meet even the reduced threshold after the April 2026 update.

The third is Consent Mode V2 enforcement. While consent requirements have been rolling out gradually, the April 2026 update made it a hard requirement for GA4 data to flow accurately into Google Ads conversion tracking — not just in the EEA and UK, but with stricter behavioral modeling thresholds globally.

All three failure modes produce the same symptom in Google Ads: “List too small to use.” And because the list doesn’t vanish — it just shrinks — most store owners don’t notice until their remarketing campaigns have been bidding on effectively empty audiences for weeks.

How Broken Consent Mode Accelerates List Decay

Consent Mode V2 is the silent multiplier behind audience depopulation — and most WooCommerce stores don’t know their implementation is broken.

When Consent Mode V2 is misconfigured, GA4 shows 30-60% less traffic than your server logs (AuditTags, 2026). That’s not a rounding error. That’s more than half your visitors invisible to Google’s advertising stack — including the remarketing audience builder.

The failure pattern is specific. Consent Mode V2 requires four consent types — analytics_storage, ad_storage, ad_user_data, and ad_personalization — all set to denied by default before any tag fires. When the visitor clicks Accept, your consent management platform must call gtag('consent', 'update', ...) with the granted values. Storing the preference in the CMP’s database is not the same thing as transmitting it to Google’s tags.

Here’s where WooCommerce stores get hit hardest. Most use free consent plugins that display a cookie banner but never actually transmit the consent signal to Google’s tags. The banner looks compliant. Tag Assistant shows green. But GA4 never receives the consent update, so every visitor is treated as denied — and denied visitors don’t enter remarketing audiences.

GA4’s behavioral modeling is supposed to fill this gap, using machine learning to estimate data from users who denied consent. But modeling requires 1,000+ daily events with analytics_storage denied for at least 7 consecutive days before it activates (Google Analytics Help). Most small WooCommerce stores never hit that threshold. So modeling never turns on, and the data loss is permanent.

73% of GA4 setups have silent misconfigurations that cause 30-40% data loss, and most store owners discover the gap only when remarketing campaigns stop delivering.

And it’s about to get worse. On June 15, 2026, ad_storage replaces Google Signals as the sole signal governing Google Ads data from linked GA4 properties (Google via Dataslayer). Every WooCommerce store with mis-propagated consent will have a single, visible failure point instead of five hidden ones. Translation: if your ad_storage signal is broken today, every downstream Google Ads function stops working on June 15 instead of just degrading gradually.

The Smart Bidding Signal Chain That Just Broke

A depopulated audience list doesn’t just affect remarketing — it degrades every automated bid decision across your entire Google Ads account.

Smart Bidding processes over 50,000 dynamic micro-decisions daily, adjusting for device, location, time, audience, search context, and thousands of other variables (ALM Corp, 2026). Audience membership is one of the highest-weight signals in that calculation. When a user on your remarketing list searches for your target keyword, Smart Bidding bids significantly more aggressively because it knows that user has already visited your store.

Remove the audience signal, and Smart Bidding treats that same visitor as a cold prospect. The bid drops. The ad position drops. The conversion you would have gotten disappears — not because the customer lost interest, but because the algorithm lost data.

The compounding effect is what kills performance. Smart Bidding learns from its own decisions. When it can’t see returning visitors, it attributes fewer conversions to the patterns that brought those visitors back. Over time, the algorithm shifts budget away from the channels, keywords, and times that were actually driving repeat visits. You get a slow, invisible decline in ROAS that looks like market saturation but is actually signal starvation.

Advertisers with rich first-party data consistently achieve 20-40% lower CPAs than those relying solely on Google’s native audience signals (MDS Media, 2026). The inverse is equally true: advertisers who lose first-party audience data see CPAs rise by the same margin, compounding weekly as Smart Bidding relearns on degraded signals.

Signal Input	Healthy Audiences	Depopulated Audiences
Returning visitor bid adjustment	Smart Bidding bids aggressively on known visitors	All visitors treated as cold prospects
Conversion attribution	Full-funnel view of customer journey	Last-click only, missing earlier touchpoints
CPA trend	20-40% lower with rich first-party data	Rising CPAs as algorithm loses signal
Performance Max audience signals	Strong seed audiences guide exploration	Algorithm defaults to broad, untargeted reach
Budget allocation learning	Directs spend toward high-converting patterns	Shifts budget away from actual conversion drivers

You may be interested in: GA4 Is Narrowing Into a Google Ads Optimization Tool — Why Everything Else Works Better on Server-Side Data

How to Audit and Fix Your WooCommerce GA4 Audiences

Five checks in sequence — each one isolates a specific failure point in the data flow between your WooCommerce store and Google Ads.

Check 1: Verify the GA4-Google Ads link. Go to GA4 Admin > Product Links > Google Ads Links. Confirm the link is active and the correct GA4 property is connected to the correct Google Ads account. If the link appears active but data isn’t flowing, remove it and re-create it. Google’s documentation confirms this resolves most post-update linking issues. After re-linking, allow 24-48 hours before expecting full data flow.

Check 2: Audit Consent Mode propagation. Open your site in incognito. Before accepting cookies, check the Network tab for the first GA4 collect request. Confirm the gcs parameter shows G100 (consent denied). Accept cookies, trigger a new pageview, and confirm gcs updates to G111. If gcs stays G100 after accepting, your consent banner isn’t transmitting the consent signal to Google’s tags.

Check 3: Validate audience definitions. In GA4, navigate to Admin > Data Display > Audiences. Check each audience exported to Google Ads. Look for any that reference custom dimensions or legacy parameters that may have been deprecated in the April update. Recreate affected audiences using current event parameters.

Check 4: Test enhanced conversion match rates. In Google Ads, check your enhanced conversion diagnostics. A drop in match rate means fewer conversions are being properly attributed, which makes audience lists populate more slowly. Common culprits are generate_lead and begin_checkout events whose validation requirements changed in the April update.

Check 5: Run a baseline comparison. Export your Google Ads audience list sizes today. Compare against your GA4 audience sizes for the same definitions. If GA4 shows 500 users in an audience but Google Ads shows 40, you have a consent or data-flow break between the two. The gap is your measurement of exactly how much data you’re losing.

Why Server-Side Tracking Is the Structural Fix

Browser-based tracking depends on JavaScript executing in the visitor’s browser, consent signals transmitting correctly, and cookies persisting across sessions — server-side tracking eliminates all three dependencies.

Server-side tracking captures purchase events at the WordPress hook level, recovering up to 40% of conversions that browser-only tracking misses (TrackSharp, 2026). When a WooCommerce order completes, the event is recorded server-side regardless of what’s happening in the visitor’s browser — ad blockers, JavaScript errors, consent banner load order, Safari ITP, or network interruptions.

The key insight for audience recovery is this: server-side tracking routes events through your own subdomain as a first-party data source. That means the data entering GA4 and Google Ads isn’t subject to the same browser-level filtering that’s currently depopulating your audiences. Users who would have been invisible to browser-based tags become visible again.

This doesn’t mean you can ignore consent. GDPR and privacy regulations still apply. But server-side tracking gives you a compliant first-party data collection system that doesn’t depend on complex client-side consent integrations working perfectly across every page, every browser, and every consent banner configuration.

The practical architecture collapses what would be eight separate failure points in a browser-based setup into one controlled hop on your own infrastructure. Transmute Engine™ captures events from WooCommerce hooks and routes them server-side to GA4, Google Ads, and other platforms simultaneously — each destination receives a version of the event tailored to its specifications, with consent state applied once at the server level rather than re-evaluated at every browser touchpoint.

For WooCommerce stores that depend on remarketing audiences for ROAS-positive advertising, server-side tracking isn’t an optimization. It’s the difference between audience lists that keep populating and audience lists that silently die.

Key Takeaways

• Audit your GA4-Ads link immediately: The April 2026 update broke or partially disconnected the product link for many accounts. Re-linking takes minutes and resolves most data-flow issues within 48 hours.
• Verify Consent Mode V2 propagation, not just banner presence: A visible cookie banner doesn’t mean consent signals reach Google’s tags. Check the gcs parameter in your GA4 collect requests to confirm.
• Recreate audiences using current event parameters: Legacy parameters and custom dimensions may no longer export to Google Ads after the April update. Rebuild affected audiences from scratch.
• Understand the June 15 deadline: Ad_storage becomes the sole signal governing Google Ads data from linked GA4 properties. Fix consent propagation now, before five overlapping consent surfaces collapse to one.
• Consider server-side tracking as the structural fix: Browser-based tracking has too many failure points for reliable audience population. Server-side capture at the WordPress hook level recovers up to 40% of lost conversions.

References

SR Analytics (2025). WooCommerce Conversion Tracking: The 8-Hop Chain. Via Seresa.

groas.ai (2026). GA4 Update April 2026: What Changed, What Broke For Google Ads Advertisers. groas.ai.

AuditTags (2026). Consent Mode v2 in 2026: Why GA4 and Google Ads Disagree. AuditTags.

Search Engine Land (2025). Google slashes audience targeting thresholds to 100 users across all networks. Search Engine Land.

Dataslayer (2026). GA4 + Google Ads Data Controls: What Changes June 15, 2026. Dataslayer.

ALM Corp (2026). Google Ads Advanced Tactics to Maximize ROAS for 2026. ALM Corp.

MDS Media (2026). Google Ads Best Practices for 2026. MDS Media.

TrackSharp (2026). Server-Side GA4 Tracking for WooCommerce. WordPress.org.

Your remarketing audiences aren’t going to fix themselves. Talk to Seresa about server-side tracking that keeps your audience lists alive.