Journey Conditions
Learn to use Conditions to create personalized journeys on the Netcore CE dashboard.
Conditions help you create personalized journeys by analyzing user attributes, actions, or behavior. Use conditions like Check attribute, Has done event, or others to segment users and ensure targeted communication. Refer to this document to learn how to create a journey.
The six type of conditions are:
- Check Attribute
- Has Done Event
- Reachable Channel
- Split Action
- Is In Segment
- Is In List
- Path Optimizer
Check Attribute
The Check attribute condition enables targeted communication and allows you to filter as per user details. Send your preferred communication based on whether these attributes meet the conditions you set. Using this condition ensures it reaches the right audience. For example, if you want to send an email to users with an email address in your contact master:
- Select the attribute: Email
- Select the operator: Exists
This configuration ensures that only users with email addresses receive the communication.
Follow the given steps to use this condition.
- Drag & drop the Check attribute condition on the Journey canvas.
- Click Check attribute to set the conditions. The Check attributes screen appears. Specify the attribute, operator, and value for each parameter. Refer to the given table to learn about the configuration options.
| Option | Description |
|---|---|
| Attributes | Select an attribute from the dropdown |
| Operator | You can use the following operators to set conditions:
|
| Value | Add a value that matches the selected attribute. For example, provide an email address for the Email attribute or a phone number for the Phone Number attribute. |
Click on + Add Parameters to add multiple attributes. Once done, click SAVE.
Important Points
- Select ALL if all attributes must be satisfied.
- Select ANY if only one attributes needs to be true.
- Attribute checks do not apply to anonymous users.
Has Done Event
The Has done event condition checks if a user has performed a specific event within a specific time range. Use this condition to segment users based on their actions, such as opened, clicked, and so on.
Follow the given steps to use this condition.
- Drag & drop the Has done event condition on the Journey canvas.
- Click Has done event to set the conditions. Conditions - Has done an event screen appears. Refer to the given table to know the options available here.
| Activity type | Description | Activity status |
|---|---|---|
| App/ web activity | Checks if a user performed specific actions on your app or website. Select the duration for which you want to view the activity. The options include: Past number of mins, Past number of hours, Past number of days, Custom Range, Last 180 days. | Select custom or system events from the dropdown. |
| Email activity | Checks if a user interacted with an email, such as opened or clicked it. | Open, Click, Hard Bounce |
| WhatsApp activity | Checks if a user engaged with a WhatsApp message, like viewing or responding. | Open/Read, Deliver, Click, Fail |
| RCS activity | Checks if a user interacted with an RCS message, such as reading or clicking links. | Open/Read, Deliver, Click, Fail |
| Viber activity | Checks if a user engaged with a Viber message, like viewing or clicking. | Open/Read, Deliver, Click, Fail |
| Zalo activity | Checks if the Zalo message was delivered or failed to the user. | Deliver, Fail |
| SMS activity | Checks if a user received or engaged with an SMS message. | Deliver, NDNC Drop, Others, Click on link |
| App push notification activity | Checks if a user interacted with an app push notification, like clicking. | Deliver, Click, Fail |
| Web push notification activity | Checks if a user engaged with a web push notification, like clicking. | Deliver, Click, Fail |
| Web message activity | Checks if a user engaged with a web message like viewing or clicking. | View, Close, Click |
Once done, click SAVE.
Reachable Channel
Set the priority to target reachable contacts. Drag and arrange the channels in your preferred order of priority. For example, if you set Email as the top priority, the system will first send communication via email. If the email fails, it will automatically try the next channel in your list, and so on.
Follow the given steps to use this condition.
- Drag & drop the Reachable channel condition on the Journey canvas.
- Condition- Reachable Channel screen appears. Set the priority of the channels and click SAVE.
Split Action
The Split action condition helps you to analyze which combination of variants works the best for your journey. Use at least one/two scenarios at a time. There are maximum of five variants available in split action to test the journey flow.
Follow the given steps to use this condition.
- Drag & drop the Split action condition on the Journey canvas.
- Map at least two variants to two different channels/ nodes.
- Click on Split action to set the percentage. Distribute this journey in variants to measure a journey report and analyze the performance screen appears.
- Set percentage for variants using the slider or manually add the value. Ensure that the sum off all the variants is 100 and click SAVE.
Variant Distribution Logic
- List & Segment: Users are distributed based on the selected percentage for each variant.
- Triggers: Users are distributed randomly when they first enter the journey.
If the journey is in repeat mode, users remain in the same variant for subsequent entries. For example, on day 1, User X enters variant A, and User Y enters variant B. On day 2 or later, both will stay in their original variants.- Editing Distribution: You can modify the variant percentages after deployment. Previously entered users may move to a different variant and receive different communications. Total distribution must always equal 100%.
Is In Segment
The Is in segment condition helps you check if a user belongs to a specific segment you wish to send your preferred communication.
Follow the given steps to use this condition.
- Drag & drop the Is in segment condition on the Journey canvas.
- Click Is in segment to set the conditions. Conditions - Is in segment screen appears.
- Select up to five segments from the dropdown and click SAVE.
Is In List
The Is in list condition helps you check if a user belongs to a specific segment you wish to send your preferred communication.
Follow the given steps to use this condition.
- Drag & drop the Is in list condition on the Journey canvas.
- Click Is in list to set the conditions. Conditions - Is in list screen appears.
- Select up to five segments from the drop-down and click SAVE.
Path Optimizer
The Path Optimizer condition allows you to automatically direct 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, they are initially distributed evenly across all defined branches. As real-time performance data (based on the selected success metric) begins to accumulate, the system automatically adjusts routing to favor the branches that are performing better.
Path Optimizer node is in beta phase & a configurable feature at present. Reach out to Netcore Support team to enable it for your panel.

Journey Path Optimizer
Note
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.
Follow the given steps to use this condition.
- Drag & Drop the Path optimizer conditions panel on the Journey canvas.
- Click the Path Optimizer node to open the configuration modal.
- Complete the following fields:
| Option | Description |
|---|---|
| Number of branches | Select the number of branches (minimum 2, maximum 5). Each branch will be named as Variant 1, Variant 2, and so on. |
| Success metric | Choose a KPI for optimization: • Clicks: Optimization based on user clicks across channel nodes. Each variant branch must include at least one channel node (Email, SMS, WhatsApp, APN, WPN, RCS, Viber, Zalo). Clicks ÷ Delivered counts are tracked across branches. • Conversions: Optimization based on conversion events across channel nodes. Same as Clicks + A journey goal must be configured. Conversion events ÷ Delivered counts are used as the optimization metric. When Conversions is selected as the success metric, the journey evaluates performance based on the configured Journey Goal event. |
Important Points to Remember:
- 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.
Reporting(Analytics on Path Optimizer Node)
Once your journey is published, the Path Optimizer node will display the following metrics in the node-wise view (on hover or in expanded analytics):
| Metric | Description |
|---|---|
| Distribution | Shows the of users routed to each variant. Helps you understand traffic distribution over time. |
| Clicks/Conversions | Displays success performance for each branch based on the selected success metric (e.g., Clicks or Conversions). |
| Winning Variant Indicator | Highlights the branch currently performing best based on real-time data. Typically shown with an icon (e.g., star or crown). |
| Variant Names | Displayed as Variant 1, Variant 2, etc., as defined during setup. |
Note
- These metrics update in near real time based on ongoing user interactions.
- The displayed success metric (Clicks or Conversions) corresponds to the one selected in configuration.
If you change the metric mid-journey, the analytics update accordingly, but only new user entries are considered under the new metric.
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:
| Industry | Use Case | Variants Tested | Optimizer Action |
|---|---|---|---|
| E-Commerce | Product Recommendation - Identify the right channel | Email carousel with trending products vs. APN with best-selling item | Routes based on clicks |
| Discount Strategy Testing - Experiment with content | Offer 10% off vs free shipping | Favors higher checkout conversions | |
| Cart Abandonment Recovery - Experiment with delay time | WhatsApp sent 2 hrs after abandonment vs. WhatsApp sent after 12 hrs | Adapts to variant with higher cart recovery | |
| BFSI | Loan Offer Journeys - Identify the right channel | Email with EMI calculator vs. APN with “Apply Now” deep link | Routes based on loan application clicks |
| Insurance Renewal Nudges - Identify right channel mix | WhatsApp followed by SMS vs. App push followed by SMS | Favors renewal conversion variant | |
| Credit Card Upsell - Experiment with content | Email with carousel of benefits vs. RCS card with CTA | Routes based on applications submitted | |
| Travel & Hospitality | Holiday Package Promotions - Identify the optimized user action | Email with destination carousel after package view event vs after package action button click | Routes to higher click-through rate |
| Booking Abandonment Recovery - Experiment urgency with different channel mix | WhatsApp with urgency message vs. App Push with countdown timer | Adapts based on completed bookings | |
| Loyalty Program Engagement - Identify the right channel that converts | Email with redemption options vs. SMS with redemption link | Favors higher redemption conversions | |
| Telecom | Recharge Reminders - Identify the right channel mix that converts | Recharge reminder offer sent as App push + follow up Whatsapp after 1 day vs send all messages at once. | Routes to higher recharge conversions |
| Upselling Data Packs - Experiment with rich media channel content | APN with data pack carousel vs. RCS card with weekend data offer | Uses click performance to decide | |
| EdTech | Course Enrollment - Identify right channel that gives higher engagement | Email with course carousel vs. APN with “Start Learning Now” CTA | Routes to higher sign-up variant |
| Free-to-Paid Conversion - Identify right channel that drives urgency | WhatsApp: “7 days left in trial” vs. App Push with countdown | Prioritizes higher paid conversions |
Updated 8 days ago
