Google Ads · Status at source date: Deadline reminder
Deadline reminder: Google Ads API v22 sunsets on 7 October
Google has reminded developers that all Google Ads API v22 requests will begin failing on 7 October 2026.
This update uses a PMC cover because no suitable source image was available when checked on 8 Sept 2026. Available source and video links are retained.
What changed
Google’s 2 September reminder says Google Ads API v22 will retire on 7 October 2026 and requests to that version will then fail. Ben Karl signs the notice on behalf of the Google Ads API Team. The article points developers to upgrade guidance and release notes, and explains that versioned method names can be found in the Google Cloud Console’s API metrics.
The notice concerns requests made through the retiring API version. It does not say that Google Ads itself closes or that every campaign stops serving on that date. An affected integration might lose a report, fail to update an account or stop completing a scheduled job, depending on what it does. That distinction makes the dependency inventory more useful than a general warning to all campaign owners.
Why it matters for advertisers
PMC analysis: an agency can depend on an old API without maintaining the code itself. Reporting platforms, internal exports and specialist automation providers may each have their own release schedule. Ask for evidence that the actual workflow has moved to a supported version, rather than accepting a generic statement that a vendor supports Google Ads.
For an internal workflow, a successful connection test is only the first check. Compare a representative report with the existing output and verify that required fields, filters and account coverage still work. For jobs that change campaigns, test the intended operation in an appropriate controlled context. A migration can connect successfully while changing the data a dashboard expects. Assigning one owner to confirm the output and one to confirm the implementation helps catch that gap before the retirement date.
What to check next
- Inventory each reporting or automation dependency that calls Google Ads, including vendor-managed connections, and identify its responsible owner.
- Ask the technical owner to inspect recent versioned requests and replace remaining v22 usage using Google’s migration guidance before 7 October 2026.
- Record a successful run and reconcile representative outputs after migration. Keep a fallback for business-critical reporting while any provider remains unconfirmed.
Sources & contributor credit
- Newsletter coverage · Paid Media Collective newsletter
Original newsletter text, contributor labels and media for this update.
- Source referenced in newsletterGoogle Ads Developer Blog
Linked from the original newsletter. The source publication date has not been independently confirmed.
Source attribution checked
Ben Karl is the named notice author, writing on behalf of Google Ads API Team. Profile unknown; no personal profile guessed.
Attribution evidence and limitations
Cached extraction contained the heading and navigation but omitted article content. Recovered exact official URL online and read full substantive post including Ben Karl’s signature and migration instructions.
Retained newsletter and official source URLs. Reviewed notice links to sunset information, supported versions, upgrade guide, release notes and Google Cloud Console. No profile URL inferred for Ben Karl.
Record has no attached source/newsletter visuals; live article includes an author portrait but it was not visually inspected and is not reproduced.
Attribution checked . This is a review date, not the original publication date.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.
Original newsletter text and archive evidence
Deadline reminder: Google Ads API v22 sunsets on 7 October
Google has reminded developers that all Google Ads API v22 requests will begin failing on 7 October 2026. Its 2 September notice points teams to migration guidance and explains how to identify versioned requests in the Google Cloud Console, indicating this is a scheduled retirement rather than a new API launch. For you, this means confirming that reporting, bidding and automation providers have tested a supported version before the deadline.
Source captured . No explicit first-contributor label was provided for this update.
