OneTrace.pro Help center

Journeys

A journey guides a customer through a scenario. It starts from an event, a segment entry, a date, or a schedule, and continues with waits, conditions, and messages. Typical examples: abandoned cart, welcome series, win-back for lapsed customers.

The section is in the menu under Engagement → Journeys. All roles can view journeys. Manager and above can edit and publish them, as can roles that have been granted permissions on specific journeys.

Journey list

The table shows the name and published version number, the status (Draft, Active, Paused, Archived), how many participants are in the journey right now (In progress), and the Total entries and Goals columns.

Tabs above the table filter journeys by status. Active opens by default; next to it are Drafts, Paused, Archived and All, each with the number of journeys. To sort the table, click a column header; click it again to reverse the order. Journeys with a schedule or date trigger show the next check and the last one, with the number of participants who entered, under their name. The journey page shows the same.

Journey list

There are two ways to create a journey:

  • enter a name and click Create to open the editor with an empty draft;
  • click From a template and choose a ready-made scenario.

Journey templates

The Journey templates page has search and categories: Essentials, Catalog, Industries, Predictions, Multichannel, Loyalty, Online casino, and Brand templates. For example, Essentials includes a welcome series, abandoned cart, abandoned browse, post-purchase review, win-back, and birthday.

  1. Click Use on a template card.
  2. In the New journey from a template dialog, enter a name. In the Channels block, choose an integration for each channel or leave Choose later. In the Segments block, choose an existing segment or Create a new one from the template.
  3. The dialog shows how many message templates will be created and which events will appear in the catalog.
  4. Click Create journey. The journey is created as a draft: check the texts, links, and delays, then publish it.

The Import from file button loads a journey exported with the Export button on a journey page, for example from another project. Further down the same page, the Template usage section shows how journeys from each template convert.

Journey template gallery

Editor

The node palette is on the left and the canvas is in the center. At the top are the name, the status, and the Versions, Test, Validate, and Publish buttons.

  • Click a node in the palette: it's placed under the selected node and connected to its free output. You can also drag a node onto the canvas and then connect an output (at the bottom) to an input (at the top).
  • Click a node to open its settings on the right. Click a connection to delete it.
  • The draft saves itself a second after each edit. Next to the name you'll see Draft saved or Unsaved changes….
  • Connections show how many participants went through each output. Nodes show how many participants are waiting there right now.

Entry

Click the Entry node and set up:

  • Trigger: Event with property filters, Entered a segment, Left a segment, Trait changed, Date from a trait (for example, 3 days before a birthday), Schedule (the whole segment once, daily, or weekly; below the settings is the segment's Email address check, see address check), Loyalty program (joining, earning, redemption, and expiry of points, a tier change, referrals; see loyalty), Chat (conversation started, closed, or rated, bot handed the conversation over; see live chat), Form (a subscription from a website form; see signup forms), Survey answer (the survey and the score range; see surveys), Catalog (price dropped, back in stock, low stock; see product prices and availability), In-store purchase (a check from a store; you can choose the store and a minimum amount; see in-store sales), Social media keyword (a rule fired in a social network or a person left a contact; see social media), or API call;
  • Audience: a segment. If you don't set one, everyone the trigger lets through enters;
  • Re-entry: Only once, Again after finishing (you can set a pause), or Every time (in parallel);
  • a Max participants at a time limit;
  • Goal (event) and the window in which it counts. For example, order_completed within 3 days. Reaching the goal ends participation and counts as a conversion;
  • events that make a participant leave the journey: Exit the journey on event;
  • Send to the control group too, if the project has a control group turned on. Without this switch, group members move through the journey like everyone else, but messages aren't sent to them.

Nodes

Group Nodes Outputs
Wait Delay for N minutes, hours, days, or weeks; Wait until time: a time of day in the customer's time zone, optionally on selected days of the week; Wait for best hour: the customer's best hour, no longer than a day (without their own hour, the project's best hour or right away) next
Wait for event, up to a set time limit received, timeout
Conditions by trait, by segment, by event yes, no
Splits A/B split: branches with shares adding up to 100%, or automatic selection of the best branch branches
Multi-branch split: the first matching branch branches, else
Decision: for each participant, the action with the highest expected uplift in revenue, purchase, or retention. See Next best action actions, nothing
Actions Send message: an integration and a template. Waits up to 3 days for the send result sent, failed
Cascade message: one message through 2–5 channels in turn until it's sent, delivered, or read. See cascades reached, failed
Send WhatsApp form: a WhatsApp form and a wait for the reply to it, no longer than the set time. Answers are saved to profile traits and an event received, timeout, failed
Update trait, Add tag, Remove tag, Static segment next
Webhook: a request to an external system success, failed
Award points: to a member of the loyalty program next, not a member
Issue a promo code: a code from a pool; the next messages get the same code next, no code
Deal in CRM, Task in CRM, Deal stage in CRM, Contact in CRM: actions in the connected CRM, see CRM success, failed
Finish Goal, Exit —

If an output isn't connected to anything, the path ends there. Journey messages go through the messaging rules: subscription, frequency, and quiet hours. Transactional templates skip these checks.

Journey editor with the entry settings open

Validation, testing, and publishing

  1. Validate highlights errors on the canvas. For example, the entry isn't connected to the first node, a node is unreachable, a loop has no wait, or branch shares don't add up to 100%. If there are no errors but something is worth checking, the "Pre-launch check" dialog opens: emails in send steps without an unsubscribe link or without a version in a project language, an unverified sending domain, an empty segment or, for a journey with a schedule trigger, a segment covering almost the whole base, a goal without a conversion window, or a goal event that has never arrived.
  2. Test runs the draft on a profile. Conditions are evaluated against the customer's data, waits are skipped, and actions aren't performed. If you enter an address for test messages, send steps deliver a test to it. The Awaited events arrive switch sends the participant down the received branches. The path taken is highlighted on the canvas.
  3. Publish creates a new version. Participants go through the journey using the version they entered, and new participants enter the latest one. After publishing, edits go to the draft again until the next publish. If the check found warnings, the same dialog opens first: publish with the button in it or go back to editing.
  4. Versions shows the publishing history. The To draft button copies the selected version into the draft.

Check before publishing a journey

If approval is turned on in the project, a journey can only be published once it has been approved. The Submit for review, Approve, and Return buttons are in the editor header. A member with the Approve journeys permission can approve, including one who has it only for specific journeys. Moving nodes around the canvas doesn't remove the approval. Changing the name, steps, their settings, connections, or entry conditions, or restoring a version with the To draft button, sends the journey back to review. The published version keeps running until a new one is published.

The Update trait, Add tag, Remove tag, Award points, Issue a promo code, Static segment steps change data in other sections. Only a member who can edit those sections can add or change them in the version being published. Steps that are already published and unchanged can be republished by anyone who can publish the journey.

Managing a journey

The journey page has the Editor, Export, Pause or Resume, and Archive buttons. Export is shown only if your role has rights to message templates and segments across the whole project: the file contains their texts and rules.

  • Pause: new participants don't enter, and current ones stay where they are. Goals and exit conditions keep working. After you resume, participants continue.
  • Pause and remove participants: the same as a pause, but all current participants leave the journey right away.
  • Archive: all current participants leave the journey, and it can no longer be changed.
  • The In progress, Completed, Exited, and Failed cards count participants for all time. The Recent participants list shows which node each participant is on and when they'll continue. The exit icon removes a participant from the journey manually.

Report and A/B test

The Journey report on the journey page shows participants who entered in the last 7, 30, or 90 days: Entered, Goals, and Conversion. The Node funnel shows these columns for each node: Reached node, Outputs, On node now, Finished here, Lost, and Average wait. If 20% or more of participants are lost, the number is highlighted in red.

Each A/B split has a table of branches and a verdict: Variant … beats the others, No difference, or Not enough data yet with an estimate of the sample size needed. The first branch is treated as the control. Significance is only calculated if the journey has a goal: a Goal node or an entry goal. Decide on a winner at a time you chose in advance, not at the first visible lead.

Journey report with an A/B split

Automatic branch selection

An A/B split has a Mode: Fixed shares divides participants by the branch percentages, while Automatic shifts participants toward the best branch on its own. In Automatic mode, branch percentages aren't set. At first, participants are split equally. Once every branch has 100 participants, the best branch's share starts to grow. Every branch still gets at least 10% of participants: a branch that looks weak on early data doesn't disappear, and the estimation error stays visible. Shares are recalculated once an hour.

In the Best branch by field, choose what counts as success:

  • journey goal: the participant reached the goal, a Goal node or an entry goal;
  • message opens or message clicks: a message sent to the participant after the split was opened or had a click.

Branch results are counted over the whole time the split has been running. The mode is available on a plan with the Automatic variant selection feature, available from the Growth plan.

A/B split settings in Automatic mode

The report for such a split shows when the shares were last recalculated, a Current share column, and a Branch shares by day chart that shows how participants shifted toward the best branch. The branch table and the significance verdict are the same as for a regular split. If branches are compared by messages, a second verdict below covers opens or clicks over the whole time of the split.

Report for an Automatic split: current share and shares by day