Google Merged Enhanced Conversions Into One Toggle — What Broke on WooCommerce

What Merged, What Moved, and Why It Matters

Google collapsed two separate Enhanced Conversions products into one toggle and simultaneously migrated offline data ingestion to an entirely new API.

Until June 2026, Enhanced Conversions came in two flavors. Enhanced Conversions for Web sent hashed customer data alongside online purchase and form completion events captured on your website. Enhanced Conversions for Leads sent hashed data for offline conversions — a lead that closed by phone a week after the ad click, uploaded later from a CRM. Each had its own settings screen, its own setup workflow, and required you to choose a single implementation method: the Google tag, Google Tag Manager, or the Google Ads API.

That split is gone. Starting June 2026, both products merged into a single feature with one on/off toggle. The method selection screen disappeared from the Google Ads interface entirely. Google Ads now simultaneously accepts user-provided data from website tags, Data Manager, and API connections — no more forcing a single implementation path.

The structural logic makes sense. The underlying operation was always identical: accept hashed first-party data, match it to an ad click, improve attribution. Splitting it into two products with two setup paths was artificial. One toggle plus multi-source ingestion matches how the data actually flows.

But here’s the thing: simplifying the interface doesn’t simplify what happens underneath. The merge carried every existing setup — working or broken — into the unified system. If your Enhanced Conversions was sending empty user data fields before the merge, it’s still sending empty fields now. The new toggle just makes it harder to see.

67% of first-implementation Enhanced Conversions setups on WooCommerce fail audit, primarily due to data layer timing issues where GTM fires the conversion tag before customer data populates — and the June 2026 merge auto-migrated every one of these broken setups into the unified system.

You may be interested in: Google Made Your CMP the Single Point of Failure for WooCommerce Conversions

The Auto-Migration Trap: Customer Data Terms

Google’s “no action required” statement has a critical qualifier that most WooCommerce store owners missed.

Google’s official documentation states that existing users will be automatically migrated to the unified Enhanced Conversions toggle — “if you have previously agreed to Google’s customer data terms.” That qualifier is doing enormous work. Plugin-based WooCommerce setups frequently skip the customer data terms acceptance step because the plugin handles tag firing, but the account-level terms must be accepted manually in Google Ads settings.

The customer data terms govern whether Google can use the hashed first-party data you send for matching purposes. Without them, the data you transmit is functionally ignored. Your conversion tag fires. Google receives the event. But the hashed email, phone, and address that make Enhanced Conversions work get discarded server-side because your account hasn’t authorized their use.

The result after the merge: your unified toggle shows “on.” Your conversion actions show activity. The diagnostics panel shows a match rate of 0% — or worse, doesn’t show Enhanced Conversions diagnostics at all because the feature was never properly activated at the account level. You’re running Google Ads campaigns with standard cookie-based attribution while the dashboard suggests you’re getting Enhanced Conversions benefits.

To check: in Google Ads, navigate to Settings → Customer data terms. If the status isn’t “Accepted,” your Enhanced Conversions has been cosmetic since the day it was enabled.

Why 67% of WooCommerce Setups Were Already Broken

Data layer timing is the silent killer — your conversion tag fires before your customer data arrives, and you won’t know for 48-72 hours.

The standard WooCommerce Enhanced Conversions implementation relies on GTM4WP (Google Tag Manager for WordPress) to populate a data layer with customer information at checkout. The sequence needs to be precise: WooCommerce processes the order, GTM4WP pushes customer data to the data layer, and the Google Ads conversion tag reads that data before firing. Miss that timing window by milliseconds and Google receives the conversion without the customer data that makes Enhanced Conversions work.

In most WooCommerce setups, the purchase event triggers, GTM sends the conversion, and the user_data fields arrive empty or incomplete. The conversion still counts in Google Ads. The match rate column shows zero or near-zero. Nobody checks because the conversion number looks correct — the issue is invisible at the campaign level.

Three specific failure modes account for the majority of the 67% failure rate. First, data layer timing: GTM4WP populates customer data after the conversion tag has already fired. Second, double hashing: some plugins pre-hash the email, then GTM hashes it again, corrupting the data so Google can never match it. Third, Consent Mode conflicts: if ad_user_data is denied or undefined, Enhanced Conversions data gets blocked even when the conversion itself fires correctly.

The diagnostic feedback loop makes all of this worse. You won’t know whether your setup works for 48 to 72 hours after implementation. Then the Google Ads diagnostic might show “Low match rate” without explaining why — sending you back to troubleshoot blind against a data layer timing issue you can’t see in real time.

Enhanced Conversions with a match rate above 50% delivers a documented 17.8% lower CPA versus pixel-only tracking — but most WooCommerce advertisers see match rates between 29% and 62%, with EU-heavy audiences sitting lower due to consent gate effects.

Match Rate Reality: What Your Diagnostics Actually Mean

The match rate column in Google Ads is the clearest signal of Enhanced Conversions health — and most WooCommerce stores have never checked it.

Match rate measures the share of conversions where Google successfully matched your hashed customer data to a signed-in Google account. A match rate of 0% means Enhanced Conversions added zero signal. A rate of 70% means roughly 70% of your conversions got richer attribution that cookie-based tracking alone couldn’t provide.

Match Rate Range	Interpretation	Smart Bidding Impact
Below 30%	Setup problem — data quality, formatting, or hashing errors	Minimal benefit; effectively pixel-only attribution
30–50%	Functional but underperforming — likely missing match keys	Moderate improvement; room for optimization
50–70% (US typical)	Healthy setup with visible Smart Bidding accuracy gains	Strong signal recovery; documented 17.8% CPA reduction
Above 70%	Excellent — capturing most available match opportunities	Maximum attribution recovery from first-party data

US accounts typically land in the 55-70% range. EU-heavy audiences sit lower because fewer users pass the consent gate — a compounding effect where privacy regulation reduces both the volume of consented data and the pool of signed-in users available for matching. Google Ads conversion rates fell 9.28% year-over-year across 13 of 14 industries in 2026, making every recovered conversion signal disproportionately valuable.

To find your match rate in Google Ads, navigate to Goals → Conversions and look for the Enhanced Conversions Match Rate column. If it isn’t visible, use the column selector to add it. If the column shows no data, your Enhanced Conversions isn’t sending usable information — regardless of what the toggle says.

The unified merge doesn’t change the underlying matching mechanics. It does remove the visual separation between web and leads implementations, making it harder to diagnose where a match rate problem originates. Before the merge, you could isolate whether the web tag or the leads upload was the source of low match rates. Now it’s one blended number.

The Data Manager API Migration Nobody Saw Coming

While everyone was focused on the toggle merge, Google quietly blocked offline conversion imports via the Ads API and forced migration to an entirely new endpoint.

Starting June 15, 2026, the Google Ads API blocked new offline conversion imports and Enhanced Conversions for Leads uploads. Developer tokens that hadn’t sent a request between January and June 2026 were not allowlisted for legacy access. The replacement infrastructure is the Data Manager API — a unified endpoint for ingesting offline conversions, Enhanced Conversions for Leads, Customer Match, and GA4 events.

This isn’t an incremental version bump. The Data Manager API represents a fundamentally different ingestion architecture. Version 1.0 supported only audience data. Version 1.1 added offline conversion event ingestion. Version 1.2 extended that to Enhanced Conversions for Leads. By May 2026, version 1.6 added store sales measurement, and version 1.7 extended offline conversion events to Campaign Manager 360, Search Ads 360, and Display & Video 360.

For WooCommerce stores that only use web-based Enhanced Conversions via tags, this specific API migration doesn’t apply directly. But for any store that imports offline sales data, uploads CRM conversions, or uses Enhanced Conversions for Leads — the June 15 cutoff was a hard deadline. Running in parallel: Google Ads API v21 sunsets on August 5, 2026, meaning all v21 API requests will begin to fail. The recommended migration target is v23 or v24, since v22 sunsets in October 2026.

The compounding effect is the real story. The toggle merge, the API migration, and the v21 sunset all landed within weeks of each other — each affecting a different part of the same attribution pipeline.

You may be interested in: Your Smart Bidding Is Training on Biased Data — Safari Made Sure of It

The Server-Side Fix That Bypasses the Entire Problem

Data layer timing failures exist because Enhanced Conversions was designed for browser-side capture. Server-side tracking eliminates the timing problem entirely.

The fundamental issue with GTM-based Enhanced Conversions on WooCommerce is architectural: customer data lives in PHP (the server) while the conversion tag fires in JavaScript (the browser). Bridging that gap requires the GTM4WP plugin to push data to a JavaScript data layer at exactly the right moment, in exactly the right format, before exactly the right tag fires. Three systems — WooCommerce, GTM4WP, and Google Tag Manager — need to coordinate in real time. When any one of them slips, the data arrives late or corrupted.

Server-side tracking eliminates this coordination problem by capturing the conversion event at the HTTP request layer, where WooCommerce processes the order. At the server level, customer data — email, phone, name, address — is guaranteed to exist because WooCommerce just used it to process the payment. There’s no timing window to miss. There’s no data layer to populate. There’s no browser dependency to break.

The server captures the customer data, applies SHA256 hashing automatically, formats it to Google’s specifications, and sends the Enhanced Conversion payload via API. The entire GTM data layer timing problem — the root cause of the 67% failure rate — simply doesn’t exist in a server-side architecture.

Brands using server-side tracking architectures in 2026 report a 12 to 15% lower CPA, with conversion recovery typically in the 20 to 40% range. The match rate advantage is structural: server-side capture sends all available customer fields with every conversion, while browser-side capture sends whatever the data layer happened to contain at the moment the tag fired — which might be everything, or might be nothing.

Post-Merge Audit Checklist for WooCommerce

Seven verification points to confirm your Enhanced Conversions actually works after the June 2026 merge — not just appears to work.

First, check customer data terms acceptance. In Google Ads, navigate to Settings → Customer data terms. If the status isn’t “Accepted,” Enhanced Conversions has never functioned on your account regardless of tag configuration. Accept the terms and allow 48-72 hours for diagnostics to populate.

Second, verify the unified toggle is on at the right level. Enhanced Conversions can be enabled at the account level or per conversion action. After the merge, check both. An account-level toggle set to “off” overrides conversion-action-level settings.

Third, check your match rate. In Goals → Conversions, add the Enhanced Conversions Match Rate column. If it shows below 30%, you have a data quality problem. If it shows no data, your setup isn’t sending usable information. If it shows above 50%, your implementation is healthy.

Fourth, test data layer timing. Open Google Tag Manager’s preview mode. Navigate to your WooCommerce checkout and complete a test purchase. In the Tag Assistant, check whether the user_data variables are populated before the Google Ads conversion tag fires. If the variables show “undefined” at the moment the conversion tag enters the timeline, you have the timing problem that accounts for most of the 67% failure rate.

Fifth, confirm all four Consent Mode parameters. Enhanced Conversions requires ad_user_data to be granted. If your CMP only transmits ad_storage and analytics_storage from a v1 configuration, the Enhanced Conversions data gets silently blocked even when the conversion tag fires correctly.

Sixth, verify you’re not double-hashing. Some WooCommerce plugins pre-hash email addresses before passing them to the data layer. GTM then hashes them again per Google’s requirements. Double-hashed data never matches. Check whether your plugin’s output is a raw email or an SHA256 hash, and configure GTM accordingly.

Seventh, assess your Data Manager API exposure. If you import offline conversions or use Enhanced Conversions for Leads, verify your integration has migrated from the Google Ads API to the Data Manager API. The June 15 cutoff has already passed — if your pipeline is still targeting the legacy endpoint, it’s failing silently.

Key Takeaways

• The merge carried broken setups forward: 67% of WooCommerce Enhanced Conversions implementations fail audit due to data layer timing issues — the June 2026 merge auto-migrated all of them into the unified toggle without fixing anything.
• Customer data terms are the hidden prerequisite: Google’s auto-migration only applies to accounts that previously accepted customer data terms — most plugin-based WooCommerce setups never completed this manual step in Google Ads settings.
• Match rate is the diagnostic that matters: Above 50% means visible Smart Bidding improvement. Below 30% means a setup problem. No data means Enhanced Conversions isn’t functioning at all, regardless of the toggle state.
• The Data Manager API migration is a separate deadline: Offline conversion imports and Enhanced Conversions for Leads uploads moved to the Data Manager API from June 15, 2026 — and Google Ads API v21 sunsets August 5, 2026.
• Server-side tracking eliminates the root cause: The 67% failure rate stems from browser-side data layer timing. Server-side capture hooks into WooCommerce order processing where customer data is guaranteed to exist, bypassing the GTM coordination problem entirely.

References

• Google Ads Help. “Updates to your enhanced conversions settings.” 2026. support.google.com
• PPC Land. “Google Ads finally collapses enhanced conversions into a single toggle.” April 2026. ppc.land
• TAGGRS. “Google Enhanced Conversions 2026 update: most agencies still haven’t checked if theirs works.” July 2026. taggrs.io
• Search Engine Land. “Google Ads simplifies enhanced conversions into a single switch.” April 2026. searchengineland.com
• DataCops. “Enhanced Conversions in Google Ads: The Complete Implementation Guide.” June 2026. joindatacops.com
• Campaigns You Love. “Set Up Enhanced Conversions in 2026: Google Ads + GTM.” July 2026. campaignsyoulove.com
• Google Ads Developer Blog. “Google Ads API v21 sunset reminder.” June 2026. ads-developers.googleblog.com
• Foundry CRO. “Google Ads CPC, CTR & Conversion Rate Benchmarks 2026.” May 2026. foundrycro.com
• Search Engine Land. “Google is moving offline conversion imports out of the Google Ads API.” May 2026. searchengineland.com

Server-side conversion capture eliminates the browser timing gap that breaks Enhanced Conversions for most WooCommerce stores. Transmute Engine™ hooks into WooCommerce order processing, hashes customer data at the server, and routes Enhanced Conversion payloads to Google Ads with every purchase — automatically. Talk to Seresa about fixing your match rate.