Google Ads Developer Blog: sunset

Feed-based Extensions Sunset in Google Ads APIs

Tuesday, May 4, 2021

Asset-based extensions

Extension
Type

Asset
Available to
Test
Accounts

Asset
Available to
Production
Accounts

Auto
Migration
Date

Feeds
Sunset
Date

Lead Form

Google Ads API v6

October 20, 2021

February 15, 2022

Promotion

Google Ads API v7

October 20, 2021

February 15, 2022

Callout
Sitelink
Structured Snippet

Google Ads API v7

Google Ads API v8
(tentative)

October 20, 2021

February 15, 2022

App
Call
Hotel Callout
Image
Price

Google Ads API v9
(tentative)

February 15, 2022

April 8, 2022

What do I need to do?You should migrate any Feed-based extensions and related code that you intend to continue to use to Asset-based extensions as soon as is feasible.migration guidetest accountWhat if the October date is too soon?forum

Andrew Burke, Google Ads API Team

Sunset of the Ad Manager API v202005

Monday, May 3, 2021

deprecation scheduleAudioCreativerelease notesLineItem.viewabilityProviderCompanyIdviewabilityProviderCompanyIds
As always, don't hesitate to reach out to us on the developer forum with any questions.

- Donovan McMurray, Ad Manager API Team

Reminder to migrate to the AdMob API

Friday, April 30, 2021

Starting on October 12, 2021, developers will no longer be able to retrieve AdMob data from the AdSense Management API v1.4. Please start to migrate to the AdMob API which is generally available. Where can I get my AdMob data? After October 12th, 2021, using the AdMob API will be the only way you can access your AdMob data programmatically. The AdMob API helps app developers retrieve:

metrics that are consistent with the AdMob UI definitions and calculations

mediation reports that are not available through the AdSense API

What do I need to do? Start migrating from the AdSense API to the AdMob API as soon as possible. If you do not 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. Follow the instructions in the migration guide to migrate your API workflow. Review these additional resources to support your migration:

Get started with the AdMob API - Follow this guide to learn how to generate credentials and make your first request using the AdMob API.

Reference documentation - Find detailed information on each REST method and its specific parameters.

Client Library Samples - Check out code samples on how to make requests in Java, PHP and Python.

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

- Amira Badreldin, AdMob API team

Google Ads API v4 and v5 sunset reminder

Friday, April 30, 2021

sunsetAfter this date, all v4 and v5 API requests will begin to fail.newer version

Upgrading to the newest version

Release notes

forumgoogleadsapi-support@google.com

- Thanet Knack Praneenararat, Google Ads API Team

Upgrade to the Google Ads API from the AdWords API by April 27, 2022

Thursday, April 29, 2021

AdWords APIGoogle Ads APIApril 27, 2022v7Migrating Features guideWhere do I start?

Webinars

Supported client libraries and associated code examples

REST interface if you are not using a supported language

Welcome Video

Migration Overview

Migrating Features

Migrating Report Fields

Migrating Services

Where can I get support?forumgoogleadsapi-support@google.com

Nadine Wang, on behalf of the Google Ads API Team

Reminder: Using v2.0 of the Content API for Shopping with new accounts ends on April 30, 2021

Tuesday, April 20, 2021

announcedbeginning April 30, 2021 we will no longer allow new merchant accounts onto v2.0 of the Content API for ShoppingWhat do I need to know?

This account restriction will not impact users accessing new sub-accounts via an existing multi-client account (MCA), provided that MCA has been actively making v2.0 requests.

New accounts using v2.1 of the Content API for Shopping will not be affected.

The sunset date for existing merchant accounts actively using v2.0 is September 30, 2021.

What do I need to do?

Migrate to v2.1 of the Content API for Shopping in order to continue interacting with new merchant accounts after April 30, 2021.

If you are concerned you won’t be able to meet the April deadline, please fill out this form to request an exemption.

Content API for Shopping forum

Ian Ballantyne, Content API for Shopping Team

Announcing v2 of the AdSense Management API

Monday, April 19, 2021

v2 of the AdSense Management APIthe status of sitesGoogle API standardsit will sunset on October 12, 2021

All deprecated methods in v1.4 have been removed in v2. This includes resource methods that did not specify an AdSense account.

Resources are now identified by a name field. For example, an AdClient’s name would be “accounts/{accountId}/adclients/{adClientId}”.

With v2, AdSense Management API reporting data now aligns with the AdSense UI. This means that AdMob and YouTube properties are no longer supported. If you need to continue to fetch AdMob data programmatically, please migrate to the AdMob API. Additionally, the AdSense Management API will only support report data going back 3 years.

release notesAdSense API forum

- Donovan McMurray, AdSense API Team

Sunset grace period for existing v2 users of the Content API for Shopping

Thursday, March 11, 2021

previously announcedfor existing merchant accounts actively using v2.0However, we will not allow new merchant accounts onto v2.0 after April 30, 2021.supportWe strongly encourage you to migrate to v2.1 as soon as possible.What do I need to know?version 2.1 of the Content API for Shopping

New features to give you more power and flexibility: return policy configuration, regional inventory (beta), simplified local inventory, and improved management of supplemental feed data.

A more consistent product validation experience: products.insert requests no longer report non-fatal warnings or errors, so you can resolve issues via feed rules in the Merchant Center, just as you would with feeds maintained outside the API.

A better experience for managing Buy on Google: improvements to orders management.

release notesmigration guideContent API for Shopping forumWhat do I need to do?

Benji Rothman, Content API for Shopping Team

Sunset date for deprecated DBM API services postponed to April 15, 2021

Tuesday, February 23, 2021

DoubleClick Bid Manager (DBM) APIoriginally scheduled for February 26, 2021, has been postponed to April 15, 2021DBM API v1DBM API v1.1 SDF DownloadDBM API v1.1 Line ItemPrior blog postsDBM API v1.1 ReportingDisplay & Video 360 (DV360) APIprevious announcements
If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Reorganizing Similar Bid Strategies

Tuesday, February 23, 2021

Update (March 12, 2021): Updated the language in this post to emphasize that this change is a reorganization of existing features.added supportMaximize conversionsMaximize conversion valueMaximizeConversions.target_cpatarget_cpaMaximizeConversionValue.target_roasTargetCpaTargetRoasWhat’s changingMaximizeConversionsMaximizeConversionValuetarget_cpatarget_roasTargetCpaTargetRoasThere will be no impact to bidding behavior due to these changes.MaximizeConversionstarget_cpaTargetCpaMaximizeConversionValuetarget_roasTargetRoas

Before

After

TargetRoas

MaximizeConversionValue.target_roas

TargetCpa

MaximizeConversions.target_cpa

target_roastarget_cparelease notesWhat to doMaximizeConversionstarget_cpaMaximizeConversionValuetarget_roasTargetCpaTargetRoasTargetCpaTargetRoasTargetCpaTargetRoasforumgoogleadsapi-support@google.com

Adam Ohren, Google Ads API Team

Changes to Showcase Shopping ads

Monday, February 22, 2021

April 5, 2021, support for Showcase Shopping ads will be removed from the AdWords API

Object

Error

AdGroups

with adGroupType SHOPPING_SHOWCASE_ADS

OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE

AdGroupAds containing ShowcaseAds

OPERATION_NOT_PERMITTED_FOR_AD_GROUP_TYPE

REMOVEDDISABLEDREMOVEDDISABLEDforumgoogleadsapi-support@google.com

Adam Ohren, Google Ads API Team

Sunsetting Portofolio Enhanced CPC Bid Strategies

Tuesday, February 9, 2021

March 22, 2021portfolio

Creating new portfolio ECPC strategies.

Attaching portfolio ECPC strategies to campaigns.

Note that standard (non-portfolio) ECPC strategies will not be affected.

Affected Portfolio Enhanced CPC Strategies

Google Ads API

Bidding_strategy.type = BiddingStrategyType.ENHANCED_CPC

AdWords API

SharedBiddingStrategy.type = MANUAL_CPC,

SharedBiddingStrategy.biddingScheme.enhancedCpcEnabled = TRUE

Change Description

Error Upon Creation

Error Upon Attaching

Google Ads API

BIDDING_STRATEGY_NOT_SUPPORTED

CANNOT_ATTACH_BIDDING_STRATEGY_TO_CAMPAIGN

AdWords API

BIDDING_STRATEGY_NOT_SUPPORTED

CANNOT_ATTACH_BIDDING_STRATEGY_TO_CAMPAIGN

Migration DescriptionSelf-migration using Google Ads APICampaignService.MutateCampaigns()manual_cpc.enhanced_cpc_enabledoperations: [ { update: { resource_mame: customers/CUSTOMER_ID/campaigns/CAMPAIGN_ID, manual_cpc: { enhanced_cpc_enabled: true } }, update_mask: manual_cpc.enhanced_cpc_enabled } ]Self-migration using AdWords APICampaignService.mutate()biddingStrategyTypeMANUAL_CPCbiddingScheme.enhancedCpc<operations> <operator>SET</operator> <operand> <id>CAMPAIGN_ID</id> <biddingStrategyConfiguration> <biddingStrategyType>MANUAL_CPC</biddingStrategyType> <biddingScheme> <enhancedCpcEnabled>true</enhancedCpcEnabled> </biddingScheme> </biddingStrategyConfiguration> </operand> </operations>forumgoogleadsapi-support@google.com

Adam Ohren, Google Ads API Team

Sunset of the Ad Manager API v202002

Thursday, January 28, 2021

deprecation schedulegetTrafficDataForecastServicerelease notesintActivityActivityGroupall later versions use type longthe developer forum

- Donovan McMurray, Ad Manager API Team

Google Ads API v3 sunset reminder

Thursday, January 7, 2021

Google Ads API v3 will sunset on February 10, 2021. After this date, all v3 API requests will begin to fail. Please migrate to a newer version prior to February 10, 2021 to ensure your API access is unaffected. We've prepared various resources to help you with the migration:

Upgrading to the newest version

Release notes

If you have questions while you’re upgrading, please reach out to us on the forum or at googleadsapi-support@google.com.

- Thanet Knack Praneenararat, Google Ads API Team

Upcoming sunset for DBM API v1, SDF Download and Line Item services

Monday, November 30, 2020

As announced in August, deprecated services in the DoubleClick Bid Manager (DBM) API, comprised of DBM API v1, the DBM API v1.1 SDF Download service, and the DBM API v1.1 Line Item service, will be sunset on February 26, 2021.

If you are still using the DBM API v1 Reporting service, you must migrate to the DBM API v1.1 Reporting service before the sunset date to avoid an interruption of service. Consult the API release notes for details of the changes between v1 and v1.1. Differences to note during this migration include:

Queries created and accessed through the Reporting service require more specific filters in the params.groupBy field in v1.1. You might have to add more values to the params.groupBy field in order to create the same report structure generated in v1.
Responses from queries.listqueries and reports.listreports calls are paginated in v1.1. You have to update your implementation to traverse multiple pages if you want to consume more than the first 100 items returned.

If you are using any version of any other DBM API service, you must migrate to the Display & Video 360 (DV360) API.

Guides are available to help you set up and start using the Display & Video 360 API to download SDFs and manage your line items.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Sunset of deprecated Geo Region targeting options in Display & Video 360 API

Friday, November 20, 2020

Starting January 2021, over 1500 deprecated Geo Region targeting options will no longer be supported in Display & Video 360. This announcement, along with the full list of deprecated options, can be found on the Geography Targeting Help Center article. These deprecated targeting options reflect outdated geographical regions and, therefore, do not change the serving of line items.

How will this happen in the API?

This sunset will be reflected in the Display & Video 360 API through the following sequence of events:

Starting today, we will begin removing deprecated targeting from older resources. These resources consist of Line Items or Insertion Orders that are currently archived or have been paused for more than six months.
In February 2021, the deprecated targeting options will no longer be retrievable through the Targeting Options service and attempts at assigning or removing deprecated targeting through the Line Item Assigned Targeting Options service will return an error.
After the deprecated targeting options are no longer able to be assigned, we will begin removing deprecated targeting from all remaining resources. Any line items only using deprecated targeting will be paused upon the removal of said targeting. This concludes the formal sunset of the deprecated targeting options.

What should I do to prepare for this?

In anticipation of this sunset, it is recommended that you do the following:

Check to see if any existing Line Items utilize deprecated targeting options. Use advertisers.lineItems.targetingTypes.assignedTargetingOptions.list to list the assigned Geo Region targeting for each active line item and check the targeting against the deprecated targeting options. Remove or replace any deprecated targeting as soon as possible using advertisers.lineItems.bulkEditLineItemAssignedTargetingOptions.
If you are storing oft-used targeting option IDs locally, cross-reference them against the list of deprecated targeting options. This will avoid errors caused by attempting to assign sunset targeting options.

Should I expect more deprecations in the future?

Users should expect the occasional deprecation and sunset of targeting options in Display & Video 360 in much smaller quantities than this deprecation. As such, future deprecations likely won’t be announced through a blog post or documentation change.

In order to account for these deprecations, it is recommended that you use targetingTypes.targetingOptions.get to confirm that a targeting option is still available before assigning it. This should be done before assigning any option not obtained through the Targeting Options service, including those stored locally or copied from existing targeting. This will avoid errors caused by attempting to assign deprecated targeting.

You can read more about the Targeting Options and Assigned Targeting Options services in our reference documentation and on the Set Targeting page of our Managing Line Items guide.
If you have questions or run into issues navigating this process, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Sunset approaching for v2 of the Content API for Shopping

Wednesday, November 11, 2020

We are writing to remind you that the Content API for Shopping v2 will sunset on March 29, 2021. On this date, all requests made against v2 of the Content API will fail. Please migrate to v2.1 as soon as possible to ensure your applications are unaffected. To help with the migration to v2.1, we have prepared the following resources:

Migration guide -- Explains how to update your applications for v2.1.

Supplemental feeds guide — In v2.1, supplemental feeds replace the v2 inventory service for partial updates to online products.

Local inventory service guide — In v2.1, the local inventory service replaces the v2 inventory service for updates to local inventory.

Release notes -- Lists all changes and new features added in v2.1, organized by release date.

If you have questions about the migration or encounter challenges that prevent you from migrating, we want to hear from you. Please reach out to us on the forum so we can help.

Benji Rothman, Content API for Shopping Team

Sunset of the Ad Manager API v201911

Thursday, November 5, 2020

On Monday, November 30, 2020, in accordance with the deprecation schedule, v201911 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

If you’re still using v201911, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v202002 we added a number of video and reporting features.

When you’re ready to upgrade, check the full release notes to identify any breaking changes, like Activity and ActivityGroup IDs changing from type int to type long in v202005. Then, grab the latest version of your client library and update your code.
As always, don't hesitate to reach out to us on the developer forum with any questions.

- Donovan McMurray, Ad Manager API Team

Target Spend Migration for Maximize Clicks Bid Strategies

Thursday, October 29, 2020

Starting January 18, 2021, we will start migrating Maximize Clicks bid strategies that still utilize the deprecated target_spend setting to use campaign daily budget pacing instead. This follows last year’s sunset of the target_spend field for Maximize Clicks. After that sunset went into effect, Google Ads has prevented users from creating any new Maximize Clicks strategies that have a target_spend setting. What’s changing As part of this migration, any Maximize Clicks bid strategies that still use the target_spend setting may have their maximum CPC bid limit lowered to minimize the performance impact that may result from this change. This would affect the following API fields:

Fields whose values may be lowered as part of the January 18, 2021, migration:

AdWords API

Google Ads API

TargetSpendBiddingScheme.bidCeiling

TargetSpend.cpc_bid_ceiling_micros

What you can do You can avoid the above changes by removing the target spend setting on your campaigns’ bidding strategies before January 18, 2021. To do so, unset the following field (set its value to 0) on any existing Maximize Clicks bid strategies:

Fields to unset (set to 0) to avoid the migration:

AdWords API

Google Ads API

TargetSpendBiddingScheme.spendTarget

TargetSpend.spend_target_micros

If you have any questions or need additional help, contact us via the forum or at googleadsapi-support@google.com.

Adam Ohren, Google Ads API Team

Google Ads API v2 sunset reminder

Thursday, August 27, 2020

sunsetAfter this date, all v2 API requests will begin to fail.newer version

Upgrading to the newest version

Release notes

forumgoogleadsapi-support@google.com

- Thanet Knack Praneenararat, Google Ads API Team

Ads Developer Blog

Feed-based Extensions Sunset in Google Ads APIs

Sunset of the Ad Manager API v202005

Reminder to migrate to the AdMob API

Google Ads API v4 and v5 sunset reminder

Upgrade to the Google Ads API from the AdWords API by April 27, 2022

Reminder: Using v2.0 of the Content API for Shopping with new accounts ends on April 30, 2021

Announcing v2 of the AdSense Management API

Sunset grace period for existing v2 users of the Content API for Shopping

Sunset date for deprecated DBM API services postponed to April 15, 2021

Reorganizing Similar Bid Strategies

Changes to Showcase Shopping ads

Sunsetting Portofolio Enhanced CPC Bid Strategies

Sunset of the Ad Manager API v202002

Google Ads API v3 sunset reminder

Upcoming sunset for DBM API v1, SDF Download and Line Item services

Sunset of deprecated Geo Region targeting options in Display & Video 360 API

Sunset approaching for v2 of the Content API for Shopping

Sunset of the Ad Manager API v201911

Target Spend Migration for Maximize Clicks Bid Strategies

Google Ads API v2 sunset reminder

Labels

Archive

Subscribe to our feeds

Google Ads API [+]

AdWords API [+]

Google Ads scripts [+]

Content API for Shopping [+]

Google Ad Manager API [+]

DCM API [+]

DV360 API [+]

DBM API [+]

Mobile Ads [+]

IMA SDK [+]