INDEPENDENT MINDS. SHARED AMBITION.
Back to the newsfeed
Strategy2 min read

Display & Video 360 · Status at source date: Official announcement

Display & Video 360 API v5 enters public beta and drops Customer Match management

Written by Paid Media Collective
IN BRIEF

The v5 API is "available in public beta starting today", adding advertiser-level YouTube video and channel exclusions, digital out-of-home insertion orders and refactored audience targeting for Demand Gen and YouTube ad groups. Customer Match audience management is removed from the API; Google points to the Data Manager API instead. Breaking changes remain possible during beta, and a v4 sunset date is not given. Any tool that uploads Customer Match lists through the DV360 API needs a Data Manager API path, so ask vendors for their migration plan.

Display & Video 360 API v5 enters public beta and drops Customer Match management. Source image from the published Week 43 newsletter.
Source image selected in Paid Media News Week 43. Announcement · API public beta. Google Ads Developer BlogView full-size image

What changed

Week 43 follow-up: 2026-10-22

Earlier coverage and context (2026-10-22)

Google made Display & Video 360 API v5 available in public beta on 22 October. Trevor Mulchay's announcement describes changes to targeting, inventory and audience-management workflows, and warns that breaking changes remain possible while the version is in beta.

The release adds full management of advertiser-level YouTube video and channel exclusions and support for Digital Out of Home insertion orders. It also changes inventory-source retrieval and targeting and refactors audience targeting for Demand Gen and YouTube ad groups.

Customer Match audience management is removed from this version in favour of Data Manager API. Teams should treat that as a migration dependency rather than assume that changing the API version alone preserves their existing audience workflow.

For an agency or advertiser with custom integrations, the practical task is to map the operations the integration actually performs. An exclusion-management script, an inventory workflow and a Customer Match process may require different migration work even when they share the same authentication setup.

Review Google's migration guide and release notes, update the client library and test the affected operations before moving production workloads. Preserve a record of the version and behaviour tested because a successful beta test is not a promise that later beta revisions will remain unchanged.

Developers maintaining reporting or campaign-management integrations should inventory the endpoints, response fields and validation rules their application relies on before testing a beta version. Run representative requests in a controlled environment and compare results with the supported production integration. A public beta is an opportunity to assess migration work, not a reason to replace a working integration immediately. Record incompatibilities against the version-specific documentation so they can be resolved before a production change.

Sources & contributor credit

  1. Original reportTrevor Mulchay

    Original announcement dated 2026-10-22.

  2. Newsletter coveragePaid Media Collective

    Published Week 43 edition; source for the approved credit, image and wording reconciliation.

Original creator unverified

Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.

Attribution evidence and limitations

Full attribution review pending.

A source link alone does not establish original authorship.

Original image and video creators have not yet been verified.

FOLLOW THE PEOPLE BEHIND THIS UPDATE
Published on this site
Article updated

This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.

Explore the source reporting