Google Ads Merges Enhanced Conversions Into One Switch in June 2026

What Already Changed in April 2026

The multi-source data acceptance phase went live before most advertisers noticed it.

Starting in April 2026, Google Ads began accepting user-provided hashed data from website tags, Data Manager, and API connections simultaneously. That single change removed the old constraint that forced advertisers to pick one implementation method per conversion action. If you had a Google Tag sending purchase hashes and a GTM container sending the same data, you previously had to choose. Now both feed the same endpoint.

For most single-channel WooCommerce stores — those tracking only online purchases — April’s change was invisible. The tag kept firing. Conversions kept counting. Nothing broke because nothing overlapped.

The stores that felt the shift were the ones running both purchase tracking on the site and a CRM-side lead import pipeline. Those stores had two separate enhanced conversion configurations, each with its own method selection, each routing different hashed data to different Google endpoints. April 2026 opened the door for both streams to arrive at the same place — but without any built-in deduplication between them.

You may be interested in: Google Ads API Blocks New Offline Conversion Imports June 15

What Happens in June 2026

Two products become one toggle — and the interface simplifies whether you’re ready or not.

Enhanced conversions for web and enhanced conversions for leads merge into a single feature with one on/off switch. The separate product identities disappear from the Google Ads interface. You no longer see different method selections, different configuration panels, or different status indicators for web versus lead conversions.

Google has stated that existing users require no action. Accounts with enhanced conversions already active will be migrated automatically. The customer data terms you previously agreed to carry forward. If you haven’t set up enhanced conversions at all, you can enable the unified version at the account level or the conversion action level.

The structural split between two products has existed since Google launched enhanced conversions for leads in 2022. Web handled on-site purchase completions. Leads handled offline outcomes imported through CRM data. Four years of separate configurations, separate documentation, and separate troubleshooting guides collapse into one setting in June 2026.

Google Ads merges enhanced conversions for web and leads into a single on/off toggle in June 2026, removing the method selector that separated purchase tracking from CRM lead imports.

The June 15 API Deadline Is a Separate Cut

The toggle merge and the API cutoff land on the same month but serve different purposes.

Starting June 15, 2026, the Google Ads API blocks new adopters of offline conversion imports entirely. The UploadClickConversions endpoint will reject requests from developer tokens that haven’t sent a request between January 2026 and June 2026. If your token hasn’t been active in that window, you don’t get allowlisted for legacy access.

This isn’t a soft deprecation. Developer tokens that miss the activity window face an error on every subsequent upload attempt. Google has directed all new offline conversion import workflows — including enhanced conversions for leads — to the Data Manager API.

The Data Manager API has been expanding fast. Version 1.0 supported only audience data. Version 1.1 added offline conversion events. Version 1.2 extended to enhanced conversions for leads. Version 1.6, released in May 2026, added store sales measurement and expanded Analytics event support. Google isn’t just migrating a feature — it’s consolidating the entire data ingestion surface into a single API that handles audiences, conversions, and store sales through one endpoint structure.

For WooCommerce stores running custom lead import scripts against the Google Ads API, the migration isn’t optional. Either your import pipeline moves to Data Manager before June 15, or your CRM-to-Google data flow stops.

The WooCommerce Dual-Flow Problem

Most WooCommerce stores don’t realise they’re running two enhanced conversion configurations — until one of them breaks.

A typical mid-market WooCommerce store running Google Ads often has two distinct conversion pathways. The first is a tracking plugin or Google Tag that fires on the thank-you page, capturing purchase events with hashed customer email and sending them as enhanced conversions for web. The second is a CRM integration — sometimes through HubSpot, sometimes through a custom script — that imports qualified leads with the same hashed email as enhanced conversions for leads.

Under the current system, these two pathways have separate method selectors, separate configuration panels, and effectively operate as independent data channels into Google Ads. That separation was messy, but it was also a form of guardrail. Each path knew what it was sending and where it was going.

WooCommerce stores running dual conversion flows — online purchases plus CRM-side lead imports — risk sending overlapping hashed data signals when both paths feed the unified toggle without deduplication.

When the unified toggle replaces both configurations, the guardrail disappears. Both streams feed the same feature. If both send a hashed email for the same customer interaction — one from the purchase event, one from the CRM lead status update — Google Ads receives two signals for what may be a single customer journey. The question is whether Smart Bidding interprets that as two conversions or one.

Why the Method Selector Disappearing Matters

The selector wasn’t just a UI choice — it was the only visibility advertisers had into which data path was active.

The method selector in Google Ads served a purpose beyond configuration. It told you, at a glance, whether your enhanced conversions were coming from a tag on the page, a GTM container, or an API call. If something broke — conversions dropped, match rates fell, Smart Bidding started behaving strangely — the method selector was the first thing you checked.

In June 2026, that diagnostic reference point vanishes. The unified toggle accepts data from all sources simultaneously. If your conversion count suddenly doubles or your cost-per-acquisition spikes, there’s no method selector to tell you which pipeline is the culprit.

This is where the change stops being administrative and starts being operational. WooCommerce stores with a single, clean purchase-only tracking setup won’t notice. Stores with a multi-touch conversion architecture — purchase events from the tag, lead status updates from the CRM, maybe a Data Manager connection feeding a third signal — lose the one interface element that made the data flow legible.

You may be interested in: Google Signals Loses Ad Authority June 15: Remarketing Lists Shrink

Deduplication Risk Under the Unified Toggle

Google’s documentation says no action required — but that assumes your data paths don’t overlap.

Here’s the thing: Google’s migration guidance assumes a clean separation between web conversions and lead conversions. Purchase events come from the tag. Lead events come from the CRM. Different conversion actions, different customer stages, no overlap.

That assumption doesn’t hold for many WooCommerce stores. A store selling B2B industrial equipment might track the initial enquiry form submission as a lead, then track the eventual purchase as a web conversion. If the customer’s email hash appears in both events, both data streams carry the same first-party identifier to the same unified toggle.

Without explicit deduplication — matching on email hash plus conversion action plus timestamp — the unified system may attribute the same customer journey twice. One attribution from the tag-side purchase. One from the CRM-side lead status update. Smart Bidding receives two positive signals and doubles down on that acquisition channel, inflating bids on a conversion path that actually happened once.

The risk scales with complexity. Stores running a single WooCommerce purchase tag have no overlap to worry about. Stores running purchase tracking plus a HubSpot CRM import plus a Data Manager feed are running three potential sources of the same hashed identifier into one toggle. Every additional data source is another deduplication surface that Google’s migration doesn’t audit for you.

Pre-Merge Audit Checklist for WooCommerce

Five checks to run before the June 2026 toggle switch completes its migration.

First, map every data path that sends hashed customer data to Google Ads. Check your WooCommerce tracking plugin configuration, your GTM container, your CRM integrations, and any direct API scripts. List the conversion actions each path feeds. If two paths feed the same conversion action with the same hashed email, you have an overlap.

Second, verify your Google Ads API token activity. If you import offline conversions through a custom script, confirm that your developer token has been active between January and June 2026. Tokens that haven’t imported during that window won’t be allowlisted after June 15. If you’re inactive, start your Data Manager API migration now.

Third, check your conversion action structure. The unified toggle works best when web conversions and lead conversions are distinct conversion actions with distinct customer journey stages. If your WooCommerce store uses a single “purchase” conversion action that receives data from both the tag and a CRM import, rethink the structure before the merge.

Fourth, audit your hashed identifier consistency. Enhanced conversions match on hashed email, phone, or address. If your WooCommerce checkout captures email in one format and your CRM normalises it differently before hashing, the same customer generates two different hashes. Under the current split system, this mismatch stays isolated. Under the unified toggle, it can create phantom conversions where Google sees two different users who are actually one.

Fifth, test your conversion count against your actual sales data. Pull your Google Ads conversion count for the last 30 days. Compare it against your WooCommerce order count for the same period. If Google Ads shows more conversions than WooCommerce shows orders, you already have an overlap — and the unified toggle hasn’t even arrived yet.

The Server-Side First-Party Answer

A first-party pipeline doesn’t care whether Google runs one toggle or ten — it controls what data leaves your server.

The architectural answer to the deduplication problem isn’t in Google Ads settings — it’s in controlling the data before it reaches Google. A server-side first-party pipeline captures every WooCommerce event at the source, hashes identifiers once using a canonical format, deduplicates against event IDs, and fans out to Google Ads (and every other platform) with deterministic control over what each destination receives.

Under this architecture, the unified toggle becomes irrelevant. Whether Google accepts data from tags, Data Manager, and API simultaneously doesn’t matter when your pipeline is the sole source of truth. One event, one hash, one transmission per destination. No overlap between browser-side tags and CRM-side imports because both originate from the same server-side event stream.

Transmute Engine™ implements exactly this pattern for WooCommerce stores. Every purchase, lead submission, and CRM status change flows through a single server-side pipeline that normalises, hashes, deduplicates, and routes to Google Ads, Meta, TikTok, and BigQuery through first-party endpoints. When the method selector disappears in June 2026, stores running a first-party pipeline don’t need to audit for overlapping signals — because the pipeline already eliminated them at the source.

Key Takeaways

• Toggle merge is June 2026: Enhanced conversions for web and leads become one on/off switch, removing the method selector from the Google Ads interface.
• API cutoff is June 15 2026: New adopters of offline conversion imports through the Google Ads API are blocked; migration to Data Manager API is required.
• Dual-flow stores face deduplication risk: WooCommerce stores running both purchase tracking and CRM lead imports may send overlapping hashed signals to the unified toggle.
• Audit before the merge: Map every data path, verify API token activity, check conversion action structure, validate hashed identifier consistency, and compare conversion counts against actual sales.
• Server-side pipelines neutralise the risk: A first-party pipeline controls what data leaves your server, making the toggle merge operationally invisible.

References

• Updates to your enhanced conversions settings — Google Ads Help Center (2026)
• Changes to Offline Click Conversion Import Support — Google Ads Developer Blog (May 2026)
• About offline conversion imports — Google Ads Help Center (2026)
• Google Ads finally collapses enhanced conversions into a single toggle — PPC.land (April 2026)
• Google Ads Enhanced Conversions Single Switch — ALM Corp (April 2026)
• Google blocks new offline conversion imports via Ads API from June 15 — PPC.land (May 2026)
• About enhanced conversions for leads — Google Ads Help Center (2026)

If your WooCommerce store runs multiple conversion paths into Google Ads, a first-party server-side pipeline eliminates the deduplication risk before it reaches the platform. See how Seresa’s Transmute Engine works →