The test run profile table

At minimum the test run profile table must contain a list of IDs appropriate for the audience level of the flowchart. For example, if the audience level of a flowchart is Household, the table referenced by the Interaction process must contain at least a list of household IDs. You have a test run profile table for each audience level. These tables are mapped for each interactive channel.

The test run profile table also includes a column for each piece of real-time session data that you use in the segmentation logic. For example, if the touchpoint designer collects the name of the web page of a visitor came from and stores it with the name linkFrom, there will be a column called linkFrom in the test run profile table.

The test run profile table may also include other data. If you are referencing all your persisted profile data in dimension tables, however, you do not have to include copies of the persisted profile data in the profile table.

The person designing interactive flowcharts, the person designing and coding the integration with the touchpoint, and the Interact administrator must all work together to design the test run profile table. The touchpoint designer must provide a list of the real-time session data available. The flowchart designer needs to provide a list of required data for segmentation, and a list of recommended sample data to test the segmentation logic. The Interact administrator must provide a list of all the optimizations and configuration settings that may affect flowchart design. For example, if you are trying to improve performance by limiting the number of times you access the database, together you must determine which data is in the profile table and which is in dimension tables.