Google on October 22, 2026 opened version 5 of the Display & Video 360 API in public beta, according to a post on the Google Ads Developer Blog signed by Trevor Mulchay of the Display & Video 360 API Team. The new version removes the methods developers used to create and fill Customer Match audiences, steering that work to the separate Data Manager API, and it changes how programmatic deals are identified so thoroughly that IDs stored under version 4 cannot be carried across. It also lets developers read digital out-of-home insertion orders for the first time and moves YouTube video and channel exclusions to the advertiser level.

In Short

Google released a test version of the software connection that big advertisers and agencies use to run campaigns in its Display & Video 360 buying platform without clicking through screens. The new version stops handling customer email and phone lists for ad targeting, which now have to go through a different Google tool, and it renumbers how private ad deals are labelled. Anyone whose systems rely on the old version can keep using it for now, but moving to the new one means rewriting several parts of their code.

What Google published

The announcement is brief. "We're pleased to announce that Display & Video 360 API v5 is available in public beta starting today," according to the post, which is dated Thursday, October 22, 2026, and filed under the labels beta, dv360_api, release and update. Google describes what follows as "a subset of changes introduced in v5" and lists five of them: full management of advertiser-level YouTube video and channel exclusion targeting, support for Digital Out of Home InsertionOrder resources, updated Inventory Source retrieval and targeting, refactored audience targeting for Demand Gen and YouTube AdGroup resources, and "removal of Customer Match audience management features in favor of upgrading to use Data Manager API."

The post links to the release notes, a v4 to v5 migration guide, a Data Manager API upgrade guide for Customer Match and a Display & Video 360 help page on buying digital out-of-home inventory. It also carries a warning that applies to every integration built against the beta. "Be aware that breaking changes may be made to v5 while in beta, and any such changes will be listed in the Display & Video 360 API release notes," Mulchay wrote. "Before using new features, make sure to update your client library to the latest version."

Google's reference overview for the API, a page that carries no publication date, now defaults to v5 and states that "Display & Video 360 API v5 is currently in beta." It describes the service in a single sentence: "Display & Video 360 API allows users to automate complex Display & Video 360 workflows, such as creating insertion orders and setting targeting options for individual line items." The service endpoint remains https://displayvideo.googleapis.com, with v5 calls running under the /v5/ path and a separate discovery document at version=v5. The overview lists 46 REST resources for v5, from advertisers and campaigns down to custom bidding scripts, Floodlight activities, reach forecasting and users.

A banner at the top of the same overview page reads: "The Display & Video 360 API now supports Demand Gen resource management." That capability predates v5. Google confirmed in May that full Demand Gen campaign management would reach the API from June 10, with a phased rollout reaching all partners by June 24, 2026.

Customer Match leaves the Display & Video 360 API

The most consequential removal concerns first-party audience lists. According to the migration guide, v5 drops three methods on the firstPartyAndPartnerAudiences resource: create, patch and editCustomerMatchMembers. The release notes also list two removed fields on the FirstPartyAndPartnerAudience object, contactInfoList and mobileDeviceIdList, which carried hashed contact details and mobile device identifiers into Customer Match lists. In the v5 overview, firstPartyAndPartnerAudiences is left with only get and list. Developers can still read those audiences and target them. They can no longer build or update them through this API.

The change reverses a capability Google added more than four and a half years ago. PPC Land reported in February 2022 that Google had updated the DV360 API to support creating and updating Customer Match lists. That route now runs to the Data Manager API instead, which Google launched on December 9, 2025 as a single ingestion point for Google Ads, Google Analytics and Display & Video 360.

The Data Manager upgrade guide, which the blog post links and which Google last updated on October 7, 2026, sets out what changes. According to Google, the Data Manager API supports confidential matching and encryption, which the Display & Video 360 API does not. It can send data to several audiences in one request, where the older API needs separate jobs per audience, and it can remove every member of a list in a single call rather than one member at a time. It adds per-ingestion diagnostics including processing status and a match rate range. Partner-level user lists, which the Display & Video 360 API can only retrieve, can be fully managed. Quotas move from project and advertiser limits to project-based quotas with per-request caps, and partner-level users managing an advertiser's audience must declare that access through a login_account setting.

The guide also describes where each API is heading. According to Google, the Display & Video 360 API's Customer Match functions will no longer be updated, while the Data Manager API will receive new Customer Match features. The guide gives no deadline for the switch and maps no individual old method to a new one on its main page.

This is the second Google platform to push audience uploads onto the same path. Google Ads API developers lost the equivalent route earlier this year: Customer Match uploads through the Google Ads API with a developer token stopped working on April 1, 2026, after a notice sent on March 4. The Display & Video 360 case is softer. Nothing in the v5 announcement disables the v4 methods, which remain available for as long as v4 is supported.

The Data Manager API is not identical across products, either. Its v1.7 release in May extended offline conversion ingestion to Display & Video 360, Campaign Manager 360 and Search Ads 360, but IP address-based Customer Match was available only for Google Ads at launch.

Deal IDs change and cached values stop working

The inventory changes are the ones most likely to break existing code. In v4, a single resource called InventorySource covered both negotiated deals and auction packages, and both were targeted with TARGETING_TYPE_INVENTORY_SOURCE. According to the migration guide, v5 splits them.

Deals are now retrieved through two new read-only resources, advertisers.inventorySources and partners.inventorySources, and targeted with a new TARGETING_TYPE_INVENTORY_SOURCE_DEAL through the inventorySourceDetails field. Auction packages are retrieved as targeting options under TARGETING_TYPE_AUCTION_PACKAGE and targeted through a new auctionPackageDetails field. The top-level inventorySources resource from v4, with its create, patch, get, list and editInventorySourceReadWriteAccessors methods, is gone entirely.

The identifiers change with it. "You can't use any previously cached InventorySource resource IDs after migration," according to the migration guide. For agencies that store deal ID mappings in their own databases to automate private marketplace and programmatic guaranteed buying, that means rebuilding those tables rather than simply changing an endpoint path. The ability to create inventory sources and edit who can read or write them through the API also disappears in v5, according to the guide. The overview page still lists inventorySourceGroups with full create, patch and delete methods, so grouping of deals remains under API control.

Digital out-of-home insertion orders become visible

Version 5 adds a new value, OUT_OF_HOME, to the InsertionOrderType enum. According to the migration guide, digital out-of-home insertion orders can now be retrieved through advertisers.insertionOrders.list, where they appear with insertionOrderType set to OUT_OF_HOME. Line items beneath those insertion orders "remain retrievable as they were in v4," according to the guide. Nothing in the documentation describes creating DOOH insertion orders through the API, so the addition is a reporting and retrieval change.

The help page linked from the blog post explains why DOOH sits apart from other Display & Video 360 inventory. According to Google, publishers estimate the size of the audience in front of a screen with an impression multiplier, so "publisher impressions" differ from served impressions, and publisher CPM is calculated on the former. Available exchanges include Perion (Hivestack), Magnite, Place Exchange, Ströer, VIOOH and Vistar, with Vistar limited to non-programmatic guaranteed deals. All DOOH deals must be negotiated with the seller before they reach the platform, CPM revenue models cannot be used, only static images and standard videos hosted in Display & Video 360 are accepted, and geo-targeting relies on IP addresses that may reflect a publisher's server rather than the screen. Display & Video 360 does not measure DOOH itself, according to the page.

YouTube exclusions and the audience targeting split

The blog post lists "full management of advertiser-level YouTube video and channel exclusion targeting" as the first change in v5. The v5 overview shows the advertisers.targetingTypes.assignedTargetingOptions resource with create, delete, get and list methods, which is where such advertiser-level assignments sit. The release notes summary repeats the item but its added and removed tables do not name a new targeting type for it, so the precise mechanics are not spelled out in the published change lists.

Audience targeting for Demand Gen and YouTube ad groups is reorganised. In v4, every kind of audience was managed through a single TARGETING_TYPE_AUDIENCE_GROUP option. In v5, according to the migration guide, ad groups use one targeting type per audience kind: TARGETING_TYPE_COMBINED_AUDIENCE, TARGETING_TYPE_CUSTOM_LIST, TARGETING_TYPE_FIRST_PARTY_AND_PARTNER_AUDIENCE, TARGETING_TYPE_GOOGLE_AUDIENCE and TARGETING_TYPE_LOOKALIKE_AUDIENCE, each with its own details field. Line items keep the single audience group option. Code that reads or writes Demand Gen ad group targeting therefore has to be rewritten, while line item targeting logic does not.

A new top-level lookalikeAudiences resource arrives alongside it, with create, get and list methods. That matches the direction of Structured Data Files: when SDF v11 became generally available on October 8, Google extended Lookalike audience targeting to nearly all ad groups. The TargetingExpansionConfig fields audienceExpansionLevel and audienceExpansionSeedListExcluded are removed from line items and ad groups in v5.

Smaller changes with real migration cost

Several field-level edits accompany the headline items, according to the migration guide and release notes.

Verification vendors. The adloox field in ThirdPartyVerifierAssignedTargetingOptionDetails is replaced by peer39, and the PARTNER_COST_TYPE_ADLOOX and PARTNER_COST_TYPE_ADLOOX_PREBID values become PARTNER_COST_TYPE_PEER39 and PARTNER_COST_TYPE_PEER39_PREBID. The rename follows the business: Peer39 acquired Adloox from Scope3 on June 2, 2026.

YouTube ad fields. On line items, relatedVideoIds in YoutubeAndPartnersSettings becomes relatedVideos. On ads, the trackingUrl field in AudioAd, CommonInStreamAttribute and VideoPerformanceAd is split into trackingUrl and userSpecifiedTrackingUrl. VideoPerformanceAd gains businessName and logo fields, which Google also added to v4 on the same day, together with support for SDF version 10.1.

Synthetic media. AdGroupAd gains a containsSyntheticMedia field in v5. It is separate from the syntheticContentAttestationStatus field that Google added to Creative and AdAsset resources in v4 in July, a field PPC Land reported cannot be returned to unset once written and which arrived ten days before EU AI Act transparency obligations took effect on August 2.

Removed enum values. Values that were already deprecated now disappear from v5 client libraries altogether, according to the guide, which names ContentRatingTier, GoogleAudienceType, SdfVersion and SensitiveCategory among the affected enums. The SensitiveCategory clean-up follows Google's decision that most sensitive categories could no longer be excluded from October 1, 2026. AdGroup also gains adSource and creativeAssignments fields, AdGroupAd gains parentCreativeId, and the FraudOption enum gains AD_IMPRESSION_FRAUD_75.

No sunset date for v4, yet

Google has not said when v4 will stop working. Its announced deprecations page lists no deprecation or sunset date for v4, and neither the blog post nor the migration guide gives one. The beta label also matters: v5 may still change in ways that break code, according to the blog post.

History offers some guide to the pace. According to the same deprecations page, v1 was deprecated on March 13, 2023 and sunset on September 14, 2023; v2 was deprecated on February 15, 2024 and sunset on September 3, 2024; v3 was deprecated on April 2, 2025 and sunset on October 7, 2025. By PPC Land's calculation, each version therefore lasted between six and seven months from deprecation to shutdown. Version 4 itself became generally available on March 27, 2025, when Mulchay described it as the recommended version, and v3 was deprecated six days later. If Google follows that pattern, a v4 deprecation notice would arrive once v5 leaves beta, and v4 integrations would have roughly half a year from that point. Google has not committed to that timeline.

Why it matters for buyers and agencies

Display & Video 360 is Google's enterprise demand-side platform, and its API is the layer that agencies, trading desks and ad tech vendors use to automate campaign setup, targeting and reporting at scale. Version changes in this API rarely make headlines, but they set the engineering calendar for teams that keep tooling running across hundreds of advertisers.

Version 5 combines several of the threads PPC Land has followed through 2025 and 2026. The API gained YouTube and Demand Gen asset management in October 2025 and full Demand Gen campaign management in June 2026. Google has been consolidating first-party data ingestion into the Data Manager API across its products, and in September added 14 alpha methods to the Google Marketing Platform Admin API for managing user groups through code. Brand safety controls in Display & Video 360 have been narrowed, and the verification vendor market has consolidated. Each of those shifts now has a corresponding change in v5.

For anyone maintaining an integration, the work divides cleanly. Customer Match pipelines need a second API, its own authentication model and its own quotas. Deal and auction package targeting needs new IDs and new targeting types. Demand Gen and YouTube ad group audience code needs to be rewritten into five separate types. The rest is renaming. None of it is required today, and Google has given no date by which it will be.

Timeline

Summary

Who: Google's Display & Video 360 API Team, with the announcement signed by Trevor Mulchay, affecting agencies, trading desks and ad tech vendors that automate Display & Video 360 through its API.

What: Version 5 of the Display & Video 360 API entered public beta. It removes Customer Match audience creation and member management in favour of the Data Manager API, replaces inventory source handling with separate deal and auction package types and new IDs, adds retrieval of digital out-of-home insertion orders, moves YouTube video and channel exclusions to the advertiser level, splits Demand Gen and YouTube ad group audience targeting into five types and renames Adloox fields to Peer39.

When: The beta opened on October 22, 2026. Google has set no deprecation or sunset date for v4, and breaking changes to v5 remain possible while it is in beta.

Where: On the Display & Video 360 API service at displayvideo.googleapis.com, documented on the Google Ads Developer Blog, the Google for Developers reference pages, the release notes and the v4 to v5 migration guide.

Why: Google is consolidating first-party audience ingestion into the Data Manager API, which it says supports confidential matching, encryption and multi-audience requests that the Display & Video 360 API does not, while bringing the API in line with changes to deals, DOOH buying, YouTube controls and verification vendors made elsewhere in the platform.