Skip to Content
GuidesJourneysExit node

Exit node

The exit node (type: exit) removes a contact from the journey. Once a contact reaches an exit node, they are no longer in any step and won’t receive further messages from this journey.

Configuration

  • Exit reason (optional) — a label for analytics (e.g., “Converted”, “Timed out”, “Not interested”, “Goal reached”)
  • No other settings — exit nodes are simple endpoints

When contacts exit

Contacts leave a journey in three ways:

  1. Reaching an exit node — the designed end of a path
  2. Journey completion — the journey is manually ended or archived
  3. Global exit rules — contact unsubscribes, is deleted, or leaves a required segment

Best practices

  • Every path needs an exit. If a branch path has no exit node and no more connected nodes, the contact silently drops off — which works, but you lose the “exit reason” in analytics.
  • Label your exits. A journey with three exit points — “Converted”, “Timed out”, “Unengaged” — tells you exactly where contacts are dropping off.
  • Don’t over-exit. A single send → exit flow is better served by a campaign. Journeys shine when contacts travel multiple steps.

What’s next

Split (A/B) nodeJourney analytics