Recently, Google announced a significant change affecting how advertisers upload Customer Match audience data through the Google Ads API.
According to recent reports, developer tokens that have not performed a Customer Match upload within the past 180 days will no longer be allowed to upload audience data using the Google Ads API. Developers in this situation must instead migrate to the Data Manager API, which Google positions as a modern and unified data ingestion framework.
This update affects only Customer Match uploads, while other API features such as campaign management, bidding adjustments, and reporting remain unaffected.
Why Google Is Shifting Customer Match to the Data Manager API
Google states that the move is designed to modernize how first-party audience data is processed across its advertising ecosystem.
The Data Manager API introduces several improvements over the existing Customer Match workflow.
Streamlined Data Ingestion
The previous process required a multi-step job system that included creating, populating, running, and monitoring offline jobs.
The new API simplifies this process by allowing direct ingestion requests, reducing operational complexity for developers.
Enhanced Security and Privacy
The new system introduces stronger protections for sensitive user data.
Key improvements include:
- Confidential matching capabilities
- Improved data encryption protocols
- Removal of the requirement for a separate developer token
These measures are designed to align with Google’s broader focus on privacy-first advertising infrastructure.
Key Changes Developers Should Be Aware Of
Several important updates accompany the Customer Match migration.
Inactive Developer Tokens Will Lose Upload Access
If a developer token has not uploaded Customer Match data within the past 180 days, the system will block future uploads through the Google Ads API.
Affected developers must transition to the Data Manager API to continue managing audience lists.
Membership Duration Limits for Customer Lists
Google has also introduced limits related to audience membership duration.
Requests that set the UserList.membership_life_span field above 540 days will now trigger an error. Existing lists exceeding this threshold will be automatically adjusted to the 540-day maximum duration.
This ensures that customer data remains refreshed and compliant with Google’s data policies.
Other API Features Remain Unchanged
Importantly, the change applies only to Customer Match uploads.
Developers can continue using the Google Ads API for other functions, including:
- Campaign creation
- Budget management
- Bid optimization
- Performance reporting
These capabilities will remain fully supported.
Advantages of the Data Manager API
The new Data Manager API introduces capabilities designed to improve scalability and operational efficiency.
Multi-Audience Data Upload
Developers can send data to multiple audiences or accounts within a single request, reducing the number of API calls required.
No Developer Token Requirement
Unlike the Google Ads API workflow, the Data Manager API uses Google Cloud OAuth credentials rather than requiring a dedicated developer token.
This simplifies authentication management for many organizations.
Improved Quota Management
Instead of developer-token-based quotas, the new API uses project-level quotas and request limits, which can provide greater flexibility for large data operations.
Recommended Migration Steps
Developers migrating Customer Match workflows can follow several key steps.
Enable Data Manager API Access
First, enable the Data Manager API within Google Cloud Console and configure the appropriate OAuth credentials.
Map Existing Fields
Developers must update field mappings to ensure that existing Google Ads API audience data structures align with the Data Manager ingestion format.
Update Membership Duration Settings
Ensure audience lists respect the 540-day membership duration limit and update code accordingly.
Verify Upload Diagnostics
Use the Data Manager API diagnostics tools to confirm successful uploads and evaluate match rates.
Monitoring diagnostics is important for ensuring the accuracy of audience targeting data.
Alternative Integration Options
Organizations that prefer not to manage API integrations directly can use third-party platforms.
Some commonly used integrations include:
- Zapier
- HubSpot
- Salesforce
These tools automate the process of syncing customer information from CRM systems into Google Ads Customer Match lists.
Before transmission, customer data is hashed to protect personally identifiable information (PII) and comply with Google’s privacy policies.
What This Means for Advertisers and Developers
For developers and advertising teams using automated audience pipelines, the migration is an important operational update.
Failing to transition affected workflows may lead to Customer Match lists no longer updating automatically, which can impact targeting performance.
However, the Data Manager API is designed to offer a more scalable and secure environment for managing audience data in the long term.
FAQs
What is the Google Ads API Customer Match migration?
The migration refers to Google’s shift from the Google Ads API to the Data Manager API for Customer Match uploads, particularly for developer tokens that have been inactive.
Why is Google introducing the Data Manager API?
Google aims to create a centralized and secure data ingestion system with stronger encryption, simplified workflows, and improved audience management.
Does the change affect all Google Ads API features?
No. The update only impacts Customer Match uploads. Other Google Ads API functions such as campaign creation and reporting continue to work normally.
What is the maximum Customer Match membership duration?
Customer lists now have a maximum membership duration of 540 days, after which they must be refreshed.
Final Takeaway
Google’s decision to shift Customer Match uploads away from the Google Ads API for inactive tokens signals a transition toward a more unified and secure data infrastructure.
While developers must update their integrations, the new Data Manager API promises simplified ingestion workflows, stronger privacy protections, and improved audience management capabilities.
Digilogy tracks these industry developments closely. For daily updates and insights, visit the Digilogy News page.
