DV360 API v5 Adds Responsive YouTube Ads on Nov 12
Google's November 12, 2026 update to DV360 API v5 enables programmatic management of responsive YouTube ads, while line items and ad groups still require SDF or UI workflows.
On November 12, 2026, Google updated Display & Video 360 (DV360) API v5 to manage responsive YouTube ads through the advertisers.adGroupAds service using the videoPerformanceAd field. Google first released DV360 API v5 in public beta on October 22, 2026, and the API remains in public beta where breaking changes may still be introduced.12
Supported and unsupported YouTube line items in v5
Responsive YouTube ads managed through the API can serve across in-stream (bumper, skippable, non-skippable), Shorts, and in-feed formats depending on the line item subtype and ad format controls. However, developers must still create and update YouTube line items, ad groups, and their targeting in the DV360 interface or through Structured Data Files (SDF) uploads.1
| API v5 Support Status | YouTube Line Item and Ad Types |
|---|---|
| Supported | YouTube & partners efficient reach, non-skippable reach, target frequency, video views |
| Unsupported | Single-format YouTube ads, YouTube Programmatic Non-Guaranteed, Guaranteed instant deals |
Workflow for deploying responsive YouTube ads
Google's recommended sequence starts with uploading Line Item and Ad Group SDFs to create the campaign structure, followed by managing creative assets via advertisers.adAssets (using advertisers.adAssets.bulkCreate for existing YouTube videos or advertisers.adAssets.upload for images), and finally calling advertisers.adGroupAds.create with the videoPerformanceAd field.1
Breaking changes: Customer Match and inventory IDs
DV360 API v5 removes three Customer Match methods: firstPartyAndPartnerAudiences.create, firstPartyAndPartnerAudiences.editCustomerMatchMembers, and firstPartyAndPartnerAudiences.patch. Google now directs advertisers to migrate Customer Match audience creation and membership management to the Data Manager API.3
Previously cached inventory source IDs cannot be reused after upgrading to v5 because identifiers for existing deals and auction packages have changed. Version 5 also adds the containsSyntheticMedia field to the AdGroupAd resource and introduces support for creating and retrieving Digital Out of Home insertion orders using the OUT_OF_HOME type.3

Targeting changes in DV360 API v5
| Targeting Category | DV360 API v5 Implementation |
|---|---|
| Inventory source deals | TARGETING_TYPE_INVENTORY_SOURCE_DEAL |
| Auction packages | TARGETING_TYPE_AUCTION_PACKAGE |
| YouTube and Demand Gen audiences | Individual assigned targeting options per audience category (replaces TARGETING_TYPE_AUDIENCE_GROUP used in v4). |