Skip to content

Commit 763edbb

Browse files
pwsegpwseg
authored
Merge pull request #7695 from segmentio/journeys-product-limits-v2-page
Add Journeys (v2) Product Limits page [DOC-1132]
2 parents c68a977 + c2b532d commit 763edbb

File tree

1 file changed

+75
-0
lines changed

1 file changed

+75
-0
lines changed

‎src/engage/journeys/v2/limits.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
title: Journeys (V2) Product Limits
3+
plan: engage-foundations
4+
---
5+
6+
This page outlines product 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](/docs/connections/destinations/actions/) | Segment only supports Action Destinations, Action List destinations, and Destination Functions in Journeys 2.0. |
41+
| Activations | 5 per destination step | Maximum number of Activations supported per destination step. |
42+
| Destination key | 31 characters | Segment auto-generates destination keys; they're not editable. |
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 (Computation 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. |
46+
47+
48+
## Data retention
49+
50+
| Name | Limit | Description |
51+
| ----------------------------------------------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
52+
| Journey instance data (while in progress) | 365 days | Maximum duration an instance can remain active before expiring. |
53+
| Journey instance data (after completed or exit) | 90 days | Data retention period after a profile completes or exits the journey. |
54+
| Analytics data | 3 years | Retention period for metrics data. |
55+
| Observability data | 3 years | Retention period for step activity and timeline data. |
56+
57+
## Analytics
58+
59+
| Name | Limit | Description |
60+
| -------------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
61+
| Date range | 180 days | Maximum date range allowed for analytics queries. |
62+
| Timeout limit | 10 seconds | Maximum time an analytics query will run. |
63+
| Metric latency | 10 seconds | Expected delay before metrics update. Can increase with large volumes; 95% of events are targeted to appear in your workspace within 30 minutes. |
64+
| Update metrics | Manual browser refresh required | Analytics don't update dynamically. You'll need to refresh to see updates. |
65+
66+
67+
## Privacy and compliance
68+
69+
| Topic | Details |
70+
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
71+
| PII access | See [PII access](docs/segment-app/iam/roles/#pii-access) for more information. |
72+
| HIPAA eligibility | [HIPAA-Eligible Services](https://www.twilio.com/content/dam/twilio-com/global/en/other/hipaa/pdf/HIPAA-Eligible-Services.pdf){:target="_blank"} |
73+
| GDPR & BCR | See [Complying with the GDPR](/docs/privacy/complying-with-the-gdpr/) for more information. |
74+
75+
Segment complies with GDPR through Binding Corporate Rules (BCR). When a customer churns, BCR-initiated deletion removes the customer’s workspace and data. To request access to, correction of, or deletion of personal data, reach out to [Segment support](mailto:[email protected]).

0 commit comments

Comments
 (0)