FlexOffers with segment and event patterns

This feature is available from version 12.1.0.4 onwards.

Segment: While creating big FlexOffer mapping tables, you can add segment as a user-defined field (with name “Segment” with datatype as string) and assign value of Segment for each FlexOffer. After big FlexOffer mapping tables are deployed to Interact RT and offer API is called, the system filters FlexOffer with Login Session associated segments.

Event Pattern: In big FlexOffer mapping tables, there are two ways to use event pattern.

  • You can use event pattern as a FlexOffer filter condition to filter the FlexOffers.

    For example, you can add user-defined field EPTest (datatype integer) and set EPTest value in big FlexOffer mapping tables. From FlexOffer filter, you can add condition EPTest = EventPattern.pattern1. After the deployment of FlexOffer to Interact RT, when you invoke get offer API call, system is based on the EventPattern.pattern1 state to filter FlexOffers. Only the FlexOffer EPTest with value meets the EventPattern.pattern1 state value and return to getOffer API call.

  • Under FlexOffer Advanced Options, under Offer Score and Eligibility tab, you can configure or define event pattern expression. If you configure the event pattern expression, the offer score is calculated based on that or the FlexOffer eligibility is based on whether the event pattern expression state is met.