Define wait periods, branch journeys based on user behavior, and tag users using journey steps.
Use Journey actions to control how and when users move through your Journey, personalize experiences, and test outcomes.
Delay the user’s Journey progression by a specific amount of time—minutes, hours, days, or weeks.
Use it to:
A wait node with users currently waiting to progress in the journey
Wait Until Action is currently in beta.
To request access, contact support@onesignal.com
with:
Hold a user at this step until they meet specific conditions:
You can set an expiration time. After the expiration:
You can also add multiple conditions and branch users based on the first condition they meet.
Wait Until user is in a segment or triggers a custom event
Restrict when users can move to the next step in the Journey based on specific days and times.
Example: Only allow users to receive a message on weekends in the evening.
Screenshot showing an example of a time window node
If a user enters this node outside the allowed time:
Example:
If your time window is Tuesdays from 1:00 PM to 6:00 PM PST, and a user hits the node on Monday, they may continue Tuesday at a random time like 5:45 PM.
Branch users based on segment membership or message behavior.
Create branches based on what segment a user is in.
Example:
If users are tagged by plan type:
Branch based on interaction with previous messages in the Journey:
Note: Safari does not support Confirmed Delivery.
Randomly distribute users across different paths to test messaging, channels, or Journey flows.
An example of a 3-way split branch
Once a Journey is live, you cannot edit a Split Branch. To change the number of branches, create a new Journey.
Split branch settings
By default, users are re-randomized each time they re-enter a Journey.
To keep them on the same branch, turn off Randomize on re-entry.
Use the Tag User action to track which branch a user followed.
Nest Split Branches to simulate more complex testing structures.
Example:
To split users equally across 3 variants:
This gives ~33% on each path.
Test the impact of messaging by leaving one branch empty (no message nodes).
Once a winning variant is identified, update the branch to send 100% of traffic down that path.
Use this action to apply or remove tags during a Journey.
Common use cases:
journeyStep: welcome
)A simple onboarding/welcome flow
onboardingJourney: active
)A tag node settings to remove the tag from the user