Your Enhanced Conversions Broke in April — Server-Side Is the Fix
GA4’s April 2026 data-layer schema change silently degraded Enhanced Conversions match rates for WooCommerce stores using GTM, even though tags still fire normally. The generate_lead and begin_checkout events were most affected — the highest-value funnel events. Advertisers typically see 5-15% more reported conversions after implementing Enhanced Conversions, which is the signal that evaporated. Safari already caps cookies at 1-7 days, making browser-fired hashed data structurally fragile. Moving Enhanced Conversions server-side eliminates the schema dependency entirely.
The Silent Break
GA4 changed the schema in April — and WooCommerce stores running GTM didn’t get a warning.
GA4’s April 2026 update changed the data-layer schema expected for Enhanced Conversion data. The field names changed. The nesting structure changed. GTM setups using the older user_data object structure still fire — but fail to pass hashed data correctly to Google.
The result: your Enhanced Conversions match rate drops, but your conversions appear to still count. Google Ads keeps reporting purchases. Your campaign dashboards look normal. The only thing that changes is the quality of the signal Google uses to match your conversion data to user profiles — and that degradation shows up not in your reports, but in your campaign performance over weeks.
GA4’s April 2026 update changed the data-layer schema expected for Enhanced Conversion data — GTM setups using the older user_data structure still fire but fail to pass hashed data correctly, so match rates drop while conversions appear to still count.
Advertisers typically see 5-15% more reported conversions after implementing Enhanced Conversions. That’s the signal that silently evaporated for many WooCommerce stores after the April schema change — even though their tags kept firing. The tag is doing its job. The data layer underneath it isn’t feeding it the right structure anymore.
Which Events Broke First
The highest-value funnel events are the ones most affected.
The generate_lead and begin_checkout events are the events most commonly demoted or revalidated by the April 2026 GA4 change. These aren’t peripheral tracking events — they’re the highest-value WooCommerce funnel events that directly feed Google Ads Smart Bidding, Performance Max, and any campaign optimising toward mid-funnel or bottom-funnel actions.
When the match rate for these events degrades, Google’s bidding algorithms receive less accurate user-level data. The algorithm doesn’t stop bidding. It bids with less information. Over weeks, that means higher CPAs, less precise audience matching, and campaign optimisation that drifts from your actual customers toward a lower-quality signal set.
Purchase events may be less affected in some configurations, but the upstream funnel events that feed audience building and remarketing are the ones that broke first. If your Google Ads campaigns optimise toward begin_checkout or generate_lead, the April schema change hit the conversion events your budget depends on most.
You may be interested in: BigQuery Connectors Are Changing Schemas in June 2026
Why Your Tags Still Fire
A firing tag and a working Enhanced Conversion are two different things.
Here’s the thing: Google Tag Manager fires tags based on trigger conditions — page URL, event name, dataLayer push. Whether the Enhanced Conversion data passes correctly is a separate question from whether the tag fires at all.
The tag fires because the trigger conditions still match. The dataLayer still pushes an event called purchase or begin_checkout. GTM sees the event, fires the conversion tag, and Google Ads receives a conversion. But the Enhanced Conversion portion of that tag — the part that sends hashed email, phone, name, and address to Google for user matching — depends on the data-layer variable mapping being correct.
The April 2026 schema change moved where those user data fields live in the data layer. If your GTM variable still points at the old location, the tag fires, the conversion records, but the hashed user data comes through empty or malformed. Google Ads counts the conversion but can’t match it to a user profile. The match rate drops. The tag doesn’t throw an error.
Advertisers typically see 5-15% more reported conversions after implementing Enhanced Conversions — that is exactly the signal that silently disappeared for stores running the older GTM schema.
This is why the break is silent. No failed tag alerts. No Google Ads diagnostic warnings. No error in Tag Assistant. You have to look at the Enhanced Conversions diagnostics page specifically, or notice a gradual CPA drift that takes weeks to become statistically significant.
The Browser Layer Was Already Fragile
Even without the schema change, browser-fired Enhanced Conversions were losing ground.
The April schema break exposed a structural weakness that existed before the change. Safari limits cookie lifespans to roughly 1-7 days and Firefox blocks third-party cookies entirely — so browser-fired hashed data was already structurally fragile regardless of whether the schema was correct.
About 30% of internet users globally run ad blockers, which intercept the tag request before hashed data ever leaves the browser. Safari’s ITP strips click identifiers like gclid from URLs in some contexts, degrading the attribution chain that Enhanced Conversions is designed to strengthen.
| Failure Layer | Browser-Based EC | Server-Side EC |
|---|---|---|
| GA4 schema changes | Breaks silently when data-layer fields move | Not affected — reads from server, not data layer |
| Ad blockers (~30% of users) | Tag blocked, no EC data sent | Server sends directly to Google API |
| Safari ITP (7-day cookie cap) | User data may be stale or missing | First-party server sets durable cookies |
| Firefox (blocks third-party cookies) | EC data may not resolve correctly | First-party data sent server-to-server |
| Consent banner dismissal | Tag may not fire at all | Server applies consent rules before sending |
Each of these mechanisms independently degrades Enhanced Conversions signal. The April schema change was the latest failure mode, not the first. The pattern is clear: every six to twelve months, a browser-level or platform-level change breaks or degrades a tracking mechanism that WooCommerce stores depend on.
The question isn’t whether the next change will break your Enhanced Conversions setup. It’s whether your architecture can absorb it without manual intervention.
The Server-Side Fix That Survives the Next Change
Server-side Enhanced Conversions removes the data-layer dependency entirely.
Server-side Enhanced Conversions sends hashed first-party data directly from your WooCommerce server to Google’s API. The data doesn’t pass through the browser data layer, so schema changes can’t break it. It doesn’t rely on the browser executing JavaScript, so ad blockers can’t intercept it. It doesn’t depend on cookies set by third-party scripts, so ITP can’t expire the signal.
The architecture is different in kind, not just in degree. Browser-based Enhanced Conversions takes user data from the data layer at the moment the tag fires in the visitor’s browser, hashes it client-side, and sends it to Google with the conversion event. Server-side Enhanced Conversions takes user data from your WooCommerce order record — the authoritative source — hashes it on your server, and sends it directly to Google’s Ads API.
Your WooCommerce order database always has the customer’s email and name. It doesn’t change format when GA4 releases a schema update. It doesn’t disappear when Safari truncates a cookie. It doesn’t fail to load when an ad blocker intercepts a script. The conversion data and the match data come from the same authoritative system, routed through infrastructure you control.
You may be interested in: Shopify Got UCP for Free — WooCommerce Must Build It
This is the durable fix. Not updating your GTM variables to match the new schema — though you should do that as an immediate patch. The durable fix is removing the dependency on a schema that changes without notice. Transmute Engine™ is built to deliver this: server-side conversion data routed from your WooCommerce order system to Google Ads with hashed first-party match keys, independent of any browser-side data layer.
How to Check Your Store Right Now
Two diagnostic steps that take five minutes and tell you whether the break hit your store.
Step one: check your Enhanced Conversions diagnostics in Google Ads. Navigate to Tools → Conversions → select a conversion action → Diagnostics. Look at the match rate trend. If it dropped in April 2026 and hasn’t recovered, your data-layer schema is likely misaligned with the current GA4 structure.
Step two: check your data-layer output in Tag Assistant. Fire a test conversion and inspect the data-layer push. Look for the user_data object and compare the field names and nesting to Google’s current Enhanced Conversions documentation. If your variable still references the pre-April structure, the tag fires but the hashed data passes empty.
The immediate fix is updating your GTM variables to the new schema. That restores match rates today. The strategic fix is moving Enhanced Conversions server-side so the next schema change — and there will be one — doesn’t require another manual intervention.
Key Takeaways
- Silent failure: GA4’s April 2026 schema change broke Enhanced Conversions match rates without affecting tag firing — conversions count but user matching degrades.
- Highest-value events hit first: The generate_lead and begin_checkout events are most commonly affected, directly impacting Google Ads Smart Bidding and Performance Max.
- Browser layer was already fragile: Safari’s 1-7 day cookie cap, 30% ad-blocker usage, and Firefox’s third-party cookie blocking independently degrade browser-fired Enhanced Conversions.
- Server-side eliminates the dependency: Server-side Enhanced Conversions reads from your WooCommerce order database and sends to Google’s API directly — no data-layer schema dependency.
- Check your diagnostics now: The Enhanced Conversions diagnostics page in Google Ads shows match rate trends — a drop in April 2026 confirms the schema break hit your store.
GA4’s April 2026 update changed the data-layer schema expected for Enhanced Conversion data. GTM setups using the older user_data object structure still fire, but fail to pass hashed data correctly to Google, so the match rate drops even though conversions appear to count normally.
The generate_lead and begin_checkout events are most commonly demoted or revalidated by the April 2026 change. These are the highest-value funnel events for WooCommerce stores running Google Ads campaigns.
The immediate fix is updating your GTM data-layer variables to match GA4’s new field names and nesting structure. The durable fix is moving Enhanced Conversions server-side, which eliminates the data-layer schema dependency entirely.
Server-side Enhanced Conversions sends hashed first-party data directly from your server to Google’s API. It bypasses the data-layer schema, is not affected by ad blockers or Safari ITP cookie restrictions, and works regardless of future browser-side changes.
Yes. That is the problem. The tags fire normally and conversions appear to count, but the hashed user data that powers Enhanced Conversions match rates is no longer being passed correctly due to the schema change. The failure is silent.
References
- Groas. “Google Ads Conversion Tracking Setup 2026: The Complete Guide.” 2026. groas.ai
- Groas. “GA4 Update April 2026: What Changed for Google Ads Conversion Tracking.” 2026. groas.com
- Apple/WebKit. “Tracking Prevention.” 2026. webkit.org
- Statista. “Ad-blocking usage worldwide.” 2024. statista.com
The next GA4 schema change is a matter of when, not if. Talk to Seresa about moving your Enhanced Conversions server-side so it doesn’t break again.