Points to consider

Remember the following tips as you write your integration.

When designing your touchpoint, create some default filler content (usually a benign branding message or empty content) for every interaction point where offers can be presented. This is in case no offers are eligible to be served to the current visitor in the current situation. You should assign this default filler content as the default string for the interaction point.

When designing your touchpoint, include some method of presenting content in case your touchpoint cannot reach the runtime server group for some unforeseen reason.

When triggering events that re-segment your visitor, including postEvent and setAudience, remember that running flowcharts does take some amount of time. The getOffers method waits until segmentation is finished before executing. Overly frequent re-segmentation may hinder getOffers call response performance.

You need to decide what an "offer rejection" means. Several reports, such as the Channel Offer Performance Summary report, present the number of times an offer has been rejected. This is a count of the number of times the Log Offer Rejection action has been triggered by a postEvent. You need to determine whether Log Offer Rejection is for an actual rejection (such as clicking a link labeled "No, thanks.") or for an offer that is ignored (such as a page displaying three different banner ads, none of which are selected).

There are several optional features you can enable to enhance Interact offer selection, including learning, offer suppression, individual offer assignments, and other elements of offer serving. You need to determine how many, if any, of these optional features would enhance your interactions.