Some time ago, Omnisend set the goal to replace static lists with dynamic Segments. Although Lists seem to be more straightforward in use, they put you within a boundary of initial selections and don't allow you to account for the changes happening with your audience.
Segments, on the other hand, are dynamic; they change over time and provide more visibility to your audience as a whole. However, you may still wonder what you should do in case you need a static Segment that doesn't change over time. Well, that's going to be the main topic of this article.
List = Segment based on the tag
Static Segment concept
While creating different lists from your contacts, you are probably looking for some similarities or shared properties. It doesn't matter how many contacts you want to add to the Segment; one or many, you should have a reason for adding them. To do this in Omnisend, you only need all you need to state your reason.
There might be a few ways to achieve that:
assign different custom properties;
In other words, we get a Segment with the rule: contact has a tag OR contact property has the following value.
In both cases, you have full power over your audience. You should be aware of all areas where your contacts can be assigned a tag or a custom property. When it comes to contacts' management, tags are more convenient to use; therefore, we are going to focus on them.
Tags as unique identifiers
There are multiple ways for you to add a tag to the customer profile. Including:
adding tags one by one;
bulk tagging for the contacts Segment;
automatic tagging with Forms and Automations.
Find more information on each of these methods in the dedicated article.
What is essential is that a contact will be added to the Segment as long as it has a tag. When you choose to remove the tag, the contact is removed from the Segment. It works the same way as with Lists, although instead of removing the contact directly, you remove a tag.
If you still have some questions, feel free to reach out to our Support Team at [email protected].