There are some limits to the amount of data that you can send to Amplitude. These limits exist to ensure that data governance is top of mind. Messy data can lead to conflicting insights!
Table of Contents
- Event Volume Limits
- Instrumentation Limits
- Chart Visualization Limits
- Limit Warnings
- CSV Download Limits
- FAQs
Event Volume Limits
All organizations have a monthly event volume limit which counts the total number of events that are being sent to Amplitude.
- Important Note: Identify and Group Identify Calls do NOT count into the total event volume
Growth and Enterprise Plans
The event volume limit for Growth and Enterprise customers is at least 10 Million and is outlined in the customer's contract. Growth and Enterprise customers that go over their limit will still have access to their account but may be subject to overage fees depending on their contract.
Starter Plan
Customers on the Starter Plan have 10 Million events per month. Starter customers who go over the monthly event volume limit will not be able to access their account; however, all data will still be collected. The account will be re-opened once the limit has refreshed on the first day of the next month.
You can learn more about the plans we offer and their corresponding event volumes here.
Instrumentation Limits
| Type | Limit |
|---|---|
| Event Type | 2000 |
| Event Properties | 2000 |
| User Properties | 1000 |
Note: If your project is over any of the instrumentation limits and you remove event types/event properties/user properties to drop below the limit, then historical data cannot be queryed from the platform. For example, let's say you are tracking 1995 event types in Amplitude. You want to add 5 more event types to your event taxonomy. On June 1st, an instrumentation bug occurs causes you to send 10 more event types to Amplitude, with the first 5 of them being unneeded ones. Your project now has 2005 event types which is over the limit. On June 5th, you fix the instrumentation bug and delete the unneeded 5 event types to bring your project down to the limit of 2000 event types. Because your project was over the limit from June 1st to June 5th, historical data that was sent at that time for the 5 event types that were over the 2000 event type limit will not be queryable. Data for those 5 event types will only show up in the UI going forward once you have brought your project back down under the instrumentation limit.
Event Types
We only show the first 2000 event types per project. Once the limit is reached, we will stop indexing the new values. New values sent while you were over the limit can only be accessed in the raw data by exporting data via a CSV file or our Export API.
To get back under the limit, you are able to delete event types through your project's Govern page. Once you are back under the limit, it will take approximately 24 hours for the new event types to appear in the UI.
Event Properties
We only show the first 2000 event properties per project. Once the limit is reached, we will stop indexing the new values. New values sent while you were over the limit can only be accessed in the raw data by exporting data via a CSV file or our Export API.
There is no limit to the number of property values you can send. However, for a specific event or user property, the Amplitude platform will only let you select from the dropdown menus the first 1,000 values sent to Amplitude (the dropdown menu will not autocomplete the strings for values that exceed that threshold). All values past that threshold will still 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 our platforms.
To get back under the limit, please delete the unessential event properties in your project's Settings page. Once you are back under the limit, it will take approximately 24 hours for the new event properties to appear in the UI.
Number of Event Properties Per Event
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. Find more information about event properties in Redshift here.
User Properties
We only show the first 1000 user properties per project. Once the limit is reached, we will stop indexing the new values. New values sent while you were over the limit can only be accessed in the raw data by exporting data via a CSV file or our Export API.
There is no limit to the number of property values you can send. However, for a specific event or user property, the Amplitude platform will only let you select from the dropdown menus the first 1,000 values sent to Amplitude (the dropdown menu will not autocomplete the strings for values that exceed that threshold). All values past that threshold will still 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 our platforms.
To get back under the limit, please delete the unessential user properties in your project's Settings page. Once you are back under the limit, it will take approximately 24 hours for the new event properties to appear in the UI.
Number of Property Values
There is no limit to the number of property values you can send. However, for a specific event or user property, the Amplitude platform will only let you select the first 1,000 values sent to Amplitude from the dropdown menus (the dropdown menu will not autocomplete the strings for values that exceed that threshold). All values past that threshold will still 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 our platforms.
String Character Limit
There is a character limit of 1024 characters for all string values (User ID, event or user property values, etc.). Arrays have a limit of 10000 characters when append/prepend is used (available for user property types only). Any string that exceeds this limit will be truncated. So if you try to append or set more than 1024 characters at once it will get truncated, but if you append/prepend them individually (1024 max each time) you can go up to 10k.
Chart Visualization Limits
Segmentation (Right) Module: Date Picker
Inline behavioural cohorts have a maximum range of 3 years. Currently, a date range that exceed 3 years in the right module will show 404 error on the chart.
Chart: Date Picker
Depending on the granularity, each visualization has its own date range limit. The chart will show a warning message when these limits have been reached:
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 11 quarters
Breakdown Table: Segment Selection
Up to 30 segments can be selected and show on the chart at once.
Limit Warnings
We will warn you when you are getting close to event type, event property, or user property instrumentation limits. In Settings > Projects, select a project to see your current instrumentation usage.
If you are nearing any limits, the text will reflect this with orange letters. If you have exceeded the event property or user property instrumentation limit, the text will reflect this with red letters.
Note: if you have exceeded your Event Type limits, they will max out at 2000 and still be displayed in orange. This is because event types past 2000 are no longer indexed.
An orange warning bar will appear at the top of the page when you are within 10% of the limit.
When you have exceeded the limit, a red warning bar will appear in the product. New event types, event properties, or user properties will not be indexed and they will not be accessible in the Amplitude platform. However, the new events and properties will still collected in the raw data. To get back under the limit for event types, event properties and user properties, please delete them in your project's Govern page. Note that the warning will not go away until you refresh the page after deleting event types to go back under the limit.
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 limitation is specifically a limitation on the number of "Group By" values you can export.
The "Group By" limits vary by tab, as follows:
| TAB | 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 that has more than 10,000 possible values, then we would only export the top 10,000 values. To export the full data table, Enterprise customers will need to perform a query through Redshift or Snowflake.
FAQs
How are events calculated towards the monthly event volume limit?
Any events sent and processed through Amplitude’s ingestion system are counted towards the monthly limit. Event volume is calculated on a calendar month basis. On the first of every month, event volume is reset to 0. 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 are still counted towards the monthly event limit. Although these events are not queryable in the Amplitude UI, 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?
The differences between each event status can be found in this FAQ article.
Will I need to do anything after blocking or deleting an event?
It is a best practice that when blocking or deleting an event type, you should update your instrumentation to stop sending those events to Amplitude. Not sending the unwanted events at all 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?
If you request for 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.