The day a user starts a journey counts as day 1. 

You can define when each step appears by specifying the number of days after the user joins the journey. The day value can range from 1 to any number, and you can also specify the time of day for delivery.

Journey notifications are sent based on absolute timestamps, not on calendar days. This means that a journey day does not run from midnight to midnight (00:00–24:00). Instead, it is determined by the time a user joins the journey and the scheduled time of each journey step.

Example 1

A journey includes:

• Step 1: Day 1 at 10:00 CEST 
• Step 2: Day 2 at 16:00 CEST 
• Step 3: Day 3 at 10:00 CEST

Example 2

A journey includes:

• Step 1: Send instantly
• Step 2: Day 1 at 16:00 CEST

No, individual user time zones are not considered when sending journey steps. The scheduled day and time refer to the time zone selected in the journey settings.

No, users cannot manage notifications related to journeys. Journeys are often used to deliver essential or time-sensitive information, such as onboarding instructions or compliance training. To ensure all intended employees receive these communications, the notification preferences for journeys cannot be managed by individual users.

Whether a notification is sent for a specific journey step depends on the notification settings configured within that step. Only users with access to the Studio and the respective journey can adjust these settings.

If a user leaves a user group linked to a journey, they are automatically removed from the journey. When the user rejoins the same user group while the journey is still active, they automatically rejoin the journey as well.

This applies only to journeys with the Onboarding users to a specific group setting.

This depends on the selected journey’s rejoining setting:

• User continues the journey
  • The user rejoins the journey, and they continue the journey’s current timeline.
  • They do not receive any notifications missed while they were not part of the journey.
  • They continue the step that matches the ongoing timeline.
• User restarts the journey
  • The user starts again from step 1.
  • All notifications and posts are sent according to the journey’s timeline, as if the user were new to the journey.
  • Previously completed steps are not considered.