Display & Video 360 API v5 beta: the changes developers need to check
Google’s DV360 API v5 release notes and v4-to-v5 migration guide outline changes to advertiser-level YouTube exclusions, DOOH insertion orders, audience targeting, Customer Match, and deal identifiers. The practical impact varies: some changes add controls, others narrow what the API can manage, and some require moving a workflow to another Google API. Here’s what the documentation confirms—and what teams should assess before migrating.
YouTube exclusions and DOOH insertion orders
The Google Ads Developer Blog announcement says v5 supports managing advertiser-level YouTube video and channel exclusions. For teams, that means an integration can work with exclusions at the advertiser level; it does not mean those exclusions should be changed automatically, or that one policy suits every campaign. Treat the new control as an API capability, then apply your existing approval and policy checks to any operation that uses it.
DOOH is a more limited change. The v5 materials describe insertion-order access as read-only, so the documented capability is retrieval and inspection—not full create-and-update management. If your workflow depends on writing to DOOH insertion orders, don’t design around that assumption: confirm the available operations in the v5 API reference.
Audience targeting differs for Demand Gen and YouTube ad groups
The migration guide describes a specific v4-to-v5 change for Demand Gen and YouTube ad-group audience targeting. In v4, those ad groups used TARGETING_TYPE_AUDIENCE_GROUP; in v5, they use separate targeting types for audience categories, with corresponding details fields. Line-item targeting remains distinct: the guide says it retains the audience-group option.
That distinction matters when migrating shared targeting code. Update request and response handling for the affected ad groups, but don’t apply the same transformation to line items simply because both involve audiences. The migration guide identifies which targeting model changes; use it to scope the code change to the relevant operations.
The v5 API reference also lists a top-level lookalikeAudiences resource and its supported methods. Its presence establishes that the resource exists, not that a particular account is eligible, that audiences will be available, or that the resource supports capabilities beyond its documented methods and fields. Confirm those details in the v5 API reference before building a workflow around them.
Customer Match uses Data Manager
The v5 migration guide identifies the removal of v4 DV360 API methods for creating and populating Customer Match audiences and directs developers to Google’s Data Manager API for that work. For an existing integration, this is a change of API boundary: the Customer Match data-ingestion steps move to Data Manager, while the documentation does not say that all audience targeting or campaign management moves out of DV360.
Find any code that calls the removed methods and map only those steps to the Data Manager API documentation. Keep data ingestion separate from DV360 campaign operations, and confirm Data Manager’s supported methods and requirements before choosing a replacement flow.
Deal IDs and migration checks
The v5 migration documentation describes changes to deal-ID handling. A deal ID stored from v4 should not be assumed to work unchanged in v5. The right migration path depends on the deal operation: follow the guide’s instructions for that operation, and refresh or resolve identifiers through the documented v5 flow rather than relying on cached v4 values.
Before switching production traffic, compare your integration’s v4 calls with the migration guide and release notes. Focus the review on affected request and response fields, removed methods, and persisted identifiers. Then test the reads and writes your integration actually uses against v5. These are migration safeguards, not additional API requirements stated by Google.
Sources
- Google Ads Developer Blog: Announcing the beta launch of Display & Video 360 API v5
- Display & Video 360 API v5 migration guide
- Display & Video 360 API release notes
- Display & Video 360 API v5 reference
- Google Data Manager API documentation
- PPC Land: Google’s DV360 API v5 beta drops Customer Match audience management
display & video api v5 beta