From 0594234d351a17c5e8eea6a93889f30d963d5a5e Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 6 Mar 2025 11:13:02 -0600 Subject: [PATCH 1/4] fix table --- src/unify/product-limits.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/src/unify/product-limits.md b/src/unify/product-limits.md index 6c5b9f583f..62a5b4997e 100644 --- a/src/unify/product-limits.md +++ b/src/unify/product-limits.md @@ -39,18 +39,18 @@ Visit Segment's [pricing page](https://segment.com/pricing/){:target="_blank"} t ## Audiences and Computed Traits -| name | limit | Details | -| --------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 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, 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 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. | -| 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. | +| name | limit | Details | +| --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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, 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 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. | +| 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. | ## SQL Traits From 95adfd7c50a5141f5314bd0f376dcdfc53df73e5 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 6 Mar 2025 11:17:48 -0600 Subject: [PATCH 2/4] Update event history row for Unify product limits --- src/unify/product-limits.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/unify/product-limits.md b/src/unify/product-limits.md index 62a5b4997e..1e2c6eda95 100644 --- a/src/unify/product-limits.md +++ b/src/unify/product-limits.md @@ -45,9 +45,8 @@ Visit Segment's [pricing page](https://segment.com/pricing/){:target="_blank"} t | 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, 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. | +| 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. | | 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 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. | | 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. | From cecad04fab6dab650d1c06c23cc05dda99b4ec8c Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 6 Mar 2025 11:18:58 -0600 Subject: [PATCH 3/4] Update Engage Product Limits event history row --- src/engage/product-limits.md | 23 +++++++++++------------ 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/src/engage/product-limits.md b/src/engage/product-limits.md index ee999c65b6..3fb2c52262 100644 --- a/src/engage/product-limits.md +++ b/src/engage/product-limits.md @@ -23,18 +23,17 @@ To learn more about custom limits and upgrades, contact your dedicated Customer ## Audiences and Computed Traits -| name | limit | Details | -| --------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 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, 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 | 12-15 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 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. | -| 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. | +| name | limit | Details | +| --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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, 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. | +| Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | +| 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. | +| 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 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. | +| 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. | ## SQL Traits From f7cfe5d679ef9cdb586400a9b3e36d00e7bba3a8 Mon Sep 17 00:00:00 2001 From: pwseg Date: Thu, 6 Mar 2025 12:29:33 -0600 Subject: [PATCH 4/4] add clarification on three-year limit [netlify-build] --- src/engage/product-limits.md | 2 +- src/unify/product-limits.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/engage/product-limits.md b/src/engage/product-limits.md index 3fb2c52262..c7d74d06ce 100644 --- a/src/engage/product-limits.md +++ b/src/engage/product-limits.md @@ -30,7 +30,7 @@ To learn more about custom limits and upgrades, contact your dedicated Customer | 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. | | Real-time to batch destination sync frequency | 12-15 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | -| 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. | +| 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.

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. | | 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 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. | | 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. | diff --git a/src/unify/product-limits.md b/src/unify/product-limits.md index 1e2c6eda95..9f7c9c1df5 100644 --- a/src/unify/product-limits.md +++ b/src/unify/product-limits.md @@ -46,7 +46,7 @@ Visit Segment's [pricing page](https://segment.com/pricing/){:target="_blank"} t | 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. | | 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` | 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. | +| 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.

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