Google’s Enhanced Conversions Merge: What WooCommerce Stores 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 need to choose between the two and accepting user-provided data from website tags, Data Manager, and API simultaneously (PPC Land, 2026). Before the merger, advertisers had to pick one path — web or leads — and configure it separately. Now it’s one switch.

The simplification sounds like good news, but the migration wasn’t seamless. Stores that had Enhanced Conversions for Leads configured through the Google Ads API found their upload path deprecated. Stores running the web variant through GTM may have had their configuration silently carried over — or silently broken, depending on whether the tag setup survived the transition.

Google merged Enhanced Conversions for Web and Leads into a single toggle in June 2026, eliminating the legacy distinction (PPC Land, 2026).

Was the Google Ads API for enhanced conversions deprecated?#

Yes — from June 15, 2026, legacy Google Ads API uploads for offline conversions and Enhanced Conversions for Leads are blocked (PPC Land, 2026). Existing setups using the API must migrate to the Data Manager API or website tags. The Data Manager API is the replacement path, but it requires a different authentication flow and payload structure.

For WooCommerce stores that were pushing conversion data through the old API — typically via a custom integration or a third-party plugin — this is the highest-priority check. If your conversions were flowing through that endpoint, they stopped on June 15. The Google Ads interface won’t necessarily flag the failure; the conversion action still exists, it just stops receiving data.

Related: Your Google Ads Enhanced Conversions Have Been Quietly Failing Since April

How do you check if Enhanced Conversions still work after the merger?#

Check the diagnostics report in Google Ads — “Recording enhanced conversions” means it works, while “Waiting to receive enhanced conversion data” may reflect the diagnostics status lag of up to 48 hours (TAGGRS, 2026) or a genuine failure. Here’s the thing — the lag means you can’t trust a positive status either. A setup that broke yesterday might still show green today.

The more reliable check is GTM Preview mode. Fire a test conversion and inspect the tag output: look for the user_data object in the Google Ads Conversion Tracking tag. If the email or phone fields are empty, hashed incorrectly, or missing entirely, the diagnostics report will eventually catch up — but you’ll have lost 48 hours of conversion data before it does.

Enhanced Conversions diagnostics show a status lag of up to 48 hours, masking real failures (TAGGRS, 2026).

Why do Enhanced Conversions silently fail?#

A setup can look active in Google Ads while sending empty or malformed user data — common causes include CSS selectors that broke after a site redesign, JavaScript errors that corrupt data before hashing, and double-hashed email addresses that produce an invalid SHA-256 output. Google’s tag accepts the payload regardless; it only flags the failure in diagnostics days later.

The most common WooCommerce failure is a CSS selector mismatch. Enhanced Conversions for Web relies on CSS selectors to pull email addresses from the confirmation page. When a theme update changes the markup, the selector grabs nothing — or worse, grabs the wrong element. The tag fires successfully, Google records the conversion, but the user data attached to it is blank. Your bidding algorithm learns from half the picture.

Do you need to accept Google’s customer data terms for Enhanced Conversions?#

Yes — accounts that never accepted Google’s Data Processing Terms may show Enhanced Conversions as available but inactive, and the automatic migration didn’t always carry the terms acceptance forward. If you set up your Google Ads account before the GDPR-era terms update, this step may be silently missing.

Check it under Google Ads > Admin > Data Processing Terms. If the terms aren’t accepted, Enhanced Conversions won’t process user data regardless of your tag configuration. The conversion tracking still fires — you’ll still see conversion counts — but the enhanced matching that ties conversions to specific ad clicks won’t work. Translation: you’re paying for Smart Bidding that can’t see who actually converted.

Related: What are Google Enhanced Conversions for WooCommerce?

Does ad_user_data consent affect Enhanced Conversions?#

Yes — Enhanced Conversions require ad_user_data consent through Consent Mode V2, not just ad_storage consent. Many implementations only wire up ad_storage, which blocks user data transmission entirely while the conversion tag still fires normally. The result is a conversion count with no enhanced matching data behind it.

The question isn’t whether your consent banner works. The question is whether it sends the right signals. Consent Mode V2 introduced separate consent types: ad_storage controls cookies, ad_user_data controls whether first-party data (email, phone) can be sent to Google, and ad_personalization controls remarketing. Enhanced Conversions specifically need ad_user_data granted. Without it, Google drops the user data from the conversion payload silently.

How does server-side GTM improve Enhanced Conversions reliability?#

Server-side GTM removes several browser-dependent failure points — ad blockers that prevent the tag from loading, CSS selectors that break after redesigns, and JavaScript errors that corrupt user data before hashing. With server-side, the user data is extracted on the server where the environment is controlled and predictable.

A managed server-side tracking tool like Transmute Engine takes this further by handling the hashing, consent signal forwarding, and data formatting as a first-party endpoint. The Enhanced Conversions data flows from WooCommerce’s order object directly to Google — no CSS selectors, no browser JavaScript, no opportunity for a theme update to break the chain. For stores that have been chasing silent failures across GTM tags and consent banners, server-side eliminates the entire failure category.

What should WooCommerce stores do about the Enhanced Conversions changes?#

Verify the diagnostics report shows “Recording enhanced conversions,” check GTM Preview for populated user_data values, confirm ad_user_data consent is wired correctly in Consent Mode V2, and accept Google’s Data Processing Terms if you haven’t. These four checks cover the most common post-merger failure modes (Google Ads Help, 2026).

If you were using the legacy Google Ads API for offline conversions, migrate to the Data Manager API immediately — that endpoint stopped accepting data on June 15. If you’re running client-side Enhanced Conversions through GTM, open Preview mode and trigger a test purchase: if the user_data object is empty, your Smart Bidding has been flying blind since the merger. Let that sink in. Every day without working Enhanced Conversions is a day your bidding algorithm makes decisions on incomplete data.

Key Takeaways#

• The merger isn’t cosmetic: Google combined two separate Enhanced Conversions paths into one toggle and deprecated the legacy API upload on June 15, 2026.
• Diagnostics lag by 48 hours: a green status today doesn’t mean your data was flowing yesterday — verify with GTM Preview, not the diagnostics report.
• Consent Mode V2 is non-negotiable: Enhanced Conversions need ad_user_data consent specifically, not just ad_storage.
• Server-side removes the failure class: CSS selectors, ad blockers, and JavaScript errors can’t break what runs on your server.

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. Google Developers (2026). Enhanced Conversions Documentation. Source
4. Google Ads Help (2026). About Enhanced Conversions. Source