(Translated by https://www.hiragana.jp/)
Google Ads Developer Blog: January 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.

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.

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

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.

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.

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.

Today, we are pleased to announce several guide enhancements to improve the experience of creating, managing and reporting on Performance Max campaigns with the Google Ads API.

Today, we are pleased to announce several guide enhancements to improve the experience of creating, managing and reporting on Performance Max campaigns with the Google Ads API.

Improving Performance Max integrations Blog Series

This article is part of a series that discusses new and upcoming features that you have been asking for. Keep an eye out for further updates and improvements on our developer blog, continue providing feedback on Performance Max integrations with the Google Ads API, and as always, contact our team if you need support.

Today we’re deprecating cross-device conversion metric values in Bid Manager API. The following values will sunset on February 28, 2024:

  • METRIC_CM360_POST_CLICK_REVENUE_CROSS_ENVIRONMENT
  • METRIC_CM360_POST_VIEW_REVENUE_CROSS_ENVIRONMENT
  • METRIC_POST_CLICK_CONVERSIONS_CROSS_ENVIRONMENT
  • METRIC_POST_VIEW_CONVERSIONS_CROSS_ENVIRONMENT
  • METRIC_TOTAL_CONVERSIONS_CROSS_ENVIRONMENT

Upon sunset, queries.create requests using these values will return an INVALID_ARGUMENT error, and these values will be removed from existing Query resources.

Today we’re deprecating cross-device conversion metric values in Bid Manager API. The following values will sunset on February 28, 2024:

  • METRIC_CM360_POST_CLICK_REVENUE_CROSS_ENVIRONMENT
  • METRIC_CM360_POST_VIEW_REVENUE_CROSS_ENVIRONMENT
  • METRIC_POST_CLICK_CONVERSIONS_CROSS_ENVIRONMENT
  • METRIC_POST_VIEW_CONVERSIONS_CROSS_ENVIRONMENT
  • METRIC_TOTAL_CONVERSIONS_CROSS_ENVIRONMENT

Upon sunset, queries.create requests using these values will return an INVALID_ARGUMENT error, and these values will be removed from existing Query resources.

We’ve added the upcoming sunset to our change log. To avoid an interruption of service, we recommend that you stop creating any reports using these values before the applicable sunset date.

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

Google Ads API v13 will sunset on January 31, 2024. After this date, all v13 API requests will begin to fail. Please migrate to a newer version prior to January 31, 2024 to ensure your API access is unaffected.
Google Ads API v13 will sunset on January 31, 2024. After this date, all v13 API requests will begin to fail. Please migrate to a newer version prior to January 31, 2024 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: In addition, using the Google Cloud Console, you can view the list of methods and services to which your project recently submitted requests:
  1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
  2. Click on Google Ads API in the table.
  3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v13.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
  4. (Optional) Click on the time frame at the top right of the page if you need to change it.
If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.