Tag Archives: dv360_api

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.

- Trevor Mulchay, Display & Video 360 API Team

Changes coming to Display & Video 360 API in May and June 2023

Throughout May and June 2023, we will be making four changes in the Display & Video 360 API that may impact your integration. These changes and relevant dates are as follows, with links to further details:

With the announcement of these deprecations, we are launching a new Announced Deprecations page listing all announced deprecations and sunsets. This includes version deprecations and API-wide feature deprecations.

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

- Trevor Mulchay, Display & Video 360 API Team

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.

- Trevor Mulchay, Display & Video 360 API Team

Deprecation of Display & Video 360 API v1

Today we are deprecating Display & Video 360 API v1. While deprecated, v1 will no longer be updated. We will sunset v1 on September 14, 2023. Migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about new features available in v2, such as the ability to retrieve YouTube & Partners line items, ad groups, and ads. Follow the steps in our v2 migration guide to help you migrate from v1 to v2.

After supporting and regularly updating Display & Video 360 API v1 for over three years, we are excited to introduce new Display & Video 360 API features using a more consistent version release and sunset schedule. A projected schedule will be announced on this blog at a later date.

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

- Trevor Mulchay, Display & Video 360 API Team

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.

- Trevor Mulchay, Display & Video 360 API Team

Updating Display & Video 360 API creative asset media ID values on April 5, 2023

On April 5, 2023, we will be updating mediaId values in the Display & Video 360 API for all uploaded Asset resources and requiring that customers use these new ID values when associating assets with Creative resources.

What is changing?

We are changing the ID space that is used to identify creative assets. This means that assets previously uploaded to Display & Video 360, such as image, video, and HTML files, will now have new IDs.

This change will have the following effects:

  • Existing mediaId values of assets associated with a creative resource through the assets field will automatically be updated to use this new ID space.
  • Attempting to use any previously generated mediaId values to associate an asset to a creative will return an error.

What do I need to do?

In preparation for this change, we recommend that you stop using any cached media IDs when creating or updating creatives, and instead upload assets immediately before using them for creative production.

After April 5, 2023, we recommend updating any cached media IDs to the new values by retrieving them from associated creative resources or re-uploading them using advertisers.assets.upload.

If you are not caching media IDs, you do not need to do anything in regards to this change.

If you have questions regarding this change, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

February 2023 update to Display & Video 360 API

Today we’re announcing the February 2023 update to Display & Video 360 API. This update includes the following features:

More detailed information about this update can be found in the Display & Video 360 API release notes.

Before using these new features, make sure to update your client library to the latest version. We have also added a new guide page on retrieving YouTube & Partners line items using the Display & Video 360 API.

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

- Trevor Mulchay, Display & Video 360 API Team

Display & Video 360 API v2 entering general availability

Today we’re announcing the launch of Display & Video 360 API v2 out of public beta, and into general availability, and updates to both v1 and v2. As Display & Video 360 API v2 enters general availability, it becomes our recommended version. Our existing guides have been updated to reflect v2 features and conventions.

The following features have been added to v2:

The following updates have been made to both v1 and v2:

  • Removed the character limit for the description field in InsertionOrderBudgetSegment objects.
  • Increased the max page size of a subset of list requests from 100 to 200. The default page size for these methods is still 100.

In addition to these updates, we’ve also fixed two known issues in v2 regarding enum targeting and the line item bulkUpdate method. More detailed information about this update can be found in the Display & Video 360 API release notes, and updated instructions on migrating from v1 to v2 can be found in our migration guide. Before using these new features, make sure to update your client library to the latest version.

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

- Trevor Mulchay, Display & Video 360 API Team

Optimized targeting launch in Display & Video 360 postponed

The launch of optimized targeting and deprecation of targeting expansion for display, video, and audio line items in Display & Video 360 have been postponed. Optimized targeting was previously announced to gradually launch for all Display & Video 360 partners from November 7 to November 9, 2022.

The changes in Display & Video 360 API behavior that were previously announced have also been postponed. The targetingExpansion field in the LineItem resource will continue to represent the targeting expansion feature.

We will announce a new date for these changes at a later date.
- Trevor Mulchay, Display & Video 360 API Team

Upcoming changes to targeting expansion in Display & Video 360 API

On November 7, 2022, optimized targeting will gradually begin replacing targeting expansion for display, video, and audio line items under a Display & Video 360 partner, with the new feature launched for all partners by November 9, 2022. We will be making changes to the Display & Video 360 API to reflect this. These changes may impact the existing configurations of your resources, and the behavior for your currently successful requests.

Read the optimized targeting and targeting expansion guides to understand the differences between optimized targeting and targeting expansion. Optimized targeting is not available for over-the-top line items, or line items that use fixed bidding.

There will be no structural changes to the existing targetingExpansion field or 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 manner:
  • The targetingExpansionLevel field will only support two possible values:
    • NO_EXPANSION: optimized targeting is off
    • LEAST_EXPANSION: optimized targeting is on
  • 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 continue to set whether first-party audiences should be excluded from targeting. This will now apply to optimized targeting instead of targeting expansion.
  • 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.
  • Optimized targeting will not automatically be turned on for eligible line items created or updated by the Display & Video 360 API.
We will also be updating the configurations of existing line items as follows: To prepare for this change, it is recommended that you turn on automated bidding for line items currently using fixed bidding with targeting expansion before November 7, 2022 to continue using audience expansion to improve campaign performance.

If you have questions regarding these changes or need help with these new features, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team