Deadlines: Google announced three unversioned Display & Video 360 API and Structured Data File changes. On October 1, 2026, digital-content-label exclusions and the majority of sensitive-category exclusions change. On October 12, YouTube responsive-ad uploads require a business name and logo when the parent advertiser has no defaults. Audit your fields and validators before those dates.
“Unversioned” means these changes can affect existing integrations without a new API-version migration. It does not prove that every account or file will fail automatically. Your API version, SDF version, targeting values, advertiser defaults and upload path still need a read-back.
I checked Google’s Ads Developer Blog and DV360 reference pages on August 30, 2026. DMT’s Google Ads API v25.1 migration guide covers a separate versioned Google Ads API/Shopping workflow; this page is the narrower DV360 API/SDF checklist.
The three October changes at a glance
| Effective date | Change | Likely integration surface | First action |
|---|---|---|---|
| October 1, 2026 | Specific digital content labels can no longer be excluded with targeting. | API target type TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION; Line Item SDF column Digital Content Labels - Exclude. | Inventory values and update the serializer/validator for the documented ?/empty boundary. |
| October 1, 2026 | The majority of sensitive categories can no longer be excluded with targeting. | API target type TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION; Line Item SDF brand-safety settings. | List deprecated enum values, stop sending unsupported custom settings and obtain a brand-safety owner decision. |
| October 12, 2026 | YouTube responsive ads need a business name and logo if the parent advertiser has no defaults. | Ad SDF Business Name and Logo Asset IDs columns; API/ad creation workflows. | Check advertiser defaults or require valid values in every affected upload path. |
October 1: digital content-label exclusions
Google says the API will no longer offer the affected digital-content-label exclusion options. The deprecation page names TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION and the Line Item SDF column Digital Content Labels - Exclude. It says the column will accept only ?; otherwise it must be empty. Uploading another label value will result in an error.
- Export the current Line Item SDF and retain the download date, advertiser and line-item scope.
- Search serializers, templates, validation rules and API code for the targeting type and column.
- Classify every current value as documented
?, empty or unsupported. - Update the file generator and pre-upload validator before sending a production file.
- Run a controlled validation/upload path and compare the downloaded value with the intended state.
October 1: sensitive-category exclusion changes
Google says the majority of sensitive categories will no longer be excludable through targeting. The deprecation page lists affected values including adult, alcohol, derogatory, downloads/sharing, drugs, gambling, politics, profanity, religion, sensitive social issues, shocking, suggestive, tobacco, tragedy, transportation accidents, violence and weapons. The exact live enum page is the authority; do not infer that every brand-suitability control disappears.
For SDFs, Brand Safety Sensitivity Setting will no longer allow Use custom, and Brand Safety Custom Settings will no longer be supported and will download as an empty value. Stop sending those fields as if they still have the old meaning. Ask the brand-safety owner what replacement controls and review evidence are required before altering the campaign’s suitability approach.
For campaign context, DMT’s target-bidding change guide and language-targeting migration guide cover separate settings. They do not override DV360’s deprecation rules.
October 12: YouTube responsive-ad business identity
Starting October 12, Google says a business name and logo are required when creating or updating YouTube responsive ads if the parent advertiser has no default values. The deprecation page maps this to the Ad SDF Business Name and Logo Asset IDs columns. If defaults are assigned at the advertiser level and the columns are empty, the ad can inherit those values on save.
- Inventory every YouTube responsive-ad create/update path, including bulk Ad SDFs.
- Check the parent advertiser’s default business name and logo asset configuration.
- If defaults are absent, require valid values in the file/API payload and validate them before upload.
- Retain the advertiser, ad, asset IDs, source file/version and post-save read-back.
- Do not copy a business identity from another advertiser without an approved owner and asset record.
A field-level migration workflow
- Snapshot: Export current Line Item/Ad SDFs, API configuration, validators and effective advertiser defaults.
- Search: Find target types, enum names and SDF columns in code, templates, jobs and documentation.
- Decide: Assign owners for digital-label, sensitive-category and business-identity changes; do not let a parser silently choose a brand-safety policy.
- Patch: Update serializers and validators for
?/empty, deprecated sensitive values, removed custom settings and required identity fields. - Test: Use a controlled advertiser or approved file path, inspect API/SDF errors and compare the result with the intended state.
- Release: Record source date, code diff, reviewer, account scope, file checksum/version and downloaded read-back.
- Monitor: Watch failed uploads, API responses and ad status after each effective date; do not infer delivery or performance from a field error alone.
Keep the release evidence easy to audit: DMT’s site SEO audit checklist offers a general evidence structure, but it cannot validate DV360 fields or decide a brand-safety policy.
Keep the surrounding automation layer separate from the field migration. DMT’s Google Ads automation guide discusses broader automation choices, while the Demand Gen and asset update provides campaign-surface context. Neither replaces the live DV360 deprecation page or a successful upload read-back.
Frequently asked questions
Does October 1 retire the whole DV360 API?
No. Google announced three unversioned feature changes. The article identifies affected targeting types and SDF columns; it does not claim that the complete API or every targeting feature is retired.
What should the digital-content-label SDF column contain after October 1?
Google’s deprecation page says Digital Content Labels - Exclude will accept only ?; otherwise it must be empty. Confirm the current reference page and validate your generated file before upload.
Are all brand-safety controls gone after the sensitive-category change?
No. Google says the majority of sensitive categories can no longer be excluded using the named targeting type and lists affected enum/SDF changes. Your broader suitability design needs an owner decision; do not infer that every safety control disappears.
When is a business name and logo required for a YouTube responsive ad?
Starting October 12, 2026, Google says the values are required when creating or updating a YouTube responsive ad if default values are not assigned to the parent advertiser. If defaults exist, empty ad-level columns can inherit them on save. Check the actual advertiser and SDF/API path.
