Google yesterday said its Ads API will ship two releases a month starting with version 26, doubling the monthly cadence it adopted in January 2026, while keeping four major versions a year and leaving sunset dates unchanged. A tentative schedule published on the Google Ads Developer Blog lists 25 versions between October 2026 and December 2027.

In Short

Google is going to update the toolkit that software uses to talk to Google Ads twice a month instead of once a month. Most of those updates only add things, so code that already works keeps working, and the number of big updates that can break code stays at four a year. If you build or run tools on top of Google Ads, new features arrive sooner, but the deadlines for moving off old versions do not come any faster.

What changed

The announcement, signed by Anash P. Oommen of the Google Ads API Team and dated October 12, 2026, is short. It sets out one change of pace and several things that stay the same.

The change: starting with v26, the Google Ads API moves to two releases per month. According to Google, the faster cadence gives "automated agents and workflows near-instant access to cutting-edge features." The company frames the decision around what it calls "a new agentic era where speed and agility are paramount."

What stays the same is arguably more important for anyone who maintains production code. Google will still ship four major releases per year. Every other release will be a minor release that, according to the post, adds "only new, non-breaking features." Each major release remains available for one year after its launch. And sunset schedules, according to Google, "are also unchanged, so you will not need to migrate more often." Each minor release retires on the same date as its parent major version.

Communication changes too. Release blog posts and YouTube live events will move to twice a quarter, each covering key updates from several releases at once. Developers who want to follow individual releases are directed to save the Google Ads API release notes page, which will notify them when it changes.

From one release a month to two

The new cadence comes barely a year after the last one. On September 4, 2025, Google moved the Ads API to monthly releases starting January 2026, raising major releases from three to four per year and filling the months between them with minor versions. That plan projected v23 in January, v24 in April, v25 in July and v26 in October, with an optional v26.1 in November and nothing in December.

The 2026 releases broadly followed that pattern. Version 23 launched on January 28, 2026. Version 24 arrived on April 22, with breaking changes that removed the campaign-level video brand safety setting and much of the keyword forecasting method. Minor release v24.2 followed on June 24, adding synthetic content labeling and network segmentation for Performance Max placement reporting, and was billed as a drop-in upgrade. Version 25 landed on July 22 and removed the CustomerLifecycleGoal and CampaignLifecycleGoal resources outright. A month later, v25.1 shipped on August 19 as the first minor release of that cycle.

The 2025 plan allowed for at most 11 releases across 2026. The schedule published today lists 21 for calendar 2027 alone: four majors (v27, v28, v29 and v30) and 17 minor versions. Every month from February to October 2027 carries two releases. January, November and December carry one.

The schedule, version by version

Google describes every date in the table as an estimate. The company says it "may also add or remove releases, or switch a release between major and minor."

Rest of 2026

Version Type Projected launch Projected sunset
v26 Major October 2026 November 2027
v26.1 Minor October 2026 November 2027
v26.2 Minor November 2026 November 2027
v26.3 Minor December 2026 November 2027

2027

Version Type Projected launch Projected sunset
v27 Major January 2027 February 2028
v27.1 Minor February 2027 February 2028
v27.2 Minor February 2027 February 2028
v27.3 Minor March 2027 February 2028
v27.4 Minor March 2027 February 2028
v28 Major April 2027 May 2028
v28.1 Minor April 2027 May 2028
v28.2 Minor May 2027 May 2028
v28.3 Minor May 2027 May 2028
v28.4 Minor June 2027 May 2028
v28.5 Minor June 2027 May 2028
v29 Major July 2027 August 2028
v29.1 Minor July 2027 August 2028
v29.2 Minor August 2027 August 2028
v29.3 Minor August 2027 August 2028
v29.4 Minor September 2027 August 2028
v29.5 Minor September 2027 August 2028
v30 Major October 2027 November 2028
v30.1 Minor October 2027 November 2028
v30.2 Minor November 2027 November 2028
v30.3 Minor December 2027 November 2028

Two December releases, v26.3 and v30.3, carry a caveat: Google says it may skip them because they fall during the holiday season. The v27 cycle has four minor versions rather than five, according to Google, because its January launch also falls in the holiday period. The v26 and v30 cycles run to three minor versions each, with one of those three at risk in each case.

Sunsets in 2027

The separate sunset table covers four versions that reach end of life next year. Minor versions such as v23.x retire with their parent.

Version Projected sunset
v23 February 2027
v24 May 2027
v25 August 2027
v26 November 2027

The first two dates match what Google projected in September 2025, when it listed v23 and its minor versions for February 2027 and v24 for May 2027. The v25 date is new. When v25 shipped in July, PPC Land's reading of the twelve-month lifecycle pointed to a sunset around July 2027. The table now places it in August 2027.

What "one year" means in practice

Google's post says each major release "will still be available for one year after the release." The table suggests something slightly longer. Every major version in it sunsets in the month after its launch month a year later: v26 arrives in October 2026 and retires in November 2027, v27 goes from January 2027 to February 2028, and the pattern holds through v30. Using the actual 2026 launch dates, v23 (January 28, 2026) is slated to retire in February 2027 and v25 (July 22, 2026) in August 2027. Read month to month, that is roughly 13 months of availability rather than 12. Google's wording and its table do not line up exactly, and the post does not explain the gap.

Minor versions are a different matter. Because a minor release retires with its parent major, its useful life depends on how late in the cycle it arrives. Version 28.1, projected for April 2027, gets about 13 months before its May 2028 sunset. Version 28.5, projected for June 2027, gets about 11. The same compression applied under the monthly plan; when Google set the v19 sunset for February 11, 2026, v19.1 and v19.2 shared the same date, and PPC Land noted at the time that minor versions typically received about 10 months of support against roughly 12 for majors. Doubling the number of minor releases does not lengthen any of them.

There is also a period when five major versions overlap. If v27 arrives in January 2027 as projected and v23 is not retired until February 2027, then v23, v24, v25, v26 and v27 will all be live at the same time for several weeks. This is an inference from the projected dates, not something Google states.

Why minor releases matter less than they look

For a developer, the number that drives workload is not how many versions ship but how many require code changes. On that measure, today's announcement changes nothing. Four majors a year was already the rule. Breaking changes, such as the lifecycle goal removals in v25 or the field removals in v24, arrive with majors. Minor releases are additive: v24.2 and v25.1 were both described by Google as drop-in upgrades.

What changes is the effort required to keep track. With 17 minor versions scheduled for 2027 and the blog and YouTube recaps cut to twice a quarter, the release notes page becomes the main place where individual changes are documented. A team that only reads the quarterly-ish roundups may learn about a feature weeks after it became available through the API. Whether that matters depends on how quickly an integration needs new features, which is exactly the argument Google makes for the change.

There is an operational question, too. Every API version is a target that client libraries, internal wrappers and test suites have to recognize, so twice-monthly releases imply more frequent library updates, even if most of them are optional. The post does not address client library cadence.

The agentic framing

The stated rationale is unusual for an API housekeeping post. Google ties the faster pace explicitly to automated agents, saying it allows "your automated agents and workflows near-instant access to cutting-edge features." That language fits a sequence of moves Google has made around the Ads API over the past year.

On October 7, 2025, the company released an open-source, read-only MCP server for the Ads API, letting AI tools query Google Ads data through natural language. MCP, the Model Context Protocol, has since become the standard way ad platforms expose their systems to AI assistants; Meta opened its ads MCP server to any developer with a Meta app on July 16, 2026, with write access for campaign management.

Google has also tightened who can build on its API. Updated developer policies published on August 31, 2026 banned programmatic proxies from Ads API access, a definition that covers hosted MCP servers and wrapper APIs that re-expose Google Ads capabilities to third parties, and required each integration to run through its own Google Cloud project. Then on September 10, 2026, Google moved Ads API signup and access management into the Google Cloud Console, transferred access levels from developer tokens to Cloud projects and made brand verification mandatory for new Basic and Standard Access applications. Google said at the time that it would reject developer tokens in API calls in a future major version, without naming which.

That last point gives the new schedule more weight than its tone suggests. With majors still arriving every quarter, any one of v27 through v30 could carry the developer token removal, and the projected dates now indicate roughly when those versions will appear.

Put together, the picture is of a platform building for agentic AI integrations on its own terms: faster feature access for direct integrations, tighter control over intermediaries, and a release structure designed to deliver features within weeks of their appearance in the Google Ads interface.

How it compares

Google's approach contrasts with Meta's. Meta's Graph API and Marketing API do not follow a fixed monthly rhythm. Graph API v26.0 arrived on July 29, 2026, about five months after v25.0, and blocked 47 Commerce Order Management endpoints with no replacement. Meta's older versions remain accessible for considerably longer; v21.0 is scheduled for removal on January 21, 2027, more than two years after its October 2024 release.

Within Google's own advertising stack, the Display & Video 360 Structured Data Files follow yet another rhythm. In June 2026, Google set a January 28, 2027 sunset for SDF v9, v9.1 and v9.2, giving users about seven months to move to v10 or later.

Against Meta's schedule, the Google Ads API now pairs a shorter major-version lifespan with far more frequent releases.

Why this matters for advertisers and agencies

Most advertisers never touch the Google Ads API directly. They encounter it through bid management platforms, reporting dashboards, feed tools, agency scripts and, increasingly, AI assistants. The schedule matters to them because it governs how quickly those tools can expose new Google Ads features and how often vendors must spend engineering time on migrations.

On the first point, Google's stated aim is to shorten the delay between a feature appearing in the Google Ads interface and the same feature becoming available to third-party tools. The post gives no figure for how long that delay has been under the monthly cadence, or how much shorter it is expected to become.

On the second point, Google's promise that migrations will not become more frequent holds only as long as the minor-release rules hold. If the company uses its stated right to "switch a release between major and minor," a planned minor version could become a breaking release. The post offers no notice period for such a switch.

For agencies running in-house tooling, the more practical consequence may be the information flow. Release recaps every six weeks or so, rather than with each version, mean that tracking individual changes now depends on watching the release notes page directly.

And for anyone building agent-based tools on top of Google Ads, the message from the past 13 months is consistent: faster features, but only for integrations that connect directly through their own Cloud project, under Google's verification rules.

Timeline

Summary

Who: The Google Ads API Team, in a post signed by Anash P. Oommen, affecting developers, ad tech vendors, agencies and advertisers whose tools connect to Google Ads programmatically.

What: Google is moving the Ads API to two releases per month starting with v26, while keeping four major releases per year, one-year availability for each major and unchanged sunset schedules. A tentative schedule lists 25 versions from October 2026 to December 2027, and sunsets for v23, v24, v25 and v26 in February, May, August and November 2027. Release blog posts and YouTube live events drop to twice a quarter.

When: Announced today, October 12, 2026, with the new cadence starting at v26, projected for October 2026.

Where: Published on the Google Ads Developer Blog; the change applies to the Google Ads API worldwide.

Why: Google says the faster cadence gives automated agents and workflows quicker access to new Ads features, framing the move around agentic AI. The change follows a year in which Google released an MCP server, banned programmatic proxies and moved API access management to Google Cloud.