Google Ads Developer Blog: 一月 2024

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

2024年1月31日星期三

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:

You can retrieve Floodlight Activities and YouTube & Partners resources (line items, ad groups, and ads) using the Display & Video 360 API.

Starting with Structured Data Files v7, you can use IDs retrieved through the Display & Video 360 API in place of 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

2024年1月29日星期一

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

A new floodlightGroups.floodlightActivities service that enables the programmatic retrieval of FloodlightActivity resources. This was previously only possible using Entity Read Files.

Support of a new inventory source configuration field for YouTube & Partners Line Items.

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

2024年1月24日星期三

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

Performance Max Guide Enhancements

2024年1月18日星期四

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.

New Getting Started guide that outlines the steps to create

Reorganized guide structure to better reflect entity relationships in Performance Max campaigns

Clarified asset requirements

Revamped Performance Max reporting guide

Better surfaced features such as campaign-level conversion goals and asset group signals

Additional troubleshooting content

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.

- Devin Chasanoff, on behalf of the Google Ads API Team

Deprecation of cross-device conversion metric values in the Bid Manager API

2024年1月17日星期三

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.

- Trevor Mulchay, Bid Manager API Team

Google Ads API v13 sunset reminder

2024年1月8日星期一

sunsetAfter this date, all v13 API requests will begin to fail.newer version

Upgrading to the newest version

Release notes

Google Cloud Console

Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.

Click on Google Ads API in the table.

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.

(Optional) Click on the time frame at the top right of the page if you need to change it.

forumgoogleadsapi-support@google.com

- Thanet Knack Praneenararat, Google Ads API Team

Ads Developer Blog

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

January 2024 update to Display & Video 360 API

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

Performance Max Guide Enhancements

Deprecation of cross-device conversion metric values in the Bid Manager API

Google Ads API v13 sunset reminder

标签

Archive