Google updated the Data Manager API with new audience management tools, more flexible data ingestion and expanded support for user-provided address data, making it easier to maintain Customer Match lists and improve data quality. The release aims to reduce manual work while giving better visibility into data issues that should not fail an entire ingestion request.
The headline addition is a RemoveAllAudienceMembers method, which clears an entire audience list in a single operation. An optional timestamp parameter lets advertisers remove only members added before a specified date, making full audience refreshes much easier.
Google also introduced field-level ingestion warnings. Rather than failing a whole request when optional fields contain invalid data, the API now processes valid records while returning detailed warnings identifying the problematic fields and explaining why validation failed.
The update expands the address information that can be sent to Google Analytics destinations: developers can now include street address, city and state or province alongside existing fields such as name, postal code and region. User-provided data can also satisfy identifier requirements for certain multi-source events when other identifiers are unavailable.
Google additionally released new AI agent skills in its Google Skills GitHub repository to help developers build Data Manager API integrations more efficiently within AI-assisted coding environments.
The update removes several friction points for developers managing first-party data. Audience refreshes get simpler, ingestion issues become easier to troubleshoot without interrupting workflows, and the expanded address fields add flexibility when sending user data to Google Analytics — streamlining customer data management across Google Ads, Display & Video 360 and Google Analytics.
Bulk clearing simplifies scheduled refresh pipelines. Instead of separately tracking which members to remove, you can now expire members by timestamp.
Field-level warnings mean rewriting your validation logging. Partial success plus warnings becomes the default response, so without a process that collects and monitors those warnings, quality degradation goes unnoticed.
Expanded address fields can lift match rates, but confirm collection basis and consent scope first. Being able to send a field is not the same as being permitted to.
For the parallel tightening of API access itself, see Google Pilots an Allowlist for the Google Ads API; for a customer-data sync example on the commerce side, see Stibee Syncs With Imweb in Real Time.
It clears an entire audience list in one operation, with an optional timestamp parameter to remove only members added before a specified date.
Instead of failing the whole request when optional fields contain invalid data, the API processes valid records and returns warnings identifying the problematic fields and why they failed validation.
Street address, city and state or province, in addition to existing fields such as name, postal code and region.
To apply what you just read to your own site, start with a free audit of where things are now.
A strategist replies within 24 hours on business days.
A new Enhanced matching option is appearing in Customer Match settings, extending first-party audience reach by matching consented users with consented publisher users.
Google is adding multi-campaign A/B testing, experiments that keep brand and location controls on, and expanded Performance Planner forecasting to AI Max for Search campaigns.
Demand Gen starts where there is no keyword and no existing interest. As that protection disappears, PPC specialists need creative strategy, audience research and full-journey measurement.