Google Analytics is used on a large number of sites across the Internet. The traffic on these sites vary widely, from light-traffic blogs to globally well known websites. If your site sends more than 10 million hits per month to Google Analytics, the following limits may affect your data.
Data collection limit: If you exceed 10 million hits per month, there is no assurance that the excess hits will be processed. If your account exceeds this limit, please consider the following options:
- Upgrade your account to Google Analytics Premium. Google Analytics Premium is a paid service that includes SLAs, technical and implementation support and support for higher hit volumes. You can learn more about Google Analytics Premium at http://www.google.co.uk/analytics/premium/.
- Send fewer hits. You can do this, for example, by using the _setSampleRate method or by removing excessive tracking code calls like _trackEvent.
Every user interaction with your site or app can be sent as an individual hit to Google Analytics, including (but not limited to) each Pageview, Screenview, Event or E-commerce transaction. As a result, a single visit can result in many hits. To learn more about the methods that send hits, refer to the ga.js Tracker Object Methods and the analytics.js Method Reference for the web. References for Android and iOS apps are also available in the SDK packages.
Data processing latency: 24-48 hours. Standard accounts that send more than 200,000 visits per day to Google Analytics will result in the reports being refreshed only once a day. Daily processing begins at 12:00 UTC and continues for approximately 10 hours. This can delay updates to reports and metrics for up to two days. To restore intra-day processing, reduce the number of visits you send to < 200,000 per day. For Premium accounts, this limit is extended to 2 billion hits per month.