--- title: "Transactional Journeys: Check Conditions" slug: "transactional-journeys-check-conditions" description: "Check Conditions in Insider One Transactional Journeys splits users into up to 10 condition paths and a Not Matching path by their profile and events." updated: 2026-11-16T09:35:23Z published: 2026-11-16T09:35:23Z canonical: "academy.insiderone.com/transactional-journeys-check-conditions" --- > ## Documentation Index > Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt > Use this file to discover all available pages before exploring further. # Transactional Journeys: Check Conditions > **Suggested readings**: [Transactional Journeys](/docs/transactional-journeys), [Transactional Journeys: Canvas and Navigation](/docs/transactional-journeys-canvas-and-navigation), [Transactional Journeys: Check Interaction](/docs/transactional-journeys-check-interaction), and [Architect Check Conditions](/docs/architect-check-conditions). Check Conditions splits the users of a transactional journey into paths based on the conditions you set. Each path has its own conditions. Users take the first path whose conditions they meet, and users who meet none of them take the **Not Matching** path. This way, each group of users gets the follow-up that fits them. Consider a travel company that sends a booking confirmation through an API call. Users in a loyalty tier should get a different follow-up than everyone else. Bookings above a certain amount should get an upgrade offer. To build this flow, add a Check Conditions element after the confirmation email. Give it one path for loyalty members and one path for bookings whose amount in the API request is above the limit. Users who match neither take the Not Matching path. One API call covers the whole flow. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/Screenshot at Nov 16 12-33-56.png) > [!NOTE] > The 30-second SLA of Transactional Journeys does not apply to journeys that use Check Conditions or any other check or wait element. This includes [Check Interaction](/docs/transactional-journeys-check-interaction), Wait for Some Time, and Wait Until a Time Slot. This guide explains the following concepts: - [Use cases](/docs/transactional-journeys-check-conditions#use-cases) - [How Check Conditions works](/docs/transactional-journeys-check-conditions#how-check-conditions-works) - [Paths](/docs/transactional-journeys-check-conditions#paths) - [Use Check Conditions](/docs/transactional-journeys-check-conditions#use-check-conditions) - [Check Conditions statistics](/docs/transactional-journeys-check-conditions#check-conditions-statistics) ## Use cases With Check Conditions in Transactional Journeys, you can: - Send a different follow-up to users in a segment or with a certain attribute, such as a loyalty tier or a preferred language. - Route users by the data in the API request, such as an order amount, a delivery method, or a booking type. - Skip a reminder for users who already completed an event, such as a payment. ## How Check Conditions works Check Conditions uses the same condition builder as Check Conditions on promotional journeys. For the condition types and operators, see [Architect Check Conditions](/docs/architect-check-conditions). On a transactional journey, you can also use **Constant Starter Property** to compare an event parameter with a value from the API request. The values you can pick are the fields of the Sample API Request in the On API Call starter. Each entry is checked against the data of its own API request, so two entries of the same user can take different paths. For details, see [Constant Starter Property Value](/docs/constant-starter-property-value). The paths are checked in the order they appear on the element. A user takes the first path whose conditions they meet. Users who meet none of the conditions take the **Not Matching** path. > [!NOTE] > If a condition refers to a field that is missing from a user's API request, that path is skipped for that user. If none of the paths can be checked, the user takes the Not Matching path. ## Paths - When you add Check Conditions, it comes with one condition path and the **Not Matching** path. You cannot delete the Not Matching path. - Click the **Split Path** button to add more condition paths, up to 10 condition paths in total. - Each path can continue with channel elements, wait elements, or another check element. - You can reconnect paths to another point of the journey. See [Reconnect Paths](/docs/reconnect-paths). ## Use Check Conditions To use the Check Conditions element in your transactional journey, follow these steps: 1. Click the **+ (Add)** button where you want to split users, hover over **Check**, and select **Check Conditions**. 2. Click the Check Conditions element to open its settings. 3. Set the conditions of the first path. To compare an event parameter with a value from the API request, select **Constant Starter Property** and pick the field from the Sample API Request. 4. Optionally, click the **Split Path** button to add another path and set its conditions. 5. Click the **Save** button. If a required field is empty, the message "Fill in all required fields to continue." is shown, and the element is not saved. 6. Return to the canvas and add the elements that each path should continue with. > [!NOTE] > Constant Starter Property needs an event in the [On API Call starter](/v1/docs/transactional-journeys-on-api-call-starter). If you change the starter event, the parameters that came from the old event are removed from the conditions. Select them again. > [!NOTE] > You cannot launch a journey while a condition uses a field that is not in the Sample API Request of the On API Call starter. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/Screenshot 2026-11-06 at 15.18.45.png) ## Check Conditions statistics On a launched journey, the Check Conditions element on the canvas shows the following statistics: - **Arrived:** Shows the users who reached the element. - **Each condition path:** Shows the users who took that path, one row for each path. - **Not Matching:** Shows the users who took the Not Matching path. - **Exited:** Shows the users who completed the journey at the element, because their path has no element after it. - **Dropped:** Shows the users who reached the element while the journey was paused. This row appears only when at least one such user exists. You can use [Track User](/v1/docs/track-user) to see which path a specific session took, also when paths are reconnected later in the journey. --- Check Conditions sends users down the first path whose conditions they meet, and everyone else down the Not Matching path. Add up to 10 condition paths, and reconnect them when they should meet again later in the journey. To split users by how they interacted with an earlier message instead, read [Transactional Journeys: Check Interaction](/docs/transactional-journeys-check-interaction). To see how the pieces fit together on the canvas, read [Transactional Journeys: Canvas and Navigation](/docs/transactional-journeys-canvas-and-navigation) and [Reconnect Paths](/docs/reconnect-paths).