Tag Archives: sunset

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

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

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

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

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:
  1. 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.
  2. 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.
  3. 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:

  1. 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.
  2. 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

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

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

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 [email protected].

 Adam Ohren, Google Ads API Team

Google Ads API v2 sunset reminder

Google Ads API beta v2 will sunset on October 21, 2020. After this date, all v2 API requests will begin to fail. Please migrate to a newer version prior to October 21, 2020 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: If you have questions while you’re upgrading, please reach out to us on the forum or at [email protected].
 - , Google Ads API Team

Sunset of DBM API v1, SDF Download and Line Item services

Today we’re announcing the deprecation of the Doubleclick Bid Manager (DBM) API v1.1 Line Item service and the sunset of all deprecated DBM API services on February 26, 2021. Deprecated DBM API services include the entirety of DBM API v1 and DBM API v1.1 Structured Data File (SDF) Download service. This sunset was originally scheduled for June 15, 2020, but was postponed due to COVID-19.


Refer to the table below to verify if the methods you are currently using will be available in v1.1 after February 26, 2021:

Service Methods Available in v1.1 after
February 26, 2021?
Reporting queries.createquery

queries.deletequery

queries.getquery

queries.listqueries

queries.runquery

reports.listreports 		Yes
Line Item lineitems.downloadlineitems

lineitems.uploadlineitems		 No. Use the new Display &
Video 360 API instead.
SDF Download sdf.download No. Use the new Display &
Video 360 API instead.


If you are still using the DBM API v1 Reporting service, you must migrate to v1.1 by the sunset date to avoid an interruption of service. Consult the API release notes for the finer 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. Users have to update their implementation to traverse multiple pages if they wish 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 the Display & Video 360 API and get started using it 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 the Ad Manager API v201908

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

If you’re still using v201908, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v201911 we improved reporting error messages and added the ability to break down reports by CMS Metadata.

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

Sunset of v2 for the Content API for Shopping

The Content API for Shopping v2 will sunset on March 29, 2021. On this date, all requests made against v2 of the Content API for Shopping 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 migration, please reach out to us on the forum.
Benji Rothman, Content API for Shopping Team