Google Ads July 2026: API v25, Appeal Caps & Missed Opportunities

Google Ads shipped three unrelated but same-week changes on July 21–22, 2026: API v25 landed as a major release that deletes two lifecycle-goal resources with no deprecation window, policy appeals picked up a six-month expiry with zero advance notice, and the report formerly known as “Missed Growth Opportunities” moved out of Labs and into the main Recommendations tab as a beta.

Every trade outlet covered exactly one of these stories. That’s the problem: an account manager doesn’t experience Google Ads one headline at a time. If your team runs API integrations, has any disapproval history older than a few months, or leans on the Recommendations tab, all three changes touch your account in the same week — and one of them quietly closed a door the day it was announced.

This post bundles the week into a single dated ops sweep: what each change is, the primary source behind it, and the specific action to take before the end of the month. It follows this month’s earlier governance bundle (published July 15, before this news window opened) and picks up where our April API coverage left off.

Here is the full picture an account team needs, with each item pinned to its actual date. Three of the four landed inside the July 21–22 window; the fourth — video campaign groups going global — rolled out on July 13 and is included only for completeness, because it already has a dedicated post on this site.

The pattern worth noticing: none of these arrived as a headline product announcement. The appeals change came as a documentation update spotted by Search Engine Roundtable; the Missed Opportunities move was first flagged by a practitioner, PPC consultant Thomas Eccel, on LinkedIn; only the API release got a proper blog post — aimed at developers, not media buyers. If your change-monitoring process only watches Google’s announcement channels, you missed two of the three.

Google announced v25 of the Google Ads API on Wednesday, July 22, 2026. In the words of Anash P. Oommen of the Google Ads API Team: “Today, we’re announcing the v25 release of the Google Ads API. This major release brings support for new reporting features and goals. To use these new capabilities, you must upgrade your client libraries and client code.” The additive features cluster around YouTube reporting depth and a new retention-oriented goal type.

Worth flagging on the loyalty goal specifically: the v25 announcement describes schema and mechanism, not outcomes. There are no published adoption numbers and no lift benchmarks, so any agency deck promising a specific retention improvement from this goal type is ahead of the evidence. Treat it as a capability to test, not a result to forecast. Google also hosted a live release walkthrough on Discord and Ads Developers YouTube Live on July 23 — recorded and posted afterwards, useful for engineering teams scoping the upgrade.

The part that breaks code: v25 removes the legacy CustomerLifecycleGoal and CampaignLifecycleGoal resources and services outright. There is no deprecation window, no dual-write period, and no field-mapping guide — they are replaced by Goal and CampaignGoalConfig under what Google calls a revamped unified goals schema. Independent coverage at ppc.land framed it bluntly: the release “kills two lifecycle goal resources, forcing code rewrites.”

One precision note, because it’s easy to garble: this is a different breaking change from the one we covered in our April API v23 migration playbook. v23 (January 2026) removed CallAd and CallAdInfo; v25 (July 2026) removes the two lifecycle-goal resources. Different releases, different deleted resources — if your codebase survived the v23 migration, that says nothing about whether it touches lifecycle goals today.

The cadence table is the strategic story. The API moved to a monthly release rhythm starting January 2026 — four major versions a year plus additive monthly minors. The v24 line alone shipped three releases in nine weeks (April 22 to June 24). Major versions carry a 12-month support lifecycle, so v25 is expected to remain supported into July 2027 — but the practical takeaway for engineering leads is that API migration is no longer an annual project. It’s a standing quarterly line on the roadmap, and breaking changes now arrive without deprecation windows. Budget for it accordingly.

The second change is smaller in surface area and larger in urgency. Effective July 21, 2026, Google Ads no longer lets you appeal a policy decision directly from your account once that decision is more than six months old. After the window closes, the only route is contacting Google Ads support — and no exception process has been disclosed.

The actionable angle nobody else is emphasizing: this converts your disapproval backlog into a depreciating asset. Any disapproved ad you’ve been meaning to contest — the false-positive healthcare flag, the misfired trademark disapproval from last winter — has a clock on it now. Pull your policy issues in Policy Manager, sort by decision date, and appeal anything worth contesting before its six-month window lapses. For decisions already older than six months, the in-account door is closed; route through support and expect slower turnaround.

One related friction point surfaced in practitioner reaction. PPC consultant Greg (@PPCGreg) reported on X that Google also recently removed the option to select “All affected ads in the account” when filing an appeal: “We also used to be able to select ‘All affected ads in the account’, which they’ve recently removed. This flag continues to be an issue for us, forcing us to appeal the violation every time we update the ads.” That bulk-appeal removal is a single practitioner’s observation, not a documented Google change — but if it matches your experience, it compounds the case for batching your appeal work now rather than drip-feeding it.

The third change moves a report, not a policy. Around July 21–22, Google relocated the report formerly called “Missed Growth Opportunities” out of Labs and into the main Recommendations tab, renaming it “Missed Opportunities” and categorizing it as a beta. The report itself looks the same; what changed is who will see it. Labs was opt-in territory for the curious. Recommendations is where every account manager — and every auto-apply setting — lives.

The underlying report was announced at Google Marketing Live 2026 and first covered by Search Engine Roundtable in October 2025. It estimates the performance you could have achieved over the last year had you adjusted bids and budgets on constrained campaigns: missed clicks, missed conversions, and missed conversion value, each attributed to either “low bids” or “low budgets,” with a campaign-level table pairing each estimate with an algorithmic suggestion — raise your budget, lower your ROAS target — tied to auction data and seasonality. Google has also signaled upcoming bidding-consistency changes for budget-constrained Target CPA, Target ROAS, and Target CPC campaigns, which would make this report’s constraint diagnostics more consequential over time. How Google’s automated bid and budget guidance behaves under constraints is ground we’ve mapped before in our June bidding and budgeting playbook.

Here’s our read on why the relocation matters more than it looks: moving a report from Labs to Recommendations changes its epistemic status inside an organization. In Labs, it was an experiment you interpreted. In Recommendations, it arrives with the implicit authority of Google’s optimization guidance — the same surface that feeds optimization score and, in many accounts, auto-apply. A backward-looking model of foregone growth is now sitting one click away from being treated as an instruction.

Paid-ads consultant Sarah Stemen published the sharpest critique of the report back in June, identifying five structural limitations. Existing coverage either reports the feature move or critiques it in prose; nobody has turned the critique into a verification workflow. So here is ours — each limitation converted into a concrete check to run before accepting a Missed Opportunities suggestion.

Run the five checks and the report becomes genuinely useful — a structured prompt for finding real constraint problems, filtered through your own economics. Skip them and you’re letting a growth-biased, backward-looking model set your budgets. This is the same discipline we apply to Smart Bidding suggestions generally — Smart Bidding guidance we’ve covered before follows the identical accept-with-verification pattern. It’s also the core of how our paid media practice handles platform recommendations across client accounts: recommendations are inputs to judgment, never substitutes for it.

Pulling the sweep together into assignments. Two of these are engineering tasks, two belong to the media team — and all four are bounded, definable pieces of work rather than open-ended projects.

Two adjacent items round out the July picture without needing new work this week. Video campaign groups — YouTube reach and frequency optimization across multiple campaigns — went global on July 13, and we covered the feature in depth in our dedicated video campaign groups post. And if this kind of dated sweep is useful, the systematic version is our 100-item Google Ads audit checklist — the standing framework these weekly changes slot into.

Looking forward: the direction of travel across all three changes is consistent. Google is tightening the windows in which humans can contest its decisions, while widening the surfaces through which its recommendations reach them. Appeals expire faster; recommendations graduate into the default view; API contracts break without deprecation periods. None of that is sinister — but it shifts the burden of vigilance onto the advertiser, and it rewards teams that treat platform-change monitoring as a scheduled discipline rather than something absorbed from headlines.