Google Ads API moves to two releases a month starting with v26

Google Ads API moves to two releases a month starting with v26

12 October 2026: Google has published its Google Ads API release and sunset schedule for 2026 and 2027. From version 26 the API ships two releases a month instead of one, while the date on which each older version stops working stays where it was. The four major versions that sit in production today, v23 to v26, switch off between February and November 2027.

Not yet independently verified. Single source: the Google Ads Developer Blog post; every date in it is stated by Google as projected. We will update this when it can be confirmed, and remove this note.

Two releases a month, one breaking change a quarter

Google's Google Ads API team moved to a monthly release schedule a year ago. The October 2026 post takes that further: starting with v26, there are two releases per month. Only four a year are major releases, which are the ones that can change or remove existing behaviour. Every other release is a minor release that adds new features without breaking existing calls.

The team lists the plan as tentative and subject to change. In its table, v26 is a major release due in October 2026, with v26.1 the same month, v26.2 in November and v26.3 in December, which the post says may be skipped. The next major, v27, is projected for January 2027, v28 for April 2027, v29 for July 2027 and v30 for October 2027, each followed by its minor releases in the months between.

The release blog posts and YouTube release events that accompany each version are also thinning out. They move to twice a quarter.

When each version stops working

A major version stays available for one year, and minor releases are retired together with the major version they belong to. Google says the sunset schedule is unchanged, so teams do not have to migrate more often than before.

For versions already released, the projected sunset dates are:

• v23: February 2027
• v24: May 2027
• v25: August 2027
• v26: November 2027

For versions still to come, the post gives v27 as February 2028, v28 as May 2028, v29 as August 2028 and v30 as November 2028. Every date is marked as projected, and Google reserves the right to add, remove or reclassify releases between minor and major.

The practical reading is a quarterly cadence. A team that wants to stay clear of deprecations has one major version to adopt and one to retire roughly every three months, which is how the schedule has run until now.

Who needs to read this

The post lists no formal required action. It matters most to anyone who maintains their own code against the Google Ads API: agencies with in-house reporting or bid tooling, marketing platforms that connect customers' accounts, and internal data teams that pull campaign reports into a warehouse. Customers of a packaged advertising or reporting product are one step removed, because the vendor carries the migration, but they can ask which API version the product calls and when it plans to move.

An application still pinned to v23 has until February 2027. One on v24 has until May. The first of those deadlines is about four months after the v26 launch month, which is a short time for a team that has not touched its integration in a year.

Teams that want advance notice can save the Google Ads API release notes page, which the post suggests as a way to receive change notifications. The post was written by Anash P. Oommen of the Google Ads API team and published on 12 October 2026.

Sources

• Google Ads Developer Blog: Google Ads API Release and Sunset Schedules for 2026-2027, 12 October 2026