Google Ads API v20 Sunsetted June 10: Migration Guide and Priority Order
Google Ads API v20 officially sunsetted on June 10, 2026. Calls to v20 endpoints return errors immediately. This is the migration priority order: what breaks first, what to fix first, and which version to target.
Google Ads API v20 Sunsetted June 10: Migration Guide and Priority Order
Google Ads API v20 reached its end of life on June 10, 2026. According to the official Google Ads Developer Blog sunset reminder, all API v20 calls began returning errors at midnight on that date with no grace period. Any agency or in-house team still calling v20 endpoints for bid management, offline conversion uploads, or automated reporting is now receiving error responses on every request.
Key takeaways
- Google Ads API v20 sunsetted on June 10, 2026. Calls to v20 endpoints return
VERSION_SUNSETerrors immediately -- no grace period, no warning emails. - Bidding automation and offline conversion uploads account for 80% of revenue damage from a missed migration -- they cause silent performance degradation before errors surface in reporting.
- The recommended migration target is v23 or v24, not v21. Google switched to a monthly release cadence in January 2026; v21 sunsets in August 2026 and v22 in October 2026.
- Performance Max campaigns gain access to full network-level breakdown data and product-level cost and conversion metrics only in v21 and later.
- Migration priority order: offline conversion uploads first, then bidding automation, then reporting pipelines, then read-only integrations.
What breaks when v20 calls fail
Google Ads API sunset: The date on which Google stops accepting calls to a specific API version. After sunset, any request to that version endpoint returns a VERSION_SUNSET error code rather than data.
The failure mode differs by integration type:
Bidding automation. Custom bid scripts, rules-based automation, and third-party bid management tools that call v20 to set or adjust bids stop writing bid values to campaigns. Smart Bidding campaigns running inside Google's infrastructure are not directly affected, but any automation layer built on top of the API -- portfolio rules, dayparting scripts, budget pacing tools -- stops functioning. The team often does not know until manual review reveals stale bids.
Offline conversion uploads. CRM data uploads that feed closed deals, qualified leads, or revenue values back to Google Ads for Smart Bidding optimization fail silently. Conversion volume in the UI looks normal, but the quality of what Smart Bidding is learning from degrades. This is the highest-damage failure mode because the erosion is invisible until ROAS or pipeline quality deteriorates over days or weeks.
Reporting pipelines. Data pipelines pulling campaign, ad group, keyword, or product performance data via the API return errors. Dashboards and scheduled reports go blank or stale.
Third-party tool connections. Any tool connecting to Google Ads via the API that has not updated its connector library will fail. Attribution platforms, data connectors, and agency reporting suites all have separate API version dependencies. Vendor updates do not happen automatically and may lag the sunset by weeks.
Why migrating to v21 alone is not enough
The ICP problem this creates for agencies managing multiple client accounts: Google switched to a monthly API release cadence in January 2026, as reported by Search Engine Land. Each version now sunsets roughly 6 months after release. v21 sunsets in August 2026, v22 in October 2026.
Migrating from v20 to v21 today means repeating the same migration process within approximately 8 weeks. For agencies with multiple integrations across client accounts, that is a second migration cycle before the first one is fully validated.
The operationally correct target is v23 or v24, which provides a 4-6 month runway before the next required upgrade. Later versions also unlock capabilities not available in v20: product-level metrics for Performance Max and Demand Gen campaigns via the Google Ads API (live since June 15, 2026), cart data conversion reporting, and Performance Max gender exclusions.
Prooflytics monitors Google Ads connection health and flags data pipeline sync gaps in the daily briefing when API failures interrupt data ingestion.
Stop stitching platform exports together
Every channel in one brief — plus the memory of what each one actually drove.
14 days free · no credit card
Migration priority order
Step 1: Offline conversion uploads (fix first)
Restore CRM data import to v21+ before anything else. Every day without offline conversions is a day Smart Bidding trains on lower-quality signals. Check your import files and API calls for UploadClickConversions or UploadCallConversions endpoints and update them to the v21 format. Send a test upload immediately and confirm a success response.
The connection between CRM-quality conversions and bid strategy testing accuracy makes this the highest-priority fix -- a broken conversion upload corrupts any experiment running in parallel.
Step 2: Bidding automation
Restore any script or tool writing bid values, budget adjustments, or portfolio rules via the API. After updating to v21+, trigger a manual run on a low-spend campaign and verify the script completes without error. Check the change history in the Google Ads UI to confirm the expected bid adjustments appear.
Step 3: Reporting pipelines
Restore dashboard data feeds and scheduled report exports. These cause operational pain but do not affect campaign performance directly. Fix within 48 hours to avoid decisions based on stale data.
Step 4: Read-only integrations
Attribution platforms, analytics connectors, and third-party audit tools that only read data can be scheduled last. Their failure does not affect bidding or conversion signal quality.
Validation checklist after migration
Check for remaining v20 references. Search your codebase for googleads.googleapis.com/v20 and /v20/ strings. Any remaining reference is a live risk.
Trigger a test conversion upload. Send a single test offline conversion via the updated endpoint and confirm a success response. The conversion should appear in the Google Ads UI within 24 hours.
Run a test bid automation cycle. Trigger a manual run on a low-spend campaign and verify the expected bid adjustments appear in change history.
Pull a test report. Query a standard campaign performance report via the updated endpoint. Confirm the data matches what the Google Ads UI shows for the same period.
Set the next migration reminder. Schedule the v21 to v23 migration before August 2026. Done proactively, it is a 2-4 hour task. Done reactively after the next sunset, it is a crisis.
What the data shows about API migration timing
The ICP problem this creates specifically for performance teams: the shift to monthly Google Ads API releases in January 2026 means that "set and forget" API integrations now break on a 6-month cycle rather than an 18-24 month cycle. Industry data from Google's developer communications suggests teams that treated the v20 migration as a strategic project -- auditing all integrations, migrating to v23+, setting automated version checks -- experienced zero downtime. Teams that waited for the v20 error cascade to appear in dashboards experienced an average of 3-7 days of degraded conversion tracking before restoring full signal quality.
Prooflytics tracks Google Ads sync health in the daily briefing and flags conversion data gaps as anomalies, making API-related signal loss visible in the context of overall campaign performance rather than requiring a manual audit of error logs.
Bottom line
- Google Ads API v20 sunsetted June 10, 2026. Calls return errors immediately with no grace period.
- Offline conversion uploads are the highest priority fix -- degraded Smart Bidding signal compounds daily.
- Migrate to v23 or v24, not v21, to avoid a repeat migration before August 2026.
- Validate the migration by testing each component separately: conversions, bidding scripts, reporting pipelines, and third-party tools.
- You can review independent assessments of marketing analytics platforms with Google Ads connectivity on G2.
Frequently asked questions
Can I still access Google Ads data for dates before June 10 via the v20 API?+
No. The API version refers to the interface version, not the data date range. After sunset, all calls to v20 endpoints fail regardless of the date range requested. Data from before June 10 is still available in the Google Ads system -- you just need to access it through v21 or later API endpoints.
Does the v20 sunset affect Smart Bidding performance directly?+
Smart Bidding itself runs inside Google's infrastructure and is not affected by API version changes. However, if your offline conversion upload pipeline breaks at the v20 sunset, Smart Bidding loses the downstream CRM signal it uses to optimize toward revenue. The bidding algorithm continues to run, but optimizes toward lower-quality conversion signals -- form fills instead of closed deals, for example. The performance degradation is indirect but real.
How do I find out which API version my third-party tools are using?+
Check the vendor's release notes or API compatibility documentation. Most vendors publish their current Google Ads API version under a "Changelog" or "Integrations" section. If you cannot find this information, contact the vendor directly and ask specifically which Google Ads API version their connector currently calls. Some vendors auto-update their connectors; others require a manual upgrade trigger or a contract renewal to receive the update.
Is there a free tool to audit which of my API integrations are on v20?+
Google does not provide a central API version audit tool. The most reliable approach is a codebase search for version strings (/v20/, googleads-googleads-python-v20, etc.) combined with checking the response logs of each integration for VERSION_SUNSET error codes. For hosted tools, the vendor audit is the only path.
How does Prooflytics handle the Google Ads API version dependency?+
Prooflytics maintains its own Google Ads API connection layer and updates it ahead of each sunset. When your Google Ads account is connected, the platform pulls campaign, ad group, and performance data via the current supported API version. If a sync fails due to an upstream API issue, the failure is flagged in the daily briefing as a data gap rather than silently producing stale metrics.
Stop stitching platform exports together
Every channel in one brief — plus the memory of what each one actually drove.
14 days free · no credit card
Continue reading
Google Ads API Now Reports Product-Level Metrics for PMax, Video, and Demand Gen
Google Ads API adds product-level cost and conversion data for Performance Max, Video, Demand Gen, and App campaigns on June 15, 2026. Agencies and in-house teams can now build automated product-ROI alerts without manual UI extraction.
Google Ads Data Retention Cut to 37 Months: What to Archive Before It Disappears
Starting June 1, 2026, Google Ads deletes granular reporting data older than 37 months on a rolling basis. Monthly and annual data stays for 11 years. Here is what you lose, what survives, and the exact steps to archive before the cutoff.
Google Ads Bid Strategy Testing in 2026 Requires CRM Data, Not Just Campaign Metrics
Google Ads has shifted bid strategy validation toward conversion value by time and first-party CRM data. Testing on campaign metrics alone now produces false positives. Here is the operational setup teams need before running any bid experiment in 2026.
Google Ads Bid Strategy Testing Now Requires CRM Data: What Changed in 2026
Google Ads changed bid strategy validation requirements in 2026, shifting from surface-level metrics like ROAS and CPC toward conversion value by time window and first-party CRM data integration. Testing a new bid strategy without CRM data now risks false positives and budget waste -- the model validates against aggregated campaign metrics that can be disconnected from actual customer lifetime value.