The options that used to be called "Launch once", "Launch on several days" and "Launch periodically" have been reorganized. In the Audience-based entry element you now configure an Entry schedule, which controls when the journey checks the segment and adds users. There are two entry types:
One-time entry
Users enter the journey once. Choose when:
Immediately (replaces "Launch once"): users enter as soon as the journey is activated. Timezones are not taken into account — everyone in the segment enters at once.
Schedule for a specific day: users enter on the date and time you set. You pick a timezone — the subscriber's device timezone (default, with a configurable fallback) or a fixed timezone. You also choose what happens to users whose local scheduled time has already passed: exclude them, or let them enter immediately.
Recurring entry
Users enter the journey repeatedly. Choose the schedule:
On specific dates (replaces "Launch on several days"): pick individual dates in the calendar with + Add Date, then set the time and timezone. Subscribers whose time has already passed are included on the next scheduled date.
Periodically (replaces "Launch periodically"): set the interval in ENTRY EVERY (e.g. every 1 day, every 2 weeks), pick the days, then the time and timezone.
The segment is recalculated before each scheduled entry, so users who joined the segment since the previous run enter at the next scheduled time. Users already inside the journey at that moment do not enter again.
Define who enters
Independently of the schedule, you choose which segment members are eligible:
- Existing users only (default): only users who match the segment at launch.
- Existing + new users: matches at launch, plus users who match later.
- New users only: nobody at launch, only users who start matching after activation.
Note that Existing + new users and New users only are not supported for event-based segments, and CSV-imported segments are static. RFM segments only pick up new users after you recalculate them under Audience > RFM Segmentation.
Comments
0 comments
Please sign in to leave a comment.