Skip to content

Commit 717e40f

Browse files
committed
touching up [netlify-build]
1 parent da619fd commit 717e40f

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

src/engage/journeys/event-triggered-journeys-steps.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ Deleting a Hold Until step can impact downstream steps that rely on it. When you
105105

106106
## Fixed delays
107107

108-
The **Delay** step holds profiles in a journey for a set period before they can proceed to the next step. This enables controlled timing for messages, actions, or other journey events.
108+
The **Delay** step helps you control the timing of journey actions by pausing profiles for a set period before they continue in the journey. This enables controlled timing for messages, actions, or other journey events.
109109

110110
Unlike the Hold Until step, Delay doesn't depend on a user action: profiles always move down the journey after the time you set. This makes Delay useful for pacing interactions, like spacing out emails, without requiring user engagement.
111111

@@ -115,28 +115,26 @@ When a journey reaches the Delay step:
115115

116116
1. Profiles enter the step and wait for the configured duration.
117117
2. Segment logs the profile's status in the observability timeline.
118-
3. If an exit condition is met during the hold period, the profile leaves the journey early.
118+
3. If the profile meets an exit condition during the hold period, the profile leaves the journey early.
119119
4. After the delay ends, the profile moves to the next step in the journey.
120120

121121
### Configurable parameters
122122

123123
The following table explains the parameters you can configure for the Delay step:
124124

125-
| Parameter | Details |
126-
| ------------- | ------------------------------------------------------- |
127-
| Duration | Set the delay period in minutes, hours, days, or weeks. |
128-
| Minimum delay | 5 minutes |
129-
| Maximum delay | 182 days (approximately 6 months) |
125+
| Parameter | Details |
126+
| ------------------ | ------------------------------------------------------- |
127+
| Duration time unit | Set the delay period in minutes, hours, days, or weeks. |
128+
| Minimum delay | 5 minutes |
129+
| Maximum delay | 182 days (around 6 months) |
130130

131131
### Configure the Delay step
132132

133133
1. Drag the Delay step onto the journey canvas, or click **+** to add it.
134134
2. (Optional:) Give the step a unique name.
135-
3. Enter a number for the duration and select a time unit (minutes, hours, days, weeks).
135+
3. Enter a duration and select a time unit (minutes, hours, days, weeks).
136136
4. Click **Save**.
137137

138-
The Delay step helps control the timing of journey actions by pausing profiles for a set period before they continue. This regulates user interactions and prevents premature movement through the journey. If a profile exits the journey while in the Delay step, it does not proceed further.
139-
140138
## Send to Destination
141139

142140
The **Send to Destination** step lets you send journey data to one of your [configured Engage destinations](/docs/connections/destinations/), enabling real-time integration with tools like marketing platforms, analytics systems, or custom endpoints.

0 commit comments

Comments
 (0)