{"id":2859,"date":"2026-08-30T19:03:21","date_gmt":"2026-08-30T19:03:21","guid":{"rendered":"https:\/\/dmarketertayeeb.com\/blog\/dv360-api-sdf-october-2026-changes\/"},"modified":"2026-08-30T19:03:21","modified_gmt":"2026-08-30T19:03:21","slug":"dv360-api-sdf-october-2026-changes","status":"publish","type":"post","link":"https:\/\/dmarketertayeeb.com\/blog\/dv360-api-sdf-october-2026-changes\/","title":{"rendered":"DV360 API and SDF October 2026 Changes: Migration Checklist"},"content":{"rendered":"\n\n\n

Deadlines:<\/strong> Google announced three unversioned Display & Video 360 API and Structured Data File changes. On October 1, 2026<\/strong>, digital-content-label exclusions and the majority of sensitive-category exclusions change. On October 12<\/strong>, 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.<\/p>\n\n\n\n\n\n\n\n

\u201cUnversioned\u201d 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.<\/p>\n\n\n\n\n\n\n\n

I checked Google\u2019s Ads Developer Blog and DV360 reference pages on August 30, 2026. DMT\u2019s Google Ads API v25.1 migration guide<\/a> covers a separate versioned Google Ads API\/Shopping workflow; this page is the narrower DV360 API\/SDF checklist.<\/p>\n\n\n\n\n\n\n\n

The three October changes at a glance<\/h2>\n\n\n\n\n\n\n\n
Effective date<\/th>Change<\/th>Likely integration surface<\/th>First action<\/th><\/tr><\/thead>
October 1, 2026<\/td>Specific digital content labels can no longer be excluded with targeting.<\/td>API target type TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION<\/code>; Line Item SDF column Digital Content Labels - Exclude<\/code>.<\/td>Inventory values and update the serializer\/validator for the documented ?<\/code>\/empty boundary.<\/td><\/tr>
October 1, 2026<\/td>The majority of sensitive categories can no longer be excluded with targeting.<\/td>API target type TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION<\/code>; Line Item SDF brand-safety settings.<\/td>List deprecated enum values, stop sending unsupported custom settings and obtain a brand-safety owner decision.<\/td><\/tr>
October 12, 2026<\/td>YouTube responsive ads need a business name and logo if the parent advertiser has no defaults.<\/td>Ad SDF Business Name<\/code> and Logo Asset IDs<\/code> columns; API\/ad creation workflows.<\/td>Check advertiser defaults or require valid values in every affected upload path.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n\n\n\n

October 1: digital content-label exclusions<\/h2>\n\n\n\n\n\n\n\n

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<\/code> and the Line Item SDF column Digital Content Labels - Exclude<\/code>. It says the column will accept only ?<\/code>; otherwise it must be empty. Uploading another label value will result in an error.<\/p>\n\n\n\n\n\n\n\n

  1. Export the current Line Item SDF and retain the download date, advertiser and line-item scope.<\/li>
  2. Search serializers, templates, validation rules and API code for the targeting type and column.<\/li>
  3. Classify every current value as documented ?<\/code>, empty or unsupported.<\/li>
  4. Update the file generator and pre-upload validator before sending a production file.<\/li>
  5. Run a controlled validation\/upload path and compare the downloaded value with the intended state.<\/li><\/ol>\n\n\n\n\n\n\n\n

    October 1: sensitive-category exclusion changes<\/h2>\n\n\n\n\n\n\n\n

    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.<\/p>\n\n\n\n\n\n\n\n

    For SDFs, Brand Safety Sensitivity Setting<\/code> will no longer allow Use custom<\/code>, and Brand Safety Custom Settings<\/code> 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\u2019s suitability approach.<\/p>\n\n\n\n\n\n\n\n

    For campaign context, DMT\u2019s target-bidding change guide<\/a> and language-targeting migration guide<\/a> cover separate settings. They do not override DV360\u2019s deprecation rules.<\/p>\n\n\n\n\n\n\n\n

    October 12: YouTube responsive-ad business identity<\/h2>\n\n\n\n\n\n\n\n

    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<\/code> and Logo Asset IDs<\/code> columns. If defaults are assigned at the advertiser level and the columns are empty, the ad can inherit those values on save.<\/p>\n\n\n\n\n\n\n\n