Labels are one of the primary elements allowing you to later define groups of subscribers by segments or send campaigns to specific labels.
Labels are easy to understand, implement (no-code), and manage.
Simply put, a label is a characteristic you can ascribe to a subscriber in your base.
A label consists of:
- Key - the system labels have a “sys.” prefix in their key names. You can name your keys in the user labels however you want (ex. last_visit or cart_value) and use stop marks in the name
- Value - in the form of date, number, words, or true-false value
- Time-to-live (TTL) - a time after which the label will expire on a given subscriber
System labels contain information about a subscriber’s platform, language, region, and operating system. They are useful in defining Segments.
A label can be saved to a subscriber in one of the following ways:
- append - simply put, it’s a set of values. For example a category label with the category-related values [blouses, jackets, scarves]. When appending, we can add a “beanie” value to the set.
- rewrite - a relation of key and a single value. It means that we can change the value of a last_category label from last_category: beanies to last_category: blouses.
The labels are not predefined: you can ascribe them to a subscriber according to your needs.
You don't have to configure them beforehand.
Well-defined labels in automation processes or selectors help you to define more accurate segments.
Last modified 11mo ago