State components

The State section in Journey Builder includes components that control when and for how long users remain at a specific point in a Journey.

Use State components to wait for a user action, pause a Journey for a defined period, or continue the Journey based on a specific date or time.

The following State components are available:

• On Event: Waits for a specific event before the Journey continues

• Delay: Pauses the Journey for a defined amount of time or until a specific date or day

On event

On Event allows a Journey to wait for a specific user event before continuing to the next step.

Use On Event when the next step in a Journey should depend on an action performed by the user.

For example, a Journey can wait for a Credit Application event after sending an initial message. When the user submits a credit application, the Journey continues to the next step.

Configure on event

Select the On Event step to configure the event and the conditions that determine when the Journey continues.

Step name

Enter a name for the step. Use a descriptive name that identifies the event the Journey is waiting for. For example: Credit Application Submitted

Select event

Select the event that should allow the Journey to continue. For example, select Credit Application to continue the Journey when the user submits a credit application.

The selected event cannot be changed after the Journey starts. Select the event carefully before activating the Journey.

Add trigger filters

Use Trigger Filters to specify additional criteria that the event must meet before the Journey continues. For example, select the Amount property and set the condition to:

Amount → Greater Than → 10,000

With this filter, the Journey continues only when the user triggers the Credit Application event with an Amount greater than 10,000.

Trigger filters are useful when the same event can occur under different conditions and the Journey should respond only to specific occurrences.

Add Journey Value

Use Journey Value to save data from the event and use it later in the same Journey.

For example, if the Credit Application event includes an Amount property, save Amount as a Journey Value.

The saved value can then be used in subsequent Journey steps to personalize the user's experience or make decisions based on the event data.

Add Correlation

Use Add Correlation when the Journey needs to associate the selected event with another event or data point.

Correlation can be useful when multiple occurrences of an event are possible and the Journey needs to identify the relevant occurrence based on a shared property.

For example, an Amount property can be used to associate related events that contain the same amount.

Time-out

Use Time-out to define how long the Journey should wait for the selected event.

If the event does not occur within the configured time, the user can follow the alternative path from the On Event step.

For example, if the Time-out is set to 48 hours, the Journey waits for the Credit Application event for up to 48 hours. If the event does not occur during this period, the user follows the configured time-out path.

Delay

Delay pauses a Journey before the user continues to the next step.

Use Delay when an action should happen after a specific amount of time or at a specific date or time.

For example, after a user completes an action, add a Delay before sending a follow-up message. This allows the Journey to wait for the appropriate amount of time before continuing.

Configure Delay

Select the Delay step to configure how long the Journey should wait.

Step name

Enter a name for the Delay step. Use a descriptive name that explains the purpose of the wait. For example:

Wait 2 Days Before Follow-up

A clear name makes the Journey easier to understand when reviewing the flow.

Select type of delay

Select how long the user should remain in the Delay step.

Fixed duration

Fixed Duration pauses the Journey for a specific amount of time.

Set the duration using seconds, minutes, hours, days, weeks, or years.

For example, set a 2-day delay to continue the Journey two days after the user enters the Delay step.

Use Fixed Duration when the timing should be relative to when each user reaches the step.

Until date

Until Date pauses the Journey until a specific calendar date.

Select the date when users should continue to the next step.

For example, if a user enters the Journey on September 15 and the Delay is configured for September 23, the user remains at the Delay step until September 23 before continuing.

Use Until Date when the Journey should continue on a specific calendar date regardless of when the user reaches the step.

Until day of week

Until Day of Week pauses the Journey until a specific day of the week and time.

Select the day and time when users should continue.

For example, if the Delay is configured as Tuesday 00:00, a user who reaches the step on Sunday remains there until the following Tuesday at 00:00.

Use Until Day of Week when an action should consistently occur on a particular day or time each week.