Interactions in Engage offer filtering across multiple data fields within each interaction type (schema). This upgrade allows marketers to perform more detailed analysis and personalization along with a plethora of specialized targeting.

Interactions were originally focused on measuring non-purchasing behavior, in order to reward engagement in some loyalty scheme (any kind of scheme the retailer could come up, essentially). With this expanded 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:

Previously you could only filter interactions for "count" for a specific schema but now you can filter on any of the fields. Check that option and you will be able to choose from all the properties you marked as addToSegmentation when making the interaction schema. As before, you can still access the InteractionDate that is connected to CreatedDate in the interaction payload.

Below is the interaction schema properties with filtering values added:

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 propties denoted by the addToSegmentationproperty. A validation exists in the API to enforce these limits.

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 new feature, see here.

Article last reviewed 29 September 2025 07:58