Google Ads API v19 Sunset: What Breaks Today and How to Fix It Fast

As of February 11, 2026, Google Ads API v19 Sunset. Every API request using v19 now returns a failure. No grace period. No soft deprecation warning. If your tools, scripts, or integrations still run on v19, they stopped working today.

This is not a drill. Google announced the sunset back in December 2025, giving developers roughly two months to migrate. That window just closed. Here is everything you need to know to get back online immediately.

What Actually Happened

Google maintains a maximum of four major API versions at any time. Version 19 launched on February 26, 2025, giving it a nearly 12-month lifespan. That is consistent with Google’s documented version support timeline. When a version sunsets, the endpoint stops accepting requests entirely. Any call that hits the v19 endpoint now returns an error.

This matters beyond what the developer documentation suggests. Every third-party tool that connects to Google Ads through the API uses a specific version. If the tool vendor has not updated their integration, the tool breaks. That includes bid management platforms, reporting dashboards, automated rule engines, and click fraud protection software that monitors traffic patterns through API calls.

Who Is Affected

The impact splits into two groups. The first group is developers and agencies running custom scripts. If you built Google Ads automation, reporting pipelines, or campaign management tools using the API, check your code right now. Look for any reference to version 19 in your endpoint URLs or client library configurations.

Google provides a straightforward way to check. Open the Google Cloud Console, navigate to APIs & Services, and click Google Ads API. The Methods table shows every method your project has called recently. Look for “google.ads.googleads.v19” in any method name. If you see it, that integration is broken right now.

The second group is advertisers using third-party tools. If your Google Ads management stack includes external platforms for reporting, optimization, or automation, confirm with each vendor that they have migrated. Most reputable vendors handled this weeks ago. Smaller or niche tools may not have.

Your Migration Options: v20, v21, v22, or v23

You have four active versions to choose from. Each adds features on top of the previous one. Here is what each version brings to the table:

The recommendation is clear: migrate to v23 if possible. It is the latest version and gives you the longest runway before the next required migration. If your codebase needs minimal changes, v20 gets you running again quickly but sunsets in just four months.

What Changed Between v19 and v23

The jump from v19 to v23 is significant. Google introduced breaking changes in each major version. Here are the critical ones to watch for during migration.

Performance Max negative keywords (v20): Advertisers finally gained the ability to add campaign-level negative keywords to Performance Max campaigns through the API. If you manage PMax campaigns programmatically, this alone justifies the upgrade.

AI Max for Search (v21): This version introduced API access to AI Max features, including expanded keyword match type capabilities and the campaign search term view. These give you deeper visibility into what queries actually trigger your ads.

Generative AI asset creation (v22): The AssetGenerationService arrived, allowing programmatic text and image generation using Google’s AI. This is a closed beta feature but signals where Google is heading with automated creative production.

NLP audience building (v23): The newest version lets you describe audiences in natural language. Send a text description like “eco-conscious parents in urban areas” and the API returns a structured audience definition. It also removed support for call-only ads entirely.

The New Monthly Release Cadence

This sunset also marks the beginning of a new era for the Google Ads API. Starting January 2026, Google shifted from three major releases per year to four. The remaining releases are monthly minor versions that add features without breaking existing implementations.

For advertisers and media buyers, this means new features will reach the API faster. Tools that connect to your campaign performance tracking will gain capabilities more frequently. The trade-off is that version management becomes more important than ever.

Here is the projected sunset schedule for current versions: v20 retires in June 2026, v21 in August 2026, v22 in October 2026, and v23 in February 2027. Each major version gets exactly one year of support from its launch date.

Emergency Migration Steps

If your integrations broke today, here is the fastest path back to operational status.

Step 1: Identify affected integrations. Check the Google Cloud Console for any v19 method calls. Document every tool, script, and platform that touches the Google Ads API.

Step 2: Update client libraries. If you use Google’s official client libraries for Python, Java, PHP, Ruby, .NET, or Perl, update to the latest library version. The libraries support multiple API versions simultaneously, so you can migrate service by service.

Step 3: Review breaking changes. Google publishes migration guides for each version jump. Read through the breaking changes relevant to your use case. Pay special attention to removed fields, renamed services, and changed parameter types.

Step 4: Test in a sandbox. Use a Google Ads test account to validate your updated code before pushing changes to production accounts managing real ad spend.

Step 5: Verify third-party tools. Contact vendors for every external tool in your stack. This includes click fraud protection platforms, bid management software, and reporting tools. Confirm they support v20 or later.

How to Prevent This Next Time

The v19 sunset was not a surprise. Google announced it two months ahead of time. The problem is that many teams lack a systematic process for tracking API version lifecycles.

Build a simple calendar alert system. When Google releases a new major version, add two dates to your calendar: the deprecation date and the sunset date. Subscribe to the Google Ads Developer Blog for official announcements. Monitor your API usage in the Cloud Console monthly to catch any version drift.

For agencies managing multiple client accounts, standardize your migration process. Create a checklist that covers client library updates, code review for deprecated methods, sandbox testing, and production deployment. Having this process documented means you can execute it quickly when the next sunset approaches.

The next deadline on the horizon is v20 sunsetting in June 2026. If you migrate to v23 today, you buy yourself a full year before this becomes urgent again. Use that time wisely.

Impact on Your Campaigns

The API sunset does not directly change how your ads run. Campaigns continue serving through the Google Ads UI regardless of API status. What breaks is the automation and reporting layer that sits on top.

If you rely on automated bidding scripts, custom reporting dashboards, or programmatic campaign management, those stop functioning until migration is complete. Manual campaign management through the Google Ads interface remains fully operational. Your negative keyword lists, ad schedules, and bid strategies continue running as configured.

That said, losing automation access even temporarily can impact performance. Automated rules will not fire. Scheduled reports will not generate. Any integration that creates, modifies, or reports on campaigns through the API needs immediate attention.

The Bottom Line

Google Ads API v19 is gone. If you are reading this and your systems are down, migrate to v23 immediately. If you are still running and just want to stay ahead, audit your version usage today and plan your upgrade path before the v20 deadline in June.

The shift to monthly releases means Google is accelerating its API development. Staying current is no longer optional. It is the cost of doing business with programmatic Google Ads management.