Google opened Display & Video 360 API v5 in public beta on October 22, 2026, and this release is not a cosmetic update. It removes Customer Match audience management, changes how programmatic deals are identified, and creates real migration work for agencies and ad tech teams.
The announcement came from Trevor Mulchay on the Google Ads Developer Blog. Google hasn’t set a date for v4 to stop working, so nothing breaks today—but the changes are structural enough that teams should start discovery now.
Customer Match moves off the DV360 API
The biggest functional shift: v5 no longer creates or fills first-party audience lists. In the migration guide, three methods on firstPartyAndPartnerAudiences—create, patch and editCustomerMatchMembers—are gone, along with the fields that carried hashed contact details and mobile IDs. Developers can still read and target audiences, but they cannot build or edit them through this API.
Google is routing that work to the Data Manager API, launched in December 2025 as a single ingestion point for Google Ads, Google Analytics and DV360. Google’s rationale: confidential matching, encryption, multi-audience requests and better diagnostics that the DV360 API doesn’t offer.
Cached deal IDs will not survive
Version 5 splits the old InventorySource resource into separate deal and auction package objects with new targeting types. Google’s migration guide is blunt: previously cached InventorySource resource IDs cannot be used after migration. For trading desks that store deal ID maps in their own databases, this is a table rebuild, not an endpoint rename.
Three migration workstreams
- Customer Match pipelines need a second API, its own authentication model and separate quotas.
- Deal and auction package targeting needs new IDs and new targeting types.
- Demand Gen and YouTube ad group audience code must be rewritten from a single audience group into five separate targeting types.
Other visible changes
Digital out-of-home insertion orders can now be read through advertisers.insertionOrders.list—useful for reporting, not creation. Adloox verification vendor fields are renamed to Peer39 after the June 2026 acquisition. YouTube video and channel exclusions move to the advertiser level, and a new containsSyntheticMedia field appears on AdGroupAd.
Why it matters for media teams
Display & Video 360 is Google’s enterprise demand-side platform. The API is how agencies, trading desks and ad tech vendors automate insertion orders, targeting and reporting at scale. A version change like this sets the engineering calendar for teams running tooling across hundreds of advertisers. The v4-to-v5 move also consolidates first-party data into Data Manager, narrows brand safety controls, and reflects the Peer39-Adloox acquisition in verification vendor fields.
What to do now
Google hasn’t announced a v4 sunset date, and v5 is still a beta with possible breaking changes. The right move is to treat this as a discovery window. Audit stored deal IDs, map every Customer Match pipeline, update client libraries, and monitor the release notes before rewriting anything.
If Google follows the version pattern from v1 to v3, teams would have roughly six to seven months from a deprecation notice to shutdown—once v5 leaves beta. That’s not a countdown today, but it’s close enough to start planning.
Source: PPC Land
