Back to feed
Dev.to
Dev.to
7/16/2026
Google Ads API v21 sunsets in August — three silent ways the forced version bump corrupts your reports (still 200 OK)

Google Ads API v21 sunsets in August — three silent ways the forced version bump corrupts your reports (still 200 OK)

Short summary

Google Ads API v21 sunsets around August 6, 2026, and migrating to v23+ stacks breaking changes from both v22 and v23. Three silent failure modes can corrupt your reports while still returning 200 OK: removed enum values like VIDEO_OUTSTREAM cause spend to collapse into catch-all buckets, deleted asset performance labels return empty values instead of errors, and WHERE/GROUP BY clauses on removed enums silently match nothing. Audit your GAQL queries and enum branching logic before the August deadline.

  • Google Ads API v21 sunsets ~Aug 6 2026; v23+ carries stacked breaking changes from v22 and v23
  • Silent corruption: removed enums (VIDEO_OUTSTREAM) cause spend to vanish into catch-all buckets with 200 OK responses
  • Audit GAQL queries for enum dependencies, asset performance label fields, and branch logic before migration

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more