Skip to content

Commit 4c538c5

Browse files
pwsegpwseg
authoredMar 6, 2025
Merge pull request #7477 from segmentio/6521-content-confusing-engage-limits-points
Fix inaccurate event storage limit and clarify event history behavior
2 parents c786073 + f7cfe5d commit 4c538c5

File tree

2 files changed

+22
-24
lines changed

2 files changed

+22
-24
lines changed
 

‎src/engage/product-limits.md

+11-12
Original file line numberDiff line numberDiff line change
@@ -23,18 +23,17 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
2323

2424
## Audiences and Computed Traits
2525

26-
| name | limit | Details |
27-
| --------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
28-
| 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. |
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-
| 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. |
32-
| Events Lookback History | 3 years | The period of time for which Segment stores audience and computed traits computation events. |
33-
| Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. |
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. |
35-
| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. |
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. |
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. |
26+
| name | limit | Details |
27+
| --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
28+
| 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. |
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+
| 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. |
32+
| Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. |
33+
| 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. <br><br> 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. |
34+
| 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 (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+
| 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. |
3837

3938

4039
## SQL Traits

0 commit comments

Comments
 (0)
Please sign in to comment.