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.
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
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:
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:
If you have any questions or need additional help, contact us via the forum or at [email protected].
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]
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:
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
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
IDs changing from type int to type long
in v202005. Then, grab the latest version of your client library and update your code.