Google shipped Google Ads API v25.2 on September 23, 2026, and the useful part isn't flashy: a new endpoint auto-generates a Performance Max draft from an existing Smart campaign, and a BenchmarksService shows your account's percentile standing against competitors. At WebEpex we mapped both against the ad-reporting flows we already run for clients the same week it landed. If you're still on Smart campaigns, migration risk just dropped.
What did Google Ads API v25.2 actually change?#
Google's own release notes list six changes in v25.2, released September 23. Two matter to a business owner: BenchmarksService.GenerateBenchmarksMetrics now returns percentile-tier data comparing your account against other advertisers and your category, and SmartCampaignSettingService.GeneratePMaxDraftCampaign builds a Performance Max draft straight from a live Smart campaign instead of someone rebuilding it by hand.
There's also asset-group-level URL controls, YouTube-handle search for creator insights, deeper travel-vertical reporting, and new recommendations flagging when a Target CPA or Target ROAS is set too tight to compete. Search Engine Land covered the rollout on September 25. v25.2 stays supported until August 2027; v26 is due in October 2026.
We nearly missed the benchmarks endpoint on our first read of the changelog — it's buried under the PMax headline, and we only caught it on a second pass.
Does this change anything if you're not running Smart campaigns?#
If you're already on Performance Max, or you don't touch Google Ads at all, not much changes for you today — skip to the trade-offs section below.
If you're a service business or SaaS founder still running a Smart campaign because nobody's gotten around to migrating it, this matters. Google's been pushing everyone toward Performance Max for two years, and the usual complaint is that a manual rebuild loses your history and audience signals. GeneratePMaxDraftCampaign skips that step: it drafts the PMax version from your live Smart campaign's settings, so whoever manages your account can compare the draft against the original before switching anything live.
The benchmarks endpoint is smaller but still useful. Instead of guessing whether a slow month is your account or the whole category having a slow month, percentile data against competitors gives you an actual answer. That ends a lot of pointless "why did performance drop" conversations.
What are the trade-offs?#
The upside is real: a drafted migration costs nothing to generate, and you can throw it away if it doesn't look right. The benchmarks data is genuinely useful for reporting too — it's context that's normally hard to get without buying a separate competitive-intelligence tool.
The catch: none of this is in the regular Google Ads dashboard yet. It's an API release first, so you need a developer or an agency with API access to pull it. Dashboard-only accounts wait on Google to surface it, and Google hasn't said when.
I'd also flag that a generated PMax draft is still a draft. It carries over settings, not judgment — asset quality, audience signals, and budget pacing still need a human look before anyone flips the switch. Treat the auto-draft as a faster starting point, not a finished migration.
How we're handling it#
Our own ad work for clients runs mostly through Meta — that's where our high-ticket service and D2C clients get the fastest lead response, especially with a WhatsApp handoff behind it, the kind of setup we broke down when we wrote up Meta ads management costs for service businesses. Google Ads isn't our primary channel, but a chunk of our SaaS and D2C clients across the GCC, Europe, USA, Canada and India run it in parallel, and several ask us to fold that data into the same n8n reporting flows we already build for Meta and WhatsApp.
We pulled the v25.2 changelog apart the day it landed and mapped both new endpoints against the reporting flows already live. The benchmarks call slots in cleanly — one more field in a dashboard that already pulls Meta spend and WhatsApp conversation volume into one view, so a client isn't logging into three tools to ask whether they're actually doing okay this month. It fits the pattern we've tracked before, from AI Max auto-upgrades to AI-generated ad dashboards: more automation, and it's on you to go find the transparency.
The PMax draft endpoint we're treating more carefully. We ran it against a test account before recommending it to anyone, since a drafted campaign is only as good as the settings it inherited. If a client's Smart campaign is still live because nobody's had time to touch it, that's now a lower-risk fix than it was two weeks ago.
What should I do this week if I'm running Google Ads?#
If you're on Performance Max already: nothing. The new controls are optional additions your agency can adopt if useful.
If you're still on a Smart campaign: ask whoever manages your account whether they've pulled a PMax draft yet, and get a second opinion before it goes live. A drafted campaign is a starting point, not a decision.
If you don't know which one you're running: that's worth five minutes to find out, since Smart campaigns and Performance Max report differently and it changes what your numbers mean. Doing nothing this week is a fine answer too, if none of your accounts are affected.
If you want a second pair of eyes on whether your account's ready for this, or you'd rather talk through the Meta side of things instead, send me what you're running and I'll tell you straight — two minutes, no pitch. [cal.com/webepex/growth-review]
