Google Ads API v24: What Changed and What Advertisers Need to Know
Google Ads API v24 landed April 22, 2026. Here’s what broke, what’s new, when v23 sunsets, and why ad tech vendors must migrate—Ads Anomaly Guard did on day one.
Google doesn’t ship API versions for fun. Each major bump moves fields, constraints, and report semantics forward—and quietly breaks the scripts, connectors, and SaaS tools that lag behind.
Google Ads API v24 (released April 22, 2026) is one of those “read the changelog twice” updates. If you’re responsible for Google Ads automation—in-house scripts, agencies, or a monitoring stack—this is your Google Ads API migration checklist, written for practitioners who care about uptime more than buzzwords.
Ads Anomaly Guard migrated to v24 on day one, because performance protection tools that can’t keep pace with API drift aren’t protecting anything.
What’s new in Google Ads API v24 (high-signal overview)
This post focuses on the changes that tend to surface as production incidents: required fields, removed resources, new conversion semantics, and reporting/view changes that affect Shopping and PMax workflows.
> Note: Always validate against Google’s official release notes and your account’s feature adoption. The point here is operational clarity—not an exhaustive diff.
1. Demand Gen video fields: now required in practice
Demand Gen campaigns lean heavily on creative completeness. In v24, several video-related fields are treated as required where older integrations could squeak by with partial creative payloads. If your tool creates or mutates Demand Gen campaigns, expect mutate errors until your requests include the full required creative graph.
Why it matters: “It worked yesterday” mutations start failing after upgrade—not because your logic is suddenly wrong, but because validation tightened.
2. `Campaign.video_brand_safety_suitability` removed
Brand safety controls moved. The `Campaign.video_brand_safety_suitability` field path was removed—teams must adopt the new model described in the v24 migration guide for video brand safety.
Why it matters: Any code that sets video brand safety at campaign scope must be refactored. Silent ignores are rare; this usually fails loudly—but only after you upgrade the client library.
3. Lead Gen conversion type expansions
Google continues to evolve Lead Gen measurement. v24 introduces / expands support for Lead Gen conversion typing patterns needed for newer lead workflows (exact naming varies by vertical and Ads surface). Integrations that hardcode older enums may need mapping updates.
Why it matters: Under-reporting or misclassification can make “Smart” bidding look brilliant or broken—while you’re actually measuring the wrong thing.
4. `CartDataSalesView` (Shopping) reporting shifts
Shopping advertisers and tools that reconcile cart-level performance should expect new or adjusted reporting views around `CartDataSalesView`—useful for understanding cart data sales performance with clearer aggregation semantics in v24.
Why it matters: Dashboards that assumed v23 row shapes can drift. This is classic API migration pain: the metric names look familiar, but joins and row grain differ.
5. PMax gender exclusions surface more explicitly
Performance Max gains clearer handling around gender exclusions in ways that affect how accounts express targeting constraints through the API. If you manage PMax settings programmatically, re-run parity checks against the UI.
Why it matters: PMax already hides a lot of “knobs.” API parity issues can create mystery spend or unexpected audience delivery when a migration half-succeeds.
Google Ads API v23 deprecation timeline (what “sunset” means for you)
When v23 is sunset, older client calls stop working—or worse, they behave inconsistently depending on endpoint and backoff behavior. For teams running automations:
- Freeze a migration window (staging account + QA checks).
- Bump client libraries and regenerate stubs if you use codegen.
- Run mutation dry-runs on non-production accounts first.
- Replay your most common reports and compare totals vs. UI for a 7-day window.
Why API freshness is a buying criterion for ad tech
A monitoring or automation product that “mostly works” after an API bump is how you get:
- missed alerts (failed polls),
- incomplete anomaly context (broken GAQL queries),
- failed auto-pause actions (permission + API version coupling).
If you’re evaluating vendors, use this punch list:
| Question | Why it matters | |---------|----------------| | Which API version is live in prod? | v24 is the 2026 baseline | | When did you migrate? | day-one vs. “eventually” | | How do you validate reports after upgrades? | totals mismatch = blind spots | | Do write actions have safe failure modes? | auto-pause must fail safe |
For a broader view of the tooling landscape, read Google Ads automation tools compared (2026).
What advertisers using Scripts should remember
Google Ads Scripts and API-based tools don’t share identical lifecycles, but they share the same reality: platform changes roll forward whether your Friday deploy plan agrees or not. If your org relies on scripts for catch-up tasks while a SaaS tool handles monitoring, make sure both paths are upgraded—otherwise you’ll chase contradictions between “what the script says” and “what the platform shows.”
What we recommend you do this week
1. Inventory every integration that calls Google Ads (SaaS, ETL, in-house). 2. Confirm v24 support from each vendor—or schedule your internal bump. 3. Re-validate Demand Gen creatives, Shopping cart reporting, Lead Gen conversions, and PMax settings that were “edge case” in v23. 4. Re-test budget and status mutations in a safe environment.
GAQL and reporting migrations: practical tips
Most teams feel Google Ads API migration pain first in GAQL (Google Ads Query Language) reports. Use this short checklist:
- Pin report grain: confirm whether rows are returned at campaign, ad group, or asset group scope—join assumptions change across versions.
- Compare totals, not anecdotes: for a rolling 7 days, compare API-summed metrics to UI totals with the same date boundary and attribution setting.
- Watch for “silent nulls”: some fields stop returning data rather than erroring; dashboards look “stable” while columns empty out.
- Version your queries: store GAQL strings in git with a `v24` tag so rollback is possible when debugging.
Vendor evaluation: questions a CMO should actually ask
If you buy “monitoring,” ask vendors to prove operational maturity—API version numbers are a reasonable proxy:
- Show me your v24 test plan: what reports break most often during upgrades?
- What fails closed? if polling fails, do you silently stop alerting?
- How do you validate auto-pause safety? dry runs, audit logs, revert paths?
- How quickly do you ship compatibility patches after Google emergency changes?
A one-page test matrix for reporting teams
If you own dashboards, run this matrix after upgrading:
| Report | v23 row grain | v24 row grain | Totals parity (7d) | Owner sign-off | |--------|---------------|---------------|--------------------|----------------| | Campaign daily | … | … | pass/fail | … | | Asset group daily (PMax) | … | … | pass/fail | … | | Shopping cart sales view | … | … | pass/fail | … |
Keep sign-offs in a shared doc. When an executive asks “why did these numbers move?” in March, you will want receipts.
Why “we’ll migrate later” is a revenue risk
Delayed migrations do not feel urgent until they are. The failure mode is subtle: your monitoring stack keeps some signals alive while losing precision on the ones that require updated fields—so you think you are protected.
That is incompatible with auto-pause and AI explanations, which depend on consistently rich telemetry. Ads Anomaly Guard migrates early precisely because partial observability is worse than a clean outage.
Conclusion
Google Ads API v24 is not a cosmetic release. It changes what you must send, what you can query, and what breaks if you’re still mentally living in v23—and v23’s sunset means procrastination has a due date.
Ads Anomaly Guard exists so advertisers don’t have to treat every Google changelog like an emergency. We ship compatibility updates as part of the product—so you can focus on performance, not API archaeology.
Questions about how monitoring, AI explanations, or GEO monitoring behave after migrations? Start with FAQ.
---
Try Ads Anomaly Guard free: connect Google Ads, route Slack alerts, and rely on a tool that treats API compliance as table stakes—not a someday project.