Interaction segmentation

Interactions in Engage offer filtering across multiple data fields within each interaction type. Marketers can now perform more detailed analysis, personalization and specialized targeting.

With this functionality for interactions, the retailer can access deeper segmentation and insights based on specific user events. This empowers marketing teams to deliver more tailored and impactful communication strategies, enhancing customer engagement across the platform.

Using in filtering tool and targeting

In the Filtering Tool or the Targeting tool your interaction schema will be selectable under All data criteria > Interactions. That looks like this:

Interactions in the filtering tool

To filter on interaction fields, click on the specific schema and you will be able to choose from all the properties that you marked as addToSegmentation when you made the interaction schema.

You can also access the InteractionDate that is connected to CreatedDate in the interaction payload.

Criteria for filtering

Below is the interaction schema properties with filtering values added:

Display of number of contacts in chosen segmentation

No interaction schemas that were made before the addToSegmentation property was added will be automatically updated. You will have to create a new schema to do this. See the "Upgrading" section in the developer documentation for the two ways in which you can do this.

Limitations

Some limitations are imposed on the use of interaction schemas and segmentable properties:

  1. An Engage environment can have a maximum of 15 interaction schemas
  2. Every schema can contain a maximum of 6 segmentable properties denoted by the addToSegmentationproperty. A validation exists in the API to enforce these limits.
The limit of 6 segmentable properties is the total, independent of type. So, for example, you can't have an interaction with 6 segmentable properties of type "Number", then 6 more of type "String". The addToSegmentation property can only appear 6 times in any one interaction schema.

In the example above, every property has the addToSegmentation property added, but it is only set to "true" for 6 of them. Only these ones will be segmentable.

For how to set up and configure interactions to use this feature, see here.

Was this article helpful?

/