In March of this year, we announced that beginning September 30, 2021, we will end support for the legacy v2.0 of the Content API for Shopping. We also recommended you migrate to using v2.1, which has been available since March 2019.

As of this announcement, there is now less than 1 month until support for v2.0 will end on September 30, 2021. Following this date, the legacy v2.0 of the Content API is no longer guaranteed to function. We will continue to provide support for your efforts to migrate to v2.1. To avoid disruption we strongly encourage you to migrate to v2.1 imminently.

What do I need to know?
To check your usage of Content API for Shopping, you can look it up:

• Using a Merchant Center ID
• Using a Cloud Project ID

If your application uses a multi-client account (MCA) to make changes to sub-accounts, you should also check your API usage for that account. Please note that all API usage from Content API for Shopping v2.0, is no longer guaranteed to function after September 30, 2021.

Where do I get support?
We have a comprehensive migration guide to help you migrate your implementation including all the changes and new features available in v2.1.

For support migrating the Inventory.set method, see the release of partial product updates.

For support for Google Apps Script & Google Ads scripts, see the update of the default runtime to v2.1.

If you have any questions or issues during migration, contact your Google representative for Merchant Center programs, or ask questions in the Content API for Shopping forum.
Ian Ballantyne, Content API for Shopping Team

As previously announced, all ad extensions are migrating to the new Asset-based extension paradigm. You must update extensions support in your implementation and migrate existing Feed-based extensions to Asset-based extensions. See the migration schedule for all the important migration and sunset dates.

The first automatic migration will start on October 20, 2021 and will take several weeks to complete. You have a choice to migrate your own extensions, allow the automatic migration to proceed, or to opt client accounts out of it. During the migration, Feed-based Callout, Promotion, Sitelink, and Structured Snippet extensions within client accounts will be copied into new Asset-based extensions. The new Asset-based extensions will then serve instead of the Feed-based extensions.


What will be the impact of the automatic migration?After an account has been migrated, there will be a new Asset instance for each Feed-based Callout, Promotion, Sitelink, and Structured Snippet extension. The new Assets will be linked to the same ad groups, campaigns, and customers as the Feed-based extensions from which they were copied. The new Assets will have new IDs, and there will be no connection between Assets created during the automatic migration and the original Feeds, including historic metrics. All subsequent extension-related metrics will only be accessible from the asset_field_type_view report. Additionally, you will no longer be able to issue CREATE or MUTATE requests that affect Callout, Promotion, Sitelink or Structured Snippet extensions in the account through the following services:

Service	API Reference
ExtensionFeedItemService		Google Ads API
AdGroupExtensionSettingService	AdWords API	Google Ads API
CampaignExtensionSettingService	AdWords API	Google Ads API
CustomerExtensionSettingService	AdWords API	Google Ads API
FeedService	AdWords API	AdWords API
FeedItemService	AdWords API	Google Ads API
FeedMappingService	AdWords API	Google Ads API
AdGroupFeedService	AdWords API	Google Ads API
CampaignFeedService	AdWords API	Google Ads API
CustomerFeedService	AdWords API	Google Ads API
GoogleAdsService		Google Ads API
BatchJobService	AdWords API	Google Ads API

If you choose to allow the automatic migration to proceed, you will know that an account has been migrated when any MUTATE or CREATE request to the above listed services affecting Callout, Promotion, Sitelink, or Structured Snippet extensions returns an error.


What will be the impact of opting out?You can opt out individual customer accounts from the October automatic migration. Opting out will only defer the automatic migration until the second automatic migration begins on February 15, 2022. If you choose to opt out, no resources will be created or modified in opted out accounts during the October automatic migration, and only the opted out accounts will be able to continue to issue CREATE and MUTATE requests after the October automatic migration.

You cannot opt out of the February 15, 2022 automatic migration. All remaining Feed-based extensions will be automatically migrated starting February 15, 2022 as described in the migration schedule. After this second automatic migration, all CREATE and MUTATE requests affecting Feed-based extensions will return errors.
What do I need to do?We strongly recommend that you migrate your extensions yourself if feasible. Please follow our extension migration documentation for guidance on migrating your own extensions. Be sure to remove the Feed-based extension once you have successfully copied an extension to an Asset to avoid duplication during the automatic migration.

If you choose to allow the automatic migration to proceed, you need to only update your implementations to detect when an account has been migrated and to thereafter switch over to managing Assets instead of Feeds.


If you choose to opt out, the automatic migration will make no changes to the opted out accounts. Your existing API implementations will continue to work until the second automatic migration begins on February 15, 2022. To opt out, you must complete this form with the following:

• A contact email at which you can be reached should any issues arise during the opt out process.
• The developer token that you use to manage the accounts.
• Acknowledgements of the effects of opting out.
• An uploaded text file containing the customer IDs that you wish to opt out, one per line. If you need to generate a list of customer IDs, we recommend utilizing the GetAccountHierarchy example in each client library’s AccountManagement directory. This example will return the resource names of all accounts reachable from a given manager account.

The form will open for submissions on August 30, 2021. Note that the developer token must have been used to issue requests on the customer account after July 16, 2021. The form will close on October 13, 2021.


If you have any questions or need additional help, contact us via the forum or at googleadsapi-support@google.com.
- Andrew Burke, Google Ads API Team

We're happy to announce that v202108 of the Google Ad Manager API is available starting today. This release brings new proposal line item features including a pauseRole and pauseReason, as well as support for Nielsen Digital Ad Ratings.

There are also some updates for MobileApplications, like changing the singular appStore to the list field appStores and adding an applicationCode field. This field contains the same code used to identify the app in the Google Mobile Ads SDK.

For the full list of changes for v202108 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.

- Chris Seeley, Ad Manager API Team

Today, we’re announcing the v8_1 release of the Google Ads API. To use some of the v8_1 features, you 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’s what we added:

• Support for two Smart Bidding features:
  • Seasonality adjustments to let Smart Bidding apply conversion rate adjustments for future events such as promotions or sales.
  • Data exclusions to let Smart Bidding exclude conversion data from specified dates. You can use this when there are issues with your account's conversion tracking during specific dates.
• SmartCampaignSuggestService.SuggestSmartCampaignAd() to get suggestions for up to three headlines and two descriptions for Smart campaign ads based on information such as the landing page and keyword themes provided.
• ConversionValueRule and ConversionValueRuleSet resources to adjust conversion values based on conditions like geographic location, device and audience, and to better express the value of conversions as they relate to your business.

Where can I learn more?
The following resources can get you started:

• Release Notes
• Guides
• Reference
  

If you have any questions or need additional help, contact us through the forum.
Thanet Knack Praneenararat, on behalf of the Google Ads API Team

Today we’re releasing an update to the Display & Video 360 API that includes the following features:

• Support for Open Measurement enabled inventory targeting under the targeting type TARGETING_TYPE_OMID.
• Increased maximum page size for advertiser, campaign, insertion order, and line item assigned targeting option list requests from the default size of 100 items to 5000 items.

More detailed information about this update can be found in the Display & Video 360 API release notes. Before using these new features, make sure to update your client library to the latest version.

If you run into issues or need help with these new features or samples, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

On Tuesday, August 31, 2021, in accordance with the deprecation schedule, v202008 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

If you’re still using v202008, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v202105 we added support for pushing creative previews to linked devices.

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:

• v202102
  • We renamed an AuthenticationError enum value from NOT_WHITELISTED_FOR_API_ACCESS to NETWORK_API_ACCESS_DISABLED.
  • We removed deprecated LineItem fields isPrioritizedPreferredDealsEnabled and adExchangeAuctionOpeningPriority.
• v202105
  • We removed support for filtering on field keyValueMemberContent in CmsMetadataService.getCmsMetadataValuesByStatement. Use Content.cmsMetadataValueIds instead.

As always, don't hesitate to reach out to us on the developer forum with any questions.
 - Donovan McMurray, Ad Manager API Team