Session limits and entry rules control when and how often a user joins a journey. These settings live on the entry element of each journey.
Per-journey scope
Session and re-entry settings apply only to the journey where you set them. They do not change how other campaigns in your project behave.
Active sessions
On a Trigger-based entry you choose between:
- One active session per user (default) - a user cannot be in the same journey twice at once. If the entry event fires again while the user is still inside, that event is ignored.
- Multiple active sessions per user - requires a session identifier attribute (for example
order_id) that is present in the entry event and in every Wait for Trigger and Conversion Goal used by the journey. Without it, the event is applied to all of the user's active sessions.
Re-entry
A separate setting controls whether a user who already finished the journey may start it again:
- Do not allow re-entry (default) - a user goes through the journey once.
- Allow re-entry - the user can enter again after they exit.
You can additionally restrict when entry is possible at all: Allow entry at any time or Limit entry to a specific period.
Audience-based entry and restarts
For an Audience-based entry with a recurring schedule, users who are already inside the journey at the moment of the next start do not enter again - they stay at their current step and continue from there. For a one-time entry you also choose who is eligible: Existing users only (default), Existing + new users, or New users only.
A user starts the journey from the beginning only when both the entry element conditions and the re-entry setting allow it. If either blocks the user, they do not enter.
Comments
0 comments
Please sign in to leave a comment.