Starting today, Google is blocking Customer Match uploads through the Google Ads API for any developer token that has not performed a Customer Match upload in the past 180 days. If your automation workflows have not touched Customer Match since before October 4, 2025, they are broken right now.
This is not a gradual rollout or a warning. Affected tokens will simply start returning errors where they previously returned success confirmations. For marketing teams relying on automated first-party audience syncing, this is a day-one disruption.
What Google actually changed
Google has been pushing advertisers away from Customer Match uploads in the Google Ads API for months. The April 1 deadline is the enforcement point: any developer token inactive for more than 180 days loses the ability to upload Customer Match lists via the Ads API.
The replacement is the Data Manager API, which Google is positioning as the long-term home for first-party data uploads. Everything else in the Google Ads API remains untouched. Campaign management, bidding, reporting, keyword management and conversion tracking all continue to work as normal. Only the Customer Match upload pathway is affected.
The practical impact is biggest for teams that built automated audience refresh workflows months or years ago and then stopped actively maintaining them. If your CRM-to-Google-Ads pipeline runs on a schedule but was last modified or tested before October 2025, today is when you find out it is broken.
Who is affected: Any developer token that has not uploaded Customer Match data since before October 4, 2025 will fail to upload audience lists as of today. All other Google Ads API functionality continues to work normally.
Why this matters for first-party data strategy
Customer Match is one of the highest-performing targeting tools Google offers. Uploading your customer email lists to match against signed-in Google users consistently outperforms interest and demographic targeting because you are reaching people you already know. Losing that pipeline, even temporarily, means your Google campaigns revert to cold audiences while you fix the plumbing.
More broadly, this is Google accelerating the shift to its own data infrastructure. The Data Manager API gives Google more visibility into how and when first-party data is being uploaded, which fits the pattern we have seen across the industry: platforms want your data flowing through their systems, not yours.
For marketers who have been investing in first-party data collection, this change is also a reminder that the infrastructure for activating that data needs to be maintained actively. A stale integration is not a working integration.
-> Any token unused since before October 4, 2025 is now blocked from uploading audience lists
-> The Data Manager API is the required replacement pathway going forward
-> All other Google Ads API functionality (campaigns, bidding, reporting) is unaffected
-> This is part of Google’s broader push to consolidate first-party data through its own infrastructure
What this means for marketers
If your team manages Google Ads in-house, test your Customer Match sync today. Run a manual upload and see if it succeeds. If it fails, you need to migrate to the Data Manager API or use Google Ads Manager directly to upload lists while the technical fix is underway.
If you work with an agency or use a marketing automation platform to sync audiences to Google, contact them today to confirm the integration has been updated. Many platforms will have already migrated, but the ones that have not will be returning errors silently while your audience lists go stale.
The bigger lesson: first-party data is only valuable if the pipeline delivering it to ad platforms is actively maintained. This is a good moment to audit every automated audience sync across all your platforms, not just Google. If you are looking for tools to manage your marketing automation workflows, our Best AI marketing automation tools 2026 roundup covers the platforms that handle this reliably.
-> Migrate to the Google Data Manager API if your developer token is affected
-> Contact your agency or automation platform to confirm their integration is updated
-> Audit all automated audience syncs across Google, Meta, and LinkedIn while you are at it