Data limits

In this article:

Data collection limit

Every user interaction can be sent to Google Analytics as an individual hit, including (but not limited to) each pageview, screenview, event, or ecommerce transaction. As a result, a single session can result in many hits. To learn more about the methods that send hits from website tracking, refer to the analytics.js Method Reference in the developer documentation. References for mobile app tracking are available in the SDK packages for Android and iOS.

If you exceed 10 million hits per month per property, there is no assurance that the excess hits will be processed. There are additional limits for specific client libraries. Refer to the Collection Limits and Quotas in the developer documentation for more information.

If your account exceeds the collection limit, consider the following options:

  • Upgrade to Google Analytics Premium. Google Analytics Premium is a paid service that includes a Service Level Agreement (SLA), technical and implementation support, and support for higher hit volumes. Learn more about Google Analytics Premium.
  • Send fewer hits. You can do this several ways. You can, for example, set a sample rate for your data collection or remove any extra tracking calls, like Event tracking, you've added to your basic implementation. Refer to the developer documentation to learn how to set a sample rate or remove extra tracking calls from the library you're using.

Data processing latency

Processing latency is 24-48 hours. Standard accounts that send more than 200,000 sessions per day to Google Analytics will result in the reports being refreshed only once a day. This can delay updates to reports and metrics for up to two days. To restore intra-day processing, reduce the number of sessions you send to < 200,000 per day. For Premium accounts, this limit is extended to 2 billion hits per month.

Related resources

Was this article helpful?