Re-entry criteria decide what happens when a profile that has already been through a journey qualifies for it again: it starts over, or it stays out because it already converted. Choose the setting deliberately before you launch, because goal completion never expires and the setting cannot be changed afterward — not even in a later version of the journey.
- Open Treasure Console.
- Navigate to the Audience Studio.
- Select a parent segment and then select a journey.
You can only define re-entry criteria when a journey is in draft mode.
- Select Open journey.
- Select the pencil icon (
) to edit journey details.
- Under Re-entry of Stale Profiles, choose one of the following:
- Select Never allow re-entry to prevent profiles from re-entering the journey.
- Select Allow unless goal has been met to permit profiles to re-enter the journey.
- Select Allow even if goal is met to permit profiles to always re-enter the journey.
- Select Save details.
After the first version is launched, the Re-entry of Stale Profiles option cannot be changed for any future version of the journey, and neither can stage names, numbers, or order. If you later need different re-entry behavior, you have to build a new journey.
| Profile meets | Never allow re-entry | Allow unless goal has been met | Allow even if goal is met |
|---|---|---|---|
| Exit criteria in current journey (out of journey) | Can't re-enter | Can re-enter journey | Can re-enter journey |
| Goal in current journey (out of journey) | Can't re-enter | Can't re-enter | Can re-enter journey |
| Exit criteria in current or different journey (from select a destination option) | Can't re-enter | Can re-enter journey | Can re-enter journey |
| Goal in a different journey (from select a destination option) | Can't re-enter | Can't re-enter | Can re-enter journey |
| Jump in current or different journey (from select a destination option) | Can't re-enter | Can re-enter journey | Can re-enter journey |
Journey Orchestration records the moment a profile meets the journey goal and keeps that record for the life of the journey. The record has no expiry date. Allow unless goal has been met therefore asks "has this profile ever met the goal?", not "did it meet the goal recently" — a profile that converted a year ago is still blocked from that journey today.
Two consequences shape how you plan a long-running program:
- A new journey version does not release profiles that met the goal. When you launch a new version, it excludes profiles that are still associated with earlier launched versions of the same journey. Under Allow unless goal has been met, profiles that left through exit criteria are released into the new version, but profiles that met the goal are not. (Under Allow even if goal is met, both groups are released.)
- A separate journey starts fresh. Goal history belongs to a single journey, so a journey you build later for a new campaign evaluates every profile from scratch, past converters included.
To reach converters again in a later campaign, choose one of the following approaches:
- Select Allow even if goal is met when you first create the journey, and use exit criteria or stage rules to control how often a profile flows through it. Decide this up front — the option is locked once the first version launches.
- Create a new journey for the later campaign.
See also: Journey FAQs