You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
| Compute Concurrency| 5 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.|
28
+
| Compute Concurrency| 5newconcurrent 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.|
29
29
| 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.|
30
-
| 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.|
30
+
| 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.|
31
+
| 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.|
31
32
| Events Lookback History| 3 years| The period of time for which Segment stores audience and computed traits computation events.|
32
33
| Real-time to batch destination sync frequency| 2-3 hours| The frequency with which Segment syncs real-time audiences to batch destinations.|
33
34
| 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.|
34
35
| Engage Data Ingest| 1x the data ingested into Connections| The amount of data transferred into the Compute Engine.|
35
-
| Audience Frequency Update| 1 per 8 hours| Audiences that require time windows,[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. Unless otherwise agreed upon, the audiences will compute at the limit set forth.|
36
+
| 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 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.|
36
37
| 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.|
| Compute Concurrency| 5 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.|
38
+
| Compute Concurrency| 5newconcurrent 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.|
39
39
| 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.|
40
+
| 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.|
40
41
| 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.|
41
42
| Events Lookback History| 3 years| The period of time for which Segment stores audience and computed traits computation events.|
42
43
| Real-time to batch destination sync frequency| 2-3 hours| The frequency with which Segment syncs real-time audiences to batch destinations.|
43
44
| 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.|
44
45
| Engage Data Ingest| 1x the data ingested into Connections| The amount of data transferred into the Compute Engine.|
45
-
| Audience Frequency Update| 1 per 8 hours| Audiences that require time windows,[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. Unless otherwise agreed upon, the audiences will compute at the limit set forth.|
46
+
| 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 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.|
46
47
| 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.|