"Condition" Element in Automation 360
Using the "Condition" element (block), you can build an automation flow based on the subscriber's actions.
You can track the following events: "Delivery," "Opens," "Clicks" in an email or message, and custom events.
Add an Element
Drag the "Condition" block right after the tracked block.
Select the Condition
You can select the following conditions:
| Delivery | Сhecks whether an email, message, or notification was delivered to the user. |
| Opens | Сhecks whether an email was opened by the user. |
| Clicks | Сhecks whether there were clicks on links in an email or notification, or clicks on a specific link. |
| Event | Сhecks whether the event selected in the element has occurred. |
The "Opens" and "Clicks" conditions work only for the "Email" and "Push" elements. The "Delivered" condition works for "Email," "SMS," "Viber," and "Push" elements.
Specify the Event Waiting Interval
Select the waiting interval — the period during which the system will wait for the condition to be met.
The countdown occurs when the contact reaches the "Condition" block. The condition will be checked exactly in 1 minute, 1 hour or 24 hours (1 day), and so on.
Branch Scenario
Below the "Condition" element, you can branch the flow and add elements to the branches, depending on whether the condition was fulfilled:
| The "Yes" branch | The condition was fulfilled within the set timeout interval |
| The "No" branch | The condition was not fulfilled within the set timeout interval |
Examples
For example, you want to track the delivery of an email to a user within 24 hours and send them the next email or receive a failed delivery notification.
Below the “Email” element, specify a one-day wait for the “Delivered” condition. Bind the next email in the flow to the “Yes” option, and the “No” option — to the “Send email to your address” action.
If the first email is not delivered to the recipient's email address within one day, you will receive an email notifying you about it.
If an email is delivered to the recipient's email address within one day, the next email in the flow will be sent to the user immediately after the first one is delivered or according to the time interval specified in the "Email" element.
Another example: You need to track whether users bought an item after you send them an abandoned cart email. Create a flow using the "Abandoned Cart" event, add the "Email" element to motivate them to complete the purchase, and then add the "Condition" element with the "Purchase" event.
You can add the "Email" element to the "Yes" branch to thank your customer in an email or ask them to leave a review when the "Purchase" event occurs.
If the event did not occur, you can send another email.
View Block Statistics
To view information about an element, exit the editor, and hover over the required element in the "Flow" tab.
Your element can have the following statuses:
| Expects | Contacts are waiting for the element execution time you set in the "Complete Action" settings, or contacts are waiting to be processed. |
| Done | Contacts that went through the condition match check by events. |
| Yes | Contacts for which the condition was executed during the set event waiting time, and contacts went through the "Yes" branch. |
| No | Contacts for which the condition was not executed during the set event waiting time, and contacts went through the "Yes" branch. |
To view detailed information, click an element. A panel with your element settings and statistics will open. At the top, you can see how many times the element was executed.
Below, you can filter, download, and view contacts who passed the element and its date. You can also view which branch they went to: "Yes" (the contact fulfilled the specified condition) or "No" (the contact did not fulfill the condition, and the timeout expired).
Last Updated: 27.06.2023
or