Limits and quotas
This page covers the limits Amplitude applies to data ingestion, instrumentation, charts, and exports. The in-product warnings and email alerts cover most cases when you approach or exceed a limit. The questions below explain the underlying behavior.
Every organization has a monthly event volume limit. Your signed agreement with Amplitude specifies the limit, and you can see it in Settings.
Identify and Group Identify calls don't count against total event volume.
Customers who exceed their limit might incur overage fees. Amplitude alerts admins by email and in-product when an account reaches 80%, 90%, 100%, and 110% of the limit on paid plans.
If you're a non-paying customer and you exceed your monthly limit three times, Amplitude blocks your account. With a blocked account, you can't access charts and dashboards, but you can still use administrative functions such as the User API to meet compliance obligations. If you continue to exceed your limit without upgrading, Amplitude deletes your account six months after the initial block.
How are events calculated toward the monthly event volume limit?
Any events that Amplitude ingests and processes count toward the monthly limit. Amplitude calculates event volume on a calendar-month basis and resets the count to zero on the first of every month. Computed events (for example, computed revenue events) don't count as separate events.
If I exceeded the 2,000 event-types-per-project instrumentation limit, do events sent after the 2,000th event type still count toward my monthly event volume?
Yes. Events that exceed the per-project event type limit still count toward the monthly event volume. You can't query them in Amplitude, but Amplitude ingests them and exposes them through the Export API.
How can I reduce my monthly event volume?
Block or delete events. Amplitude doesn't ingest blocked or deleted events, so they don't count toward your monthly quota. You can unblock or undelete an event at any time. Data sent during the period the event was blocked isn't retrievable, because Amplitude never ingested it.
What's the difference between blocking an event and deleting an event?
Refer to the Hide, block, or delete an event or property FAQ.
Do I need to do anything else after blocking or deleting an event?
Update your instrumentation so it stops sending those events to Amplitude. The cleanest fix is to never send unwanted events in the first place.
Do events from blocked user IDs or device IDs count?
No. If you ask Amplitude to block and filter specific user IDs or device IDs from your project, those events don't count toward event volume limits.
Do hidden and backfilled events count?
Yes. Amplitude hides hidden events in the UI but still ingests them. Backfilled events count because Amplitude ingests them.
Do inactive events count?
Yes. The monthly limit excludes only blocked and deleted events.
How can I reduce event properties or user properties to avoid hitting per-project limits?
Delete unneeded event and user properties. Amplitude doesn't ingest deleted properties, so they don't count toward the monthly quota. Use the property table in Amplitude Data to delete them. After you're under the limit, the changes take about 24 hours to appear in Amplitude.
The allowed per-project maximums for event types, event properties, and user properties are:
- Event types: 2,000.
- Event properties: 2,000.
- User properties: 1,000.
After you reach these limits, Amplitude stops indexing new values. You can no longer query data for any event types or event/user properties that exceed these limits. You can only access them in the raw data through CSV export or the Export API.
For example, an instrumentation bug might cause your product to send extra event types so that your project exceeds the limit by five. The data for those excess event types appears in Amplitude only after you bring the project back under the limit. You can't query data that Amplitude ingested while you were over the limit.
There's no limit on the number of event or user property values you can send. For a specific event or user property, only the first 1,000 values appear in dropdown menus.
There's no limit on the number of event properties you can apply to an event.
You can delete unneeded event types in Amplitude Data. After you're below the limit, the new event types, event properties, and user properties take about 24 hours to appear.
Amplitude limits most property values to 1,024 characters. Exceptions:
- User property arrays can expand to 10,000 characters when using the append or prepend methods. The initial array still has a 1,024-character limit.
- Properties that use property splitting for cart analysis have a higher limit. Event properties have a 100,000-character limit; user properties have a 10,000-character limit.
Amplitude truncates values that exceed these limits.
The limits in this section apply to the Event Segmentation chart only.
Inline behavioral cohorts have a maximum range of three years. Date ranges over three years return a 404 error.
You can add up to 10 user segments to a chart.
Each visualization has its own date range limit:
- Real-time: maximum range of 1 day.
- Hourly: 7 days.
- Daily: 365 days.
- Weekly: 52 weeks.
- Monthly: 36 months.
- Quarterly: 12 quarters.
Charts show a warning when you reach or exceed these limits.
You can select up to 30 segments and show them all on one chart.
Amplitude warns you when you're approaching event-type, event-property, or user-property instrumentation limits. View current usage at Settings > Organization settings > Projects and select a project.
Orange text marks limits you're approaching; red text marks limits you've exceeded.
If you've exceeded your event type limit, Amplitude still displays them in orange. Amplitude no longer indexes event types beyond the limit.
An orange warning bar appears at the top of the page when you're within 10% of the limit. A red warning bar appears when you've exceeded a limit.
This is the CSV download limit for the breakdown table. The CSV download limit for Download users from the microscope is 1 million rows.
The breakdown data table in the UI lists the top 100 property values when you apply a group-by. You can export roughly 10,000 rows as a CSV. This limit applies to the number of group-by values you can export.
Group-by limits vary by 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 |
| Data Tables | 10,000, with Data Tables-specific exceptions after this table |
For example, in Event Segmentation, you can export a CSV with 10,000 distinct property values. If your group-by has more than 10,000 possible values, Amplitude exports only the top 10,000. You can export the full data table to a warehouse instead.
The Data Tables baseline group-by limit is 10,000, with these exceptions:
- 300 with a conversion metric.
- 100 with a session metric.
- 20 with attribution.
For combinations, the lowest limit applies. For example, a group-by with both a conversion metric and attribution has a limit of 10.
Was this helpful?