Managing first-party audiences in Google Ads changed structurally in 2026. Google blocked Customer Match data uploads through the legacy Google Ads API from April 1, 2026, moving all audience list management to the Data Manager API. Google then expanded the Data Manager API with smarter audience management, adding tools to clear lists in one call, expire members by date, and surface field-level ingestion warnings instead of failing whole uploads. For B2B SaaS teams that lean on Customer Match, this is the pipeline your audiences now run through.
The shift is more than a plumbing change. The Data Manager API adds confidential matching and enhanced encryption, privacy features the old API lacked, which changes the risk calculus of uploading customer PII to an ad platform. Combined with the new list-maintenance methods, it makes first-party audience management both safer and more precise than the endpoints it replaced. This guide covers what the API is for, the migration you should already have completed, what the 2026 audience update added, how confidential matching works, and which lists are actually worth keeping current for a B2B SaaS account.
What changed in April 2026, and why it matters now
The Data Manager API is Google's unified interface for connecting first-party data across its advertising products, covering both audience activation and conversion measurement. As of April 1, 2026, it is not optional for audiences: Customer Match uploads through the Google Ads API were disabled, and audience list management must go through the Data Manager API. Any integration still pointed at the old endpoint stopped uploading on that date, which means lists built before then have been decaying as members age out without a refresh feeding them.
This is why the framing matters. The migration is not a deadline to plan for; it is a current-state check to run. If your Customer Match lists have looked quietly smaller or less effective since spring, a stalled upload integration is the first thing to rule out. The fix is to confirm your sync, whether hand-built or through a tag manager or partner tool, writes to the Data Manager API and is refreshing on schedule. Audience decay is invisible in the interface until targeting or exclusions start missing people they used to catch, so verifying the pipeline is live is prerequisite work before any audience strategy discussion.
Confidential matching and enhanced encryption
The Data Manager API includes two features the Google Ads API did not: confidential matching and enhanced encryption. Confidential matching uses a Trusted Execution Environment, a secured processing enclave, to match your uploaded first-party data with technical assurances that the data is processed only for audience matching and no other purpose. Instead of trusting a policy that says the platform will not repurpose your customer list, you get a technical constraint on what the platform can do with it.
For B2B SaaS, this often unblocks a stalled internal debate. Security and legal teams frequently resist uploading customer emails and identifiers to an ad platform, and that resistance kills Customer Match programs before they start. Confidential matching gives those teams a concrete, auditable answer about how the data is handled, which is usually the difference between approval and a permanent no. If your company has held back on Customer Match for privacy reasons, the move to the Data Manager API is the moment to reopen the conversation, because the technical story is materially stronger than it was under the old API.
The 2026 audience-management update in practice
The expanded API added list-maintenance tools that map directly onto how B2B SaaS teams actually sync audiences from a CRM. A new RemoveAllAudienceMembers method clears an entire audience list in a single operation, so you can rebuild a list from a fresh export cleanly rather than reconciling deltas. An optional timestamp parameter lets you remove only members added before a specified date, which makes expiring stale cohorts a one-call operation instead of a manual diff. Together they turn list hygiene from a fiddly, error-prone job into something you can automate reliably.
The update also introduced field-level ingestion warnings. A batch upload now processes the valid records and returns detailed warnings identifying the problematic fields, rather than rejecting the whole request because a handful of rows are malformed. For anyone who has watched a nightly sync fail entirely over a few bad email formats, this is a real reliability gain: your good data lands, and you get a precise list of what to fix. The practical upshot is that a well-built sync can now keep lists current with far less babysitting, which lowers the maintenance cost of running a serious Customer Match program.
Which audiences are worth maintaining
The temptation with easier list management is to build more lists. Resist it. The audiences worth maintaining are the ones that change a bidding or targeting decision. The first is your existing-customer list: used to exclude current customers from acquisition campaigns so you are not paying to re-acquire people you already have, and to power new-customer measurement. The second is a paying-customer or high-value cohort, useful as a seed for similar audiences and as an exclusion. The third is open-opportunity or active-trial lists for retargeting and RLSA, where bidding up on people already in your funnel is defensible.
Everything else is usually overhead. A list that is not wired into a campaign decision, or that is too small or too stale to matter, costs sync effort and audit confusion while returning nothing. Because the API now makes it trivial to clear and rebuild lists by date, the right discipline is a small set of well-defined, freshly synced audiences rather than a sprawl of segments nobody targets. For how these lists plug into targeting strategy, see our guide to Google Ads audience targeting for B2B SaaS, and for the conversion-side of the same API, our walkthrough of migrating SaaS conversion uploads to the Data Manager API.
An operational checklist for SaaS teams
Turn the above into a short recurring routine. First, confirm every Customer Match upload now flows through the Data Manager API and is refreshing on schedule, since anything still on the Google Ads API path has been dead since April. Second, enable confidential matching so your PII uploads carry the stronger technical guarantees, and document that for your security team. Third, use RemoveAllAudienceMembers and the timestamp parameter to rebuild lists from fresh exports and expire stale cohorts, rather than letting lists drift. Fourth, monitor field-level ingestion warnings and fix the flagged rows so match rates stay high.
Finally, prune. Once a quarter, list every audience in the account and delete any that no campaign targets or excludes. The whole point of the easier tooling is not to accumulate more segments but to keep a focused set genuinely accurate, because a Customer Match program only pays off when the exclusions actually exclude and the seeds actually reflect your best customers. Audience management done well is quiet infrastructure: a handful of lists, always fresh, wired into decisions that matter. For how those exclusions connect to measuring genuine new-logo acquisition, see our post on new-customer reporting for B2B SaaS CAC.