There are some limits to the amount of data that you can send to Amplitude. This article will describe them.
Event volume limits
All organizations have a monthly event volume limit. For customers on Growth and Enterprise plans, the maximum number of events that can be sent to Amplitude each month is at least ten million; the exact number will be specified in the signed agreement between Amplitude and each customer. Customers who exceed these limits may be subject to overage fees; however, they will still have access to their accounts.
Customers on starter plans can send up to ten million events to Amplitude each month. Customers who exceed these limits will not be able to access their accounts. However, Amplitude will continue to collect data. Access to the account will be restored on the first day of the following month.
You can learn more about the plans we offer and their corresponding event volumes here.
NOTE: Identify and Group Identify calls do NOT count against total event volume.
Instrumentation limits
The allowed per-project maximums for event types, event properties, and user properties are:
- Event types: 2000
- Event properties: 2000
- User properties: 1000
Once these limit are reached, Amplitude will stop indexing new values. Data for any event types and event or user properties that exceed these limits cannot be queried from Amplitude, and can only be accessed in the raw data by exporting data via a CSV file or Amplitude's Export API.
As an example, imagine an instrumentation bug causes your product to send several additional event types to Amplitude, causing your project to exceed its instrumentation limit by five. Data for those excess event types will be visible within Amplitude once you have brought your project back down under the instrumentation limit. However, you will be unable to query any data received for those excess event types during the period when your account was over the instrumentation limit.
There is no limit to the number of event or user property values you can send. However, for a specific event or user property, only the first 1000 values sent to Amplitude will be selectable from dropdown menus. All values past that threshold will be stored in Redshift for direct querying, and you will have to manually search for a specific value in order to segment by it in Amplitude.
There is no limit to the number of event properties you can apply to an event. However, if you apply more than 50 event properties to an event, only the first 50 event properties sent to Amplitude are columnized in the event's table in Redshift. Read more about event properties in Redshift.
You can delete unneeded event types through your project's Govern page, and event and user properties through the Settings page. Once you are under the limit, it will take approximately 24 hours for the new event types, event properties, and user properties to appear in Amplitude.
Character limit for strings
String values are limited to 1024 characters (user ID, event or user property values, etc.). Arrays have a limit of 10000 characters when append or prepend is used (this is available for user property types only). Any string that exceeds this limit will be truncated.
Chart limits
Segmentation Module
Inline behavioral cohorts have a maximum range of three years. Currently, any date range exceeding three years in the Segmentation Module will display a 404 error on the chart.
A maximum of ten user segments can be added to a chart.
Date picker
Depending on the scale, each visualization has its own date range limit. Your charts will show a warning message when these time limits have been reached or exceeded:
- Real-time: maximum range of 1 day
- Hourly: maximum range of 7 days
- Daily: maximum range of 365 days
- Weekly: maximum range of 52 weeks
- Monthly: maximum range of 36 months
- Quarterly: maximum range of 12 quarters
Breakdown table: Segment selection
Up to 30 segments can be selected and shown on the chart at once.
Limit warnings
Amplitude will warn you when you are getting close to event type, event property, or user property instrumentation limits. View your current instrumentation usage by navigating to Settings > Projects and selecting a project.
Any limits you are approaching will be delineated with orange text. Any limits you have already exceeded will be delineated with red text.
NOTE: if you have exceeded your event type limits, they will still be displayed in orange. This is because event types beyond that limit are no longer indexed.
Additionally, an orange warning bar will appear at the top of the page when you are within 10% of the limit. This will be replaced by a red warning bar when you've exceeded your limits.
CSV download limits
The breakdown data table in the UI will only list the top 100 property values (for when you perform a group-by). You can export approximately 10,000 rows as a CSV file. This is specifically a limitation on the number of group-by values you can export.
The group-by limits vary from chart to chart:
| CHART | GROUP-BY LIMIT |
|---|---|
| Event Segmentation | 10,000 |
| User Composition | 10,000 |
| User Sessions | 10,000 |
| Funnel Analysis | 300 |
| Retention Analysis | 300 |
| Stickiness | 2,000 |
| Revenue Analysis | 10,000 |
| Revenue LTV | 300 |
For example, in the Event Segmentation chart, you can export a CSV of data for 10,000 distinct property values. If you perform a group-by on a property with more than 10,000 possible values, Amplitude would only export the top 10,000 values. To export the full data table, Enterprise customers can run a query through Redshift or Snowflake.
Group-by limits for Data Tables apply only to group-bys with a large number of different property values. See our article on Data Tables for more information.
FAQs
- How are events calculated towards the monthly event volume limit?
Any events sent and processed through Amplitude’s ingestion system are counted toward the monthly limit. Event volume is calculated on a calendar month basis. On the first of every month, event volume is reset to zero. Any computed events in Amplitude (e.g. computed revenue events) do not count as separate events.
- I exceeded my 2000 event type per project instrumentation limit. Are the events that are sent after the 2000th event type still counted towards the monthly event volume limit?
Yes. Events that exceed the event type limit of 2000 events per project still count towards the monthly event limit. Although these events are not queryable within Amplitude itself, they are still ingested and can be viewed with Export API.
- How can we reduce our monthly event volume limit?
Blocking or deleting events will reduce the monthly event volume. These events will not be ingested, so they will not count towards the monthly quota.
Events can be unblocked or undeleted at any time, but note that any data that was not collected during the time the event was blocked or deleted will not be retrievable, since they were not ingested.
- What is the difference between blocking an event and deleting an event?
This answer can be found in this FAQ article.
- Will I need to do anything after blocking or deleting an event?
When blocking or deleting an event type, you should update your instrumentation to stop sending those events to Amplitude. Not sending unwanted events in the first place is the best solution for removing event types from your taxonomy.
- Do events from blocked user IDs or device IDs on the backend affect my event volume?
No. If you request Amplitude to block and filter certain user IDs or device IDs from your project, those events will not count towards event volume limits.
- Do hidden and backfilled events count towards the monthly event volume limit?
Yes. Hidden events are hidden in the UI, but they are still ingested by Amplitude. Backfilled events count as well because they are being ingested by Amplitude.
- Do Inactive events count towards the monthly event volume limit?
Yes. Inactive events count towards the monthly limit. Only blocked or deleted events will not count towards your monthly limit.