Google released version 24 of the Google Ads API on 23 April 2026. It is described as a major release, and by the standards of API versioning, that is not an overstatement. The update touches Demand Gen, travel feeds, conversion types, shopping, reporting, and video - a spread that covers almost every growth area in paid search right now.
API releases are not glamorous. They rarely make the trade headlines in the same way a product announcement does. But for anyone running AI-powered paid campaigns at scale, the API is where the real signal lives. What gets built into the API reflects where Google is directing its engineering effort - and that tells you a great deal about where advertiser controls are heading.
Why Demand Gen Keeps Getting Priority Treatment
This is the second consecutive major API version to include meaningful Demand Gen updates. That consistency is not accidental. Demand Gen sits in a specific position in Google's product thinking - it is the campaign type designed to reach users who are not yet searching, running across YouTube, Discover, and Gmail with creative-led targeting.
The ongoing API investment suggests Google is still actively building out Demand Gen's capabilities rather than treating it as a finished product. For advertisers, that means the gap between what you can do in the UI and what you can do programmatically via the API will keep widening - at least temporarily. Agencies and in-house teams with API access will have access to configurations that are not yet surfaced in the standard campaign builder.
If you are running Demand Gen at volume and relying entirely on the UI, you are probably missing options. The question worth asking your account team or agency is whether they are building and managing Demand Gen through the API or through the interface. The answer will tell you something real about their capabilities.
Conversion Type Changes Deserve Close Attention
Among the categories listed in the v24 update, conversion type changes are the ones with the most direct downstream effect on bidding performance. Smart Bidding strategies - whether Target CPA, Target ROAS, or Maximise Conversions - are only as good as the conversion signals you feed them. When Google updates how conversion types are defined or structured at the API level, that can affect how signals are categorised and how the algorithm interprets campaign performance.
This is particularly relevant for advertisers who have built out complex conversion architectures - using primary and secondary conversions differently, or separating micro-conversions from revenue-generating actions. Any structural change to conversion types in the API should prompt a review of whether your existing configuration still maps cleanly to the updated schema. Mismatches between your intended signal hierarchy and the API's current structure are a quiet source of bidding drift.
Shopping and Travel Feeds: A Sign of Where AI Automation Needs More Data
The inclusion of both shopping and travel feed updates in a single major release is worth reading carefully. Feed quality has always mattered, but as Performance Max and Demand Gen increasingly use feed data to generate and target ads automatically, the feed is no longer just a product catalogue - it is the creative brief.
Travel-specific feed improvements in particular suggest Google is investing in the data structures that allow AI campaign types to operate effectively in a sector with complex, dynamic inventory. Hotels, flights, and packages change constantly. The more granular and well-structured the feed, the better the AI can match the right creative to the right user at the right moment. UK travel brands that have not revisited their feed setup in the past 12 months should treat this update as a reason to do so.
For retail advertisers, shopping feed updates in the API generally precede broader changes to how product data surfaces in AI-driven formats - including Shopping results inside AI Overviews. Keeping feed data clean, complete, and up to date is no longer just good practice for traditional Shopping campaigns. It increasingly influences where and how your products appear across AI-generated surfaces.
Reporting Updates and the Ongoing Transparency Problem
Reporting changes in the API are always welcome, because the gap between what AI campaign types do and what advertisers can actually see has been a persistent frustration. Performance Max in particular has a history of limited reporting granularity, though Google has been adding more visibility incrementally - channel-level spend data being a recent example.
Any expansion of the reporting schema in v24 matters because it affects what third-party tools and custom dashboards can pull. If you are reporting on Demand Gen, shopping, or video performance through anything other than the native Google Ads interface, the v24 update may open up new fields that were previously unavailable. That is worth a technical check with whoever manages your reporting infrastructure.
What This Means for How You Manage AI-Powered Campaigns
The volume of changes in API v24 reinforces something that has been true for a while: managing AI-powered campaigns well is increasingly a technical discipline, not just a media-buying one. The practitioners who get the most out of Demand Gen, Performance Max, and Smart Bidding are the ones who understand the underlying data structures - conversion hierarchies, feed schemas, API fields - not just the campaign settings visible in the UI.
That does not mean every advertiser needs an in-house engineer. But it does mean that when you are evaluating how your campaigns are managed, it is reasonable to ask whether the people running them are tracking API releases and translating them into practical changes. A major release with dozens of updates is not a background event. It is an instruction manual for where the platform is going next.
For UK advertisers specifically, the combination of Demand Gen investment and conversion type updates suggests the next 12 months will reward those who have clean attribution, well-structured feeds, and campaign management that operates closer to the API than the interface. The gap between those two approaches is only growing.