Campaign system tables — beyond all the data for Campaign, the Campaign system tables contain data for Interact components you create in the design environment, such as treatment rules and interactive channels. The design environment and the Campaign system tables share the same physical database and schema.

Runtime tables — (systemTablesDataSource) contains the deployment data from the design environment, staging tables for contact and response history, and runtime statistics.

Profile tables — (prodUserDataSource) contains any customer data—beyond information gathered in real time—required by interactive flowcharts to properly place visitors into smart segments. If you are relying entirely on real time data, you do not need profile tables. If you are using profile tables, you must have at least one profile table per audience level used by the interactive channel.

Test run tables — (testRunDataSource) contains a sample of all data required by interactive flowcharts to place visitors into smart segments, including data that mimics what is gathered in real time during an interaction. These tables are required for the server group designated as the test run server group for the design environment only.

Learning tables — (learningTablesDataSource) contains all data gathered by the built-in learning utility. These tables can include a table which defines dynamic attributes. If you are not using learning or are using an external learning utility you create, you do not need learning tables.

Contact and response history for cross-session response — (contactAndResponseHistoryDataSource) either the Campaign contact history tables or a copy of them. If you are not using the cross-session response feature, you do not need to configure these contact history tables.