Journeys
Triggers and reentry
Audience, event, and field entries; reentry policies; goal exit.
A Journey starts when a contact matches one of its entries. A journey can have more than one trigger. Each entry has its own type, audience scope, optional start node, and reentry policy.
Trigger types
| Type | Fires when |
|---|---|
| Audience | The contact newly matches the Journey’s audience (typical onboarding). |
| Event | Your product sends a named event (order_placed, signup_completed). |
| Field changed | A contact property changes to a value you care about. |
| Signup | A new contact appears. |
| Birthday | Date-based (the contact’s birth date field). |
Event entries carry a data snapshot into every email of that enrollment. Audience and field triggers do not.
Additional triggers can land on a different start node so “upgraded to pro” skips the beginner emails and enters mid-graph.
Reentry
reentryPolicy is one of:
| Policy | Meaning |
|---|---|
| never | One enrollment in the lifetime of this Journey (default for audience / signup). |
| after_exit | May enroll again only after they have exited (default for field-changed / birthday). |
| always | A new qualifying event can start another enrollment (default for events). |
Open enrollments are never duplicated. If someone is already scheduled, active, holdout, or blocked on this Journey, a second trigger does not create a parallel run.
Pick always for receipts and per-order drips. Pick never for “welcome to the product” so a profile edit cannot restart onboarding.
Audience scope
Even event-triggered Journeys usually still scope to an audience (“pro plan only”). The event is the spark; the audience is the fence. Preview the audience before you attach it.
Goal exit
When the Journey goal’s exit on reach is on (default), firing goal.event while enrolled exits with goal_reached. That stops later emails in the sequence. Turn it off only when you intentionally want the rest of the path after conversion (rare).