Required databases or schemas for Interact

The Interact runtimeOpportunity Detect Design Time environment requires several databases to hold user and interaction data. You can use your Campaign Customer (user) tables or set up a unique data source.

The Interact design time environment tables are automatically added to the database or schema that holds the Campaign system tables.

According to the type of data that must be stored, determine how many databases or schemas you must create for use with the Interact runtime environment.

A database or a schema is required to hold the Interact design time tables. There must be a separate database or schema for each server group.

The following list provides a brief summary of the databases or schemas that are required for the Interact runtime environment:
  • Database or schema to hold the Interact runtime tables. There must be a separate database or schema for each server group.
  • Database, schema, or view to hold the user profile tables. The user profile tables can be in the same database as your Campaign Customer (user) tables. There can be a separate set of user profile tables for each interactive channel.
  • Database, schema, or view to hold the test run tables. The test run tables can be in the same database as your Campaign Customer (user) tables.
  • If you want to use built-in learning, there must be a database or schema to hold the learning tables.
  • If you want to use cross-session response tracking, there must be a database or schema to hold a copy of the Campaign contact history tables. Alternatively, instead of creating a copy, you can use the Campaign system tables database to run the cross-session response tracking scripts.