These rate limits were added to our product documentation on December 9, 2020.
Summary of Limits
|Inbound Data Throughput||1000 events per second|
|Inbound Historical Replay Throughput||1000 events per second|
|Outbound Downstream Destination Rate Limits||Reduced retries when failures exceed 1000 events per second|
|Profile API throughput||100 requests per second|
|Identity Merges||100 merges|
|Identity Mappings||1000 mappings|
Inbound Data Throughput
If within a ten minute period a Customer’s sources (in aggregate) send more than 600,000 events (average of 1,000 events per second) without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that does not exceed 600,000 events in any ten minute period. Any requests to raise that limit must be made in writing with Segment. Please reach out to email@example.com with details on your use case and estimated throughput.
Inbound Historical Replay Throughput
Similar to live data ingestion, any requests to replay historical customer data into Personas will be capped at a rate of 1000 events per second. Replays are initiated by the Segment support team. If you have a need for a higher replay throughput, please reach out to firstname.lastname@example.org with details on your use case.
Outbound Downstream Destination Rate Limits
Most destinations have their own rate limits that Segment cannot control. In some instances, Segment is able to ingest and attempt to deliver data faster than the downstream destination is able to accept data. Outbound requests to a destination may also fail for other reasons outside of Segment’s control. When requests to downstream destinations fail, Segment makes additional attempts to deliver the data (retries). However, when more than 1,000 requests per second to a downstream destination fail or when the failure rate for a downstream destination exceeds 50% for more than 72 hours, Segment reserves the right to reduce the number of retries until the condition is resolved.
Profile API throughput
If a Customer sends more than 100 requests a second per space to the Profile API, Segment will return a 429 rate-limiting error. Any requests to raise that limit must be made in writing with Segment. Please reach out to email@example.com with details on your use case and estimated throughput.
Personas supports up to 100 merges per profile in its identity graph. A merge occurs when two existing profile are joined together by a common external_id. For example, if a user starts their journey on mobile, and then signs in via a web application, those two user profiles are joined together by a common identifier like a user_id. Messages that attempt additional merges are usually a sign of a corrupt profile and are dropped.
Personas supports up to 1000 mappings per profile in its identity graph. Mappings are external id values like a user_id, email, mobile advertising id, or any custom id’s. Messages that attempt to add additional mappings are usually a sign of a corrupt profile and are dropped. Note that this limit counts mappings across all merged profiles.
This page was last modified: 05 Mar 2021
Questions? Problems? Need more info? Contact us, and we can help!