Google Ads API v20 Sunset in June — when and how should I migrate?

Choose whether to hop from v20 straight to a newer version now or do an intermediate upgrade before June 2026 shuts v20 off.

Jump to v22 now if you can absorb one focused regression cycle; use v21 first only when the codebase is too brittle for a two-version leap.

Blockers

Who this is for

Candidates

Jump from v20 directly to v22 now

As of 2026-03-20, Google lists v20 with a tentative sunset in June 2026, v21 with a tentative sunset in August 2026, and v22 with a tentative sunset in October 2026. Google also states you do not need to upgrade in strict sequential order and can move from version N directly to N+2, while client libraries can support gradual service-by-service migration. Major versions use separate endpoints and can include breaking changes, so this path compresses the v20 to v21 and v21 to v22 migration work into one program. As of 2026-03-20, the official docs surface access-level quotas rather than version-specific API pricing: Basic allows 15,000 operations per day and Standard allows unlimited operations for most services.

When to choose

Use this when you want to avoid doing two major-version migrations inside a few months and you can afford one concentrated regression cycle now. It is the stronger choice if your integration is mature enough to absorb both v21 and v22 breaking changes together in exchange for the longest post-migration support window currently verified.

Tradeoffs

One migration program, one endpoint hop, and the longest verified runway versus more combined breakage to test at once.

Cautions

You must review both the v20 to v21 and v21 to v22 changes together. Verified blocker-level changes include renamed video metrics in v22, removal of AssetPerformanceLabel for Performance Max, replacement of Campaign.url_expansion_opt_out handling with AssetAutomationType FINAL_URL_EXPANSION_TEXT_ASSET_AUTOMATION, a 10,000-operations limit per AddBatchJobOperations request, and stricter ListBatchJobResultsRequest page_size behavior.

Sources

Upgrade to v21 first, then move again before v21 sunsets

As of 2026-03-20, moving from v20 to v21 buys only a short extension because v21 is tentatively scheduled to sunset in August 2026, about two months after v20. v21 already introduces new surface area such as AI Max for Search controls and adds account and campaign fields for EU political advertising declaration in v21.1. This path reduces the immediate jump size, but it still requires another major-version migration shortly after because v22 was released on 2025-10-15 and remains the latest fully verified major version in the official release notes. As of 2026-03-20, the official access model remains quota-based rather than showing version-specific API pricing, with Basic at 15,000 operations per day and Standard unlimited for most services.

When to choose

Use this when your current codebase is brittle and the fastest safe move is a smaller first step that gets you off the June 2026 v20 deadline. It is mainly justified if your team needs to isolate v21-specific breakage first, especially around campaign behavior and policy fields, before taking on v22.

Tradeoffs

Smaller first migration and potentially simpler debugging now, but it creates two endpoint upgrades, two test cycles, and another forced change window before August or October 2026 deadlines arrive.

Cautions

Do not treat v21 as a durable resting place. Verified blocker-level migration issues include major-version endpoint changes, AI Max for Search additions in v21, video metric renames already visible around the v21 release, and ongoing EU political advertising declaration handling where missing self-declaration can already trigger criterion and experiment errors in some flows.

Sources

Facts updated: 2026-03-20
Published: 2026-04-03

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "Google Ads API v20 Sunset in June — when and how should I migrate?"
Missing something? Request coverage