Display & Video 360 · Status at source date: Newsletter archive
DV360 API drops several brand-safety exclusions in October
From 1 October, the Display & Video 360 API and Structured Data Files will no longer support exclusions for specific digital content labels and most sensitive categories. From 12 October, YouTube responsive ads created or updated through these routes must also include a business name and logo unless defaults already exist at advertiser level.
This update uses a PMC cover because no suitable source image was available when checked on 8 Sept 2026. Available source and video links are retained.
What changed
Google's developer announcement sets out two October 2026 milestones affecting Display & Video 360 integrations. From 1 October, specified digital-content-label exclusions and most sensitive-category exclusions cease to be supported through the API and Structured Data Files. From 12 October, YouTube responsive ads need a business name and logo when created or updated unless advertiser-level defaults supply them. Trevor Mulchay of the Display & Video 360 API Team signs the original announcement.
The linked deprecation details distinguish how these changes appear in files. Some obsolete values will no longer be accepted, while a previously used custom brand-safety column will return empty on download. The branding requirement can also be satisfied through inherited advertiser defaults. These are different behaviours to test: an upload failure is visible immediately, but a changed or empty export can pass through downstream reporting unnoticed.
An agency using a reusable trafficking sheet should trace where the affected values originate and where they are consumed. Removing an unsupported field from the upload is only part of the job if the client brief or internal audit still assumes that control is being applied. Likewise, an inherited logo needs to be the right one for the advertiser. Technical acceptance does not establish that the resulting campaign configuration matches the intended brand governance.
Why it matters for advertisers
This is a coordinated change for integration owners, trafficking teams and the people responsible for brand suitability. The useful deliverable is a field-by-field transition record and an agreed treatment of any control the workflow can no longer express. Check the resulting configuration as well as whether a file or request succeeds, so that a technical fix does not conceal a change in campaign oversight.
What to check next
- Identify every API request, SDF template and downstream report that uses the affected exclusion fields or YouTube responsive-ad branding fields.
- Check the exact accepted values and recommended actions in Google’s deprecation reference, then test representative creation, update and export cases.
- Assign an owner for any changed brand-suitability process and verify the advertiser’s business-name and logo defaults before the October milestones.
Sources & contributor credit
- Newsletter coverage · Paid Media Collective newsletter
Original newsletter text, contributor labels and media for this update.
- Source referenced in newsletterGoogle Ads Developer Blog
Linked from the original newsletter. The source publication date has not been independently confirmed.
- Supporting primary sourceDV360 announced deprecations
Read October 1 and October 12 entries linked from the original developer announcement.
Original creator unverified
Trevor Mulchay is the signed announcement author, representing the Display & Video 360 API Team. Google publishes the technical reference. No individual visual author is asserted.
Attribution evidence and limitations
Cached developer-blog extraction contained navigation but no body. Recovered and read the complete announcement through web, including Trevor Mulchay’s signature. Followed and read the relevant October entries in the official Announced Deprecations reference. No integration was changed or executed.
All original source/profile URLs and original archive dates retained; additional recovered evidence is identified explicitly.
No newsletterVisuals or sourceVisuals are attached. The developer announcement has an author-photo link, but that photo was not inspected or used to infer identity. Authorship is based on the explicit text signature.
- Archived newsletter text compared; not a fresh newsletter-page review.
- Cached developer-blog extraction contained navigation but no body. Recovered and read the complete announcement through web, including Trevor Mulchay’s signature. Followed and read the relevant October entries in the official Announced Deprecations reference. No integration was changed or executed.
Attribution checked . This is a review date, not the original publication date.
- 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.
Original newsletter text and archive evidence
DV360 API drops several brand-safety exclusions in October
From 1 October, the Display & Video 360 API and Structured Data Files will no longer support exclusions for specific digital content labels and most sensitive categories. From 12 October, YouTube responsive ads created or updated through these routes must also include a business name and logo unless defaults already exist at advertiser level. For you, this means integrations may lose controls or fail validation on fixed dates, so inventory every affected field and assign replacement governance before October deployments.
Source captured . No explicit first-contributor label was provided for this update.
