FlexOffers with segment and event patterns

Segment: While creating big FlexOffers 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 FlexOffers. After big FlexOffers mapping tables are deployed to Interact RT and offer API is called, the system filters FlexOffers with Login Session associated segments.

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

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

    For example, you can add user-defined field EPTest (datatype integer) and set EPTest value in big FlexOffers mappings. From FlexOffers filter, you can add condition EPTest = EventPattern.pattern1. After the deployment of FlexOffers 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 FlexOffers 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 FlexOffers eligibility is based on whether the event pattern expression state is met.