Tag Archives: release

Announcing v202205 of the Google Ad Manager API

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.

To migrate, please refer to the migration guide and the reference documentation for v202202 and earlier. The reference documentation has been updated to show which values are deprecated and their replacements. Here’s an example:

Enumeration Description
AD_EXCHANGE_IMPRESSIONS 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.

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

Announcing v10.1 of the Google Ads API

Today we’re announcing the v10.1 release of the Google Ads API. To use some of the v10.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 of v10.1:

Where can I learn more?

The following resources can help you get started:

If you have any questions or need additional help, contact us through the forum.

Announcing v202202 of the Google Ad Manager API

We're pleased to announce that v202202 of the Google Ad Manager API is available starting today, February 28th. This release brings a long-awaited feature – Ad Manager hosted video creatives. Simply provide a URL for the video asset, and Ad Manager will read and transcode it.

While API support has been added, this feature is still rolling out to Ad Manager networks and may not yet be available in yours. Networks with this feature disabled will continue to receive CreativeSetError.CANNOT_CREATE_OR_UPDATE_VIDEO_CREATIVES.

MCM companies now include information about the status of onboarding tasks and Sellers.json identifiers.

There are also some maintenance updates removing deprecated features, like AdExclusionRuleService and Proposal pause information.

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

Announcing v10 of the Google Ads API

Today we’re announcing the v10 release of the Google Ads API. To use some of the v10 features, you’ll need to upgrade your client libraries and client code. The updated client libraries and code examples will be published next week.

Note: Developers must migrate from the legacy AdWords API to Google Ads API by April 27, 2022. Here are the highlights of v10:
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.

Updates to Chromecast integrations with Interactive Media Ads



CAF DAI SDK Released

The Interactive Media Ads team is excited to announce that we’ve teamed up with the Cast Application Framework team to bring you the CAF DAI SDK, a fully supported solution for casting DAI video streams to Chromecast devices. This project is a complete rewrite of our original IMA SDK for Cast, significantly reducing the amount of code publishers need to write and streamlining the integration between the two SDKs.

The CAF DAI SDK provides a deep integration with Chromecast Application Framework's native Ad Breaks, meaning that adding around 30 lines of code to an existing CAF receiver can enable:
  • DAI support for both Live and VOD streams
  • Media queue management
  • Sender and receiver UI, including ad break markers
  • Bidirectional communications between sender and receiver
  • Skippable ad support on VOD streams

With the previous SDK, all of these functions required manual implementation.


A fully-featured CAF DAI integration



IMA SDK for Cast deprecated

As of December 13, 2021, both the client-side and DAI versions of the IMA SDK for cast are now deprecated. Publishers who are currently using the IMA SDK for cast to implement client-side advertisements are encouraged to migrate to using CAF native ad breaks. Publishers who are currently using the IMA SDK for cast to implement DAI advertisements are encouraged to migrate to the new CAF DAI SDK. These new implementation options offer publishers significantly simpler integrations with better stability and tighter integration with the entire cast ecosystem.
Advertisement Type Deprecated Solution Recommended Solution
Client Side IMA SDK for Cast CAF native ad breaks
DAI IMA SDK for Cast CAF DAI SDK

The Client side and DAI versions of the IMA SDK for Cast will continue to function for the foreseeable future but support and new development will be focused on the CAF DAI SDK moving forward. The IMA SDK team will continue to offer best attempt support for the deprecated SDKs through December of 2022, however, some limitations of the older platform may only be resolved by migrating to the new workflows described above.


We highly recommend that publishers who are currently using the older IMA SDK for Cast begin migrating to these new workflows for improved stability, simplified integration, and a much more polished developer experience.





For more information about these changes, check out the developer documentation. If you have any issues migrating your integration from the IMA SDK for Cast to the CAF DAI SDK, feel free to reach out via our developer forums.

Announcing v202111 of the Google Ad Manager API

We're pleased to announce that v202111 of the Google Ad Manager API is available starting today. This release brings new video features including more Video Opportunity metrics and GRP settings for proposal line items.

Additionally, MCM users can now programmatically resend expired invitations using the new ResendInvitationAction. For altering revenue share or re-inviting an inactive child publisher, continue to use the ReInviteAction.

For the full list of changes for v202111 and all other active API versions, check the release notes. Feel free to reach out to us on the Ad Manager API forum with any API-related questions.

Updated schedule of Google Ads API 2022 releases and sunsets

We’re announcing an update to the Google Ads API 2022 release and sunset schedule to help developers migrate from the AdWords API. Google Ads API v7 and v8 are expected to sunset in April/May 2022 in order to align their sunset with that of the AdWords API.

Please keep in mind that these dates are only estimates and may be adjusted going forward. Releases may be added, removed or switched between major and minor. Check our release notes and deprecation schedule for updates.

Note: The AdWords API is scheduled to sunset in April 2022. Migrate all requests to the Google Ads API by then to continue managing your Google Ads accounts.

Updated release schedule:
Version Planned Release
Type*
Projected launch* Projected sunset*
v7 Major April 28, 2021 (launched) April/May 2022
v8 Major June 9, 2021 (launched) April/May 2022
v8_1 Minor August 11, 2021 (launched) April/May 2022
v9 Major October 2021 June/July 2022
v10 Major February/March 2022 October/November 2022
v10_1 Minor April/May 2022 October/November 2022
v11 Major June/July 2022 March/April 2023
v11_1 Minor August/September 2022 March/April 2023
v12 Major October/November 2022 June/July 2023
*Estimated and subject to change

Where can I learn more?
The following resources can help you with your development planning:
If you have any questions or need additional help, contact us via the forum.

Announcing v9 of the Google Ads API

Today, we’re announcing the v9 release of the Google Ads API. To use some of the v9 features, you 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:
  • Added support for Performance Max campaigns, a new campaign type that provides a unified buying service to virtually all Google Ads inventory. Performance Max also provides a superset of Smart Shopping Campaign functionality.
  • Added support for conversion goals to help you organize your conversion actions so that you can more easily optimize toward your advertising objectives.
  • Smart campaigns is in open beta and is now available for all users. We also added a new, more robust suggestion method, which leverages your company’s business details to suggest keyword themes for your Smart campaign.
  • Added support for an App campaign for pre-registration and the pre-registration ads which helps to gauge interest before an app or a game is available to install.
  • Migrated Video ads from using MediaFile to represent videos and images to using assets: AdVideoAsset and AdImageAsset. This includes the companion_banner and video fields of Video ads-related objects.
  • To comply with ATT, ConversionUploadService now supports conversion uploads with BRAID identifiers (ClickConversion.gbraid and ClickConversion.wbraid) in place of GCLID. BRAID identifiers are used for clicks associated with conversions from iOS14 devices. This feature is currently only available to allowlisted customers.
  • The Google Ads API now distinguishes between conversions with SKAdNetwork conversion value 0 and conversions with no conversion value present in the postback from Apple. Note that this feature is only available for SKAdNetwork conversions received after September 20th, 2021.
  • Added support for asset sets, which are a collection of assets. They will eventually replace the FeedService.
  • Added support for ad customizers for Responsive Search Ads.
  • Added support for warnings for OfflineUserDataJobService as AddOfflineUserDataJobOperationsRequest.enable_warnings. When set to true, any non-blocking errors pertaining to operation failures will be returned as AddOfflineUserDataJobResponse.warning.
  • ad_group_ad_asset_view reporting is now available for App engagement ads and responsive search ads.
  • Added support for retrieving hotel_reconciliation resources, which contain booking information to reconcile bookings from commission campaigns.
  • Added support for customer match rate range with CreateOfflineUserDataJobRequest.enable_match_rate_range_preview. The customer match rate range is the efficacy of your Customer Match uploads, which is the number of matched user data rows divided by the total number of Customer Match uploaded rows.
  • Added UserAttribute.shopping_loyalty to allow for sending loyalty-related data with UserAttribute.
  • Added the following types of assets, which will be available in all accounts by the end of 2021
    • Price assets
    • Hotel Callout assets
    • Mobile App assets
    • Call assets
    • Call to action assets
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.

Announcing the release of the Authorized Buyers Marketplace API

The Authorized Buyers Marketplace API has been released. You can use the Marketplace API to manage clients, users, and auction packages, and to negotiate proposals with publishers. This new API is intended to replace the following Marketplace resources included in the Ad Exchange Buyer II API:
Although the Ad Exchange Buyer II API is not deprecated at this time, we recommend that all Marketplace integrations adopt the new API to receive the latest updates going forward. New features will only appear in the Marketplace API.

The Marketplace API introduces the following features:
  • Programmatic support for auction packages.
  • Deals are now a sub-resource of proposals.
  • The finalizedDeals resource helps you manage deals.
  • The rtbMetrics field of finalizedDeals provides performance data.
Given that the Marketplace API is distinct from the existing Real-time Bidding and Ad Exchange Buyer II APIs, please note that you need to enable the Authorized Buyers Marketplace API in your Google Cloud Console project. Additionally, you need to update your existing OAuth 2.0 credentials and workflows to include a new API scope:

https://www.googleapis.com/auth/authorized-buyers-marketplace

For any questions or feedback about this API, please contact us via our support forums.

Final reminder to migrate to the AdMob API

On October 12, 2021, you will no longer be able to retrieve AdMob data from the AdSense Management API v1.4. To retrieve AdMob data programmatically, migrate to the AdMob API.

What do I need to do?

Follow the instructions in the migration guide to migrate your API workflow. Review these additional resources to support your migration:


Start migrating from the AdSense API to the AdMob API as soon as possible. If you don’t complete the migration by October 12th, 2021, you will lose access to AdMob data through the AdSense API, which may impact your ability to make data-driven business decisions.

Feel free to reach out to us via the AdMob API Developer forum if you have questions or feedback regarding the AdMob API.