Google’s Enhanced Conversions Merge: What WooCommerce Advertisers Must Check Now

What changed with Google Enhanced Conversions in June 2026?#

Google merged Enhanced Conversions for Web and Enhanced Conversions for Leads into a single on/off toggle, eliminating the forced method selection and allowing Google Ads to accept user-provided data from website tags, Data Manager, and API connections simultaneously (PPC Land, 2026). Before June 2026, advertisers had to choose one method — now all three can feed data into the same conversion action.

The practical effect is simpler on paper. Instead of navigating separate configuration panels for web-based enhanced conversions and lead-based enhanced conversions, you get one toggle that accepts whatever data sources you’ve connected. Google’s system figures out which data came from where and matches accordingly.

The problem is what happened during the transition. WooCommerce stores that had carefully configured their Enhanced Conversions setup — choosing specific CSS selectors for checkout fields, routing hashed email through a particular method — found their configurations silently migrated. The toggle flipped on, the diagnostics showed “active,” and nobody noticed that the underlying data pipeline had changed shape. For stores relying on plugin-based implementations, the merge exposed a gap between what the interface reports and what the system actually sends.

What is the Data Manager API migration deadline?#

As of June 15 2026, offline conversion imports and Enhanced Conversions for Leads uploads are blocked in the Google Ads API (PPC Land, 2026) and must use the new Data Manager API instead. This isn’t a soft deprecation — legacy API calls now return errors.

The Data Manager API comes with specific rate limits: 100,000 requests per day, 300 per minute per Cloud project, 2,000 events per request, and 10 identifiers per record (PPC Land, 2026). For most WooCommerce stores processing under 50,000 orders per month, these limits are generous. But if you’re running a high-volume store with multiple conversion actions, the 300-per-minute cap could become a throttle during peak checkout periods.

The migration timeline started earlier than most advertisers realised. Customer Match uploads via the Google Ads API stopped working on April 1 2026 (PPC Land, 2026) — two months before the Enhanced Conversions deadline. If your audience lists went stale in April and nobody flagged it, that’s the same silent-failure pattern playing out on a different surface.

The Data Manager API migration deadline was June 15 2026, blocking legacy Google Ads API uploads for offline conversions and Enhanced Conversions for Leads (PPC Land, 2026).

Related: Google Ads Collapses Enhanced Conversions Into One Toggle in June 2026 — What WooCommerce Stores Should Audit Before Auto-Migration

Can Enhanced Conversions fail silently on WooCommerce?#

Yes — Enhanced Conversions can show as active while sending empty, double-hashed, or missing user data with no visible error in Google Ads (TAGGRS, 2026), meaning conversions still record but the enhanced matching that improves attribution quietly stops working. This is the most dangerous failure mode because there’s nothing in the interface that tells you it’s happening.

Here’s what silent failure looks like in practice. Your WooCommerce checkout fires the conversion tag. Google Ads logs the conversion. The Enhanced Conversions diagnostics page shows “active.” But the user_data object attached to that conversion is either empty (no email, no phone, no address) or contains a double-hashed value that Google can’t match against. Your conversion count stays accurate — your match rate drops to near zero, and your Smart Bidding algorithms lose the signal they need to optimise.

The root cause on WooCommerce is usually one of three things: a theme update changed the CSS selectors that the conversion tag uses to scrape checkout fields, a caching plugin is serving a stale version of the tracking script, or a security plugin is stripping the user_data parameters from outbound requests. None of these trigger an error in Google Ads because the conversion itself isn’t failing — only the enhanced data payload is.

How do I verify Enhanced Conversions are sending data after the merge?#

Check GTM Preview for the user_data object containing hashed values rather than an empty object, verify the em parameter in network requests, and note that the diagnostics report may lag up to 48 hours after changes (TAGGRS, 2026). That lag means you can’t trust the diagnostics page for real-time verification — you need to inspect the actual data leaving your site.

The verification steps, in order. First, open GTM Preview mode and trigger a test conversion on your WooCommerce checkout. In the tag details, expand the user_data object. You should see hashed values for email (em), phone (ph), and address fields — not an empty object, not “undefined,” and not a value that looks like a hash of a hash (64+ characters of hex). Second, open Chrome DevTools, filter network requests for “google,” and inspect the payload of the conversion request. The em parameter should contain a single SHA-256 hash of the email address.

If your user_data is empty or the em parameter is missing, your Enhanced Conversions are recording conversions without enhanced data. Google’s diagnostics might still show “active” for up to 48 hours, which is why the manual inspection matters more than the dashboard.

Related: Why does Google Ads Enhanced Conversions fail for most WooCommerce stores?

Browser-Side vs Server-Side Enhanced Conversions: Failure Mode Comparison

Failure Mode	Browser-Side (gtag / GTM Web)	Server-Side (sGTM / Managed Pipeline)
Ad blocker interception	Tag blocked — no conversion or enhanced data sent	Bypassed — data sent from server, not browser
CSS selector breakage after WooCommerce update	Empty user_data — silent failure, no error	Not applicable — reads order object, not DOM
Double-hashing	Common when plugins pre-hash before GTM	Controlled — single hash applied server-side
Consent rejection (GDPR banners)	Tag suppressed — conversion lost entirely	Server fires with consent-safe first-party data
Safari ITP / cookie truncation	Attribution window shortened to 1-7 days	First-party cookie set server-side, full window
Diagnostics accuracy	Up to 48-hour lag, no empty-data warning	Server logs show exact payload in real time

How much data does server-side tracking recover for Google Ads?#

Server-side tracking typically recovers 5-15% more attributed conversions in Google Ads after a clean implementation (Dataslayer, 2026), with the recovery coming from visitors whose browser-based tracking was blocked by ad blockers or consent rejection. That’s not a vanity metric — it’s conversions that Google’s bidding algorithms currently can’t see.

The recovery range depends on your audience profile. Stores with heavy European traffic see the upper end because GDPR consent rejection blocks client-side tags outright. Stores with younger, more tech-savvy demographics see higher ad-blocker rates. And stores with significant Safari traffic lose additional signal to ITP cookie truncation, though that’s a separate mechanism from Enhanced Conversions specifically.

What matters for the Enhanced Conversions context is this: server-side tracking doesn’t just recover blocked conversions — it sends the hashed user data from a server environment where ad blockers, consent banners, and browser privacy restrictions can’t intercept it. The user_data object arrives at Google’s endpoint intact because it never passed through the browser in the first place.

What causes double-hashing in Enhanced Conversions?#

Double-hashing occurs when a WooCommerce site pre-hashes email addresses before passing them to GTM, and then GTM or gtag.js hashes them again (TAGGRS, 2026) — producing a hash-of-a-hash that Google can’t match against any user record. The fix is to send raw values and let Google’s tags handle the single hash.

This is more common than it should be, and it happens two ways. First, a developer reads Google’s documentation about “sending hashed data for privacy” and SHA-256 hashes the email in PHP before pushing it to the data layer — not realising that GTM’s Enhanced Conversions tag automatically hashes whatever it receives. Second, a WooCommerce tracking plugin normalises and hashes the email before GTM touches it, and the plugin’s documentation doesn’t mention that GTM will hash again.

Double-hashed data produces zero match rate while appearing active in diagnostics (TAGGRS, 2026). That’s the worst outcome: you’ve done everything right from a configuration standpoint, the diagnostics say you’re live, and your match rate is effectively zero because Google is trying to look up a hash that doesn’t correspond to any user in its identity graph. The telltale sign is a user_data value that’s significantly longer than a standard SHA-256 hash — or, more reliably, hashing a known test email yourself and comparing it to what leaves your site.

Does server-side GTM fix Enhanced Conversions browser failures?#

Server-side GTM eliminates browser-dependent failure modes including ad blocker interception, CSS selector breakage after WooCommerce updates, and double-hashing (SignalBridge, 2026), but it doesn’t fix misconfigured data fields in the tag setup itself. It solves the transport problem, not the configuration problem.

The browser-side fragility of Enhanced Conversions on WooCommerce is structural. WooCommerce releases 6-8 updates per year (SignalBridge, 2026), each potentially changing checkout field markup. A CSS selector that scraped the billing email from #billing_email in WooCommerce 8.x might find that element renamed, wrapped in a new container, or rendered by a different block in WooCommerce 9.x. Server-side tracking sidesteps this entirely by reading the order data from WooCommerce’s PHP layer — the same data that the store uses to process the order — and sending it to Google’s endpoint without touching the browser DOM.

WordPress-native server-side solutions like Transmute Engine take this a step further by routing hashed first-party data directly to Google’s endpoints from a managed first-party server. The checkout field markup can change with every WooCommerce update and it doesn’t matter — the data comes from the order object, not from scraping HTML.

Enhanced Conversions can show as active while sending empty or double-hashed data with no visible error — server-side tracking eliminates this failure mode (TAGGRS, 2026).

Do I need to accept Google’s customer data terms for the unified toggle?#

Yes — accounts that previously accepted Google’s Data Processing Terms were automatically migrated (PPC Land, 2026), but older accounts where a previous team may not have accepted the terms may show Enhanced Conversions as available but inactive. It’s a one-click fix, but only if you know to look for it.

The terms acceptance is buried in Google Ads under Settings → Customer Data Terms. If your account was created before 2023 or has changed hands, there’s a reasonable chance the terms were never explicitly accepted — the old Enhanced Conversions setup flow prompted for acceptance, but the unified toggle migration assumed it was already done. If it wasn’t, Enhanced Conversions appears in your interface but won’t actually process any enhanced data.

Check this before debugging anything else. An unaccepted terms agreement produces identical symptoms to a double-hashing problem or a broken CSS selector — conversions record normally, enhanced data doesn’t match, and the diagnostics page doesn’t flag the root cause. It takes 30 seconds to verify and rules out the simplest explanation first.

Key Takeaways#

• Google’s June 2026 merge replaced separate toggles with one unified switch: all data sources (website tags, Data Manager, API) now feed into the same conversion action simultaneously.
• Silent failures are the real risk: Enhanced Conversions can show “active” while sending empty or double-hashed data, with diagnostics lagging up to 48 hours behind reality.
• Verify manually, don’t trust the dashboard: inspect the user_data object in GTM Preview and the em parameter in network requests to confirm actual data delivery.
• Double-hashing produces zero match rate: send raw values to GTM and let Google’s tags handle the single SHA-256 hash.
• Server-side tracking eliminates browser-side breakage: reading order data from WooCommerce’s PHP layer bypasses CSS selector fragility, ad blockers, and consent interception.

References#

1. PPC Land (2026). Google Kills 3 Enhanced Conversion Methods, Replaces All with Single Toggle. Source
2. TAGGRS (2026). Google Enhanced Conversions 2026 Update. Source
3. Dataslayer (2026). Server-Side Tracking in 2026: Cost, Setup, and ROI. Source
4. SignalBridge (2026). Best Server-Side Tracking Solutions for WordPress. Source
5. Google Ads Help (2026). Enhanced Conversions Setup. Source