Skip to content

Commit 0e2f46b

Browse files
authored
Merge pull request #3078 from segmentio/audience-timestamp-limits
Personas Event Timestamp Limit
2 parents 7757835 + ba77fe1 commit 0e2f46b

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

src/personas/product-limits.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -37,12 +37,13 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
3737

3838
## Audiences and Computed Traits
3939

40-
| name | limit | Details |
41-
| ----------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
42-
| 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. |
43-
| 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. |
44-
| Events Lookback History | **Essentials**: 1 year <br><br> **Advanced**: 3 years | The period of time for which Segment stores audience and computed traits computation events. This limit depends on your Personas service. Contact your account team to upgrade your Personas service. |
45-
| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. |
40+
| name | limit | Details | |
41+
| --------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --- |
42+
| 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. | |
43+
| 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. | |
44+
| Events Lookback History | **Essentials**: 1 year <br><br> **Advanced**: 3 years | The period of time for which Segment stores audience and computed traits computation events. This limit depends on your Personas service. Contact your account team to upgrade your Personas service. | |
45+
| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | |
46+
| 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. |
4647

4748
## SQL Traits
4849

@@ -58,7 +59,7 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
5859

5960
| Item | Limit description | Details |
6061
| ------------ | -------------------------------- | ---------------------------------------------------------------------------- |
61-
| Steps | 500 | The maximum number of steps per Journey. |
62+
| Steps | 500 | The maximum number of steps per Journey. |
6263
| Step Name | Maximum length of 170 characters | Once the limit is reached, you cannot add additional characters to the name. |
6364
| Key | Maximum length of 255 characters | Once the limit is reached, you cannot add additional characters to the key. |
6465
| Journey Name | Maximum length of 73 characters | Once the limit is reached, you cannot add additional characters to the name. |

0 commit comments

Comments
 (0)