Tag Archives: dv360_api

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.

- Trevor Mulchay, Display & Video 360 API Team

Display & Video 360 API v3 entering general availability

Today we’re announcing the launch of Display & Video 360 API v3 out of public beta and into general availability. With this launch, v3 becomes our recommended version, and our guides have been updated to reflect v3 features and conventions.

Today’s launch also makes the following changes:

Read the Display & Video 360 API release notes for more details on this and previous updates. Instructions on migrating from v2 to v3 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 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 v3 entering general availability

Today we’re announcing the launch of Display & Video 360 API v3 out of public beta and into general availability. With this launch, v3 becomes our recommended version, and our guides have been updated to reflect v3 features and conventions.

Today’s launch also makes the following changes:

Read the Display & Video 360 API release notes for more details on this and previous updates. Instructions on migrating from v2 to v3 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 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

Updates to Customer Match, Conversions, and Store Sales Uploads

Google announced in September that there would be upcoming changes to support the Digital Markets Act (DMA). Google is releasing changes to the Google Ads API and the Display & Video 360 API as quickly as possible so that our developers have time to make application changes before DMA starts being enforced, expected March 6, 2024. Review the EU user consent policy for a reminder on our consent requirements for users in the European Economic Area.

What should I change for the Google Ads API?

The Google Ads API v15 release introduced the Consent object for uploading consent with your data. This Consent is used across all uploads for call conversions, click conversions , Customer Match, and Store Sales. Here is where to set the Consent for each feature.

Feature Code change
Call Conversions Set Consent for each call conversion event at CallConversion.consent. See the guide for details.
Click Conversions Set Consent for each click conversion event at ClickConversion.consent. See the guide for details.
Customer Match Set Consent for each Customer Match job at CustomerMatchUserListMetadata.consent. See the guide for details.
Store Sales Set Consent for each Store Sales event at UserData.consent. See the guide for details.

What should I change for the Display & Video 360 API?

The Display & Video 360 API will be releasing similar changes in the following months announced via this blog. Check back in the release notes for updates to existing versions and the Customer Match feature guide for updated implementation instructions.

Where can I get support?

If you have questions, reach out to us [email protected] for the Google Ads API or the support form for the Display & Video 360 API.

Nadine Wang, on behalf of the Google Ads API and Display & Video 360 API Teams

Announcing beta launch of Display & Video 360 API v3

We’re pleased to announce that Display & Video 360 API v3 is available in public beta starting today.

v3 includes a number of new features and breaking changes. Here are some of the changes introduced in v3: More detailed information about this release can be found in our release notes. Follow the steps in our migration guide to migrate from v2 to v3. Be aware that breaking changes may be made to v3 while in beta and will be listed in the Display & Video 360 API release notes.

If you run into issues or need help with these new features or samples, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

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.

- Trevor Mulchay, Display & Video 360 API Team

August 2023 update to Display & Video 360 API v2

Today we’re announcing the August 2023 update to Display & Video 360 API v2. 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.

If you need help with these new features, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

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.

- Trevor Mulchay, Display & Video 360 API Team

Display & Video 360 API v1 will sunset on September 14, 2023

As announced in March 2023, Display & Video 360 (DV360) API v1 will sunset on September 14, 2023. Please migrate to DV360 API v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1 to v2.

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

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.

- Trevor Mulchay, Display & Video 360 API Team