Skip to content

Commit cc7f079

Browse files
author
markzegarelli
authored
Add new product limits for Engage (#3965)
1 parent 161b9af commit cc7f079

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

src/engage/product-limits.md

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,17 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
2121

2222
## Audiences and Computed Traits
2323

24-
| name | limit | Details |
25-
| --------------------------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
26-
| Compute Concurrency | 5 concurrent audiences | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional audience computations until one of the five audiences finishes computing. |
27-
| 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. |
28-
| Events Lookback History | 3 years | The period of time for which Segment stores audience and computed traits computation events. |
29-
| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. |
30-
| 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. |
31-
| 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. |
24+
| name | limit | Details |
25+
| --------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
26+
| Compute Concurrency | 5 concurrent audiences | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional audience computations until one of the five audiences finishes computing. |
27+
| 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. |
28+
| Events Lookback History | 3 years | The period of time for which Segment stores audience and computed traits computation events. |
29+
| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. |
30+
| 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. |
31+
| Engage Data Ingest | 1x the data ingested into Connections | The amount of data transferred into the Compute Engine. |
32+
| 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. |
33+
| 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. |
34+
3235

3336
## SQL Traits
3437

0 commit comments

Comments
 (0)