Cross-session response tracking data source configuration

Interact cross-session response tracking matches session data from the runtime environment with the Campaign contact and response history. By default, cross-session response tracking matches on treatment code or offer code. You can configure the runtime environment to match on a custom, alternate code.

If you choose to match on an alternate code, you must define the alternate code in the UACI_TrackingType table in the Interact runtime tables.

The runtime environment must have access to the Campaign contact history tables. This can be by either configuring the runtime environment to have access to the Campaign contact history tables, or by creating a copy of the contact history tables in the runtime environment.

This access is read-only, and is separate from the contact and response history utility.

If you create a copy of the tables, it is your responsibility to ensure data in the copy of the contact history is accurate. You can configure the length of time the CrossSessionResponse service retains unmatched responses to match the how often you refresh the data in the copy of the contact history tables using the purgeOrphanResponseThresholdInMinutes property. If you are using the contact and response history module, you should coordinate the ETL updates to ensure you have the most current data.