We are pleased to announce the launch of the Google Ads API Research Group. As a Developer Relations team, we want to ensure your voice is not only heard, but that your suggestions are incorporated into product decisions. Our goal is to turn your feedback into real improvements to the Google Ads API developer experience.

Read More

We are pleased to announce the launch of the Google Ads API Research Group. As a Developer Relations team, we want to ensure your voice is not only heard, but that your suggestions are incorporated into product decisions. Our goal is to turn your feedback into real improvements to the Google Ads API developer experience.

As a member of the research group, we'll invite you to participate in user research opportunities, such as surveys and usability studies. These opportunities let you voice your opinions and ideas about the Google Ads API, inform product design and prioritization, and ultimately shape the Google Ads API developer experience.

To sign up for the Google Ads API Research Group, fill out the opt-in form. This form takes about 5 minutes to complete. We are deeply committed to improving developer experience and appreciate your feedback.

 - Laura Chevalier, Google Ads API Team

Starting on March 3, 2025, the Google Ads API and Google Ads scripts search term insight reports will return all search subcategories as empty. The Google Ads UI already removed this field, and the API is also rolling out this change to be consistent across Google Ads.

Read More

Starting on March 3, 2025, the Google Ads API and Google Ads scripts search term insight reports will return all search subcategories as empty. The Google Ads UI already removed this field, and the API is also rolling out this change to be consistent across Google Ads.

What do I need to do?

Starting March 3, 2025, it is expected that all values for segments.search_subcategory will be empty.

If you query segments.search_subcategory in the campaign_search_term_insight or customer_search_term_insight reports, then:

1. Check that your code can handle an empty value in segments.search_subcategory. An empty string already is a catch-all, so your code should be already handling this.
2. We recommend removing segments.search_subcategory from your query.

If you have any questions or concerns, you can reach out to us through our support form.

Nadine Wang, Google Ads API Team

The IMA DAI SDK now supports passing the network code parameter when creating a full-service stream request. This change is specifically for IMA DAI integrations using either LiveStreamRequest or VODStreamRequest classes. Adding the network code is a one-time change that enables IMA DAI to respect your Ad Manager settings.

Read More

The IMA DAI SDK now supports passing the network code parameter when creating a full-service stream request. This change is specifically for IMA DAI integrations using either LiveStreamRequest or VODStreamRequest classes. Adding the network code is a one-time change that enables IMA DAI to respect your Ad Manager settings.

We recommend you provide the network code for IMA to apply your Ad Manager settings to the stream request. For example, if you turn off programmatic limited ads in Ad Manager, use the Google Ad Manager network code parameter to ensure local storage is also disabled for limited ads in DAI on your app.

The following example constructs an IMA DAI HTML5 LiveStreamRequest class with the network code in the request to Ad Manager:

function requestLiveStream(assetKey, apiKey, networkCode) {
  var streamRequest = new google.ima.dai.api.LiveStreamRequest();
  streamRequest.assetKey = assetKey;
  streamRequest.apiKey = apiKey;
  streamRequest.networkCode = networkCode;
  streamManager.requestStream(streamRequest);
}

You can pass the network code using the IMA DAI SDK for full-service DAI on all of the platforms:

• HTML5
• Android
• iOS
• tvOS
• Chromecast
• Roku

For more information, see the programmatic limited ads Ad Manager article. Additionally, follow Find your Ad Manager network code. If you have any questions, feel free to reach out using the IMA technical forum.

 - Jackson Sui, Interactive Media Ads Developer Relations

As part of our goal of aligning more closely with industry standards, we previously announced the sunset of the Authorized Buyers Real-time bidding protocol on February 15th, 2025. After the deprecation period, OpenRTB will be the only supported protocol for Authorized Buyers, Open Bidding, and SDK Bidding. Since the announcement, we have worked closely with migrating partners to provide guidance and technical assistance, as well as an A/B experimentation framework.

Read More

As part of our goal of aligning more closely with industry standards, we previously announced the sunset of the Authorized Buyers Real-time bidding protocol on February 15th, 2025. After the deprecation period, OpenRTB will be the only supported protocol for Authorized Buyers, Open Bidding, and SDK Bidding. Since the announcement, we have worked closely with migrating partners to provide guidance and technical assistance, as well as an A/B experimentation framework.

We have seen a lot of enthusiasm and progress from many partners migrating to OpenRTB, as well as significant improvements in bidding performance for a number of partners compared to Google RTB integrations. However, to provide additional support and further optimize bidding integrations with the OpenRTB protocol, we have decided to extend the Authorized Buyers Real-time Bidding protocol's deprecation period.

The sunset date is now April 30th, 2025. Following this date, bid requests will no longer be sent with the Authorized Buyers Real-time bidding protocol, and the only supported protocol will be OpenRTB.

If you have any questions about how OpenRTB differs from Authorized Buyers Real-time Bidding protocol, we recommend that you reference the OpenRTB migration guide. If you have other questions or feedback concerning your migration, feel free to contact us using the Authorized Buyers support forum, or adxbuyerapi-support@google.com.

- Mark Saniscalchi, Authorized Buyers Developer Relations

Google Ads API v16 will sunset on February 5, 2025. After this date, all v16 API requests will begin to fail. Migrate to a newer version prior to February 5, 2025 to ensure your API access is unaffected.Read More

Google Ads API v16 will sunset on February 5, 2025. After this date, all v16 API requests will begin to fail. Migrate to a newer version prior to February 5, 2025 to ensure your API access is unaffected.

Here are some resources to help you with the migration:

• Upgrade to the newest version
• Release notes

You can view a list of methods and services your project has recently called using the Google Cloud Console:

1. Open the APIs & Services in the Google Cloud Console.
2. Click Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as google.ads.googleads.v18.services.GoogleAdsService.Mutate.
4. (Optional) Choose the timeframe you want to view for your requests.

If you have questions while you’re upgrading, reach out to us on the forum or at googleadsapi-support@google.com.
 - Thanet Knack Praneenararat, Google Ads API Team