Skip to content
Last updated

Journey Simulation

This feature is in BETA version. For more information, contact your Customer Success Representative.

Overview

Journey Simulation allows marketers and customer experience teams to validate how profiles move through a Journey before launching it live. With Simulation Mode, you can instantly preview entry logic, branching behavior, wait steps, and message paths in a safe, controlled environment.

This helps teams test journeys confidently, reduce configuration errors, and launch campaigns with greater accuracy.

When to Use Journey Simulation

Use Simulation Mode when you need to:

  • Confirm that your entry criteria are correct

  • Preview how profiles will pass through decision points or A/B tests

  • Validate wait steps without real-time delays

  • Understand branching logic before publishing

  • Share and review journey behavior during QA

  • Troubleshoot unexpected logic before a journey goes live

Simulation Mode is designed for pre-launch validation and works best for journeys in the Draft state.

Entering Simulation Mode

Below is where you will find the Simulation Mode entry point on the Journey Builder canvas.

Journey Simulation

  • Simulation Mode Button – Click this to begin validating and testing your journey.

  • Draft State Requirement – Simulation is only available when the journey is in Draft state.

  • Safe Testing Environment – No real profiles or activations are affected.

Key Capabilities

One-Click Simulation Mode

From any Draft journey, select Simulation Mode to begin validation instantly. The system automatically checks for missing or invalid configurations before entering the simulation environment.

Automatic Profile Selection

Journey Simulation automatically selects profiles from the Parent Segment that meet the entry criteria at the time simulation begins. This provides a fast, frictionless way to test the journey.

Fast-Forwarded Wait Steps

Simulation Mode skips real wait times so you can immediately see how profiles progress through time-based steps. Each wait node displays simulated “entered” and “exited” timestamps.

Simulation Results

Journey Simulation Result

  • Highlighted Paths – Shows which branches profiles actually followed.

  • Profile Counts – Each node displays how many profiles passed through it.

  • Simulated Wait Times – Displayed as “Entered” and “Exited” timestamps.

Simulation Log

A detailed log panel summarizes key information, including:

  • Simulation start and end time

  • Parent Segment refresh time

  • Node-level entry and exit timestamps

  • Execution outcomes for each step

This helps teams validate logic and timing at a glance.

How It Works

Open a journey in Draft state.

  1. Click Simulation Mode.

  2. Resolve any validation errors if prompted.

  3. Allow the system to auto-select profiles or manually choose your own.

  4. Click Run Simulation.

  5. Review highlighted paths and the simulation log.

  6. Rerun or exit simulation when finished.

  7. Simulation Mode never modifies real profiles or live campaigns.

Current Limitations

The following behaviors are expected in the current Early Access release:

  • Simulation is static: all profiles that satisfy the entry criteria enter the journey simultaneously.

  • Performance may vary based on journey size and system activity.

  • Jump steps are not supported in Milestone 1.

  • Profile attributes cannot be edited during simulation.

  • Simulated results are visible only while Simulation Mode is active.

FAQ

Is Journey Simulation generally available?

Journey Simulation is currently available as an Early Access feature. Please contact your Customer Success Manager (CSM) to request enablement.

Does simulation impact real customer data?

No. Simulation Mode does not affect any profiles, campaigns, or reporting.

Can I simulate a published journey?

No. Simulation Mode is available only for journeys in Draft state.

Does the simulation send real messages?

No. Simulation evaluates logic only. External systems are not triggered.

Why are some branches or steps greyed out?

This indicates that no profiles visited those paths during the simulation.

Why might simulation time vary?

Simulation time may vary depending on journey complexity and overall system activity.