Conditional Split Node
Learn how to use the Conditional Split node to create personalized user journeys based on user details or actions.
Overview
The Conditional Split node in CleverTap Journeys empowers marketers to route users dynamically based on real-time behavior and profile attributes. The node evaluates the most recent user data at the exact moment a user reaches the node. Based on conditions configured using event properties or user profile attributes, CleverTap instantly determines which path the user should follow. This enables real-time segmentation within a journey, eliminating the need for static, pre-defined segments and unlocking adaptive, data-driven engagement flows.
For example, a music streaming app wants to split users based on the plan_type user property as soon as the user signs up. The Conditional Split node acts as a decision point within a journey. When a user completes sign-up and reaches this node, CleverTap evaluates the defined conditions using the most recent user data and instantly routes the user to the matching path.
Here, the triggering event is Sign Up Completed:
plan_type= Premium → Sends a thank-you email with loyalty rewards.plan_type= Free → Sends an upgrade prompt.Others→ Sends a generic thank-you message.

Split Based on Conditions
Key Features
The following are the key features of the Conditional Split node:
-
Real-Time Evaluation: Distribution happens in real time when the previous node is a live trigger or delay node. This ensures users are routed instantly based on their latest property or behavior data. For example, a journey starts when a user launches the app. The Conditional Split node immediately checks the user’s most current
Subscription status:
Real-time Evaluation of Subscription Status
This ensures that if a user upgraded their subscription before launching the app, the journey reflects that in real time.
-
Dynamic Targeting Based on User Property: Users are routed based on real-time user profile attributes. For example, you are running a regional promotion. You can use the Conditional Split node to check the user property
location. This helps you personalize messages geographically without needing separate journeys or static segments.
Dynamic Targeting Based on User Location
-
Contextual Event Property-Based Routing: Trigger routing decisions based on live user actions, such as purchases, searches, or job applications, using event properties directly from the triggering event. This allows real-time branching of users into relevant paths the moment they perform an action, enabling instant, context-aware engagement. For example, a job portal app wants to tailor onboarding based on the type of job the user is looking for when they sign up. Now, with Conditional Split, the journey triggered by the Sign Up Completed event (Action node) can immediately route users based on the
preferred_job_typeevent property submitted during signup:
Event Property-Based Targeting
-
Combined Logic with Flexible AND/OR Operators: Combine user and event properties, making split logic highly granular. For example, you are running a luxury promotion and want to tailor offers based on both
Loyalty Tiertier andProduct Interest.
Combined Logic with Flexible AND/OR Operators
-
Sequential Splitting: Supports chaining up to three Conditional Split nodes within a journey. This allows you to evaluate multiple criteria step by step, creating layered, decision-based flows that adapt as more context becomes available. Each split adds more nuance based on what you know about the user, leading to hyper-relevant engagement without overwhelming a single decision point. For example, you are running a journey to promote tailored travel packages to users based on their travel intent and destination interest.
- Split 1: Check Travel Intent
- If Intent = Leisure, go to Split 2
- If Intent = Business, send corporate travel offers
- Others → Send a survey to understand user preferences
- Split 2: Travel Destination Interest
- If Interest = Beach, show tropical getaway packages
- If Interest = Mountains, highlight hiking and cabin stays
- Others → Recommend trending travel spots
- Split 1: Check Travel Intent
-
Fallback Path: Always includes an Others path to handle users who do not qualify for any of the paths. For example, if a Conditional Split is configured with conditions for
plan_type= Premium andplan_type= Free, any user with a different or missingplan_typevalue is routed to the Others path and can be sent a generic message or a prompt to complete their profile.
Resources
Updated about 4 hours ago
