| ---------------------------------------------| -------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| 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| 2 concurrent audiences or computed traits| You can edit two concurrent audiences or computed traits at a time. Once the limit is reached, Segment queues and locks additional computations until one of the two 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,subsequent computations are delayed 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.|

| 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.|

| Events Lookback History| 3 years| The period of time for which Segment stores audience and computed traits computation events.|

| Real-time to batch destination sync frequency| 2-3 hours| The frequency with which Segment syncs real-time audiences to batch destinations.|

| Event History|`1970-01-01`| Events with a timestamp less than`1970-01-01` aren't always ingested, which could impact audience backfills with event timestamps prior to this date.|

| 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](/docs/engage/audiences/#funnel-audiences),[dynamic properties](/docs/engage/audiences/#dynamic-property-references), or[account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once every8 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.|

| Audience Frequency Update| 1 per 8 hours| Audiences that require time windows (batch audiences),[funnels](/docs/engage/audiences/#funnel-audiences),[dynamic properties](/docs/engage/audiences/#dynamic-property-references), or[account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once everyeight 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.|