Google Ads API Version Sunsets: Why Client Dashboards Break and How to Stay Ahead

It usually starts with a message from a client: "Our ads dashboard is empty. Did the campaigns stop?" The campaigns are fine. What stopped is the connection between Google Ads and the tool that draws the charts. Looker Studio connectors, custom scripts and third-party dashboards all read campaign data through the Google Ads API, and when the version a tool calls reaches its sunset date, Google stops answering it.

These breaks are predictable. Google publishes the dates months ahead and sends reminders before each one. Yet agencies are often the last to hear, because the version number lives inside a vendor's code, not in anything the account manager sees. This guide explains the release cycle, what actually fails, and a short checklist that keeps a sunset from turning into an awkward client call about their white-label Google Ads reports.

Why did a client's Google Ads dashboard suddenly go blank?

A Google Ads dashboard usually goes blank because the tool behind it is still calling an API version that Google has switched off. Google's wording is blunt: from the sunset date, all requests to that version "will begin to fail". The tool gets an error instead of numbers, and depending on how it was built, the client sees an error banner, a chart with no bars, or a total frozen at the last good refresh.

Other causes look the same on screen, so rule them out quickly. An expired login, a removed user on the ad account, or a disconnected manager account can all empty a dashboard. The tell for a version sunset is timing: every client who uses the same connector breaks on the same day, and that day matches a date on Google's schedule.

That pattern is why the problem lands on agencies so hard. A single outdated connector can empty ten or twenty client dashboards at once, usually right before a monthly review. Agencies that rely on scheduled PDF client reports have a second risk: a report that runs on schedule while the data source is failing can go out with empty sections unless someone checks it first.

How does the Google Ads API release and sunset cycle work?

Google now releases a new version of the Google Ads API every month, except over the end of year holidays. Google announced the change in September 2025: major releases went from three a year to four, the remaining releases became minor versions, and each major release is now available for one year after it ships.

The difference between the two kinds of release matters for reporting. According to Google's versioning guide, minor versions only add backward-compatible changes, so a tool on version 25 picks up 25.1 and 25.2 without breaking. Major versions can include breaking changes and use a separate endpoint, which means the vendor has to change code and ship an update. When a major version is released, older ones are marked deprecated; they still work until their sunset date, and then they stop.

The dates come from Google's deprecation and sunset schedule and its sunset reminder posts. Google labels future dates as tentative, so treat the 2027 rows as a planning guide, not a promise. The practical takeaway is simple: with four majors a year and a one-year life for each, a sunset now comes around every few months, and any tool that upgrades only once a year will eventually miss one.

What breaks when a tool falls behind on the Google Ads API?

Two things break when a reporting tool falls behind: requests stop working on the sunset date, and data can change shape when the tool finally upgrades. The first is loud and obvious. The second is quiet, and it is the one that produces wrong numbers rather than missing ones.

The loud failure is the one described above. Every call to the old version is rejected, so the connector cannot refresh. Some tools show an error, some show nothing, and some keep displaying a cached figure that looks current but stopped updating days ago. A frozen number is the most dangerous of the three, because nobody notices until a client compares it with their own Google Ads account.

The quiet failure comes from breaking changes in major versions. For example, Google's v23 release replaced the campaign start and end date fields with new date and time fields. A tool that upgrades but still asks for a field that was renamed or removed may get back an empty column instead of an error, and a chart built on it simply goes flat. Metrics and segments also get added in new versions, so a tool stuck on an old one cannot show newer breakdowns at all. When you check a report after an upgrade, compare totals for spend, clicks and conversions against the Google Ads interface, and confirm efficiency figures such as return on ad spend still calculate.

An agency checklist for every sunset date

The way to stay ahead of a sunset is to know which version each tool calls, watch Google's schedule, and test reports on the day a version is retired. None of this needs a developer. It needs a calendar and five questions.

1. Ask every vendor which version they call. Ask which API version their Google Ads connector uses today, when they plan to move to the next major one, and how they will tell you. A vendor that cannot answer is a risk to every client on that connector.
2. Watch the developer blog. Google posts a sunset reminder about five to six weeks before each date. The v22 sunset reminder went out on September 2 for an October 7 cutoff.
3. Check your own scripts and apps. If your agency built anything that calls Google directly, open APIs and Services in the Google Cloud Console, select the Google Ads entry and read the Methods table on the Metrics tab. Each method name includes the version it calls.
4. Test reports after each sunset. The day after a sunset, open a sample of client dashboards and the next scheduled report. Compare a few totals with the Google Ads interface before anything reaches a client.
5. Keep exports. Save a monthly export or PDF of every client report. If a connector breaks, the history the client has already seen still exists outside the tool.

This checklist also makes vendor choice easier. A tool that keeps its connectors current saves you from running the whole list by hand, and a list of supported marketing data sources tells you how many connections your agency depends on. Fewer, better-maintained connectors mean fewer sunset dates to worry about.

What to tell clients when a Google Ads chart goes blank

Tell the client three things: the campaigns are running, their data is safe in Google Ads, and you know when the report will be back. Most clients panic because a blank chart looks like a stopped campaign or lost money, so lead with the reassurance and follow it with facts.

Attach the numbers. Pull spend, clicks, conversions and cost per conversion straight from the Google Ads interface so the client sees real figures, not just an apology. If the outage crosses a reporting deadline, send the usual report with a short note at the top that names the gap, rather than letting a section with empty charts arrive without explanation.

Then fix the cause, not just the symptom. If one connector has broken twice in a year, move those clients to a tool that tracks Google's schedule for you. AgencyReportr's Google Ads integration is maintained by AgencyReportr, and the report covers campaigns, ad groups, search terms, conversions, devices, impression share and wasted spend inside branded client reporting dashboards under your own logo and domain. Because plans are priced by client count, you can compare per-client reporting plans against what a broken connector costs in account manager time.

Google Ads API FAQ

What happens when a Google Ads API version sunsets?

Every request sent to that version fails from the sunset date. Any dashboard, connector or script still calling it stops receiving Google Ads data until its owner moves it to a newer version. The data itself is safe inside Google Ads.

When does Google Ads API v22 sunset?

Google's developer blog says v22 sunsets on October 7, 2026. Earlier in the year, v20 sunset on June 10, 2026 and v21 on August 5, 2026.

How often does Google release new API versions now?

Monthly, apart from the end of year holiday period. Four releases a year are major versions that can contain breaking changes, and the rest are minor versions that only add non-breaking features. Each major version is available for about one year.

How do I know which version my reporting tool uses?

For a vendor tool, ask the vendor directly and ask when they plan their next upgrade. For your own scripts or apps, open APIs and Services in the Google Cloud Console, select Google Ads API and check the Methods table on the Metrics tab, where each method name includes the version.

Will a client lose historical Google Ads data when a dashboard breaks?

No. The campaign data stays in the Google Ads account, and the dashboard can pull it again once its connection is fixed. What the client can lose is the report itself, which is why agencies should keep monthly exports or PDF copies.