Tag Archives: dv360_api

Deprecation of Display & Video 360 API v2

Today we are deprecating Display & Video 360 API v2 and will sunset v2 on September 3, 2024. Migrate to Display & Video 360 API v3 before the sunset date to avoid an interruption of service.

You can read our release notes for more information on updates made to the API in v3, such as the addition of proximity location list management and updates to resource and field names. Follow the steps in our v3 migration guide to help you migrate from v2 to v3.

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

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.

- Trevor Mulchay, Display & Video 360 API Team

January 2024 update to Display & Video 360 API

Today we’re announcing the January 2024 update to the 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.

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

- Trevor Mulchay, Display & Video 360 API Team

Update to Display & Video 360 API Terms of Service to ensure Online Behavior Advertising compliance

On February 9, 2024, we will update the Display & Video 360 API Terms of Service to add new language that supports announced changes to promote advertiser transparency and content reporting in Display & Video 360.

The new language specifies that, by setting the Advertiser resource field obaComplianceDisabled to true, you are attesting to using an alternative ad badging, transparency, and reporting solution for ads served in the European Economic Area (EEA) such that the following requirements are met:

  • The alternative solution includes any required transparency information and a mechanism for reporting illegal content.
  • You notify Google of any illegal content reports using this form.

The obaComplianceDisabled field description will also be updated to reflect this change.

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

- Trevor Mulchay, Display & Video 360 API Team

Update to Display & Video 360 API Terms of Service to ensure Online Behavior Advertising compliance

On February 9, 2024, we will update the Display & Video 360 API Terms of Service to add new language that supports announced changes to promote advertiser transparency and content reporting in Display & Video 360.

The new language specifies that, by setting the Advertiser resource field obaComplianceDisabled to true, you are attesting to using an alternative ad badging, transparency, and reporting solution for ads served in the European Economic Area (EEA) such that the following requirements are met:

  • The alternative solution includes any required transparency information and a mechanism for reporting illegal content.
  • You notify Google of any illegal content reports using this form.

The obaComplianceDisabled field description will also be updated to reflect this change.

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

- Trevor Mulchay, Display & Video 360 API Team

Updates to Display & Video 360 API Customer Match uploads

Last month we announced new changes launching in Google Ads API v15 to enable customers to pass end-user consent when uploading data. Today we are adding similar fields to Display & Video 360 API v2 and v3 that you can use when uploading Customer Match audience members.

You must start sending consent signals when uploading Customer Match audience members by March 2024 to adhere to the EU User Consent Policy and continue using European Economic Area (EEA) user data to populate Customer Match audiences.

What’s changing?

The Display & Video 360 API has added a Consent object for uploading consent with your Customer Match data. The Consent object specifies two distinct types of consent. For the EEA user data to be used in Customer Match user lists, both types of consent must be granted to indicate that you have received user consent.

What should I do?

Consent signals are set for all users added in a single firstAndThirdPartyAudiences.create or firstAndThirdPartyAudiences.editCustomerMatchMembers request. Use separate requests to upload users with different consent signals.

Make the following updates to requests creating and updating Customer Match audiences of the following audience types:

Audience Type Relevant update
CUSTOMER_MATCH_CONTACT_INFO Set the consent field of the included ContactInfoList.
CUSTOMER_MATCH_DEVICE_ID Set the consent field of the included MobileDeviceIdList.

We have updated the existing Customer Match feature guide with information on passing consent signals. Read our release notes for an itemized list of the changes.

Before using these new features, make sure to update your client library to the latest version.

Where can I get support?

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

- Trevor Mulchay, Display & Video 360 API Team

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