You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.
Engage Default Limits
FREE x
TEAM x
BUSINESS ✓
ADDON ✓
To provide consistent performance and reliability at scale, Segment enforces default use and rate limits within Engage. Most customers do not exceed these limits.
To learn more about custom limits and upgrades, contact your dedicated Customer Success Manager or friends@segment.com.
(information)
Info
Beginning August 18, 2023, Segment has updated product limits that apply to new Engage and Unify users.
| Name | Limit | Details |
|---|---|---|
| Inbound Data Throughput | 1000 events per second | Total event stream from sources connected to Engage, including historical data replays. Segment may slow request processing once this limit is reached. |
| Outbound Downstream Destination Rate Limits | Reduced retries when failures exceed 1000 events per second | Outbound Destination requests may fail for reasons outside of Segment's control. For example, most Destinations enforce their own rate limits. As a result, Segment may deliver data faster than the Destination can accept. When Destination requests fail, Segment tries to deliver the data again. However, if more than 1000 requests per second fail or if the failure rate exceeds 50% for over 72 hours, Segment may reduce additional delivery attempts until the failure condition resolves. |
| Name | Limit | Details |
|---|---|---|
| Compute Concurrency | 5 new concurrent audiences or computed traits | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional computations until one of the five finishes computing. |
| Edit Concurrency | 5 concurrent audiences or computed traits | You can edit five concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the five finishes computing. |
| Batch Compute Concurrency Limit | 10 (default) per space | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish. |
| Compute Throughput | 10000 computations per second | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing. |
| Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. |
| Event History | 1970-01-01 | Segment may not ingest events with a timestamp earlier than 1970-01-01, which can impact audience backfills for older events. Segment stores data indefinitely, but ingestion depends on event timestamps. While Segment stores all events, event conditions typically evaluate data from the past three years by default. Your plan or configuration may allow a longer time window. |
| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. |
| Audience Frequency Update | 1 per 8 hours | Audiences that require time windows (batch audiences), funnels, dynamic properties, or account-level membership are processed on chronological schedules. The default schedule is once every eight hours; however, this can be delayed if the "Batch Compute Concurrency Limit" is reached. Unless otherwise agreed upon, the audiences will compute at the limit set forth. |
| Event Properties (Computed Traits) | 10,000 | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values. |
| Name | Limit | Details |
|---|---|---|
| SQL Traits | 25 | The number of SQL traits you can sync to your Space. |
| SQL Traits - Sync Frequency | customizable, up to hourly | The frequency with which Segment runs your SQL traits. Contact your account team to customize your schedule. |
| SQL Traits - Rows | 25 million | The number of rows each SQL trait can return. |
| SQL Traits - Columns | 25 | The number of columns each SQL trait can return. |
| Item | Limit description | Details |
|---|---|---|
| Steps | 100 | The maximum number of steps per Journey. |
| Step Name | Maximum length of 170 characters | Once the limit is reached, you cannot add additional characters to the name. |
| Key | Maximum length of 255 characters | Once the limit is reached, you cannot add additional characters to the key. |
| Journey Name | Maximum length of 73 characters | Once the limit is reached, you cannot add additional characters to the name. |
| Compute credits | Half a credit for each step (up to 250 compute credits) | Each step in a published Journey consumes half of one compute credit. |
For Journeys V2, see Product Limits.
| Item | Limit description | Details |
|---|---|---|
| Channels | Does not support Regional Segment | Workspaces with Channels functionality enabled must be deployed in the default region (Oregon, US). |