Key details

  1. October 22, 2026: DV360 API v5 public beta launched.
  2. Inventory deals and auction packages split into separate retrieval and targeting paths; cached v4 IDs cannot be reused.
  3. Demand Gen/YouTube ad groups move from a single audience-group targeting assignment to per-audience-type assignments.
  4. Customer Match write methods removed from DV360 v5; Google directs integrators to Data Manager API.
  5. Advertiser-level YouTube video/channel exclusions and Digital Out of Home insertion orders gain additional API support.
  6. V5 remains beta and may receive breaking changes; v4 is still the latest GA version.

What builders should take away

  1. Inventory all DV360 v4 calls, especially inventorySources, targeting, Customer Match and YouTube ad groups.
  2. Build a migration map for deals versus auction packages; invalidate cached v4 inventory-source IDs when testing v5.
  3. Migrate Customer Match write workflows to the Data Manager API rather than expecting equivalent v5 endpoints.
  4. Test client-library and enum changes with representative campaigns before production rollout.
  5. Track beta release notes and avoid presenting this as a mandatory immediate v4 shutdown.

What changed

On October 22, 2026 Google launched Display & Video 360 API v5 in public beta. The version separates inventory-source deals from auction packages, changes resource IDs and targeting types, refactors audience targeting on Demand Gen and YouTube ad groups, and removes firstPartyAndPartnerAudiences methods used to create or edit Customer Match audiences. It also adds advertiser-level YouTube video/channel exclusion management and Digital Out of Home insertion-order support. Google's public documentation warns that breaking changes can still occur during beta; v4 remains the latest general-availability API.

Why it matters

This is an integration migration, not just a new set of features. Code that reuses cached inventory-source IDs, sends v4 audience-group assignments to Demand Gen/YouTube ad groups, or writes Customer Match members through DV360 v5 will need changes. Agencies and SaaS tools managing many advertisers should run dual-version tests and avoid treating the public beta as a forced v4 sunset.

Inventory IDs and targeting are not portable

In v4, InventorySource resources represent both deals and auction packages, targeted under TARGETING_TYPE_INVENTORY_SOURCE. In v5, inventory deals use advertiser/partner inventorySources and TARGETING_TYPE_INVENTORY_SOURCE_DEAL; auction packages use targetingTypes.targetingOptions and TARGETING_TYPE_AUCTION_PACKAGE. Google explicitly says previously cached InventorySource IDs cannot be reused after migration. Reconcile IDs and targeting records rather than merely changing /v4/ to /v5/.

Demand Gen and YouTube audiences are refactored

For Demand Gen and YouTube ad groups, v5 replaces the single TARGETING_TYPE_AUDIENCE_GROUP assignment with distinct assigned targeting options for combined audiences, custom lists, first-party/partner audiences, Google audiences and lookalikes. Line items continue using TARGETING_TYPE_AUDIENCE_GROUP, so a generic targeting adapter must branch by resource type. Customer Match creation and membership editing move out of DV360 v5 to the Data Manager API.

New capabilities come with compatibility work

V5 adds write access to advertiser-level YouTube video/channel exclusions, Digital Out of Home insertion-order handling, lookalike audience resources and fields for generated ad creatives. Integrations may also need to replace Adloox/Scope3 references with Peer39, update YouTube related-video fields and handle synthetic-media flags. Review the exhaustive official release notes before changing production clients.

Public beta is not a mandatory cutover

Google calls v5 an open beta and warns its schema can change during beta. Its published release notes still identify v4 as the latest generally available API. Upgrade client libraries and test payloads against v5 in a non-production integration before rolling out; monitor release notes for beta breaking changes and the eventual v4 sunset policy.

What to watch next

  • V5 beta schema changes and general availability.
  • Google's future v4 sunset timetable.
  • Data Manager API permissions, limits and migration guidance for Customer Match.
  • New Digital Out of Home and YouTube exclusion tooling adoption.

Still unclear

  • The beta API may introduce further breaking changes.
  • Google has not established a mandatory v4 migration date in the October 22 announcement.
  • Operational migration cost depends on each integration's use of inventory IDs, audiences and Customer Match.

Sources

Direct reading behind this dossier.

3 sources

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment