You can limit the audience that receives your message to get even more targeted with your automation flows. For example, if a welcome flow triggers for someone who recently signed up via one of the Omnisend forms and added their preferred language, an audience filter could be added to send the email in that specific language only. Audience Filters get applied alongside the trigger and let the right contacts into your workflow only.
Contents
Before you start
Audience filters can be used for any automation workflow you are setting up.
The feature is available on all the Omnisend plans. Find more information on Omnisend pricing.
⚠️Segment-based Audience filter adds a little overhead to the system. Jump to this section for more information.
Set-up process
The audience filter is one of the options available alongside the trigger rules. Up to 5 filters can be added to a single workflow. The rules in the Audience filter can be based on Profile data, Tags, and Segments.
Profile-based Audience filter
In the menu with your customers' profile data, you can find various options, including your customers' addresses, gender, birthdate, etc. All these options can help you target the email to a specific group of your customers and tailor your communication accordingly.
For example, if your Audience filter is set to Country is the United States or the United Kingdom, only customers from either one of these countries will enter the workflow.
💡 If you create a workflow (i.e., order confirmation) for a specific segment (i.e. , English language) and have the same regular order confirmation workflow for all of your contacts, you will need to ensure you don't send duplicate order confirmation emails to your contacts. This can be done in three ways:
Add a specific segment as a filter, "Segment IS NOT," in your regular order confirmation flow.
Create multiple flows with segments covering different languages and disable the regular workflow.
Use the Conditional Split instead of the Audience filter.
Segment-based Automation
Building a Segment reduces the system's overhead, delaying the condition check. For example, when the customer places an order in your store, we process this event in the following way:
the event is passed to the system;
automation is triggered;
customer is added to the segment.
Let's imagine we need to send the automation to the customer placing his first order.
The most obvious solution is to set the Audience filter to Customer placed 1st order. But, without adding a delay to the sequence and letting the Segment process this information, the trigger won't work. We also can't use the Customer enters a segment trigger since this event doesn't carry the information about the order. Find more details about the event-based triggers.
Therefore, the most straightforward solution is to add a slight delay (1-2 min) to the flow and set this specification in the Segment-based split. However, there is another solution to this problem that eliminates the need for a delay block:
Step 1. Set up a Segment of the customers that have placed at least one order already
Step 2. Use this Segment in the Automation trigger settings
The customer placing his first order won't be added to your Segments. Therefore, he will qualify with the rule Segment is not Placed at least one order and trigger this automation. Still, you must set up another Automation with the Audience filter set to Segment is Placed in at least one order to send messages to repetitive customers.
Have any questions? Reach out to our Support Team at any time.
