Overview
Journeys define who gets messaged, when, and with what content. Each journey starts with an Entry Node and ends with an Exit Node. In between, you can arrange any combination of nodes to create rich, personalized experiences. By default, a new journey does nothing—until you add messaging logic with the AI Builder. Tranthor’s AI Builder recommends nodes and paths as you design, optimizing your journey for engagement and compliance.AI Journey Builder
The AI Journey Builder provides an intuitive drag-and-drop interface, powered by Tranthor AI. As you build, it suggests the best sequence of nodes and highlights opportunities to personalize or automate. Journey Nodes:- Entry Node: Define which users can enter and when.
- Message Node: Send personalized messages across channels.
- Wait For Node: Pause until a user meets a condition (e.g., enters a segment).
- Delay Node: Wait a specific amount of time before progressing.
- Segment Split Node: Branch logic for different user segments.
- Exit Node: Mark a user’s journey as complete.
Journey Status
Journeys move through three statuses:- Not Started: Draft state; users cannot enter.
- Running: Live; eligible users enter and progress automatically.
- Paused: Entry is halted; current users continue until a message step, which is skipped if not resumed.
Edit a running journey
You can change a journey that is running or paused without stopping it. Your edits are a draft, and the live version keeps running until you publish.- While you edit, the journey shows how many changes are not live, and each step you touched is marked New, Changed or Removed.
- Publish changes lists every change before it goes live. People already in the journey finish the version they entered. People who enter afterwards get the new one.
- The ··· menu has See live version, What changed and Discard changes, which drops the draft and leaves the live journey as it is.
Version history
Every publish that changes the journey makes a numbered version. Version history, in the ··· menu, lists each version with who published it, when it was live, how many people entered it and how many are still finishing it. Open an older version to view it, or select Make a draft from it to start a new draft from that version.Measure results
Once a journey is running, the Results tab shows how it is performing.- Goal and revenue. Shows the conversions and revenue attributed to the journey’s messages. If you have not set up conversion tracking, the tab shows Configure a goal and revenue metrics stay blank.
- Message performance. For each message step, the delivery and engagement results for its channel, such as opens or reads, unsubscribes, and spam complaints.
- Steps and paths. How many users each step processed and where they went next, including the branches of a split.
- Holdout comparison. If you use a holdout group, the tab compares held-out customers with the rest. Early results are labelled Holdout test measuring or preliminary, and the comparison is described as an observed difference, not proven causal lift. Lift is unavailable until the observation window is mature and the measurement is complete.
Track conversions and revenue
Turn on Conversion tracking in the journey’s Settings tab to count what happens after a message.
A conversion is credited to the customer’s most recent matching message inside the window, for that journey only. The same settings are available for broadcasts.

