Interact | services | responseHist

The configuration properties in this category define the settings for the service that writes to the response history staging tables.

enableLog

Description

If true, enables the service that writes to the response history staging tables. If false, no data is written to the response history staging tables.

The response history staging table is defined by the responseHistoryTable property for the audience level. The default is UACI_RHStaging.

Default value

True

Valid Values

True | False

cacheType

Description

Defines whether the cache is kept in memory or in a file. You can use External Loader File only if you configured Unica Interact to use a database loader utility.

If you select Memory Cache, use the cache category settings. If you select External Loader File, use the fileCache category settings.

Default value

Memory Cache

Valid Values

Memory Cache | External Loader File

actionOnOrphan

Description

This setting determines what to do with response events that do not have corresponding contact events posted yet. The setting applies to in-session response events. If set to NoAction, the response event is processed as if the corresponding contact event was posted. If set to Warning, the response event is processed as if the corresponding contact event was posted, but a warning message is written into interact.log. If set to Skip, the response even is not processed, and an error message is written into interact.log. The setting that you choose here is effective regardless if response history logging is enabled.

Default value

NoAction

Valid Values

NoAction | Warning | Skip

suppressionActionOnResponse

Description
This setting handles the suppression of an offer responded by a response event in a session. It has the following four options.
  • NoSuppression. Do not suppress this offer.
  • SuppressionTillAudienceChange. This offer is suppressed until the active audience ID in this session changes.
  • SuppressionForAudience. This offer is suppressed as long as the active audience ID in this session is same as the one when this offer was returned.
  • SuppressionInSession. This offer is suppressed throughout this session even if the audience ID changes.
The following is an example with an API sequence.
  1. startSession (audience 1)
  2. getOffers -> return offer A
  3. postEvent (contact of offer A)
  4. postEvent (accept or reject offer A)
  5. getOffers
  6. setAudience (audience 2)
  7. getOffers
  8. setAudience (audience 1)
  9. getOffers
Default value

SuppressionTillAudienceChange

Valid Values

NoSuppression | SuppressionTillAudienceChange| SuppressionForAudience| SuppressionInSession

The following table shows whether offer A is suppressed in Steps 5, 7, and 9.
Setting Step 5 Step 7 Step 9
NoSuppression N N N
SuppressionTillAudienceChange Y N N
SuppressionForAudience Y N Y
SuppressionInSession Y Y Y