Set who enters, exits, and re-enters your Journey—and when it starts or stops.
Your Journey Settings define how users interact with your Journey.
Journey Settings
Start by giving your Journey a name and description that clearly communicates its purpose to your team. Common examples include:
Entry rules define how users can enter your Journey based on their segment membership or custom events (beta).
Important notes:
Entry rules for a Journey
Use Include Segments and Exclude Segments to control who qualifies for your Journey. Segment checks are done at the subscription level and consider all of a user’s subscriptions. If a user is qualified to enter the Journey but also fits the Exit Rules, they will enter the first step of the Journey before exiting.
Journeys evaluate audience eligibility using all of a user’s subscriptions.
To avoid unexpected behavior, always define both included and excluded segments explicitly.
Example:
You’re targeting users inactive for 60+ hours (last_session > 60hrs
).
last_session > 60hrs
last_session ≤ 60hrs
Segments are dynamic and have users entering and exiting them constantly. Checking this option means any user currently in the included or excluded segment at the time the Journey is set live will never enter the Journey. Even if the user leaves the segment and enters again, they will never enter the Journey.
This is ideal for one-time onboarding campaigns where users should not re-enter after completing the Journey once.
Custom events are currently in beta and there may be slight changes to the API or UI.
To request access, email support@onesignal.com
with:
Once enabled, you can select a custom event to trigger Journey entry. Users that satisfy the event requirements can be in the Journey more than once at the same time.
Journey entry rules for a custom event
Enter the Event Name that you plan to send via API. Add any additional properties that you’d like to reference to filter who enters the Journey:
Select event properties
Finish adding the sequence you’d like to build and then set the Journey live.
Exit rules define when users automatically leave the Journey. They may re-enter later based on your re-entry settings.
Journey exit rules
As soon as the user returns to your app or website with the OneSignal SDK, their “last session” updates making them active again. Therefore, they exit the Journey.
Useful for re-engagement or reactivation Journeys.
Automatically remove users if they stop matching the original segment filters. Best for behavior-based targeting.
If a user enters a selected segment at any point, they are removed from the Journey and stop receiving messages.
If they are already in the segment when they enter the Journey, they will complete only the first step and be marked as “Exited Early.” Use a Wait step as the first step to prevent any messages from being sent.
Tag User on Early Exit
Apply or remove a tag when users exit early.
Trigger another Journey:
Tag users (e.g. exited-journey-1:true
), then use that tag to define a segment for your next Journey.
Limit concurrent Journeys:
Tag users when they enter (in-journey:true
), and remove the tag when they finish or exit. This allows you to exclude them from other Journeys using that tag.
Re-entry rules determine if—and when—users can enter a Journey again after exiting.
Journey re-entry rules.
Use this for:
Re-entry settings only apply to users who exit after the rules are updated.
Earlier exits follow the original re-entry configuration.
Journey schedule options
To stop new users from entering but let current ones finish:
This ensures existing users continue through to the end.
If your account has reached its Journey limit: