To get even more targeted with your automation flows, you can limit the audience that receives your message. 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. Segment filters get applied alongside the trigger and let the right contacts into your workflow only.

Contents

Set-up process
Profile-based Audience filter
Segment-based Automation

Before you start

Important note: Audience filters only works for the current base of contacts that are in the segment. To trigger the automation for a specific audience segment, including the incoming new contacts, use segment entry and exit based automation instead.

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 the Profile data, Tags and Segments.

Profile-based Audience filter

You may use such information as your customers' address, country, gender, and even birth date. Therefore, you may use this data to trigger more targeted automation workflows for your customers.

With the Audience filter set to country is United States or United Kingdom, only customers from either one of these countries will trigger the flow.

Important note: 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:

  • Make sure that specific segment is added as a filter "Segment IS NOT" in your regular order confirmation flow.
  • Create multiple flows with segments to cover all different languages and just disable the regular workflow.
  • Use Conditional Split instead of the Audience filter.


Segment-based Automation

Building a Segment adds a little overhead to the system, therefore delaying the condition check. For example, when the customer places the order in your store, we process this event in the following way:

  1. the event is passed to the system;
  2. automation is triggered;
  3. customer is added to the segment.

Let's consider the example that we need to send the automation to the customer that places his first order.

Step 1. Set-up a Segment of the customers that 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 any of your Segments. Therefore, he will qualify with the rule Segment is not Placed at least one order, and the customer will be entering the sequence.

Have any questions? Reach out to our Support Team any time.

Did this answer your question?