In Interact, all event pattern data for a given AudienceID is stored as a single collection in the runtime database tables. To perform any SQL queries or reporting based on event patterns, this new ETL process is required to break up the collection of event pattern data into tables in a target database. To accomplish this, the stand-alone ETL process takes event pattern data from the
Interact runtime database tables, processes it on the schedule you specify, and stores it in the target database where it is available for SQL queries or additional reporting.
Using the Interact application programming interface (API), two API calls deliver offers:
getOffers and
getOffersForMultipleInteractionPoints.
getOffersForMultipleInteractionPoints can prevent the return of duplicate offers at the
OfferID level, but cannot deduplicate offers across offer category. So, for example, for
Interact to return only one offer from each offer category, a workaround was previously required. With the introduction of two parameters to the
startSession API call, offer deduplication across offer attributes, such as category, is now possible.