Skip to main content

GA4's Data API quotas are breaking Looker Studio reports

Dara Fitzgerald1 December 20223 min read
GA4's Data API quotas are breaking Looker Studio reports

We wanted to share some information about a recent change Google Analytics has made to the GA4 Data API, that could be causing your GA4-based Looker Studio (formerly Data Studio) dashboards to error.

Since the 7th November, Looker Studio reports that connect to Google Analytics 4 data are subject to Google Analytics Data API (GA4) quotas.

Note: this is not just affecting Looker Studio. These quotas are for the GA4 Data API so any tools that pull data from GA4 via this API will be subject to these same quotas. For example, Power BI, Tableau, Google Sheets or Excel add-ons for GA4, etc.

If any of your Looker Studio reports are affected by these quotas, you will see one of the errors listed here https://support.google.com/looker-studio/answer/12182485#ga4-quota&zippy=%2Cin-this-article%2Csteps-to-resolve.

The actual quotas can be seen here https://developers.google.com/analytics/devguides/reporting/data/v1/quotas, but the one most likely to impact reports from what we have seen so far is the one I've highlighted below for the maximum number of concurrent requests being set at 10.

A table of the GA4 Data API quotas, with the 10 'Core Concurrent Requests Per Property' highlighted.

That is, only 10 requests can be made to the API at any one point in time. This can effectively make any dashboard with >10 charts per page useless at present (although the requests do not quite work in such a one-to-one way).

We at Measurelab are not alone in being very frustrated about this. There is a lot of dissatisfaction online within the analytics community, with many people experiencing issues with reports that were previously working, now erroring.

A small silver lining however, is that the Looker Studio team have replied to a public community post about this, saying they are looking into solutions to work around this quota limitation. But there is no ETA, and we don't really know what this solution will look like yet.

The official suggestions from the Google Looker Studio team to deal with this are listed here (but also below in bullets) https://support.google.com/looker-studio/answer/12182485#ga4-quota&zippy=%2Cin-this-article%2Csteps-to-resolve.

In our view, these are far from ideal. We are hoping that the backlash will lead Google to reconsider, but of course we have no way of knowing that or their motivations for making this change in the first place.

If you have reports that are affected by this change (i.e. suddenly breaking, with one of the errors shown on the page linked at the top of this post) then please let us know and we can discuss it together to determine the best course of action.


Suggested content

Measurelab awarded Google Cloud Marketing Analytics Specialisation

At the start of the year, if you’d asked us whether Measurelab would be standing shoulder to shoulder with Europe’s biggest consultancies by September, we would've been surprised. Not because we don't believe in ourselves, but because these things feel so distant - until suddenly, they’re not. So, here it is: we’ve been awarded the Marketing Analytics Services Partner Specialisation in Google Cloud Partner Advantage. What’s the big deal? In Google’s own words (with the obligatory Zs): “Spec

Will Hayes11 Sept 2025

BigQuery AI.GENERATE tutorial: turn SQL queries into AI-powered insights

BigQuery just got a major upgrade, you can now plug directly into Vertex AI using the new AI.GENERATE function. Translation: your analytics data and generative AI are now best friends, and they’re hanging out right inside SQL. That opens up a whole world of new analysis options for GA4 data, but it also raises some questions: * How do you actually set it up? * What’s it good for (and when should you avoid it)? * Why would you batch the query? Let’s walk through it step by step. Step 1: H

Katie Kaczmarek3 Sept 2025

How to start forecasting in BigQuery with zero training

If you’d told me five years ago that I’d be forecasting product demand using a model trained on 100 billion time points… without writing a single line of ML code… I probably would’ve asked how many coffees you’d had that day ☕️ But its a brand new world. And it’s possible. Let me explain What is TimesFM? TimesFM is a new foundation model from Google, built specifically for time-series forecasting. Think of it like GPT for time, instead of predicting the next word in a sentence, it predicts t

Katie Kaczmarek14 Jul 2025