Google to Disable Customer Match Uploads in Ads API

Why It Matters

The change forces advertisers to update their audience data workflows, or risk losing the ability to target customers through Customer Match. It also signals Google’s push toward a more secure, centralized data platform.

Key Takeaways

• Inactive tokens lose Customer Match upload ability after April 1
• Migration required to Data Manager API for audience data
• Data Manager offers enhanced encryption and confidential matching
• Other Ads API functions remain unchanged
• Early migration avoids campaign disruptions

Pulse Analysis

Customer Match has been a cornerstone of Google’s audience targeting, allowing advertisers to upload first‑party lists for search and display campaigns. Since its introduction, the feature lived within the broader Google Ads API, which handled everything from bidding to reporting. However, as data privacy regulations tighten and Google consolidates its data pipelines, the company introduced the Data Manager API—a purpose‑built, security‑focused ingestion layer. By positioning Data Manager as the default for audience uploads, Google aims to streamline compliance, reduce legacy code, and offer advanced matching capabilities.

The immediate impact falls on developers whose tokens have not performed a Customer Match upload in the last 180 days. After April 1, any such upload attempt will return an error, forcing a migration to the Data Manager endpoint. Practically, this means updating OAuth scopes, revising request payloads to the new schema, and testing confidential matching settings. Early migration is advisable; it prevents campaign downtime and gives teams time to validate encryption keys and audit list hygiene under the stricter security model.

This shift reflects a broader industry trend toward centralized, encrypted data hubs that limit surface‑area for breaches. Advertisers benefit from tighter access controls and the ability to leverage Google’s confidential matching, which hashes identifiers before they ever leave the platform. At the same time, agencies must invest in developer resources to refactor legacy integrations. Companies that act quickly can maintain seamless audience targeting, while those that delay risk losing a key channel for personalized advertising and may face compliance scrutiny.