What changed
Google's October 12, 2026 developer announcement accelerates the Google Ads API from its existing monthly releases to two releases per month beginning with v26, expected October 2026. Four major versions per year remain the only scheduled breaking-version boundary. Other releases are additive, non-breaking minor updates that sunset with their parent major release. Google says the major version lifetime and existing sunset schedule are unchanged: v26 is tentatively due October 2026 with November 2027 sunset; v27 January 2027 with February 2028 sunset; v23, v24 and v25 sunset in February, May and August 2027 respectively. Individual release dates remain estimates and may move or be skipped.
Why it matters
Agencies, SaaS advertising tools and internal campaign automation systems can access newly introduced Google Ads features sooner, but the monitoring burden rises: a team reading only quarterly launch posts may miss additive fields, services and enum values introduced between major releases. Because minors share the parent's sunset, integrators should not assume each new minor creates a separate one-year migration clock. Version pinning, schema-aware tests and a release-notes watch are more useful than blanket upgrades after every announcement.
Two updates a month, but only four breaking-version milestones
Google says v26 starts the twice-monthly schedule. Four annual major releases remain; all other releases are minor and add non-breaking features. The company expects v26 and v26.1 in October, v26.2 in November, and may skip a December minor. The projected v27 series starts January 2027, followed by more frequent minors; the dates and release types are explicitly tentative.
The support and sunset clock does not double
Minor versions expire when their parent major version does. Google's published schedule currently projects v23 retirement February 2027, v24 May, v25 August and v26 November 2027. This means teams can adopt useful minor features while planning breaking migrations around the four major-version deadlines rather than a new expiry for every minor.
Release notes become the primary operational feed
Google plans consolidated release blog posts and live events twice a quarter, rather than a post for each minor update. Developers should subscribe to the Google Ads API release notes and use schema and integration tests to identify when newly available fields, resources or services are needed. A more frequent additive schedule is not a promise that any particular desired UI feature will be available immediately.