> For the complete documentation index, see [llms.txt](https://support.growlytics.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.growlytics.in/journeys-and-automation/journey-builder/journey-condition-steps.md). # Journey Condition Steps Journey Conditions enable you to target a particular section of your customer base depending on the end goal of your campaign. There are three condition blocks to choose from. 1. **Past Behavior:** Determine which customer will proceed with the next steps of the journey based on their past behavior, that is, user attributes, events performed, and events not performed. 2. **Is in Segment:** Applying this condition will ensure that customers belonging to a specific segment will proceed with the next steps in the journey. 3. **Is Reachable:** This condition block will help identify which platforms, such as email, Mobile Push, Web Push, SMS, WhatsApp, or in-app, your customers are available on and send communications accordingly.

Watch this quick tutorial to see how to apply a condition block in between a journey. {% embed url="" %} Apply a Condition between Journey Steps {% endembed %} Let's take a closer look at the various setting available in each condition block. ### Past Behavior Add a **‘Past Behavior’** block, link it to the 'Custome Entry Event' block, and ‘Click to edit’. With this option, you can filter out customers based on their past behavior and accordingly get them to proceed with the journey. There are three behavior filters. 1. User Attribute 2. Performed Event 3. Not Performed Event

Here is how you can use these three filters optimally, with the help of an example. You have a site-wide sale where all your products are available at 50% off and you want to send the first notification to your returning customers who have made two or more purchases. To do this, * Click on ‘User Attribute’, * Select property as ‘Total Orders’, * Set the condition as ‘Greater than or equal to’, * Enter ‘2’ as the value.

Next, we will add one more filter to send this announcement specifically to those customers who have looked at products worth ₹ 3,000 and more, at least 5 times, in the last thirty days. To do this, * Click on ‘Performed Event’, * Select event performed as ‘Product Viewed’ * Set the condition as ‘Greater than or equal to’, * Enter ‘5’ as the value, * Set the time period to ‘last 30 days’, * Click on ‘Add product viewed condition’ * Select the property as ‘Price’, * Set the condition as ‘Greater than or equal to’, * Enter ‘3000’ as the value.

Further, we would like to filter out those customers who have viewed the product but did not purchase it in the last 30 days. To do this, * Click on ‘Not Performed Event’, * Select event not performed as ‘Purchased’, * Set the time period to ‘last 30 days’, * Click on ‘Add Purchased Condition’, * Select the property as ‘Amount’, * Set the condition as ‘Greater than or equal to’, * Enter ‘3000’ as the value.

Now that all the required filters have been applied, give a Behavior Description ‘Product Viewed, Not Purchased’. This description will be visible on the ‘Past Behavior’ condition Block in the Journey Steps. Click on ‘Save Changes’ and proceed further. If the ‘Past Behavior’ Condition is not met, send out an email to the customers notifying them about the ‘Sale’. Add an ‘Email’ engagement block and link it to the ‘Past Behavior’ condition block by clicking on ‘No’.

### Is in Segment If the ‘Past Behavior’ Condition is met, we will add another condition, that is, **‘Is in Segment’**. Link this block by clicking on ‘Yes’. Click to edit. Select the segment from the dropdown, for this example, we will choose ‘Not purchase last three month’. Click on ‘Save Changes’ and proceed further. If the ‘Is in Segment’ condition is not met we will send out an SMS to the customer notifying them about the Sale. Add an SMS engagement block and link it to the ‘Is in Segment’ condition block by clicking on ‘No’.

### Is Reachable If the ‘Is in Segment’ condition is met, we will add the last and final condition, which is, **‘Is Reachable’**. Link this block by clicking on ‘Yes’. Click to edit. To check where the user is available, click on the drop-down and click on email for this particular scenario. Click on ‘Save Changes’ and proceed further. If the user is not reachable by email we will send a WhatsApp message to the customer notifying them about the Sale. Add a WhatsApp engagement block and link it to the ‘Is Reachable’ condition block by clicking on ‘No’. If the user is reachable by email we will send an email to the customer notifying them about the ‘Sale’. Add an Email engagement block and link it to the ‘Is Reachable’ condition block by clicking on ‘Yes’.

Applying Conditions between Juorney Steps

There you have it, you have successfully applied conditions in between your journey steps. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.growlytics.in/journeys-and-automation/journey-builder/journey-condition-steps.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.