Skip to content

Commit d1bf3fc

Browse files
markzegarelliashton-huxtableforstisabellapwsegsarahrudy
authored
Release 23.3.2 (#4071)
* Update faq.md * Developer Center 2.0 documentation (#4007) * Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <[email protected]> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <[email protected]> * Update Amplitude Classic Destination DOC-629 * Update EU Endpoint Language DOC-629 * Update index.md Add note about the API Key being region specific * Revert commit * Add section highlighting User Data parameter mappings to Facebook Conversions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]> * added react native quick link * add section for api token security * update copy * Small edits * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update vale rules (#4055) * posthog: update instructions for Cloud EU * Add Audiences and Journeys Guide [netlify-build] * add correct actions slug (#4060) Co-authored-by: Niall Brennan <[email protected]> * Add platform code for setting writekey (#4050) * add platform code * add platform code * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: markzegarelli <[email protected]> * add info about how data comes from Clearbit (#4040) * add info about how data comes from Clearbit Customers in the past have been confused about dataflow with Clearbit and about why they see analytics-ruby events in their Debugger. This update clarifies that a bit. There are past Zendesk tickets that all confirm Clearbit data comes back to Segment using analytics-ruby. In addition, Clearbit published this line about it in one of their blog posts: https://clearbit.com/blog/enterprise-grade-analytics-for-startups-2#:~:text=Segment%E2%80%99s%20robust%20API%20and%20Ruby%20library%20enabled%20our%20engineering%20team%20to%20quickly%20build%20an%20event%20emitting%20service%20that%20sends%20usage%20and%20behavioral%20data%20from%20Clearbit%20applications%20and%20services%20into%20Segment%2C%20tracking%20everything%20from%20API%20usage%20and%20page%20views%20to%20signups%20and%20subscribe%20events.. * Update src/connections/destinations/catalog/clearbit-reveal/index.md Co-authored-by: markzegarelli <[email protected]> * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * catalog update (#4064) * Add new product limits for Engage (#3965) Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]>
1 parent e427cf8 commit d1bf3fc

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)