Runtime tables

If you have more than one audience level, you must create staging tables for the contact and response history data for each audience level.

The SQL scripts create the following tables for the default audience level:

You must create copies of these three tables for each of your audience levels in the runtime tables.

If your Campaign contact and response history tables have user defined fields, you must create the same field names and types in the UACI_CHStaging and UACI_RHStaging tables. You can populate these fields during runtime by creating name-value pairs of the same name in session data. For example, your contact and response history tables contain the field catalogID. You must add the catalogID field to both the UACI_CHStaging and UACI_RHStaging tables. Later, the Interact API populates this field by defining an event parameter as a name-value pair named catalogID. Session data can be supplied by the profile table, temporal data, learning, or the Interact API.

The following diagram shows sample tables for the audiences Aud1 and Aud2. This diagram does not include all tables in the runtime database.

All fields in the tables are required. You can modify the CustomerID and the UserDefinedFields to match your Campaign contact and response history tables.