Google Killed Customer Match Uploads in the Ads API on April 1
Google disabled Customer Match uploads through the Google Ads API on April 1, 2026, cutting off any developer token inactive for 180+ days. WooCommerce stores relying on OfflineUserDataJobService or UserDataService for audience list uploads now receive CUSTOMER_NOT_ALLOWLISTED errors. The mandatory migration path is Google’s Data Manager API, a unified first-party data ingestion layer launched December 2025 that replaces five separate data workflows with a single endpoint. Stores using BigQuery’s native connector or manual CSV uploads in Audience Manager are unaffected.
What Google Actually Turned Off
Google’s April 1 cutoff targeted a specific API pathway, not all Customer Match functionality.
On March 4, 2026, Google notified developers that Customer Match data uploads through the Google Ads API would stop functioning from April 1, 2026. The notification targeted developer tokens that hadn’t performed a Customer Match upload in the previous 180 days — roughly any token inactive since October 2025. Any WooCommerce store using scripts that call OfflineUserDataJobService or UserDataService now receives the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE instead of a successful upload.
This wasn’t a deprecation warning. It was a hard cutoff. No grace period, no phased rollback. Tokens that qualified as inactive on April 1 lost access permanently.
Developer tokens inactive for 180+ days before April 1, 2026 now return the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when attempting Customer Match uploads via the Google Ads API.
The important distinction: non-Customer Match operations through the Google Ads API are completely unaffected. Campaign creation, bidding strategy management, ad group configuration, reporting — all of it continues working. Google is drawing a sharper line between general advertising operations and data-heavy, privacy-sensitive ingestion workflows.
You may be interested in: Google Ads Data Manager API Replaces Legacy Conversion Imports by June 2026
Which WooCommerce Setups Are Affected
Not every Customer Match workflow breaks — the impact depends on how you upload.
WooCommerce stores push customer data into Google Ads Customer Match lists through several different paths, and only one of them broke on April 1. Custom scripts using the Google Ads API to call OfflineUserDataJobService or UserDataService are the affected pathway. If your store runs Python, Node, or PHP scripts that push hashed email addresses, phone numbers, or postal addresses into Customer Match lists programmatically, those scripts now fail for inactive tokens.
Manual CSV uploads through Google Ads Audience Manager? Unaffected. BigQuery native connector syncing customer lists through Data Manager in the Google Ads interface? Also unaffected — it was built on the Data Manager layer from the start. The breakage is specifically in the programmatic API pathway that many WooCommerce stores automated years ago and haven’t touched since.
There’s a third category that’s easy to miss: third-party tools. Reverse ETL platforms like Hightouch, Census, and RudderStack, along with automation connectors like Zapier and Make, often call the Google Ads API under the hood. Hightouch announced their migration to the Data Manager API in late 2025, but not every vendor has completed the transition. If your WooCommerce store syncs audiences through a third-party tool, check whether that tool has migrated before assuming you’re clear.
What the Data Manager API Replaces
Five separate data workflows collapse into a single ingestion endpoint.
Google launched the Data Manager API on December 9, 2025, with eleven integration partners including Treasure Data, Tealium, Hightouch, and Zapier. It isn’t a rename of the Customer Match API. It’s a unification layer that replaces five previously separate data workflows: Customer Match uploads, offline conversion imports, enhanced conversions for leads, store sales data, and mobile device identifiers.
Google’s Data Manager API replaces five separate data workflows with a single ingestion endpoint handling Customer Match, offline conversions, enhanced conversions, store sales, and mobile identifiers.
Treasure Data, one of the first integration partners, reported an 80% reduction in engineering effort and twice-as-fast advertiser onboarding after consolidating onto the Data Manager API. That consolidation benefit matters for WooCommerce stores maintaining separate integrations for audience syncing, conversion tracking, and enhanced conversions — all of which now collapse into one API call that fans out to Google Ads, GA4, and DV360.
The Data Manager API also introduces confidential matching, a privacy-enhancing feature that processes customer data inside a trusted execution environment. According to Google’s product team, even the system administrator cannot access the data being processed. This isn’t available through the legacy Google Ads API pathway at all.
| Capability | Legacy Google Ads API | Data Manager API |
|---|---|---|
| Customer Match uploads | Disabled for inactive tokens (April 2026) | Supported |
| Offline conversion imports | Blocked for inactive tokens (June 2026) | Supported |
| Enhanced conversions for leads | Available (legacy path) | Supported |
| Store sales data | Available (legacy path) | Supported |
| Confidential matching | Not available | Built-in |
| Multi-product fan-out (Ads + GA4 + DV360) | Separate integrations required | Single endpoint |
| Requests per day per project | Varies by token | 100,000 |
| Audience members per request | Varies | 10,000 |
The Migration Timeline
The April 1 cutoff is one stop on a longer migration calendar that runs through March 2027.
Google isn’t making this change in isolation. The Customer Match cutoff is part of a systematic consolidation of data ingestion pathways that began in late 2025 and extends well into 2027. Understanding the full timeline matters because WooCommerce stores running multiple Google integrations face overlapping deadlines.
In January 2026, Google blocked session attributes and IP address imports through the Google Ads API — the data fields most commonly used for identity matching. In June 2026, UploadClickConversions requests will be blocked for developer tokens without recent activity, affecting WooCommerce stores using plugin-based Enhanced Conversions. The full legacy API sunset for all remaining Customer Match endpoints is scheduled for March 2027.
The enhanced conversions unified toggle coming in June 2026 adds a layer of complexity. Auto-migration only works for accounts that previously accepted Google’s customer data terms. If your WooCommerce setup used a plugin-based approach that didn’t explicitly accept those terms, the auto-migration pathway won’t be available. Every deadline in this calendar points in the same direction: the Data Manager API is the only long-term path for programmatic first-party data ingestion into Google’s advertising ecosystem.
What Changes in the New API
The Data Manager API simplifies the workflow but changes the authentication and request structure.
The migration isn’t a find-and-replace operation on existing scripts. The Data Manager API operates through both REST and gRPC protocols, uses OAuth 2.0 credentials with a dedicated datamanager scope, and routes through Google Cloud projects rather than developer tokens. Each Google Cloud project supports up to 100,000 requests per day and 300 requests per minute, with up to 10,000 audience members per individual request.
The workflow simplification is real. The legacy Google Ads API required creating an OfflineUserDataJob, adding operations to it, running the job, and then polling for completion status — a multi-step asynchronous process. The Data Manager API reduces this to a single ingestion request with no job management overhead. For WooCommerce stores that automated Customer Match years ago and have been running essentially the same script since, the new API is architecturally cleaner despite requiring a rewrite.
You may be interested in: Ad Blocking Didn’t Peak: 1.77 Billion Users Entrenched in 2026
The WooCommerce Migration Path
WooCommerce stores have three options, and the right one depends on how much automation you need.
The simplest path for WooCommerce stores that don’t need real-time audience syncing: export your customer list as a CSV and upload it manually through Google Ads Audience Manager. This workflow was never affected by the API change and requires no development resources. It’s appropriate for stores with stable customer lists that refresh monthly or quarterly.
For stores that need automated syncing, the BigQuery native connector is the path of least resistance. Link a BigQuery project in the Google Ads interface under Tools → Data Manager, select a dataset and table, map the fields, and synchronisation runs automatically. This connector was integrated into the Data Manager layer from the start and bypasses the API entirely. WooCommerce stores already pushing order and customer data to BigQuery through a server-side pipeline can simply expose the right table and connect it.
For stores that require full programmatic control — custom audience segmentation, real-time list updates based on purchase behaviour, or integration with internal CRM systems — the Data Manager API is the destination. The migration requires new OAuth 2.0 credentials with the datamanager scope, a Google Cloud project, and a rewrite of the ingestion logic. Server-side tracking recovers 20–40% of previously lost conversions in typical e-commerce implementations, and the Data Manager API extends that recovery into audience quality by ensuring your Customer Match lists are fed with the same first-party data your conversion tracking uses.
Translation: the stores that invested in server-side data infrastructure already have the hardest piece in place. The Data Manager API migration is plumbing. The first-party data strategy is the foundation.
Key Takeaways
- Hard cutoff, not deprecation: Google disabled Customer Match uploads through the Ads API on April 1, 2026 for inactive tokens. No grace period, no rollback. Active tokens still work but face a March 2027 full sunset.
- Only the programmatic path broke: Manual CSV uploads and BigQuery native connector syncs are unaffected. The breakage is in custom scripts using OfflineUserDataJobService or UserDataService.
- Five workflows become one: The Data Manager API consolidates Customer Match, offline conversions, enhanced conversions, store sales, and mobile identifiers into a single ingestion endpoint with confidential matching built in.
- Third-party tools need checking: Reverse ETL platforms and automation connectors may still use the legacy API under the hood. Verify your vendor has migrated before assuming your audience lists are updating.
- Server-side data is the foundation: WooCommerce stores with server-side tracking and BigQuery pipelines already have the infrastructure for the easiest migration path — the BigQuery native connector bypasses the API entirely.
Google disabled Customer Match uploads through the Google Ads API for any developer token that had not performed a Customer Match upload in the previous 180 days. If your token was last active before October 2025, it now returns the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE. Non-Customer Match operations like campaign management, bidding, and reporting continue to work normally through the existing Google Ads API.
It depends on how you upload. If your WooCommerce store uses custom scripts calling OfflineUserDataJobService or UserDataService, yes — migration to the Data Manager API is mandatory. If you sync audiences through BigQuery’s native connector in Google Ads or upload CSV files manually through Audience Manager, those paths are unaffected. Third-party tools like Hightouch, Tealium, and Zapier may also need updating if they relied on the legacy API under the hood.
Inactive tokens were cut off on April 1, 2026. Active tokens — those with at least one Customer Match upload in the 180 days prior — continue working for now, but Google has not communicated a final sunset date for active tokens. The full legacy API sunset for all remaining Customer Match endpoints is scheduled for March 2027. New developer tokens can no longer be registered for Customer Match through the Google Ads API at all.
The audience functionality stays the same — Customer Match lists still power targeting, exclusions, and the New Customer Acquisition bidding objective. What changes is the ingestion path. The Data Manager API simplifies the workflow from a multi-step asynchronous job to a single ingestion request, adds confidential matching inside a trusted execution environment, and consolidates five separate data workflows into one unified endpoint.
References
- Google Ads Developer Blog — Changes to Customer Match Support in the Google Ads API (March 2026)
- PPC Land — Google Forces Customer Match Uploads to Data Manager API by April 1 (March 2026)
- Google for Developers — Upgrade from the Google Ads API to the Data Manager API (May 2026)
- PPC Land — Google’s Data Manager API Wants to Kill Your Three-Pipeline Headache (April 2026)
- ALM Corp — Google Disabling Customer Match Uploads: Complete Migration Guide (March 2026)
- Seresa — Google Ads Data Manager API Replaces Legacy Conversion Imports by June 2026
- SignalBridge — 2026 Server-Side Tracking Benchmark Report (March 2026)
If your WooCommerce audience lists went quiet on April 1, the fix isn’t complicated — but it does require knowing which migration path fits your setup. Seresa builds server-side data infrastructure that feeds both your conversion tracking and your audience lists through a single first-party pipeline.