Tag Archives: sdf

Launching Structured Data Files QA format and v7.1

Today we’re announcing the general availability of the Structured Data Files (SDF) v7.1 and the open beta of our new QA format. Both are available to all Display & Video 360 users.

While in open beta, the QA format might be updated without notice. These updates will be reflected in the documentation. We will announce the QA format release to general availability at a later date.

What’s new in v7.1?

All users can now use SDF v7.1 to upload and download SDFs in the Display & Video 360 UI, and to download SDFs through the Display & Video 360 API.

The update from v7 to v7.1 includes the following changes:

  • Added new TrueView Video Ad settings to the Line Item resource.
  • Renamed three insertion order columns to use “Kpi” instead of “Performance Goal.”
  • Introduced a new objective column to the insertion order resource. This column is currently in beta and only available to participating clients.

Full details on the changes made in v7.1 can be found in our Structured Data Files release notes. If you are currently using SDF v5.5 or v6, follow the instructions on our v7 migration guide first before migrating to v7.1.

What’s the SDF QA format?

The new SDF QA format provides SDFs with human-readable data to make it easier to review Display & Video 360 resource settings in bulk.

All supported SDF versions offer this format through two new file types: Line Item - QA and YouTube Ad Group - QA. These file types provide the same information as standard format files of the same version, and convey a subset of that information using display name values instead of numeric IDs.

SDF QA files are read-only and cannot be uploaded to modify or create Display & Video 360 resources. Currently, QA format files are only available through the Display & Video 360 interface.

We are accepting feedback on the QA format while it is in open beta. To submit feedback, please use the Send Feedback button on the relevant reference documentation page. We will consider suggested updates before releasing the QA format to general availability.

If you run into issues or need help with this new format or version, please follow the instructions on our support guide or contact us using our contact form.

Deprecation of Structured Data Files v5.5

Today we’re announcing the deprecation of Structured Data Files (SDF) v5.5. This version will sunset on October 3, 2024.

Migrate to v7, the most recent version, by the sunset date. Instructions on how to migrate to v7 can be found in our migration guide.

Once v5.5 is sunset:

  • The default version of partners and advertisers using those versions will be updated to the oldest supported version, v6.
  • sdfdownloadtasks.create requests using the sunset version in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our support contact form.

Sunsetting Display & Video 360 Entity Read Files on October 31, 2024

On October 31, 2024, Display & Video 360 Entity Read Files (ERFs) will sunset. Public and private ERFs won’t be generated after this date. Migrate to the Display & Video 360 API to continue programmatically retrieving Display & Video 360 resource configurations.

ERFs were deprecated in June 2021. Since then, we’ve made updates to help you migrate from ERFs:

See our migration guide for more information on migrating from ERFs to the Display & Video 360 API.

If you have questions regarding these changes, please contact us using our support contact form.

Launching Structured Data Files v7

Today we’re announcing the general availability of Structured Data Files (SDF) v7. All users can now use v7 when uploading and downloading SDFs in the Display & Video 360 UI or downloading SDFs through the Display & Video 360 API.

The following material and superficial changes have been made from v6 to v7 to decouple SDF from the deprecated Entity Read Files tool and add support for newer Display & Video 360 features:

Full details on the changes made in v7 can be found in our Structured Data Files release notes. Instructions on migrating from SDF v6 to v7 can be found in our migration guide.

If you run into issues or need help with this new version, please contact us using our support contact form.

Introducing a new way to discover Display & Video 360 bulk tools

Today we’re announcing a new guide to help Display & Video 360 users discover available bulk tools that they can use to optimize their integrations.

The guide offers a high-level overview of each of the following tools that allow you to integrate with Display & Video 360 at scale:

The guide also provides a recommendations page that can help you choose the right bulk tool based on your needs and circumstances and a page proposing potential platform-wide integrations using multiple bulk tools.

You can navigate to this new guide from the existing Display & Video 360 API, Bid Manager API, or Reporting Data Transfer documentation using the Discover Bulk Tools tab at the top of the page.

Deprecation of Structured Data Files v5.4

Today we’re announcing the deprecation of Structured Data Files (SDF) v5.4. This version will be fully sunset on February 27, 2024.

Please migrate to v6, the most recent version, by the sunset date. Once v5.4 is sunset::

  • The default version of partners and advertisers using those versions will be updated to the oldest supported version, v5.5.
  • sdfdownloadtasks.create requests declaring the sunset versions in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our support contact form.

Deprecating outcome-based buying in Display & Video 360 API and Structured Data Files on August 1, 2023

On August 1, 2023, outcome-based buying will be deprecated in Display & Video 360. After this date, all resources using outcome-based buying will be archived, line items using outcome-based buying will stop serving, and you will no longer be able to create resources that use outcome-based buying.

Outcome-based buying is set at the insertion order level, and is used by their child line items. Outcome-based buying is set in the following ways:

Effective August 1, 2023, all relevant insertion orders and line items will be archived. Display & Video 360 API requests creating new insertion orders and line items using outcome-based buying will return 400 errors. Structured Data File uploads will fail for rows attempting to do the same.

Read more about this change on our Announced Deprecations page.

If you have questions regarding these changes, please contact us using our support contact form.

Launching Structured Data Files v6

Today we’re launching Structured Data Files (SDF) v6. This version can now be used when uploading and downloading SDFs in the Display & Video 360 UI or downloading SDFs through the Display & Video 360 API.

Significant changes have been made from SDF v5.5 to v6:

Full details on the changes made in v6 can be found in our Structured Data Files release notes.

Assign v6 as the default SDF version in Display & Video 360 at the Partner or Advertiser level. Generate v6 SDFs when using the Display & Video 360 API with the new SdfVersion value SDF_VERSION_6.

If you run into issues or need help with this new version, please contact us using our support contact form.

Display & Video 360 optimized targeting rollout extended through early May 2023

The period for the gradual rollout of optimized targeting in Display & Video 360 has been extended and will now complete in early May instead of mid-April as previously announced.

The extension of this rollout does not alter any of the changes to the Display & Video 360 API and Structured Data Files (SDFs), so users should continue to apply the recommendations detailed in the previous blog post to prepare.

If you have questions regarding these changes or need help with these new features, please contact us using our support contact form.

Rescheduled changes to targeting expansion in Display & Video 360 API and Structured Data Files

On March 25, 2023, optimized targeting will gradually begin replacing targeting expansion for all display, video, and audio line items in Display & Video 360. By mid-April, optimized targeting will be live for all partners. These changes will be reflected in Display & Video 360 API and Structured Data Files (SDF), and might impact your existing implementation and the success of your requests.

Similar changes were previously announced and subsequently postponed late last year, but these rescheduled changes have some important differences. Please read this blog post in its entirety if you use the targetingExpansion field in the Display & Video 360 API or the “Audience Targeting - Similar Audiences” column in SDF to configure your Display & Video 360 line items.

Changes in the Display & Video 360 API

Optimized targeting will be configured using the existing targetingExpansion field and TargetingExpansionConfig object in Display & Video 360 API LineItem resources. Once optimized targeting replaces targeting expansion for your partner, these fields will be used to manage optimized targeting in the following ways:

  • The targetingExpansionLevel field will only support two possible values:
    • NO_EXPANSION: optimized targeting is off.
    • LEAST_EXPANSION:optimized targeting is on.
  • Optimized targeting will not automatically be turned on for eligible line items created or updated by the Display & Video 360 API. NO_EXPANSION will be the default value for the targetingExpansionLevel field and will be automatically assigned if you do not set the field.
  • If you set targetingExpansionLevel to one of the following values, it will automatically be reset to LEAST_EXPANSION:
    • SOME_EXPANSION
    • BALANCED_EXPANSION
    • MORE_EXPANSION
    • MOST_EXPANSION
  • excludeFirstPartyAudience will be deprecated. If set to true, it will automatically be reset to false.
  • If you turn on optimized targeting for an ineligible line item, the request will not return an error and the change will persist. However, you must update the line item to be eligible before it will use optimized targeting when serving.

We will also update the configurations of existing line items as follows:

To aid in this migration, we are adding a new LineItemWarningMessage value to Display & Video 360 API v1 and v2. The warning value DEPRECATED_FIRST_PARTY_AUDIENCE_EXCLUSION will be added to the warningMessages field of line items that have excludeFirstPartyAudience set to true.

Changes in the Structured Data Files

Targeting expansion is currently set using the “Audience Targeting - Similar Audiences” column in Line Item and Insertion Order SDF formats. These columns will be deprecated when optimized targeting replaces targeting expansion. When downloading SDFs, this column will always be set to FALSE and when uploading SDFs, the value of this column will be ignored.

Eligible line items created using SDF upload will have optimized targeting turned off by default. You will not be able to manage optimized targeting configurations using existing SDF versions and must instead use the Display & Video 360 UI or API.

Upcoming SDF v6 will support optimized targeting configurations. The SDF v6 launch will be announced on the Google Ads Developer Blog and in the SDF release notes.

Preparing for these changes

To prepare for these changes, we recommend the following:

  • Turn on automated bidding for line items currently using fixed bidding with targeting expansion before March 25, 2023 so that they are eligible for optimized targeting.
  • Update your Display & Video 360 API integration to directly exclude any first-party audiences using audience targeting before March 25, 2023 to account for the deprecation of the excludeFirstPartyAudience field.
  • Update your Structured Data Files integration to no longer use the “Audience Targeting - Similar Audiences” column in Line Item and Insertion Order SDFs before March 25, 2023 to account for the column deprecation.

If you have questions regarding these changes or need help with these new features, please contact us using our support contact form.