Deprecation and sunset

Page Summary

outlined_flag

• When a new API version is released, a deprecated version is given a sunset date after which it will no longer be available.

• Google aims to keep at most four major versions available at any time, with major versions lasting around 12 months and minor versions around 10 months.

• You will need to perform at most two upgrades per year, and you can upgrade directly to a non-sequential later version.

• There is at least a 20-week overlap between the release of client libraries for the latest version and the sunset date of the version being retired.

• You can view the Google Ads API versions used by your project in the Google Cloud Console under APIs & Services.

• Deprecated versions are still usable but not the latest, while sunset versions are no longer functional and require an immediate upgrade.

• The timetable provides specific release, deprecation, and tentative sunset dates for available API versions, encouraging upgrades to the latest version.

• Specific client library versions support different Google Ads API versions as detailed in the provided tables for various programming languages.

• Feature deprecations, such as changes to conversion environment usage and handling of gclid/gbraid values, are also announced with effective dates and details on the developer blog.

With the release of a new version, a deprecated version is given a sunset date, after which that version will no longer be available. Here are some other guidelines to keep in mind:

• We strive to keep at most five major versions available at any one time.
• Major versions have a lifespan of around 12 months—minor versions: 10 months.
• You'll have to perform at most two upgrades per year, and you don't have to upgrade in strict sequential order — for example, you can upgrade from version (N) directly to version (N+2).

Our client libraries support any available versions of a service, so you can gradually upgrade by specifying different versions of used services.

Timetable

The following table lists the specific deprecation and sunset dates for each available version, and projected release dates for future versions. We encourage you to upgrade to the latest version as soon as feasible after its release. The tentative date means that the sunset could happen any time in that month, and the dates could change. Subscribe to the blog for API version sunset announcement reminders.

API version	Release date	Sunset date	Upgrade guide
Released versions
v21	August 6, 2025	August 2026 (tentative)	Upgrade from v20 to v21
v22	October 15, 2025	October 2026 (tentative)	Upgrade from v21 to v22
v23	January 28, 2026	February 2027	Upgrade from v22 to v23
v23.1	February 25, 2026	February 2027	Upgrade from v23 to v23.1
v23.2	March 25, 2026	February 2027	Upgrade from v23.1 to v23.2
v24	April 22, 2026	May 2027	Upgrade from v23.2 to v24
v24.1	May 13, 2026	May 2027	Upgrade from v24 to v24.1
v24.2	June 24, 2026	June 2027	Upgrade from v24.1 to v24.2
Upcoming versions
v25	July 2026	August 2027
v25.1	August 2026	August 2027
v25.2	September 2026	August 2027
v26	October 2026	November 2027
v26.1*	November 2026	November 2027

* v26.1 is designated as an optional release due to overlap with the holiday season.

View the versions your project is using

You can view a list of methods and services your project has recently called using the Google Cloud Console:

1. Open the APIs & Services in the Google Cloud Console.
2. Click Google Ads API in the table.
3. On the METRICS subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as google.ads.googleads.v24.services.GoogleAdsService.Mutate.
4. (Optional) Choose the timeframe you want to view for your requests.

Differences between deprecation and sunset

Term	Deprecation	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 upgrade to the latest version as soon as possible to benefit from new features.	You need to upgrade from the sunset versions immediately in order to use the Google Ads API. We highly recommend that you upgrade to the latest version, using the upgrade 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 1 year after its release.
API	API endpoints for the deprecated versions still function as usual. You can access our API endpoints using our client libraries and REST. 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.

Supported client library versions

The table shows which client libraries work with which API versions.

The listed minimum client library version is sufficient for the major Google Ads API release (such as v24). To see the required client library version for minor releases, refer to the linked Changelog.

Feature deprecations and changes

While this page focuses on API version-level lifecycles, individual feature deprecations (such as the deprecation of Smart Campaigns) and unversioned workflow changes (such as new Demand Gen campaign budget requirements) are tracked separately.

To check upcoming feature lifecycles and behavioral shifts across active versions, see the Feature deprecations and unversioned changes guide.