Control your Google Analytics data collection against property limits and quotas with a Data Studio report
I’m happy to introduce a new tool I’ve just created to control Google Analytics limits and quotas for data collection and be sure to not reach them.
I’ve made it inside Google Data Studio with the related benefits and constraints: Google Analytics data is aggregated and GA limits we need to control are technically at property level
The documentation and advises are directly included in the reporting and I hope you will enjoy playing with this free tiny tool switching from a GA data raw view to another and see how far your data collection are to reach these limits. Let’s take care about your analytics device and the risk management we need to think about, reducing data loss as a mandatory step for data quality.
I’ve tried to make this report the more generic and applicable to any Google Universal Analytics view.
Enjoy and feel free to give me your feedback on Twitter or #measure Slack, giving me the opportunity to improve this tool.
For more information without accessing to the report, you will find below details about GA limits and quotas with applied solutions to control it through a Google Data Studio report.
This Google Data Studio report helps you to control your data collection on Google Analytics regarding the applied limits and quotas.
Select your Google Analytics view through the dropdown menu at the top right corner, preferring raw data views: Collection limits and quotas are applied to GA properties, so selected views must closely reflect what is collected on the property level. Even if they can provide good trends, filtered or altered views would underestimate metrics and related Google Analytics limits.
10 million hits per month per property
“If you go over this limit, the Google Analytics team might contact you and ask you upgrade to Analytics 360.” (Official technical documentation).
Contrary to technical documentation, Terms of Service indicate that the limit of 10 million hits per month is at the account level (no evidence of enforcement but be careful).
This Google Analytics limit gets the biggest probability to be reached. If your measurement plan is hits consuming and/or you generate a huge traffic on your website, dangerously close to this limit, you must control consumed hits by month regularly to consider to :
- Reduce your tracking hits removing useless interactions, focusing on essential data (ex: Scroll depth for all pages, videos reading every 5 secondes, slides visibilities for a slider never clicked…)
- Use it as an opportunity to comply your analytics tracking with regulations (GDPR, e-privacy…) 😬…why provisioning data collection if you will reduce your tracking mechanically because of an “incoming” mandatory regulatory compliance…do it now…
- Switch/add a paid analytics software or an open source self-hosted software, covering your data collection needs
- Upgrade to Google Analytics 360 if you’ve got enterprise needs in addition to this limit about data collection
- Think about GA App+web property as an alternative for non critical data and sandbox to track and experiment what you remove from your measurement plan for GA Universal (first point)
- Think about client tracking sampling (last and least…if you have no other choice…)
500 hits / session (for free and 360 Universal version – formally current version)
“This limit applies to gtag.js, analytics.js, Android SDK, iOS SDK, and the Measurement Protocol…If you go over either of these limits, additional hits will not be processed for that session…These limits apply to Analytics 360 as well”. (Source : Official technical documentation)
Following the data loss and for which purpose you use your GA collected data (power users studies,…), you can consider it as critical and launch related actions to reduce hits by session.
200,000 hits per user per day
“This limit applies to gtag.js, analytics.js, Android SDK, iOS SDK, and the Measurement Protocol…If you go over either of these limits, additional hits will not be processed for that…day…These limits apply to Analytics 360 as well”.
Because of some limitations related to data aggregation from Google Analytics, to control this limit, I chose to apply a segment isolating all users with more than 150k hits and display it by date.