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.
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.
- Chris Seeley, Ad Manager API Team
- Ben Karl, on behalf of the Google Ads API Team
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.
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.
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:
queries or queries.reports services identifying an Audience Composition Report will return an error.
queries.create requests creating a new Audience Composition Report will return an error.
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.
- Trevor Mulchay, Bid Manager API Team
campaign_simulation.SKAdNetwork conversion value schemas for iOS App campaigns. Learn more about setting up your schema and best practices for your iOS campaigns.LeadFormField.has_location_answer to support specifying whether locations of the location assets at the campaign or customer level should be displayed with a lead form.VEHICLES listing type in the newly Campaign.listing_type field. This replaces ShoppingSetting.use_vehicles_inventory, which will be reserved for Smart Shopping campaigns.
- Thanet Knack Praneenararat, on behalf of the Google Ads API Team
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.
Pierrick Voulet, Google Ads API Team
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:
thirdPartyImpressionTrackingUrl with the list field thirdPartyImpressionTrackingUrls for multiple creative types including ImageCreative. Currently only a single URL may be provided in the list.
OPTIMIZATION reporting columns.As always, feel free to contact us on the developer forum with any questions.
- Chris Seeley, Ad Manager API Team