Skip to content

Commit 34ac294

Browse files
pwsegpwseg
committed
cleanup
1 parent baeee12 commit 34ac294

File tree

1 file changed

+27
-24
lines changed

1 file changed

+27
-24
lines changed

‎src/engage/journeys/limits.md

Lines changed: 27 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -35,39 +35,42 @@ This page outlines the current limitations for Event-Triggered (V2) Journeys.
3535

3636
## Send to destination
3737

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). |
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 | 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 (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. |
4646

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

4957
## Analytics
5058

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

62-
---
6366

6467
## Privacy and compliance
6568

66-
| Topic | Details |
67-
|-------|---------|
68-
| PII access | [Learn more](https://segment.com/docs/segment-app/iam/roles/#pii-access) |
69+
| Topic | Details |
70+
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------ |
71+
| PII access | See [PII access](docs/segment-app/iam/roles/#pii-access) for more information. |
6972
| 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/) |
73+
| GDPR & BCR | [Complying with the GDPR](https://segment.com/docs/privacy/complying-with-the-gdpr/) |
7174

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

0 commit comments

Comments
 (0)