The IMA Dynamic Ad Insertion (DAI) SDK lets apps make stream requests for ad and content video streams, either VOD or live content. The SDK then enables a video player to play the combined stream so you don't have to manage switching between ad and content video within your apps.
To improve support for HTML5 publishers, we have expanded the features provided by the Video.js-IMA plugin to include DAI for HLS streams. With the latest version of the plugin, you can enable a Video.js player to request ads and content in a single HLS stream. Check out the new DAI sample app and the DAI README file for implementation details on how the Video.js-IMA plugin can simplify your IMA DAI integration.
In the Content API for Shopping, Merchant IDs are now 64-bit signed integers. Applications that integrate with the Content API must be able to handle ID values in that range.
Historically, Merchant IDs in the Content API for Shopping were within the maximum value of a 32-bit signed integer, but have recently exceeded this range. In order 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. Benji Rothman, Content API for Shopping Team
Today we're releasing v4 of the Campaign Manager 360 API. This release adds support for the following Billing Services:
Details of these and all other changes are covered in our release notes.
Deprecation and sunset reminder In accordance with our deprecation schedule, this release marks the beginning of the depreciation period for v3.5, which will sunset on Feb 15, 2023. After this date, any requests made against v3.5 will begin returning errors.
See the migration guide for details. For most, you just need to upgrade to the latest version of your preferred client library. We recommend you to review the release notes to learn about important changes you might need to be aware of.
If you have questions about this or anything else Campaign Manager 360 API related, feel free to reach out to us on our support forum.
Learn More As with every new version of the Campaign Manager 360 API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.
Today, we’re announcing the v11 release of the Google Ads API. To use some of the v11 features, you will need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week. Here are the highlights:
As previously announced, the error rate for requests to the AdWords API will start increasing toward 100% beginning on May 31, 2022. If you are currently using the AdWords API, you need to upgrade to the Google Ads API now or your applications will experience an increased rate of errors per the schedule below:
AdWords API Error Rate
June 1, 2022
July 1, 2022
July 8, 2022
July 15, 2022
July 22, 2022
July 31, 2022
Starting July 31, 2022 all requests to the AdWords API will fail.
Where do I start? See the following resources to get started:
We're pleased to announce that v202205 of the Google Ad Manager API is available starting today, May 17th. This release adds support for CPM sponsorships for ProposalLineItems.
It also updates the ReportService for the upcoming "Ad Exchange Historical" to "Historical" report type conversion. Ad Exchange Historical dimensions and metrics are now available for Historical reports. Because of this change, several Ad Exchange dimensions and metrics have been renamed or replaced in the API.
Ad Impressions on mapped Ad Exchange properties. When multiple text ads fill a single display slot it is only counted once, when the top text ad is recognized. In these cases, the Ad Impression is attributed to the top text ad. Deprecated as part of the "Ad Exchange Historical" to "Historical" report type conversion. Use AD_EXCHANGE_LINE_ITEM_LEVEL_IMPRESSIONS instead.
Starting in July 2022, all remaining Search campaigns that use standard TargetCpa and TargetRoas bidding strategies will be converted to MaximizeConversions and MaximizeConversionValue strategies, with the same target_cpa and target_roas settings applied, respectively. The migration of portfolio strategies is planned later in 2023.
With this change there will be no impact to bidding behavior. Using MaximizeConversions with a target_cpa setting will have the same bidding behavior as TargetCpa. Likewise, using MaximizeConversionValue with a target_roas setting will have the same bidding behavior as TargetRoas.
The following sample Campaign object illustrates what a migrated Search campaign’s bidding strategy settings would look like before and after the transition.
The Google Ads API already prohibits creating or updating standard (non-portfolio) TargetCpa or TargetRoas bidding strategies for Search campaigns. In July, any code that reads or manages remaining strategies of those types should account for the settings migrating to MaximizeConversions and MaximizeConversionValue.