Google Ads Data Manager API Replaces Legacy Conversion Imports by June 2026
Google launched the Data Manager API on December 9 2025 as a unified first-party data ingestion layer across Google Ads, GA4, and DV360. Starting June 15 2026, the Google Ads API will reject new offline conversion imports from developer tokens without recent activity. WooCommerce stores using plugin-based Enhanced Conversions face a forced migration. The Enhanced Conversions unified toggle coming in June 2026 adds urgency, as auto-migration only works for accounts that previously accepted Google’s customer data terms — a condition 67% of WooCommerce plugin setups fail.
What the Data Manager API Actually Replaces
Five separate data workflows collapse into one API — and the old paths are being shut down systematically.
Google launched the Data Manager API on December 9 2025 with eleven integration partners including Treasure Data, Tealium, Hightouch, and Zapier. Before this, developers maintaining Google Ads integrations had to build and manage separate pipelines for Customer Match uploads, offline conversion imports, enhanced conversions for leads, store sales data, and mobile device identifiers. The Data Manager API replaces all five with a single endpoint that works across Google Ads, GA4, and Display & Video 360.
This is not a cosmetic rebrand. The old APIs are being systematically restricted. In January 2026, Google began blocking session attributes and IP address imports through the older Google Ads API. The Customer Match API no longer accepts new developers or advertisers — anyone starting fresh must integrate directly with the Data Manager API. Existing Customer Match API users face a March 2027 deadline to complete migration.
Treasure Data, one of the first integration partners, previously maintained separate integrations for Google Ads Customer Match, Google Analytics audiences, and DV360 audience management. After consolidating onto the Data Manager API, they reported an 80% reduction in engineering effort and twice-as-fast advertiser onboarding. The consolidation is real, and the engineering benefits are significant — but the migration clock is running.
Google launched the Data Manager API on December 9 2025 as a unified first-party data ingestion layer replacing five separate data workflows across Google Ads, GA4, and DV360.
The June 15 Deadline Is Real
Developer tokens without recent offline conversion activity face immediate rejection — and the error will be silent for most WooCommerce stores.
Google announced on May 15 2026 that the UploadClickConversions request in the Google Ads API will stop working after June 15 for developer tokens that cannot demonstrate recent usage. The qualifying condition is specific: the token must have successfully imported offline conversions between December 2025 and May 2026.
Tokens that fall outside that window and attempt to upload after June 15 will receive the CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE error. Unless the calling system has explicit error handling for that response code, the upload fails silently from the advertiser’s perspective. Your WooCommerce store stops sending conversion data to Google Ads, and nothing in your dashboard tells you why.
This affects a narrow but critical API method — ConversionUploadService.UploadClickConversions — which is precisely the method most custom WooCommerce integrations depend on. If your store invested in offline conversion imports because you understood that client-side pixels miss phone sales, CRM conversions, and cross-device journeys, that investment now faces forced migration.
Plugins using client-side pixels or Google Tag Manager are not directly affected by this specific API change. But they are already missing every conversion that happens after the browser session closes — the very problem offline conversion imports were designed to solve.
Starting June 15 2026, the Google Ads API rejects UploadClickConversions requests from developer tokens that have not imported offline conversions between December 2025 and May 2026.
The Enhanced Conversions Toggle Makes It Worse
The unified toggle assumes your setup is correct — but 67% of WooCommerce plugin setups are not.
Running in parallel with the Data Manager API migration, 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. 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 official line is no action required. That is only true if your current setup is already correct.
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. Seresa’s analysis of first-implementation Enhanced Conversions setups on WooCommerce found that 67% fail audit. The most common failures: customer data terms not accepted, hashing implemented incorrectly, and the purchase event firing before the customer’s email address exists in the page.
Auto-migration carries whatever state you are in into the new system. If your Enhanced Conversions setup was sending partial or malformed data before the toggle change, it continues sending partial or malformed data after — but now with even less visibility into the problem because the method selection controls are gone.
| Migration Path | Estimated Effort | Key Requirement |
|---|---|---|
| CDP or martech platform with connector | Approximately 1 week | Platform must support Data Manager API |
| Custom server-side pipeline | Approximately 1 month | New Google Cloud project + OAuth scope |
| Plugin-based (tag only) | No API migration needed | Still missing offline conversions entirely |
| Plugin-based (API integration) | Depends on plugin update | Plugin vendor must migrate endpoint |
You may be interested in: Google Ads Collapses Enhanced Conversions Into One Toggle in June 2026
The WooCommerce Plugin Gap
Most WooCommerce tracking plugins send conversion data via client-side pixels — the Data Manager API requires server-side infrastructure they do not have.
WooCommerce powers over 4.5 million active stores globally with a 33.4% market share by store count. Most use tracking plugins that rely on client-side JavaScript conversion pixels fired from the browser. The Data Manager API is a server-side API that requires a Google Cloud project, OAuth 2.0 authentication with the datamanager scope, and hashed user-provided data sent from your server — not the browser.
This is a structural mismatch. Client-side pixels fire a JavaScript tag when the browser loads your thank-you page. The Data Manager API expects your server to send a structured payload containing hashed email, phone, address, transaction ID, and conversion value to Google’s ingestion endpoint. These are fundamentally different architectures that serve fundamentally different data flows.
The browser pixel fires before the customer’s email exists in the page — a structural timing problem that Enhanced Conversions was designed to solve but plugin implementations frequently get wrong. Enhanced Conversions with first-party data sees up to 35% higher conversion accuracy than click-ID-only tracking according to Google Ads documentation, but only when the hashing and data collection are correct.
For WooCommerce stores that want to use the Data Manager API, the question is whether their tracking plugin will update to support it — or whether they need server-side infrastructure that sends data independently of any browser event.
67% of first-implementation Enhanced Conversions setups on WooCommerce fail audit, meaning auto-migration to the unified toggle will carry broken attribution into the new system.
You may be interested in: Chrome Kept Third-Party Cookies — Why Are You Still Losing Conversion Data?
The Full Migration Timeline
Four overlapping deadlines are compressing the migration window — and more are coming.
The Data Manager API migration does not exist in isolation. Google is running parallel deprecations across multiple API products, creating a compounding effect for WooCommerce stores that have not yet started migration planning.
December 9 2025: Data Manager API launched with eleven partners. Customer Match API closed to new developers and advertisers.
January 2026: Google began restricting session attributes and IP address imports through the older Google Ads API. The data fields most commonly used for identity matching are being removed from the legacy path.
June 2026: Two deadlines converge. Enhanced Conversions unified toggle removes method selection from the Google Ads interface. UploadClickConversions requests blocked for developer tokens without recent activity.
August 18 2026: Content API for Shopping is shut down entirely, replaced by the Merchant API. WooCommerce stores managing product feeds programmatically face a parallel migration on the commerce data side.
March 2027: Full legacy API sunset for all remaining Customer Match endpoints. Every advertiser and developer must be on the Data Manager API by this date.
The pattern is consistent across Google’s API portfolio: purpose-built successor APIs with firm deprecation timelines. The Data Manager API, the Merchant API, and the Enhanced Conversions consolidation all follow the same playbook — launch the replacement, restrict the legacy, set a sunset date.
Server-Side Tracking as the Migration Bridge
A server-side event pipeline sends data to both legacy and Data Manager API endpoints simultaneously — no downtime, no data gaps during migration.
The practical solution for WooCommerce stores facing these overlapping deadlines is a server-side tracking pipeline that can send hashed user-provided data to multiple destinations in parallel. During migration, the pipeline sends conversion data through both the legacy tag endpoints and the Data Manager API simultaneously. When the legacy path shuts down, the pipeline continues through the Data Manager API without interruption.
This multi-destination approach is exactly the posture the Enhanced Conversions unified toggle expects. Google now accepts user-provided data through tags, Data Manager, and API in parallel. A server-side pipeline that addresses all three ensures your store’s conversion signals reach Google regardless of which endpoint Google deprecates next.
Both migration paths — CDP connector or custom pipeline — require a new Google Cloud project with the Data Manager API enabled and a dedicated OAuth scope. For WooCommerce stores already running server-side tracking, the incremental work is adding the Data Manager API as an additional destination. For stores without server-side infrastructure, this is the forcing function to build it.
Transmute Engine™ sends WooCommerce purchase and engagement events to Google Ads via both Data Manager API and tag endpoints in parallel — the multi-source posture that handles the June 2026 transition without conversion data gaps.
Key Takeaways
- Data Manager API is the only path forward: Launched December 9 2025, it unifies five separate data workflows. New implementations must use it from day one.
- June 15 deadline blocks legacy imports: Developer tokens without recent offline conversion activity will receive errors. Most WooCommerce stores will not see an alert — the failure is silent.
- Enhanced Conversions toggle adds urgency: The unified toggle auto-migrates your current state — including broken configurations. 67% of WooCommerce setups fail audit.
- Client-side pixels are not directly affected: But they are already missing every offline conversion. The Data Manager API was designed to fill exactly that gap.
- Server-side is the migration bridge: A pipeline that sends to both legacy and Data Manager API endpoints in parallel protects conversion data during the transition.
The Data Manager API, launched December 9 2025, is Google’s unified first-party data ingestion layer. It replaces five separate data workflows — Customer Match uploads, offline conversion imports, enhanced conversions for leads, store sales data, and mobile device identifiers — with a single API endpoint that works across Google Ads, GA4, and DV360.
Starting June 15 2026, the Google Ads API will reject UploadClickConversions requests from developer tokens that have not imported offline conversions between December 2025 and May 2026. Tokens with recent activity get a transition window. New implementations must use the Data Manager API from day one. WooCommerce stores using client-side pixels only are not directly affected by this specific API change.
Yes. Google is merging Enhanced Conversions for Web and Enhanced Conversions for Leads into a single toggle in June 2026. Auto-migration only works if your WooCommerce store previously accepted Google’s customer data terms — 67% of first-implementation setups have not. Stores that skip this step carry broken attribution into the unified system without receiving any error notification.
Server-side tracking pipelines can send hashed user-provided data to both the legacy tag endpoints and the Data Manager API in parallel, exactly the multi-source posture the unified toggle expects. This means WooCommerce stores with server-side infrastructure can migrate progressively without losing conversion data during the transition.
December 9 2025: Data Manager API launched. January 2026: Google began restricting session attributes and IP imports via Google Ads API. June 2026: Enhanced Conversions unified toggle and offline conversion import restrictions. August 2026: Content API for Shopping shutdown. March 2027: Full legacy API sunset for remaining Customer Match endpoints.
References
- Google Ads Developer Blog (December 9, 2025). The Data Manager API Is Now Generally Available.
- Google Blog (December 10, 2025). Data Manager API helps advertisers improve measurement and get better results from Google AI.
- PPC Land (May 18, 2026). Google blocks new offline conversion imports via Ads API from June 15.
- PPC Land (April 4, 2026). Google’s Data Manager API wants to kill your three-pipeline headache.
- Seresa (April 20, 2026). Google Ads Collapses Enhanced Conversions Into One Toggle in June 2026.
- Seresa (May 27, 2026). Google Ads API Blocks New Offline Conversion Imports June 15.
- XICTRON (January 2026). Google Merchant API Migration: What Shop Owners Need to Know by August 2026.
- Google Developers (2026). Data Manager API documentation.
If your WooCommerce store needs to audit its Enhanced Conversions setup before the June 2026 deadline, start with a Seresa tracking diagnostic.