The current Google Ads API release is v24.2, published on June 24, 2026. The most recent major version is v24, which landed on April 22, 2026 and is supported until roughly May 2027. Google's 2026 roadmap puts the next major version, v25, in July 2026. This page tracks what each version changed, which ones still answer requests, and when the one you're on stops working.
It's written for people who query the API directly — in-house scripts, custom dashboards, feed automation. If you reach Google Ads data through a third-party platform, migration is your vendor's job and none of the field names below are your problem. The sunset dates still are, though: a vendor that misses one takes your reporting down with it, and the dates are public, so they're worth knowing well enough to ask.
Straight to Google's documentation
- Release notes — the full changelog, every version, every field. The authority on what changed.
- Deprecation and sunset dates — the official version lifecycle table. Check here before trusting any date, including the ones below.
- v24 reference — field-level docs for the current major version, with a query builder and validator.
- The v24 announcement — Google's own write-up of the release. The developer blog announces each version and runs a walkthrough event for the majors.
Closest deadline
v21 sunsets on August 5, 2026 — the nearest deadline in the table below. If anything you own still calls v21, jump straight to v24 rather than to v22; see migrating.
How Google Ads API versioning works now
Google changed its release model in January 2026, and understanding the new shape saves you from reacting to releases that can't affect you. The API now ships monthly, pausing only around the end-of-year holidays. That sounds like eleven migrations a year. It isn't.
Only four of those releases are major versions — up from three per year under the old quarterly model. In 2026 they fall in January (v23), April (v24), July (v25), and October (v26). Major versions are the ones allowed to contain breaking changes: removed fields, renamed enums, behaviour that no longer works the way your code assumes.
Everything in between is a minor version — v24.1, v24.2, and so on. Minors only add incremental, non-breaking features. You can adopt one by pointing your client library at it, or ignore it entirely and keep running the parent major. Minors also don't get their own sunset date: v23.1, v23.2, and v23.3 all retire on the same day v23 does, rather than on eleven separate schedules.
Key takeaway
Only the major version number can force you to change code, and there are four of those a year. Each major is supported for one year from its release date, so the practical question is never "am I on the newest release" — it's "how long until the major I'm on stops answering".
Where each version stands today
Sunset dates are what turn a version number into a deadline. Google publishes them on its deprecation and sunset page, which is the authority — the table below is the July 2026 snapshot, with dates beyond the next release still approximate until Google confirms the exact day.
| Version | Status | Sunset |
|---|---|---|
| v19 | Sunset | February 11, 2026 |
| v20 | Sunset | June 10, 2026 |
| v21 | Expiring | August 5, 2026 |
| v22 | Supported | October 2026 |
| v23 | Supported | February 2027 |
| v24 (v24.2 current) | Latest | May 2027 |
| v25 | Expected | July 2026 release — roughly July 2027 |
A sunset is abrupt. Requests to a retired version return errors from that day, with no throttling ramp and no grace period, and Google doesn't send a warning at the moment of cutover — the reminders come in the weeks before, on the Google Ads Developer Blog and by email to the developer token's contact. Everything on that version fails together: bidding scripts, conversion uploads, dashboards, feed jobs.
What v24 added
v24 shipped on April 22, 2026. Most of it is retail-shaped, which is unusual for a Google Ads API release and worth a closer look if you sell products.
CartDataSalesView: what sold, not what was clicked
This is the headline change for Shopping. Google Ads reporting has always credited the product that was clicked — someone clicks your blue running shoe, buys a red one plus two pairs of socks, and the whole order's revenue lands on the blue shoe. That's fine for measuring which product wins the auction and misleading for almost everything else.
The new CartDataSalesView resource reports on what the customer actually bought. You can segment conversion metrics by the sold item's attributes, such as product_sold_brand, and it exposes non-biddable metrics prefixed with all_ — all_cost_of_goods_sold_micros, for instance. The gap it closes is the cross-sell blind spot: the products that never win a click but ride along in the cart, and the hero SKUs whose ROAS is partly borrowed from things sitting next to them.
It requires cart data to be sent with your conversions, so it isn't a switch you flip in a reporting query alone.
Click-through vs view-through in Shopping reports
v24 adds a conversion_attribution_event_type segment to shopping_performance_view, which splits conversions by whether they followed a click or a view. If you've ever wondered why a product's conversion count doesn't square with its click count, this is the segment that answers it — and it pairs directly with the question of which attribution model is crediting what. The Shopping segments reference covers the rest of what you can slice that view by.
Retail filters for product targeting
Two new criterion types, RETAIL_FILTER and RETAIL_FILTER_BUNDLE, allow tag-based product filtering using logical expressions, with a matching SharedSetType of RETAIL_FILTER so filter sets can be shared across ad groups. It's a more expressive way to carve up a catalog than nesting listing groups. One catch: it's allowlisted, so it won't work on your account unless Google has enabled it.
Smaller additions
Campaign.view_through_conversion_optimization_enabledlets Demand Gen and App campaigns bid on view-through signals (off by default).- Gender exclusions for Performance Max, following the earlier age exclusions.
- Nine new conversion action types across GA4 and Firebase covering three lead stages — generate, qualify, and close — such as
GOOGLE_ANALYTICS_4_GENERATE_LEAD. VideoResponsiveAdInfois now mutable, withvideos,business_name, andlogo_imagesrequired.- A read-only
travel_feed_datafield onAssetSet.
What v24 breaks
Being a major version, v24 removes and renames things. If you're moving up from v23 or earlier, these are what will fail on you:
| Removed or changed | What to use instead |
|---|---|
Campaign.video_brand_safety_suitability |
Customer.video_brand_safety_suitability (moved to account scope) |
youtube_select_lineups |
youtube_select_lineup_targeting |
is_brand_connect_creator |
Check for CREATOR_PARTNERSHIPS in partnership_opportunities |
CampaignToForecast.geo_modifiers[] |
geo_target_constants[] |
ForecastAdGroup.biddable_keywords[] |
keywords[] |
ad_sub_network_type segment |
Removed from campaign_budget reporting |
click_type segment |
Removed from asset views; still available on ad_group_ad |
InsightsAudience.topic_audience_combinations |
Moved into the common namespace |
One behaviour change that won't show up in a field diff: ShareablePreviewService.GenerateShareablePreviews no longer handles partial failures. Previously a bad ID in a batch was reported and the rest went through; now any failure errors the whole request. If you batch preview generation, that's a silent assumption worth rechecking.
The v24 minor releases
Two minors have shipped on top of v24, both non-breaking.
v24.1 (May 13, 2026) added mobile device platform segmentation to campaign and customer reports, static image support for Demand Gen on the Display Network, passkey field detection, and an expanded Experiments framework covering AI Max, Video, Demand Gen, and Performance Max with per-arm metrics.
v24.2 (June 24, 2026) is the more consequential one. It adds SyntheticContentInfo and SyntheticContentAttestation to assets and ads, so AI-generated creative can be identified and labelled programmatically. That has a date attached to it: the EU AI Act's transparency obligations for AI-generated content apply from August 2, 2026, which turns this from a nice-to-have into compliance plumbing for anyone producing creative at scale in the EU. The attestation status and source fields are immutable in v24.2 and become writable in v25.
v24.2 also brings multi-party approvals, requiring a second administrator to sign off on sensitive account actions like user invitations — useful if you're an agency. Performance Max placement reporting gained ad_network_type segmentation across Search, Display, and partner networks, extending the campaign-level PMax channel breakdown that arrived in v23. SKU Analyzer's PMax Analyzer charts that campaign-level split without any of this.
You may not need v24 for these
Multi-party approvals and AI content labelling were backported to v23.3, v22.2, and v21.2 at the same time. If you're mid-migration and need either capability, check whether the version you're already on has it before rushing the upgrade.
v23, still supported until February 2027
v23 (January 28, 2026) opened the monthly-release era and, with support running to February 2027, is still a perfectly reasonable place to be. Its four notable additions:
- NLP audience building.
AudienceInsightsService.GenerateAudienceDefinitiontakes a plain-text description — "eco-conscious parents in urban areas looking for sustainable wooden toys" — and returns a structured audience definition, instead of you clicking through the targeting taxonomy by hand. - Performance Max network breakdowns. Ad network type segmentation for PMax, which answered the oldest complaint about the campaign type: you couldn't see whether Search, YouTube, Display, or Discover drove the result.
- Precision scheduling.
start_date_timeandend_date_timereplace the date-onlystart_date/end_date, so a flash sale can start at a minute rather than a day. - Campaign-level invoice data.
InvoiceServicemaps costs, regulatory fees, and adjustments to individual campaigns, which removes a manual reconciliation step for agencies.
Also in v23: store location data in PerStoreView, a LIFE_EVENT_USER_INTEREST dimension, and conversion rate suggestions for Demand Gen.
Migrating without doing it twice
The mechanics are dull; the sequencing is where people lose time.
Find out what you're actually on. The version is usually pinned in a client library config or baked into an endpoint path, and it's rarely in only one place — a reporting job, a conversion uploader and an ad-hoc script written two years ago can each hold a different number. Grep for it rather than trusting memory.
Go straight to the newest major. Stepping v21 to v22 buys you until October 2026 and a second migration; going v21 to v24 buys you until May 2027 and collects every feature above in one pass. The intermediate versions have no advantage — you'd be paying the same testing cost for a shorter runway.
Update the client library. Google maintains official libraries for Java, Python, PHP, .NET, Ruby, and Go. A library release generally supports several API versions at once, so upgrading the library and switching the version are two separate steps you can take on different days.
Compare numbers over a window, not a day. When you validate the new version's output against the old, conversion lag will make recent days look wrong in both. Give it a week before concluding that a metric moved.
Frequently asked questions
What is the latest version of the Google Ads API?
As of July 2026 the current release is v24.2, published on June 24, 2026. The most recent major version is v24, released April 22, 2026. Google's 2026 roadmap puts the next major version, v25, in July 2026.
Do I need to migrate for every monthly Google Ads API release?
No. Only major versions carry breaking changes, and Google ships four per year. The monthly releases in between are minor versions that add features without breaking existing code, and they sunset alongside their parent major version rather than on their own schedule.
What happens when a Google Ads API version sunsets?
Requests to that version stop working and return errors. There is no gradual throttling and no grace period, so anything built on it — bidding scripts, conversion uploads, dashboards, feed automation — fails at once. Google sends reminder emails ahead of the date but does not warn you at the moment of cutover.
When does Google Ads API v23 sunset?
Google Ads API v23 is scheduled to sunset in February 2027, one year after its January 2026 release. Its minor versions, v23.1 through v23.3, sunset on the same date rather than separately.
What is CartDataSalesView in Google Ads API v24?
CartDataSalesView is a reporting resource added in v24 that reports on the products actually sold rather than the product that was clicked. It lets you segment conversion metrics by attributes of the sold item, such as product_sold_brand, and exposes non-biddable metrics prefixed with all, such as all_cost_of_goods_sold_micros.
Which Google Ads API version should I migrate to?
Migrate straight to the newest major version rather than stepping through the versions in between. Each major gets one year of support from its release date, so jumping to the newest one buys the longest runway before the next forced migration and collects the new features in a single pass.
Keeping up without watching for releases
Four majors and seven minors a year is a lot of release notes for something that mostly doesn't concern you. Two things are worth actually monitoring: the sunset dates page, because that's the only part with a deadline, and the Google Ads Developer Blog, which announces each release and runs a walkthrough event for the majors. Industry coverage from Search Engine Land and PPC Land is usually faster to tell you whether a release matters to retail specifically.
This page is updated as each version ships, so it's a reasonable thing to bookmark instead. For the fields themselves, see the Google Ads API metrics reference and the Shopping segments guide; for the wider context, the Google Ads API for Shopping hub. And if maintaining an API integration is not the job you want, SKU Analyzer keeps the Shopping half of it current for you — version migrations included.