The Filter element in Automation 360
Use the filter to segment your audience by their preferences, client status, and other personal data. It can help you interact with your clients better: send targeted messages, send webhooks to your system, assign or update variables and tags, create deals in CRM, and more.
Let’s talk about how you can add the Filter element and track user data using values in their variables in our A360 flow builder.
Unsubscribed contacts can go through all flow elements except the Email element. When the system verifies email addresses, it processes the following types of unsubscriptions: Unsubscribe from the entire service, Unsubscribe from a category, and Unsubscribe from a specific flow.
If you use the Launch for mailing list option, contacts who unsubscribed from all campaigns will not be added to your flow start, and contacts who unsubscribed from this category or this flow will go further down your flow, skipping the Email elements.
Add the element
Drag and drop the Filter element from the left panel to your workspace. Link it with an element after which you need to branch your flow scenario based on variable values.
You can also change your element name to differentiate between elements. Click the Element name option, and enter your new name in the field.
Specify your sending time
Specify when you want to execute the element. You can select the Right away option to send the message immediately or choose the After option to delay the sendout.
Read more: Element execution time.
Set up filter conditions
Adding conditions
You can add up to 5 filter conditions and link them with operators. By default, you will go to set up your first filter.
Specify a variable
With variables, you can pass and store information about your client, including their name, contact info, order details, registration, and other events. Depending on your scenario, you can personalize your communication with each client, sending them specific scenario branches.
Select a contact variable where you need to check values.
In the Flow start element, you can select a triggers that will start your flow. If you have selected:
- the Add subscriber, Special date, Contact webhook, or Change variable triggers, then the variables will be filled in from the specified mailing list;
- the Create a deal or Change deal stage triggers, then the variables will be filled in from the fields in the selected CRM pipeline;
- the Start the flow by event trigger, then the variables will be filled in from the event body or from the body of both the event and the mailing list if the mailing list is selected (if there is a contact in that mailing list).
Select a condition
You can select the variable value existence condition to check if a variable has any value or select a condition with a value to check if values match in the third field.
Possible filter conditions vary depending on the variable type:
| Type | Condition | Value |
| Number | > | Checks if the variable number is more than the entered value.
The specified value is not included in the range of the condition sample. |
| < | Checks if the variable number is less than the entered value.
The specified value is not included in the range of the condition sample. |
|
| = | Checks if the variable number is equal to the entered value. | |
| ≠ | Checks if the variable number is not equal to the entered value. | |
| between | Checks if the variable number is included in the selected range. | |
| String | contains | Check if the variable contains the entered value. Used for partial matches. |
| not contains | Check if the variable does not contain the entered value. Used for partial matches. | |
| equal | Check if the variable equals the exact entered value. Used for total matches. | |
| not equal | Check if the variable does not equal the exact entered value. Used for total matches. | |
| starts with | Check if the variable contains the entered value at the beginning of the variable. | |
| ends with | Check if the variable contains the entered value at the end of the variable. | |
| Date | is after | Check if the date is after the entered value. |
| to | Check if the date is before the entered value. | |
| equal | Check if the date matches the entered value. | |
| between | Checks if the date in a variable is included in the selected range. |
If you choose the date filter condition, you can limit your future events when a user action occurs before or after the date you select. To do this, click a date, and select one from the calendar.
You can also set a specific expression. To do so, add a variable of the Date type, and click {}. Select a dynamic date value (day, hour, or minute), and enter its amount — these data points will be checked for consistency. You can also use negative values.
For example, you can send reminders 3 hours before your event to those who registered a long time ago. Select the registration day variable, set your conditions to is after, and specify 3 hours. Afterward, your email will be sent only to those who registered earlier than 3 hours before the start.
Enter a value
Once you select a condition, specify a value using which you want to check clients' data in a variable.
Please note that if you try to filter a variable without a value or if its value is blank, the filter will not work in the Yes and No branches, as filtered variables must have a value. To check for a variable or value, select the corresponding condition.
Adding additional conditions
To add another condition, click Add condition, and set up your filter by analogy.
Select an operator to link your conditions.
Any
This operator is used to add alternative conditions — the filter will check the execution of any condition.
Let’s say that you have a home delivery service only in specific cities. You can check if your delivery address matches the required city and send a chatbot flow to specify client data and close the deal. If it does not match, create a card in CRM so that your manager can contact the client to find their nearest post office.
All
This operator is used to add dependency conditions — the filter will check if each condition is executed.
Let’s say that you have a special offer: if a client makes an order on certain days, they will have it delivered for free or get a discount. You can add additional conditions with a purchase event date.
Once you set up the element, click Apply.
Branch your scenario
Below the Filter element, you can branch your flow and add elements to your branches based on whether the condition was fulfilled:
| The Yes branch | The condition was executed during the moment of element execution |
| The No branch | The condition was not executed during the moment of element execution |
View element 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 filter condition match check |
| Yes | Contacts that match the filter conditions and went through the Yes branch |
| No | Contacts that do not match the filter conditions and went through the No branch |
To view detailed information about contacts, click an element. A panel with your element settings and statistics will open. Below, you can filter, download, and view contacts who passed the filter and its date.
You can also click an element ID and start editing the element.
Last Updated: 05.08.2024
or