You might want to run different Omnisend automations that each target a different population coming from popup campaigns. For example, one automation per language, or one automation per audience segment. This guide explains why Omnisend requires an extra setup step compared to other ESPs, and walks through exactly how to configure it.
The Core
In other ESPs, a custom property that Alia passes onto a contact's profile can be referenced directly inside an automation's trigger or filter conditions. Omnisend does not support this.
In Omnisend, automation trigger filters and audience filters cannot reference a custom profile property directly. The only way to filter an automation's audience is by referencing a Segment.
This means that if you need multiple Omnisend automations filtered by different Alia-driven populations, the custom property has to be turned into a Segment first, and the automation then filters on that Segment — not on the property itself.
Step-by-Step Setup Process
Step 1: Confirm what populations need to be separated
Before making changes in Omnisend, confirm which populations each automation needs to target — e.g., language, a specific popup/campaign, a quiz result, etc. Each population will need its own segment.
Step 2: Make sure Alia is passing the custom property to the contact profile
Confirm the relevant custom property (e.g., Language or a campaign/tag identifier) is being passed from Alia to the contact's profile fields in Omnisend when they subscribe. This is usually a standard profile property (such as Language) and/or a Tag applied by the Alia integration (such as "alia") — these are what the segment conditions will be built on.
Step 3: Create one Segment per population in Omnisend
Go to Audience → Segments → Create segment. Build the segment using "All contacts whose" conditions that reference the property/tag passed from Alia. Typically, this is a combination such as:
Language is [value], and Tag is [alia tag]. Name the segment clearly so its purpose is obvious later (e.g. ALIA_nl, ALIA_de) and save/activate it.
Step 4: Add the Segment as the audience filter on the automation
Open the relevant automation, go to its Audience filters, and add a filter for "Segment is [segment name]" instead of trying to filter on the custom property directly. This is what actually restricts the automation to the intended population.
Step 5: Repeat for each population, then test
Repeat Steps 3–4 for every population/automation pair you need (one segment + one audience filter per automation). Test by adding a sample contact matching each segment's conditions and confirming they enter only the correct automation, then monitor the automation's Entered/Completed stats to confirm volumes look right.