Looker Studio
Why does my Looker Studio Google Ads report keep breaking?
Updated 1 November 2026
Most breaks come from five things: the person whose credentials the data source uses lost access to the Google Ads account, a filter on campaign names stopped matching after a rename, a chart combines fields Google won't return together, a page asks for too much data at once, or a field the connector used has changed.
Fix the first two once and most reports stop breaking: connect data sources with an account that won't leave, and filter on campaign IDs or a stable naming pattern instead of exact names.
Symptom, cause, fix
| What you see | Likely cause | Fix |
|---|---|---|
| Every chart errors, saying it can't connect to the data set | The data source uses someone's credentials, and they lost access to the Google Ads account or left | Reconnect with an account that keeps access, and make it the data source owner |
| A chart shows "No data" or a campaign has vanished | A filter on campaign name no longer matches after a rename | Filter on campaign ID, or on a stable part of the name with "contains" |
| One chart errors, the rest work | It combines fields Google Ads can't return together, or uses a field that changed | Remove fields one at a time until it works; rebuild with the current field |
| Slow pages, timeouts, charts loading at random | Too many charts, too long a date range, or too fine a breakdown on one page | Fewer charts per page, shorter default range, or an extract |
| Figures don't match Google Ads | Averaged rates, time zone, conversion column, cached data | See why reports don't match, then refresh the data |
Credentials: whose access the report runs on
A Looker Studio data source fetches data with one of two kinds of credentials. With the owner's credentials, every viewer sees data fetched as the person who connected it. With viewer's credentials, each viewer needs their own access to the Google Ads account, which clients often don't have.
Most agency reports use the owner's credentials, so the report depends on one person. When that person loses access to the client's account (a freelancer moves on, an employee leaves, the client removes a user during a clean-up) every chart stops at once.
The fix: connect data sources from an account the agency controls and doesn't share with a single person, give that account access to every client account, and make it the owner of the data sources.
Renamed campaigns
A filter such as "Campaign equals Brand — Search" stops matching the moment someone renames the campaign to "Brand — Search — 2026". The chart doesn't error; it just shows less, or nothing, which is worse, because nobody notices until the client does.
- Filter on campaign ID where you mean one specific campaign. IDs never change.
- Use a naming pattern and filter with "contains" on the part that won't change, such as a "BRAND" prefix.
- Check totals. A scorecard of total account spend beside a filtered chart shows at once when the filter has started dropping spend.
Fields that can't be combined
The Google Ads connector passes requests through to Google, and Google only returns certain combinations together. Some metrics aren't available with some breakdowns, and some breakdowns can't be crossed with each other. A chart that asks for one of those combinations fails or comes back empty, sometimes only for some accounts or date ranges.
If one chart breaks while the others work, remove fields one at a time until it loads. That finds the combination; then split it into two charts. The same applies after Google changes the connector: a field that was renamed or retired leaves the charts using it broken until you swap in the current one.
Quotas, timeouts and slow pages
Every chart on a page is its own request. A page with twenty charts over twelve months of daily data, segmented by device and network, asks for a lot at once, and some of those requests time out. Keep pages to a handful of charts, default to a shorter date range, and move detail onto separate pages. For large accounts, the Extract Data connector takes a snapshot of the fields you choose and serves charts from that, which is much faster.
Looker Studio also caches data, so a report can show figures a few hours old. Use "Refresh data" from the report's menu before you send it.
When to stop patching
Looker Studio is free and flexible, and for a handful of clients the fixes above are enough. The cost shows up as client numbers grow: every report is built and maintained by hand, and each break is found by someone looking at it. If you're spending part of every month repairing reports instead of writing the commentary, compare the alternatives. Our Roster vs Looker Studio page sets out where each is the better choice.
Questions
- Why does my Looker Studio report say it can't connect to the data set?
- Usually because the data source uses the owner's credentials and that person has lost access to the Google Ads account. Reconnect the data source with an account that has access, ideally one the agency controls rather than one person's login.
- Do I have to rebuild my report after renaming a campaign?
- Only the charts that filter on the campaign's exact name. Change those filters to the campaign ID, or to a stable part of the name with "contains", and they will survive the next rename.
- Why is my Looker Studio report so slow?
- Each chart is a separate request to Google Ads. Many charts, long date ranges and fine breakdowns on one page add up. Use fewer charts per page, a shorter default date range, or the Extract Data connector for large accounts.