Planning your Interact implementation
When you plan the design of your Interact implementation, you must consider the following factors: the strategies that you use to interact with your customers, and the data that is required to segment your customers. Designing your Interact implementation requires the coordination of several components.
The following example proposes one method of organizing the different questions that you should answer to design a successful Interact implementation. These questions are for designing an interaction configuration.
The first step of designing your implementation is asking, "How and where do I want to interact with my customers?" This question has an almost unlimited number of answers. Are you considering integrating with a website, an interactive voice response (IVR) system, or a point of sale (POS) system? Do you want to display banner ads that are based on site navigation, a list of further choices that are based on previous selections, or money-saving coupons that are based on the current purchases? Most touchpoints have more than one location available for interaction, so you may need to ask this question several times.
After you know what you want to do with Interact, you must define what configuration components you must create. You must coordinate with the touchpoint administrator to define what interaction points and events must be created. You must also consider what offers you present, how you segment your customers, and what sampling, integration, or tracking strategies you are using. The answers to these questions help define what information you must create in the profile database. At the same time, consider how you want to organize the interaction points into zones that are meant to serve a common purpose so you can fine-tune your offer presentation.
There are several optional features, including offer suppression, learning, individual offer assignments, and score override, which you may want to implement. Most of these features require specific database tables, and require little or no configuration in the design environment. For more information about these features, see the Interact Administrator's Guide.
Since performance is an integral part of Interact, you must consider the data that is required to segment your customers. Since there is a performance impact each time data is retrieved from the database, you must carefully design the information that you provide for the runtime environments. For more information about designing and maintaining your customer data, see the Interact Administrator's Guide.