Google confirmed on April 10 2026 that Enhanced Conversions for Web and Enhanced Conversions for Leads will merge into a single on/off toggle in June 2026. The official line is no action required. That’s only true if your current setup is already correct. 67% of first-implementation Enhanced Conversions setups on WooCommerce fail audit (Seresa analysis, 2026) — which means a majority of auto-migrated accounts are about to carry broken attribution into the unified system without noticing. Here’s what to audit on your WooCommerce store in the next 60 days, before Google migrates you.
What WooCommerce Stores Should Audit Before Auto-Migration
The change itself is narrow and specific. Two features collapse into one. Method selection — tag, Data Manager, or API — disappears from the Google Ads interface. From April 2026, Google accepts user-provided data through all three channels in parallel rather than asking you to pick one. The unified toggle simply turns the whole capability on or off.
If that sounds like housekeeping, it is — for accounts that built Enhanced Conversions correctly the first time. For WooCommerce stores running a plugin-based setup nobody has audited since install, the word automatic is doing a lot of work.
What’s actually changing in June 2026
Three things are moving at once, and they’re connected.
The toggle itself. Google’s own help documentation confirms that starting June 2026, Enhanced Conversions for Web and Enhanced Conversions for Leads combine into a single feature with one on/off switch. The previous interface, where you chose between website tags, Data Manager, or an API connection, is being replaced by a simpler status view.
Multi-source ingestion from April 2026. The underlying data intake changed two months before the interface catches up. Search Engine Land reports that from April 2026, advertisers can send user-provided data via website tags, Data Manager, and API connections simultaneously. Before this, the recommended pattern was to pick one method and stick with it. Now parallel sending is the default posture.
Data Manager as the strategic destination. The Data Manager API launched December 9 2025, and in January 2026 Google began restricting session attributes and IP address imports through the older Google Ads API. The toggle unification is the visible part of a larger shift — one ingestion point for first-party data across Google Ads, GA4, and DV360.
Translation: Google is simplifying the front end while consolidating the plumbing. One toggle for advertisers, one API for data, one expectation that you’re sending user-provided data from somewhere server-side.
Why “no action required” is a warning, not a reassurance
Google’s documentation states that existing users will be “automatically migrated to the new unified status” — but only if they have previously agreed to Google’s customer data terms. That conditional is the whole story.
Auto-migration assumes your starting point is clean. For WooCommerce plugin-based setups, that assumption frequently breaks.
Consider the install pattern most stores follow. A store owner installs a Google Ads tracking plugin. The plugin handles tag firing on the thank-you page. Enhanced Conversions ships enabled by default. The store owner never opens Google Ads to review account-level settings because the plugin handles it — except the plugin cannot accept the customer data terms on behalf of the account. That step lives inside the Google Ads interface and has to be confirmed by someone with admin access.
The result: thousands of WooCommerce stores have Enhanced Conversions firing tags that Google is silently ignoring because the account-level terms were never accepted. June 2026 auto-migration will skip those accounts entirely. The toggle will appear disabled, conversion volume will drop, and the store owner will have no idea why.
You may be interested in: Google Ads Enhanced Conversions: Why 67% of WooCommerce Setups Fail
The four-item pre-flight audit for WooCommerce stores
Sixty days is enough time to walk through each of these carefully. Doing them in order matters — item two depends on item one, and item four depends on item three.
1. Customer data terms — accepted at the account level
This is the gate. Without it, auto-migration doesn’t happen, and your unified Enhanced Conversions toggle will come online disabled.
In Google Ads, open Tools → Setup → Preferences → Account-level settings. Confirm that the customer data terms show as accepted. If you see a pending acceptance or an empty state, click through and agree before June. This step cannot be automated by a WooCommerce plugin.
2. Current Enhanced Conversions implementation method — documented
Before Google collapses the interface, write down how your data is getting there. Is Enhanced Conversions running through a Google tag on the thank-you page? Through GTM? Through a plugin that uses the Google Ads API directly? Through a Data Manager connection?
You need this record because once the method selector disappears from the interface, the only way to diagnose a broken implementation is to know what the implementation was. A screenshot of the current configuration, saved somewhere you’ll find it in September, is the simplest insurance policy against the unified view erasing the audit trail.
3. GTM and plugin tag integrity — tested
The tags that carry Enhanced Conversions data have to fire at the right moment, with the right payload, after consent is granted. A tag that fires before consent sends no user-provided data. A tag that fires after the payload is populated but before the conversion event is registered sends data against nothing. The unified toggle doesn’t fix any of that.
This is where GTM tag sequencing becomes the silent determinant of whether your migration lands clean. Use Google Tag Assistant or the Google Ads conversion diagnostics report to confirm that the user-provided data block is actually populating — email, phone, first/last name, address fields hashed client-side — on a real checkout. Don’t trust the plugin’s success screen; trust the diagnostic report.
4. Data Manager API option — understood
You don’t have to use Data Manager. Tags continue to work. The older Google Ads API continues to work for now, with the January 2026 session and IP restrictions noted. But the unified feature accepts all sources simultaneously, and Google’s roadmap points at Data Manager as the eventual centre of gravity.
The audit question isn’t should I migrate to Data Manager this month. It’s do I understand what Data Manager is, and do I have a path to send to it if my tag-based setup degrades further. Server-side stacks already send to it; plugin-only stores generally don’t. Knowing that gap exists is the audit.
Where this is actually going: server-side, multi-source
Two threads run together. The toggle unification simplifies advertiser UX. The multi-source parallel ingestion simplifies advertiser architecture — specifically by rewarding setups that can send from multiple places at once. Those are not accidents of product planning. They’re a signal of what Google expects the ingestion shape to look like.
Meanwhile the identity layer that Enhanced Conversions depends on is getting thinner in the browser. iOS 26 Link Tracking Protection strips gclid from standard Safari sessions, covering roughly 24% of global browser traffic. Click-ID-only setups are structurally insufficient heading into the unified toggle era. Hashed user-provided data, sent server-side, is the input Google has been optimising for all along.
The architecture Google is now explicitly designing for is the one server-side-first vendors have been building for years.
How you actually do this
Transmute Engine™ is a first-party Node.js server that runs on your subdomain and sends hashed user-provided data to Google Ads via both the Data Manager API and Google’s tag endpoints in parallel — which is exactly the multi-source posture the unified toggle accepts from April 2026. The inPIPE plugin captures WooCommerce events at the PHP hook level (not the browser), so consent sequencing and ad-blocker losses stop being the points of failure.
Key Takeaways
- The change is narrow: two features collapse into one toggle in June 2026, method selection is removed from the interface, and multi-source ingestion becomes the default.
- Auto-migration is conditional: it only fires for accounts that have already accepted the customer data terms at the account level — not automatic for plugin-only setups.
- Audit four items in the next 60 days: customer data terms, current implementation method, GTM/plugin tag integrity, and Data Manager API readiness.
- 67% of WooCommerce Enhanced Conversions first implementations fail audit, which means “no action required” is a warning for the majority of stores, not a reassurance.
- Server-side, multi-source sending is where Google’s roadmap is pointing — the unified toggle and Data Manager API are two surfaces of the same architectural shift.
Frequently Asked Questions
Only if your current setup is correct. Google will auto-migrate accounts that have already accepted the customer data terms and have a working Enhanced Conversions implementation. If your Enhanced Conversions tag is firing before consent, missing user-provided data, or routing from an untested plugin path, auto-migration will carry that broken setup forward. Audit four items first: customer data terms, current implementation method, GTM/plugin tag integrity, and Data Manager API readiness.
The tag itself will continue to fire, because the unified feature still accepts data from website tags. What changes is that method selection is being removed from the Google Ads interface — you can no longer toggle between “tag only” or “API only”. From April 2026, Google accepts all sources simultaneously. A GTM tag that was poorly sequenced (firing before consent, before the user-provided data layer is populated) will silently continue to send bad data into the unified feed.
Data Manager API is Google’s centralized first-party data ingestion point, launched December 9 2025. It unifies how advertisers send user-provided data across Google Ads, GA4, and DV360. You do not have to use it — tags and the older Google Ads API continue to work — but Google’s roadmap clearly favours Data Manager, and in January 2026 restrictions were introduced on session attributes and IP imports through the older Google Ads API. Server-side stacks that send directly to Data Manager are positioned for the direction of travel.
Enhanced Conversions for Web sent hashed user-provided data for online purchase and lead events captured on your website. Enhanced Conversions for Leads sent hashed data for offline conversions uploaded later — for example, a lead that closed by phone a week after the click. Google is merging them because the underlying operation is identical: accept hashed first-party data, match it to an ad click, improve attribution. Splitting it into two features with two setup paths was artificial. One toggle plus multi-source ingestion matches how the data actually flows.
Then auto-migration does not apply to you. Google explicitly states that the automatic transition to the unified feature requires prior agreement to the customer data terms. Plugin-based setups frequently skip this step because the plugin handles tag firing but the account-level terms must be accepted manually inside Google Ads by someone with admin access. Check Tools → Setup → Preferences → Account-level settings in your Google Ads interface before June 2026.
The unified toggle is coming in June. Audit the four items now, and the migration becomes a non-event. Start with your Google Ads account-level settings at seresa.io.