Multi-entity segmentation is an advanced feature available as part of Adobe Experience Platform Segmentation Service. This feature enables you to extend Real-time Customer Profile data with additional “non-people” data (also known as “dimension entities”) that your organization may define, such as data related to products or stores. Multi-entity segmentation provides flexibility when defining audience segments based on data relevant to your unique business needs and can be performed without having expertise in querying databases. With multi-entity segmentation, you can add key data to your segments without having to make costly changes to data streams or wait for a back-end data merge.
Multi-entity segmentation requires a working understanding of the various Adobe Experience Platform services involved in segmentation. Before continuing with this guide, please review the following documentation:
To illustrate the value of multi-entity segmentation, consider three standard marketing use cases that illustrate the challenges present in most marketing applications:
A marketer building an email campaign may have attempted to build a segment for a target audience by using recent customer store purchases within the last three months. Ideally, this segment would require both the item name and the name of the store where the purchase was made. Previously, the challenge would have been capturing the store identifier from the purchase event and assigning it to an individual customer profile.
It is often complex to create and qualify users into segments targeting cart abandonment. Knowing which products to include in a personalized retargeting campaign requires data regarding which products were abandoned by each individual. This data is tied to commerce events which were formerly challenging to monitor and extract data from.
Creating a multi-entity segment first requires defining relationships between schemas before using the Segmentation API or Segment Builder UI to build the segment definition.
Defining relationships within the structure of your Experience Data Model (XDM) schemas is an integral part of multi-entity segment creation. For relationships, the field in the destination needs to be marked as the primary identity of that schema. An identity can only be marked on strings and cannot be marked on arrays. Additionally, relationships do not necessarily need to be one-to-one, as you can connect profiles and experience events to multiple destinations.
Defining relationships can be done either using the Schema Registry API or the Schema Editor. For detailed steps showing how to define a relationship between two schemas, please choose from the following tutorials:
Once you have defined the necessary XDM relationships, you can begin to build a multi-entity segment. This can be done using either the Segmentation API or the Segment Builder UI. For more information, please choose from the following guides:
After creating a segment, you can evaluate and access the segment results using the Segmentation API. Evaluating a multi-entity segment is very similar to evaluating a standard segment. This process can only be done using the Segmentation API. For a detailed guide showing how to use the API to evaluate and access segments, please read the evaluating and accessing segments tutorial.