Skip to content

Commit baeee12

Browse files
pwsegpwseg
committed
add more sections
1 parent dfafcd3 commit baeee12

File tree

1 file changed

+71
-1
lines changed

1 file changed

+71
-1
lines changed

‎src/engage/journeys/limits.md

Lines changed: 71 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,74 @@
11
---
22
title: Journeys Product Limits
33
plan: engage-foundations
4-
---
4+
---
5+
6+
This page outlines the current limitations for Event-Triggered (V2) Journeys.
7+
8+
## General limits
9+
10+
| Name | Limit | Description |
11+
| ------------------- | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
12+
| Steps | 25 | Maximum number of steps per journey. |
13+
| Journey name | 73 characters | Maximum length for Journey names. Names must be unique. |
14+
| Step name | 73 characters | Maximum length for step names. |
15+
| Branch name | 73 characters | Maximum length for branch names within a split step. Branch names must be unique across the journey. |
16+
| Additional branches | 5 | Maximum number of branches supported in a split or Hold Until step. |
17+
| Delay duration | Minimum: 5 minutes<br>Maximum: 6 months | Allowed time range for Delay and Hold Until steps. |
18+
| Unique identifier | 500 characters | For “Re-enter every time event occurs” rules, you must define a unique identifier. The value is limited to 500 characters. |
19+
20+
21+
## Throughput
22+
23+
| Name | Limit | Description |
24+
| ------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
25+
| Requests per second (RPS) | 25 events/sec/profile | Maximum events per second per Segment ID. Timer events are excluded. Excess events get dropped. |
26+
| Instances per profile | 25 concurrent instances | Maximum concurrent Journey instances per profile. |
27+
| Loop back branch | 100 instances | Maximum instances that can pass through a Wait Until loop-back. |
28+
29+
## Journey context
30+
31+
| Name | Limit | Description |
32+
| ------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
33+
| Journey context object | No limit (subject to payload size) | No object limit in Journey context, but must remain within the 32 KB payload limit. |
34+
| Event name conflicts | Must be unique unless aliased | Duplicate event names in the Journey context will overwrite each other unless aliased using `[event_name] + [branch_name]`. |
35+
36+
## Send to destination
37+
38+
| Name | Limit | Description |
39+
|------|-------|-------------|
40+
| Supported destinations | [Action Destinations only](https://segment.com/docs/connections/destinations/actions/) | Only Action Destinations are supported in Journeys 2.0. |
41+
| Activations | 5 per Destination step | Maximum number of Activations supported per Destination step. |
42+
| Destination key | 31 characters | Auto-generated and not editable. Based on `{Journey_Name} + {Destination_Step_Name} + {Unique_Step_State_Key}`. |
43+
| Destination event name | 73 characters | Can be customized. Defaults to the destination step name. Event names do not need to be unique. Use the Sync Key for disambiguation. |
44+
| Payload size | 32 KB (~700 lines) | Maximum allowed size of the payload sent to destinations. |
45+
| Parameter mappings | 100 mappings | Maximum number of field mappings per Destination step. For more info, see [FAQs & Best Practices for Journeys 2.0](https://twilio-productivity.atlassian.net/wiki/spaces/MSRND/pages/772571588/FAQs+Best+Practices+for+Journeys+2.0#How-do-Journeys-affect-Destination-mapping-limits%3F). |
46+
47+
---
48+
49+
## Analytics
50+
51+
| Name | Limit | Description |
52+
|------|-------|-------------|
53+
| Journey instance data (in progress) | 365 days | Maximum duration an instance can remain active before expiring. |
54+
| Journey instance data (completed) | 90 days | Data retention period after a profile completes or exits the Journey. |
55+
| Analytics data | 3 years | Retention period for metrics data. |
56+
| Observability data | 3 years | Retention period for step activity and timeline data. |
57+
| Date range | 180 days | Maximum date range allowed for analytics queries. |
58+
| Timeout limit | 10 seconds | Maximum time an analytics query will run. |
59+
| Metric latency | 10 seconds | Expected delay before metrics update. Can increase with large volumes. 95% of events are targeted to appear in the UI within 30 minutes. |
60+
| Update metrics | Manual browser refresh required | Analytics do not update dynamically. Refresh required to see updates. |
61+
62+
---
63+
64+
## Privacy and compliance
65+
66+
| Topic | Details |
67+
|-------|---------|
68+
| PII access | [Learn more](https://segment.com/docs/segment-app/iam/roles/#pii-access) |
69+
| HIPAA eligibility | [HIPAA-Eligible Services](https://www.twilio.com/content/dam/twilio-com/global/en/other/hipaa/pdf/HIPAA-Eligible-Services.pdf) |
70+
| GDPR & BCR | [Complying with the GDPR](https://segment.com/docs/privacy/complying-with-the-gdpr/) |
71+
72+
Segment complies with GDPR through Binding Corporate Rules (BCR). When a customer churns, BCR-initiated deletion removes the customer’s workspace and data. Customers can request access to, correction of, or deletion of personal data.
73+
74+
---

0 commit comments

Comments
 (0)