Google preparing to shut down Ads API v19 in February 2026

Google introduced on December 15, 2025, that model 19 of the Google Advertisements API will sundown on February 11, 2026. Beginning on that date, all API requests utilizing v19 will start to fail, forcing builders to finish migrations to newer variations earlier than the sundown deadline.

The announcement from Ben Karl and the Google Advertisements API Group offers builders roughly two months to improve their implementations. Model 19 first launched on February 26, 2025, giving it a lifespan of practically 12 months earlier than deprecation—in step with Google’s documented model help timeline.

Based on the deprecation documentation, Google maintains a most of 4 main API variations concurrently. The corporate releases new variations each three to 4 months on common, with every main model receiving help for about 12 months. Minor variations obtain help for round 10 months.

The sundown means builders face necessary code modifications earlier than February 11. The Google Advertisements API staff emphasised that “all v19 API requests will start to fail” beginning on the sundown date. This tough cutoff differs from deprecation, which marks a model as now not present whereas sustaining performance till sundown.

The sundown announcement arrived amid Google’s shift to monthly API releases starting January 2026. That change will increase main releases from three to 4 yearly whereas introducing month-to-month minor variations containing non-breaking function additions.

Migration timeline compresses as vacation season concludes

The February sundown date leaves minimal respiration room for builders who delayed migration in the course of the November-December vacation interval. Google’s month-to-month launch schedule excludes end-of-year intervals, recognizing lowered improvement exercise throughout conventional vacation seasons.

Builders should improve to model 20, 21, or 22 to keep up API entry past February 11. Model 20 launched on June 4, 2025, whereas version 21 arrived on August 6, 2025. The latest main launch, version 22, became available on October 15, 2025.

The deprecation documentation specifies that builders can improve on to non-sequential variations. Organizations operating v19 implementations can leap on to v22 with out migrating by v20 or v21, although they have to assessment cumulative breaking adjustments throughout a number of variations.

Google maintains improve guides for every model transition. The corporate printed particular steerage for upgrading from v18 to v19, although builders concentrating on v22 should assessment adjustments throughout all intermediate variations to account for deprecated fields and renamed metrics.

Monitoring model utilization by Cloud Console

Google offers strategies for builders to determine which API variations their tasks at the moment use. The corporate directs builders to the Google Cloud Console to assessment current API request patterns.

The APIs & Companies part of the Cloud Console shows current requests plotted throughout graphs. Builders can look at the Strategies desk to see which particular API strategies acquired requests. Technique names embody the API model, service, and technique title in codecs like “google.advertisements.googleads.v19.providers.GoogleAdsService.Mutate.”

Builders can filter these metrics by timeframe to grasp model utilization throughout totally different intervals. This performance helps organizations audit their implementations and determine which code paths require upgrades earlier than the February sundown.

The Cloud Console visibility addresses a standard problem the place organizations function a number of functions or integrations in opposition to the Google Advertisements API. Completely different code repositories or improvement groups could use totally different variations, making centralized model monitoring important throughout migration intervals.

Shopper library help ends for sundown variations

The deprecation schedule impacts each API endpoints and consumer library availability. Google maintains formally supported consumer libraries for Java, C#, PHP, Python, Ruby, and Perl that simplify API integration.

Based on the deprecation documentation, Google stops together with deprecated API variations in new consumer library releases after the deprecation date. This observe reduces consumer library file sizes by eradicating outdated code. The documentation emphasizes that “deprecated API variations are nonetheless accessible in beforehand launched consumer library variations.”

Builders can proceed downloading and utilizing older consumer library variations that embody v19 help till the API model sunsets. After February 11, 2026, consumer libraries now not help v19 in any new consumer library variations.

The consumer library model compatibility desk reveals that Java consumer library variations beginning at 36.0.0 help v19. The utmost model supporting v19 stays unspecified within the documentation, as Google continues publishing updates till the sundown date.

For v20, Java consumer library help begins at model 38.0.0. Model 21 requires minimal Java consumer library model 39.0.0, whereas v22 help begins at model 41.1.0. Related minimal model necessities exist for different programming language consumer libraries.

Model overlap offers transition flexibility

Google’s model help technique maintains overlap between launch and sundown dates to facilitate gradual migrations. The overlap between when all consumer libraries launch for the newest model and when the earlier model sunsets spans no less than 20 weeks.

This overlap interval allows organizations to check new variations totally earlier than legacy variations expire. Improvement groups can validate performance, determine breaking adjustments, and modify integration code whereas sustaining manufacturing methods on older variations.

The documentation specifies that consumer libraries help any accessible service variations. This functionality permits builders to specify totally different variations for various providers inside single functions throughout transition intervals, enabling incremental migration methods.

Model 19 contains three releases: the bottom v19 from February 26, plus v19.1 from April 16 and v19.2 from August 6. All three v19 variants share the February 2026 sundown date. The minor model releases added options with out breaking present implementations, permitting builders to undertake new capabilities whereas sustaining v19 compatibility.

EU political promoting necessities span a number of variations

One important function launched throughout a number of variations impacts campaigns containing European Union political promoting content material. Google added the “contains_eu_political_advertising” discipline to the Marketing campaign object in v19.2, v20.1, and v21.

This discipline signifies whether or not campaigns comprise political promoting content material focused towards the European Union. Campaigns marked as containing EU political promoting will now not serve within the EU beginning September 22, 2025.

The documentation specifies that for present campaigns, builders ought to set the “contains_eu_political_advertising” discipline earlier than trying to alter proximity, location, or location group concentrating on at marketing campaign or advert group ranges. API calls creating or updating these concentrating on standards for present campaigns fail with a “CriterionError.MISSING_EU_POLITICAL_ADVERTISING_SELF_DECLARATION” error if the marketing campaign hasn’t accomplished self-declaration.

For v19.x and v20.x, the requirement to set this discipline is just not but enforced, although enforcement will arrive sooner or later. Google promised advance announcement of this enforcement change.

Trials and Experiments throw an “ExperimentError.MISSING_EU_POLITICAL_ADVERTISING_SELF_DECLARATION” error if experiment campaigns have not self-declared whether or not they comprise political promoting concentrating on the European Union.

Migration sources consolidate throughout documentation

Google directs builders encountering questions throughout upgrades to contact [email protected]. The corporate additionally maintains a Google Promoting and Measurement Group Discord server the place builders can talk about migration challenges.

The announcement contains direct hyperlinks to improve documentation and launch notes. These sources element function additions, deprecations, and breaking adjustments requiring code modifications. Builders using renamed metrics or deprecated fields should replace queries and discipline references to keep up compatibility.

The discharge notes for v19 by v22 doc tons of of adjustments throughout belongings, campaigns, conversions, Demand Gen options, Efficiency Max capabilities, planning providers, reporting sources, and video promoting. Main additions embody AI Max for Search campaigns in v21, targetless bidding for App campaigns in v22, and expanded automation capabilities throughout a number of marketing campaign varieties.

Breaking adjustments in newer variations embody elimination of feed-related entities in v19, renamed video metrics in v21 and v22, and changes to batch operation limits. Organizations with advanced implementations spanning a number of providers should assessment adjustments comprehensively to make sure clean transitions.

The sundown timeline aligns with Google’s broader sample of standard model retirement to keep up safety, efficiency, and have consistency throughout the platform. The February 11 deadline applies absolute enforcement, that means improvement groups face exhausting cutoffs slightly than gradual degradation of performance.

For advertising and marketing know-how distributors, companies, and advertisers working programmatic Google Advertisements implementations, the v19 sundown requires rapid consideration to deployment calendars. Organizations should allocate improvement sources to finish migrations, execute testing protocols, and deploy up to date code earlier than the February deadline.

Timeline

• February 26, 2025 – Google releases Ads API v19 with account administration enhancements, asset automation, and conversion objective enhancements
• April 16, 2025 – Google releases Advertisements API v19.1 introducing Demand Gen channel controls and Native Companies suggestions mechanisms
• June 4, 2025 – Google releases Advertisements API v20 with expanded Efficiency Max campaign-level adverse key phrase help
• August 6, 2025 – Google releases Ads API v21 introducing AI Max for Search campaigns and marketing campaign search time period view
• August 6, 2025 – Google releases v19.2, v20.1, and v21 with EU political promoting self-declaration necessities
• September 4, 2025 – Google announces monthly API releases beginning January 2026, extending main model help to at least one 12 months
• October 15, 2025 – Google releases Ads API v22 including targetless bidding for App campaigns and generative AI asset creation
• December 15, 2025 – Google proclaims Advertisements API v19 sundown for February 11, 2026
• February 11, 2026 – Google Advertisements API v19 sundown takes impact; all v19 requests start failing

Abstract

Who: Google Advertisements API builders, advertising and marketing know-how distributors, companies, and advertisers utilizing model 19 of the Google Advertisements API for programmatic marketing campaign administration.

What: Google will sundown model 19 of the Google Advertisements API on February 11, 2026. All API requests utilizing v19 will fail beginning on this date. Builders should improve to model 20, 21, or 22 earlier than the sundown deadline to keep up API entry.

When: The sundown takes impact on February 11, 2026. Google introduced the sundown on December 15, 2025. Model 19 initially launched on February 26, 2025, giving it roughly 12 months of help in step with Google’s documented model lifecycle.

The place: The sundown impacts all Google Advertisements API v19 endpoints throughout Google’s promoting platform. Builders can monitor their present model utilization by the Google Cloud Console by inspecting APIs & Companies metrics for current requests.

Why: Google maintains a most of 4 main API variations concurrently, with every receiving roughly 12 months of help. Model retirement allows Google to keep up safety, efficiency, and have consistency whereas directing developer sources towards present platform capabilities. The sundown aligns with Google’s broader shift to month-to-month API releases starting January 2026.