With the release of a new version, a deprecated version may be given a sunset date, after which that version will no longer be available.
Our client libraries support any available versions of a service, so you can gradually upgrade by specifying different versions of used services.
Differences between deprecation and sunset
|Definition||The deprecated version is a version that is not the latest one. Once a new version is released, all previous versions will be marked deprecated.||The sunset version can no longer be used. Requests sent to this version will fail on or after the sunset date.|
|Implication||You can still use the deprecated versions until they're sunset,
but the references of the deprecated versions are de-highlighted to show
that they're not the latest version anymore.
We encourage you to migrate to the latest version as soon as possible to benefit from new features.
|You need to migrate from the sunset versions immediately in
order to use the Google Ads API.
We highly recommend that you migrate to the latest version, using the migration guide.
|Timing||On average, we release a new version every 3 to 4 months, so the given version will be deprecated after approximately 3 to 4 months.||We aim to sunset a version 8 to 10 months after its release.|
|API||API endpoints for the deprecated versions still function as
You can access our API endpoints using our client libraries, REST, etc., however, new features are not added to deprecated versions.
|API endpoints for the sunset versions stop working after the sunset dates. The Google Ads API will throw an error if you try to access the API endpoints of the sunset versions.|
|Client libraries||For purposes of providing compact client libraries, we will stop including deprecated API versions in a new client library version after the deprecation date. This helps you save space when incorporating our client libraries in your projects.||Client libraries no longer support the sunset API versions in any new client library versions after the sunset dates.|
|Support||We provide regular support for the deprecated versions.||The sunset versions are no longer supported after the sunset date.|
The table below lists the specific deprecation and sunset dates for each available version. We encourage you to migrate to the newest version as soon as feasible after its release.
|API version||Release date||Deprecation date||Sunset date||Migration guide|
|v12||October/November 2022||June/July 2023|
|v11||June/July 2022||March/April 2023|
|v10||February 9, 2022||October/November 2022|
|v9||November 3, 2021||February 9, 2022||July 13, 2022||Migrating from v9 to v10|
Subscribe to the Google Ads developer blog to be the first to hear about upcoming feature deprecations.
The table below lists the specific feature deprecations that are currently planned for the Google Ads API. More details for each deprecation can be found in the linked blog posts.
|Feature||Description||Effective Date||Additional Notes|
|Expanded text ads||Expanded text ads have been deprecated and starting June 30, 2022, you'll no longer be able to create or edit them.||June 30, 2022||After the sunset, expanded text ads will continue to serve, and you'll still see reports on their performance going forward. You'll still be able to pause, resume, or remove them if needed. However, we strongly encourage you to transition to responsive search ads.|
|Smart Shopping and Local Campaigns||
Smart Shopping (SSC) and Local Campaigns (LC) are being upgraded to
Performance Max. Once
upgraded, existing SSC and LC will be marked as
|September 30, 2022||There will be a self-upgrade period using a future recommendation type. This will be followed by a rolling auto-upgrade period.|
|Feed-based dynamic remarketing (second batch)||
Feed-based DSA page feeds and dynamic remarketing will be replaced with asset-based equivalents for the following types:
|October 5, 2022||Feeds will automatically migrate to Assets on October 5, 2022. Check out the documentation for more details on migrating.|