Condition
A condition is a rule checked before a flow moves to its next step, such as a customer's consent, a cart value or an order count.
A condition is the yes-or-no question a flow asks. The trigger starts the flow, and the condition decides whether everyone who arrived should carry on. If the answer is yes, the flow continues. If it is no, the flow stops for that customer. Typical questions: does the customer have marketing consent, is the cart value high enough, is this their first order, have they bought a certain product?
Conditions keep the same event from producing the same result for everyone. Welcoming a customer on their first order and thanking a loyal customer on their fifth can start from the same trigger. The condition draws the line between them. A well-written condition takes the right message to the right person and cuts unnecessary sends at the source.
Why It Matters
- A condition keeps messages from going to customers without consent or with no link to the topic.
- It lets one trigger treat different customer types differently.
- By cutting needless messages, it lowers the chance that customers tire of the flow.
How It Works
- Choose what to checkPick a fact such as consent status, cart value, customer type or order count. It should relate directly to what the flow needs.
- Write the thresholdState the rule with a clear measure: a cart value of ₺1,000 or more, at least three orders placed.
- Plan both outcomesIf the condition passes, the flow continues. Think about what happens when it fails too: most often the flow simply stops for that customer.
- Check consent firstFor any flow that sends marketing messages, the first condition should be contact consent. Other rules come after it.
Example
At Liva Butik, two customers leave their carts on the same day. Elif Arslan leaves the ₺1,490 Linen shirt and has marketing consent. Mert K. leaves the ₺890 Straw bag and has none. The store owner added two conditions to the flow: the customer must have marketing consent, and the cart value must be ₺1,000 or more. Elif passes both and gets a reminder. Mert stops at the consent condition and nothing is sent. The trigger was the same for both of them, and the condition made the difference.
Not to Be Confused With
Being in a segment does not mean meeting every sending condition. A customer in the segment may lack consent or fall short of the amount the flow asks for. A segment describes an audience, while a condition is re-checked for each customer inside the flow.
In Creato
In Creato automations, conditions decide whether a customer who entered the flow carries on.
- Condition examples: VIP customer, new customer and cart value.
- With the New Order trigger you can pick first order, Nth order and at least N orders. This trigger is available on ikas, Shopify and T-Soft.
- In WhatsApp Marketing the conditions are: customers with marketing consent, a given segment and buyers of a given product.
Frequently Asked Questions
What is the difference between a condition and a trigger?
A trigger starts the flow and a condition decides for whom the started flow continues. The order is always the same: the trigger runs first and the condition checks right after it. If the condition does not hold, the flow ends there for that customer and the later steps do not run. A condition on its own starts nothing without a trigger.
Is a condition the same as a segment?
No. A segment is a group of customers who share something, prepared in advance. A condition is a check made inside the flow for the customer currently running through it. A condition can use a segment, for example by asking whether the customer is in a given segment, but they are not the same idea.
Can a flow have more than one condition?
Logically yes, and most flows want that: is there consent, is the amount enough, is it a first order. Every condition shrinks the number of people who get through, though. Rules that are too tight leave the flow almost idle, so make sure each condition has a real purpose.