Learn how to use BayEngage’s User filter
The very purpose of using filters in automation workflows is to ensure that only qualified people receive their respective emails/SMS. BayEngage’s Activity and User filter lets you do just that.
Activity filter helps you control the very action that triggers the flow and is evaluated alongside the trigger itself so that only qualified people enter the flow. On the other hand, user filters can target a particular customer behavior/outcome after they enter the flow and before every action (Email/SMS) in the flow is sent.
Let us understand how activity and user filter work with an Abandoned cart flow example -
On a given day, say 100 people visit your website, of them, say 50 people start their checkout. But finally, only 20 people placed their orders.
In the above example, all 50 people who started their checkout would enter the Abandoned Cart Flow. Here the action/activity that pushed the 50 people into the flow is them starting their checkout.
Given that 20 of these 50 have placed their order, you wouldn’t want them to receive an Abandoned Cart email/SMS. This is exactly where the User Filter comes into place. With the user filter, you can control who should receive the email/SMS and who should not. In this case, people who have not placed an order after they enter the flow are the ones who are supposed to receive the emails.
Further, let’s say 10 of the 30 people who didn’t place an order initially now place an order after receiving the first email in the flow (ex-discount email).
The user filter condition is checked every time an email/sms is sent to ensure that the user is qualified to continue the flow. The 10 people who have placed an order will no longer receive any emails/SMS as they do not satisfy the User Filter condition of not placing an order after entering the flow. Thus only the rest of the 20 customers who have not placed an order will continue to receive the subsequent emails/SMS set by you.
Diagrammatic illustration of how activity and user filters work on BayEngage
Let’s take another example of Recovering a Cancelled Subscription. Here all the users who cancel their subscription will enter the flow, i.e., the action that triggers the recover canceled subscription flow is the user’s canceling their subscriptions. Now you want to send a winback email and nudge them to re-subscribe. Therefore the User Filter condition of this flow will be not re-subscribed after entering this flow.
Following the first email (discount email), 20% of the users re-subscribe. This 20% of users do not satisfy the User Filter condition and hence will exit the flow while the rest 80% of users will continue the subsequent emails till they resubscribe or till the flow ends.
Note: Activity conditions on BayEngage are inbuilt, making it easier. You can access 14+ pre-built automation recipes with activity filters set for your business or create workflows according to your needs.
FAQs
1. Can I use more than 1 user filter in the same flow?
Absolutely YES, you can use the AND and OR Operators to include any number of user filter conditions for a given flow.
2. What are the user filters conditions available on BayEngage?
BayEngage offers nearly 15+ trigger conditions that can be used to send targeted emails to the right audience. These filter conditions include email activity, subscription status, order status, and order value, demography, etc.
3. Can I alter the user filter condition in the middle of the flow?
Yes, you can change the filter condition, but the condition shall not be validated for those who have already received their emails. The new filter condition shall hold true for those newly entering the flow.
4. How can I setup a filter condition only for one step of the flow?
You can use BayEngage’s User Split to achieve this objective. User splits can be used to subdivide your target audience further, and this filter condition will be checked only for that flow step.
5. Does BayEngage have pre-built automation recipes?
BayEngage offers nearly 15 pre-built automation recipes that fit all your automation needs.