Author Archives: Google Ads Developer Advisor

Campaign criterion simulations being removed in the Google Ads API

We are announcing that the campaign_criterion_simulation report will be deprecated in the Google Ads API. This change will be effective on July 10, 2023. After this date, all campaign_criterion_simulation report requests will return blank responses.

We recommend that you start updating your applications to account for this change as soon as possible.

Please contact us on our forum or at [email protected] if you have any questions.

Announcing v202305 of the Google Ad Manager API

We're pleased to announce that v202305 of the Google Ad Manager API is available starting today, May 23rd. This release brings support for new DAI ingestion statuses and removes deprecated SPM reporting dimensions.

For the full list of changes, check the release notes. Feel free to contact us on the Ad Manager API forum with any API-related questions.

Deprecating Python 3.7 Support in the Google Ads Client Library for Python

On June 27, 2023, Python 3.7 will reach end-of-life and will no longer be supported by the Python Software Foundation. Once Python 3.7 officially reaches end-of-life status, it will also no longer be supported by the Google Ads client library for Python.

While this will not change the functionality of the client library, any issues or bugs related to the library's compatibility with Python 3.7 will not be addressed, and any documentation related to Python 3.7 will be removed.

We recommend library users upgrade their systems to Python 3.8 or higher as soon as possible.

If you have any questions about this change, please file an issue on the client library repository.

Prepare to test Privacy Sandbox APIs with Google’s ads platforms

Last week, Chrome announced the upcoming general availability of Privacy Sandbox APIs for the ads ecosystem. We welcome this opportunity to test these APIs in Google’s ads platforms, and we invite ad technology partners to get involved and be ready for Chrome’s third-party cookie deprecation in 2024.

We’ve seen encouraging results from our recent interest-based advertising experiments, and we plan to integrate Topics, Protected Audience and Attribution Reporting APIs into our ads products. We’ll use Privacy Sandbox APIs alongside other privacy-preserving innovations to help deliver relevant ads and accurate measurement insights without the need to track people across the web.

We encourage advertisers and publishers to continue to adopt the full range of Google’s privacy-first ads solutions, and encourage their ad technology platform partners to adopt and test Privacy Sandbox APIs.

Through the rest of 2023, we will work with our ad technology partners to test the Privacy Sandbox APIs alongside first-party data and AI-powered solutions, and prepare for Q1 2024 when Chrome plans to deprecate third-party cookies for one percent of its users. The Q1 2024 tests will help us to evaluate the effectiveness of these solutions, and share our findings with Chrome, the UK’s Competition and Markets Authority, and the industry.

We encourage technology partners to review the below guidance to prepare for testing with Google’s Ads solutions:
  • If you’re a Google Authorized Buyer or participant in Open Bidding, see integration guidance for Topics and Protected Audience.
  • If you’re a publisher platform working with Google Ads or Google Marketing Platform (Display & Video 360 or Campaign Manager 360), see integration guidance for Topics, Protected Audience and Multiple seller testing.
  • If you’re a measurement provider working with Google Marketing Platform (Display & Video 360 or Campaign Manager 360), see integration guidance for the Protected Audience API.
  • If you’re a publisher or ad tech provider working with Google Marketing Platform (Display & Video 360, Campaign Manager 360 or Search Ads 360), see integration guidance for the Attribution Reporting API.
We’re excited to continue building privacy-first innovations that help partners drive performance, earn revenue and get accurate measurement insights without third-party cookies.

Announcing new testing features for ad inspector

We’re excited to announce the launch of new testing features on ad inspector across all platforms for our AdMob and Ad Manager publishers.

Previously, ad inspector tested all ads in context - in other words, you had to fire up your app, navigate to the appropriate screen in the UI, and have your ad load as it would for any other user. While this provides for the most accurate testing scenario, it also puts more work on you as the publisher and tester of your app. You don’t want ads buried in more obscure screens in your app to lose out on the testing attention and care they need!

With our latest update, you can now use test ads to load requests for any ad unit - no matter where it's located in your app. Rather than needing to navigate through your app to test each ad unit, you can execute your tests directly from ad inspector.

How do I use ad inspector’s new testing features?

Beginning with version v10.0.0 on iOS and v21.4.0 on Android of the Google Mobile Ads SDK, ad inspector supports running tests directly from the ad unit detail screen via a “Request test ad” button:

All of your requests made from your app’s UI or within ad inspector will appear in the SDK request log; your requests made from within ad inspector will be differentiated by being labeled with “Requested from ad inspector”. For these special requests you’ll be able to tap the “View” button one time to view the actual ad, see which network filled the slot, and more.

Alongside single ad source testing, these new testing features will allow you to rigorously test each individual ad network integration in your app.

To learn more about how to test your ads with ad inspector, check out our developer guides here:

If you have any questions or need additional help, please contact us via the developer forum.

Deprecating Audience Composition Reports in Bid Manager API on June 8, 2023

On June 8, 2023, Audience Composition Reports will be deprecated in Display & Video 360. This means that you will no longer be able to retrieve, create or run Audience Composition Reports using the Bid Manager API.

In the Bid Manager API, an Audience Composition Report is a Query resource with a ReportType of AUDIENCE_COMPOSITION assigned to params.type. After deprecation:

  • Any request to the queries or queries.reports services identifying an Audience Composition Report will return an error.
  • All queries.create requests creating a new Audience Composition Report will return an error.
  • All queries.list responses will no longer include Audience Composition Report queries.

To avoid an interruption of service, we recommend that you stop creating or retrieving any existing reports of this type.

If you have questions regarding this change, please contact us using our support contact form.

Announcing v13_1 of the Google Ads API

Today, we’re announcing the v13_1 release of the Google Ads API. To use some of the v13_1 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. This version has no breaking changes.

Here are the highlights: Where can I learn more?
The following resources can help you get started: If you have any questions or need additional help, contact us via the forum.

Removing support for PHP 7 in the Google Ad Manager SOAP API Client Library for PHP

In August 2023, the Google Ad Manager SOAP API Client Library for PHP will start requiring PHP version 8.0 or higher. The version of the client library that adds support for Google Ad Manager API v202305 will be the last version that supports PHP 7. We’ll still fix security issues for this client library version until Google Ad Manager API v202305 is sunset, but no new features will be added.

All PHP 7 versions reached their end of life in 2022. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to newer versions as soon as possible.

Here are useful resources to help with the PHP migration:

If you have any questions regarding this change, feel free to comment directly on the GitHub issue.

Ad Manager API v202205 sunset and v202202 extension

On Wednesday, May 31, 2023, in accordance with the deprecation schedule, v202205 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

Additionally, support for Ad Manager API v202202 is being extended until the same date, May 31, 2023. We've heard from a number of users that they need additional time to complete the Ad Exchange Historical report migration. Note that v202202 is the last version with support for Ad Exchange Historical reports.

When you’re ready to upgrade, check the full release notes to identify any breaking changes. Here are a few examples of changes that may impact your applications:

  • v202211
    • Replaced the string field thirdPartyImpressionTrackingUrl with the list field thirdPartyImpressionTrackingUrls for multiple creative types including ImageCreative. Currently only a single URL may be provided in the list.
    • Removed support for OPTIMIZATION reporting columns.

As always, feel free to contact us on the developer forum with any questions.

New Merchant IDs are now 64-bit in Content API for Shopping

In the Content API for Shopping, we informed you last June that new Merchant IDs were migrating from 32 bit to 64-bit signed integers.

Existing Merchant IDs haven’t changed. Beginning on March 13, 2023 new Merchant IDs created could be in the 64-bit signed range. Through a slow rollout over the next few months, a higher percentage of new Merchant IDs will be in the 64-bit signed range. By June 2023, all new Merchant IDs created will be in the 64-bit signed range.

To avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.