Combining Segments

Segment inclusion simplifies the way you create segments in CrossEngage by allowing you to reuse existing conditions and build on top of them. You can include segments with broader characteristics as a default audience and use it as a baseline. You can then drill down on this default audience by adding further characteristics that are important for user targeting.

If used properly, combining multiple segments can help create complex User Segments that are still easy to comprehend and use.

Segment Overlap

By combining multiple existing segments, you can reach users that belong to all of the added segments.

Example Use Case: Optimization of RFM segment building (add link)

Targeted Exclusion of Users

By adding a Segment and some Conditions, you can exclude Users who have not performed a certain activity or who do not possess certain characteristics.

Depending on available data, you can implement this in several different ways:

  • True/False fields: Data fields of boolean type allow you to select whether the entered value applies to a user (“true”) or not (“false”). Choose “false” if you want specific user information to be excluded. Example: traits.activeCustomer equals false

  • Status fields: Your customers and their orders may be assigned to certain statuses. Providing “active” and “inactive” options is one of the most common examples. Should you, for example, want to target inactive customers, select the “inactive” status in the segment condition. Example: traits.status equals inactive

  • Exclusion of available options: Find out what available values you can use and define those you are not looking for by selecting the “unequals” operator in the segment condition. For example, if you’d like to reach all customers that live outside of Berlin, build a segment where the value for a user’s city does not equal “Berlin”. Example: unequals Berlin

  • Event history: Should you want to target users who have not reacted to a message or visited your website in a while, set the number of occurrences for this event to “0” and choose a specific timeframe if needed. Example: Completed Order equals 0

Last updated