Google Ads API v19 stops working February 11, 2026. If you're running custom scripts, third-party connectors, or automated reporting tools that haven't been updated, your integrations will fail completely starting that date.

Google announced the v19 sunset on December 15, 2025. That gave developers about two months to migrate. Version 19 launched February 26, 2025, which means it got the standard 12-month lifespan before deprecation.

Why Google Ads API Versions Get Deprecated

Google maintains a maximum of four concurrent API versions. When v23 shipped on January 28, 2026, v19's clock ran out.

Starting January 2026, Google moved to monthly API releases, four major versions annually plus monthly minor updates with non-breaking changes. This accelerated schedule means you'll need to update at least twice per year instead of quarterly.

Current supported versions:
‍

• v23 (latest, January 2026)
• v22 (stable, October 2025)
• v21 (September 2025)
• v20 (August 2025)

Each version gets roughly 12 months of support after its successor launches. Plan migrations 2-3 months before sunset dates to avoid last-minute scrambles.

What Breaks When Google Ads API v19 Sunsets

All v19 requests return immediate failures. No warnings, no grace period.

Authentication errors even with valid OAuth tokens. Google rejects the v19 endpoint entirely, your credentials work fine, but the API version is gone.

"Customer not found" failures because v19 used numeric customer IDs (1234567890) while v20+ requires resource name format (customers/1234567890).

Silent failures in some reporting tools. Instead of error messages, you get zero rows. Looks like a successful query with no data, which makes debugging harder.

Dashboard breaks in Looker Studio, Google Sheets, Power BI, anywhere you pull Google Ads data programmatically.

Some integrations show partial data for 24-48 hours before total failure. Don't assume everything's fine just because it's still running on February 11.

Who Needs to Migrate from Google Ads API v19

You're affected if:
‍

• Custom scripts reference "v19" anywhere in the code
• Third-party tools show "Google Ads API v19" in settings
• Automated reports stopped refreshing after February 11
• You built API integrations in-house

You're safe if:
‍

• You only use the Google Ads web interface
• Your connector explicitly states they handle migrations automatically
• You use managed tools that auto-update (check with your provider)

Check Google Cloud Console → APIs & Services → Google Ads API → Metrics to see which versions your project calls.

How to Migrate to Google Ads API v22

Update API Version References

Change endpoint URLs in your code:
‍

// Old (breaks February 11)
https://googleads.googleapis.com/v19/customers/1234567890/googleAdsService

// New
https://googleads.googleapis.com/v22/customers/1234567890/googleAdsService

Update version constants:
‍

// Old
const API_VERSION = 'v19';

// New
const API_VERSION = 'v22';

Fix Customer ID Format

v20+ requires the full resource name:
‍

// Old format
customerId: '1234567890'

// New format  
customerId: 'customers/1234567890'

This single change fixes most "customer not found" errors after migration.

Review Breaking Changes

Google's official migration guide lists field name changes, deprecated metrics, and new requirements between versions. Budget 1-2 hours reading through changes that affect your specific implementation.

Some common changes between v19 and v22:
‍

• Renamed video ad metrics
• Removed deprecated feed entities
• Modified batch operation limits
• New EU political advertising self-declaration requirements

Test in Non-Production First

Deploy to a test account or low-spend client before touching production. Run queries for at least 24 hours to catch intermittent issues.

Watch for:
‍

• Query timeouts (v22 enforces stricter query optimization)
• Missing or renamed fields
• Different metric calculation methods

Session Tracking Deprecation (Separate Issue)

Don't confuse the v19 shutdown with the session tracking changes announced January 7, 2026.

February 2, 2026: Google Ads API stopped accepting new implementations of session attributes and IP addresses in conversion imports. New advertisers must use Data Manager API instead.

Important: Existing users are grandfathered. If you're already importing session attributes through Google Ads API, you can continue indefinitely. The restriction only affects new implementations.

This is separate from v19 sunset. Session tracking affects what features you can implement, v19 shutdown affects whether your code runs at all.

Choosing Which Google Ads API Version to Use

v23 gives you the longest support window (until ~March 2027) but has less community documentation and potential undiscovered bugs.

v22 is the current stable choice. Extensively tested, most third-party tools support it, widely documented. Good for production deployments.

v21 still works but you'll need to migrate again sooner.

Most teams pick v22 for immediate migration, then schedule v24 upgrade for Q3 2026. Leapfrogging versions is fine, you don't need to migrate through every intermediate release.

If Your Google Ads API Integration Is Already Broken

Scripts failing right now?
‍

1. Find v19 references in your code (search for "v19", "googleads.googleapis.com/v19")
2. Update to v22
3. Fix customer ID format (add "customers/" prefix)
4. Deploy to one test account
5. Monitor 24 hours before full rollout

The code changes take 15-30 minutes. Testing takes longer but prevents breaking all your accounts simultaneously.

For Google Sheets connections specifically, see our guide on connecting Google Ads to Google Sheets which covers both native methods and automated approaches.

Understanding the Google Ads API Evolution

Google has been pushing developers toward the newer Ads API architecture since 2018. The old AdWords API sunset completely in April 2022. If you're still wrapping your head around the differences, our Google Ads API vs AdWords API comparison breaks down the major architectural changes.

Next Google Ads API Sunset: 2027

Whatever version you migrate to today will eventually sunset. Track the official deprecation schedule and set quarterly calendar reminders.

Approximate future sunsets:
‍

• v22: ~February 2027
• v23: ~March 2027
• v24: ~April 2027

The monthly release schedule means more frequent but smaller migrations. Better than the old quarterly system where breaking changes piled up.

FAQ

Can I get an extension past February 11?
No. The shutdown is automatic and applies globally.

Does this affect the Google Ads web interface?
No. Only programmatic API access is affected.

Will historical data be deleted?
No. Your Google Ads account data stays intact. Only the v19 API endpoint stops working.

What if my reporting tool uses v19?
Contact their support. Most providers should have migrated already. If they haven't, consider switching to a provider that keeps up with Google's deprecation schedule.

Do I need to migrate through every version?
No. You can jump directly from v19 to v22 or v23.