The Path Optimizer condition automatically directs users to the best-performing journey branch based on real-time engagement or conversion data.

Rather than distributing users equally across variants and manually checking performance, this node uses statistical learning to evaluate outcomes and adjust user routing in real time.

You select a metric (Clicks or Conversions), and the system tracks each branch's performance, optimizing which variant gets more traffic as data accumulates.

Use this condition when you want to optimize user routing based on ongoing performance.

When users pass through the Path Optimizer node, the Journey Path Optimizer's ML model gets to work, evaluating each branch's performance in real time. As data accumulates, the model balances exploring all available branches while progressively favoring those that drive better results.

📘

Important Points to Remember

• Choose Clicks when the goal is to maximize engagement (e.g., message interactions), and choose Conversions when the goal is to drive specific outcomes like purchases or sign-ups.
• You must include at least one communication channel node (Email, SMS, WhatsApp, etc.) in each branch.
• For Conversions, ensure a Journey Goal is set. Without it, the optimizer cannot function.
• You cannot publish the journey until these conditions are satisfied.
• Re-deploying the journey resets the Path Optimizer node—treating it as a fresh start with no prior winner or metric data.

Video Tutorial

Refer to the video below to understand how to use Journey Path Optimizer in your Journey.

Business Use Cases for Path Optimizer

The Path Optimizer can be applied across various industries to test and improve message performance, timing, and conversion outcomes. Below are common real-world use cases categorized by vertical:

How JPO Optimizes Across Journey Types

The Path Optimizer is powered by an ML model that recalibrates in real time, continuously evaluating variant performance and adjusting traffic routing as engagement data flows in. Before optimizing, the model establishes performance benchmarks across all active variants. This learning phase is what enables JPO to make increasingly intelligent routing decisions over time.

The speed at which optimization becomes visible is directly influenced by how users enter the journey, specifically by the rate and continuity of the data the model receives.

In the dataset journeys, users enter in large volumes simultaneously. Since the model recalibrates on a rolling basis, users processed within the same window are routed using the current benchmark, with refined insights applying to the next scheduled run. The larger and more continuous the data flow, the faster the model evolves.

In trigger-based journeys, users enter continuously over time, providing the model with a steady and uninterrupted stream of engagement signals. This allows JPO to recalibrate between entries, adapting routing decisions in real time and surfacing the best-performing variant faster as data matures.

📘

BEST PRACTISE

Trigger-based journeys unlock JPO's full optimization potential. The continuous user flow gives the ML model the data density and time it needs to explore variants, identify top performers, and shift traffic decisively — delivering measurable engagement uplift with every passing hour.