Are your Looker Studio dashboards suddenly breaking down?
Our suggestions for overcoming Google’s newly imposed quota on the Looker Studio GA4 connector
- Article
- Technical Web Analytics
- Data Analytics


Did the following scenario happen to you last week? While enjoying your morning coffee you take a look at your pride and joy: a meticulously created Looker Studio dashboard built with the GA4 connector. You rub the sleep from your eyes and see your charts are all broken. Frantic phone calls from colleagues are pouring in. What is happening? Find out in this post what the consequences of Google’s newly imposed quota on the Looker Studio GA4 connector are.
What has happened?
On November 10 the release notes for Looker Studio (formerly Google Data Studio) were updated. In the notes it was announced that there would be quotas enforced for Looker Studio reports. Within days of this announcement being made, we noticed multiple clients losing practically all functionality in Looker Studio reports using the GA4 connector.
Google has simultaneously introduced two quota: 1) how many times you can simultaneously query the service (the GA4 connector) and 2) how much data you can request per hour and day.
What does this mean in practice? Let’s pretend you have a Looker Studio report with 6 charts on a page and it is being used by two colleagues at the same time. The number of requests will be 12 (=6*2) which exceeds 10; as a result the charts will not be loaded and you will be shown an error message that reads ‘Exhausted concurrent requests quota’.
Apart from the request quota mentioned above, there is also a token quota set on both an hourly and daily basis. This quota limits the number of actions users perform within the dashboard (e.g. applying filters, sorting tables, changing date range etc.). Once your tokens are used up your charts will return an error.
The following table shows the exact limit for all types of quotas:

Unfortunately there is no simple way to keep track of how many tokens are consumed by each of your requests. Google claims that most requests will consume 10 or less tokens; however, having a long date range, multiple columns and many rows can significantly increase the token cost per request.
Update november 23: Google has announced work is underway on a feature that will display quota token consumption by report components as well as the amount of remaining tokens before the target is reached.
Who is impacted?
Firstly we would like to stress that the quota is currently only enforced on data being pulled into Looker Studio from GA4 properties. If your Looker Studio reports are still connected to Universal Analytics you will not be impacted by the quota. This unfortunately does not mean that you can lay back and watch GA4 dashboard owners tear their hair out. After all, Universal Analytics is an end-of-life product and data collection for free users will be cut off on July 1, 2023 (GA360 users can benefit from the extended grace period and have one extra year). You do however have some time to think about alternatives for the Looker Studio GA4 connector.
Secondly we should ask ourselves the question of whether GA360 users can still confidently rely on the Looker Studio GA4 connector. After all, paying a minimum of $50,000 a year for the license gets you 10 times as many tokens than free users have. The answer unfortunately is ambiguous. Small and medium sized users of the tool are probably going to be ok while larger sized users will experience the same issues as free users.
Take the scenario described below. Do you find your company’s situation to be similar to the picture painted below? If so, being a GA360 client will not be your saving grace and you will run into quota issues.
If your business has:
- 5 hourly Looker Studio users
- each of whom view about 3 pages
- with an average of 10 charts on each page
- and use a filter approximately 5 times while browsing the dashboard
- Assuming the average cost is 20 tokens per data request
you are already looking at 15K tokens an hour which is well over the 360 limit.
To summarise: almost everyone using GA4 will be impacted by the newly imposed quota. Only if your business falls in a very specific category (e.g. small / medium sized company with GA360 license) you might not be impacted.
It is important that you take time to think about sustainable alternatives that in the future will not only preserve your current level of reporting but might even allow you to improve your dashboards.
What alternatives are available?
We’ve split the alternatives in short, medium and long term solutions.
Short term solutions (next 4-8 weeks)
Bring Universal Analytics back to life
This fix only applies in the scenario that you are currently still running your Universal Analytics tagging. When this is not the case we suggest that you look at other solutions. Falling back on Universal Analytics may sound counterintuitive especially after all the pushing Google has done to move all of us to GA4 implementations. However if your reports have broken down and you’re losing out on valuable insights it might be worthwhile to temporarily resort back to using UA data (providing the data quality is similar to your GA4 implementation). Your team will be glad to be seeing their dashboards working again and you will be given time to think about longer term solutions.
Use GA4 Explorations
One of the major perks of GA4 is its Exploration module. Although the functionality of this tool is far below what Looker Studio has to offer, it could make for a decent fall-back option in times of need. The major constraints here are that the date range cannot be larger than 90 days, there might be cardinality issues and shared reports cannot be modified by anyone but their owner.
Sheets add-on for Google Analytics / Supermetrics
The Google sheets add-on is free to use and allows you to pull your Analytics data through the Google Analytics API. You could schedule a query to run on a daily basis which for most cases should clear you from data sampling / quota restraints. The sheet that contains the Google Analytics output can then be used as a data source for Looker Studio. In this scenario the Looker Studio GA4 connector will not be involved, thus you will no longer run into the quota issue.
In the long term there will be sustainability issues with this solution as spreadsheets can become unwieldy when they contain large amounts of data.
Medium term solutions (next 8 – 52 weeks)
Get Google Bigquery up and running
Bigquery is Google’s data warehouse solution which is (among other things) designed to store your GA4 property’s raw data. The sky becomes the limit when GA360 is combined with Bigquery. If you are using the free version of Google Analytics 4, the number of events that you can send daily to Bigquery is capped at one million. Both as a free or enterprise user of Google Analytics 4 you can enjoy an unlimited amount of data storage and run as many queries as you like. Setting up the Bigquery integration for Google Analytics 4 is very easy and can be done directly from the GA4 admin panel.
So why is not everyone already using Google Bigquery for their Google Analytics 4 properties? For one, the service comes at a cost. Google will charge users for storing their data as well as running queries on the service. Another hurdle is that to get something out of Bigquery you need to be able to write SQL commands. It is likely that companies lack the in-house capacity to carry out this task. We have the capacity and the expertise to assist your company with this.
The cost component should not be seen as a deterrent for using Bigquery. When thoughtfully setting up your data source tables, you will be able to run large dashboards that load much faster than anything you could expect from the Looker Studio Google Analytics 4 connector for a reasonable cost. On the other hand, you could find yourself running up a massive bill if you make mistakes in your set-up.
A final thought on Google Bigquery is that once set up it frees you of the obligation of using Looker Studio. A Bigquery source table can just as easily be connected to a Microsoft Power BI dashboard (or any other BI tool for that matter).
Not sure how to start with Google Bigquery? We would love to think along with you and choose the best possible set-up.
Long term solutions (>1 year)
As the impact of the recent changes is starting to sink in, it becomes apparent that the group of Google Analytics 4 users that see their needs met with the free version is shrinking fast. In the long term this will leave you with two major options:
Purchase a GA360 license
If you are determined to stay in the Google stack, upgrading to GA360 for the sake of acquiring more Looker Studio tokens makes little sense. More likely, you’ll want to upgrade due to the Google imposed event cap on Bigquery streaming (one million events / day). On a large traffic volume website with many measurements implemented, this cap might quickly prove problematic. In such a case you are left with little alternatives then to upgrade to GA360.
Nowadays pricing for GA360 is no longer based on a fixed rate but instead is dependent on the volume of your event collection. According to Google, you will be looking at a price of $50,000 per year for collecting about 25 million events per month.
In return for the license fee you will get more tokens to use in Looker Studio as well as access to unsampled GA4 explorations.
Consider alternatives to Google Analytics
Google Analytics has been the market leader in the Web Analytics industry for many years. However, there are competitors out there who might also deliver great value for your business. One of Google’s main advantages over its competitors was that they offered a great product for free that had many awesome plug-and-play applications. With GA4 it is becoming apparent that free users are getting fewer perks and more hassles on their path.
We are tool agnostic which allows us to look together with you for the tool that can deliver the greatest value to your business.
Receive data insights, use cases and behind-the-scenes peeks once a month?
Sign up for our email list and stay 'up to data':