IBMInteract911UsersGuide en Us

IBM Interact
Version 9 Release 1.1

November 26, 2014
User's Guide

Note
Before using this information and the product it supports, read the information in “Notices” on page 115.
This edition applies to version 9, release 1, modification 1 of IBM Interact and to all subsequent releases and
modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2001, 2014.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Chapter 1. IBM Interact . . . . . . . . 1 Adding an event and pre-defined action to your
Understanding Interact . . . . . . . . . . . 2 touchpoint. . . . . . . . . . . . . . 36
Interact architecture . . . . . . . . . . . . 2 Use categories to group events . . . . . . . 36
Campaign key concepts. . . . . . . . . . . 5 Use event patterns to personalize offers to the
About Campaign . . . . . . . . . . . . 5 visitor . . . . . . . . . . . . . . . . 37
Audience levels . . . . . . . . . . . . 5 Event pattern types. . . . . . . . . . . 38
Campaigns . . . . . . . . . . . . . . 6 How Interact processes event pattern states and
Cells . . . . . . . . . . . . . . . . 6 statuses. . . . . . . . . . . . . . . 38
Flowcharts . . . . . . . . . . . . . . 7 Creating an event pattern to identify visitor
Offers. . . . . . . . . . . . . . . . 7 behavior patterns . . . . . . . . . . . 39
Sessions . . . . . . . . . . . . . . . 7 Use constraints to limit the number of times an offer
Interact key concepts . . . . . . . . . . . 7 is presented . . . . . . . . . . . . . . 42
Design environment . . . . . . . . . . . 8 Creating a constraint for an offer . . . . . . 42
Interactive channels . . . . . . . . . . . 8 Modifying a constraint to change when an offer
Interactive flowcharts . . . . . . . . . . 8 is presented . . . . . . . . . . . . . 43
Interaction points . . . . . . . . . . . . 8 Enabling or disabling an offer constraint. . . . 43
Events . . . . . . . . . . . . . . . 9 Deleting a constraint that is no longer needed . . 44
Profiles . . . . . . . . . . . . . . . 10 Use learning models to select offers . . . . . . 44
Runtime environment . . . . . . . . . . 10 Adding a learning model to customize offers for
Runtime sessions . . . . . . . . . . . 10 a visitor . . . . . . . . . . . . . . 44
Smart segments . . . . . . . . . . . . 10 Editing a learning model . . . . . . . . . 45
Touchpoints . . . . . . . . . . . . . 10 Deleting a learning model . . . . . . . . 45
Treatment rules . . . . . . . . . . . . 11 Enabling and disabling a learning model . . . 45
Interact API . . . . . . . . . . . . . 11 Use with smart segments to refine offers . . . . 46
Zones . . . . . . . . . . . . . . . 11 Create a Campaign session for interactive
Interact users . . . . . . . . . . . . . . 11 flowcharts . . . . . . . . . . . . . . 46
Interact workflow for implementing the Define an interactive flowchart to segment your
marketing plan . . . . . . . . . . . . 12 visitors . . . . . . . . . . . . . . . 46
Planning your visitor interaction . . . . . . 15 Define real-time interactive offers for visitors . . . 46
Logging in to IBM EMM . . . . . . . . . . 15 Creating offer templates for Interact . . . . . 48
Setting your start page . . . . . . . . . . 16 Use real-time offer suppression to fine-tune
Interact documentation and help . . . . . . . 17 visitor offers . . . . . . . . . . . . . 48
Working with treatment rules . . . . . . . . 50
Chapter 2. Create the marketing Offer eligibility . . . . . . . . . . . . 51
Marketing score . . . . . . . . . . . . 51
campaign in the design environment. . 19 Treatment rule advanced options . . . . . . 52
Configuration information shared by the user Working with the Interaction Strategy tab . . . 52
interface and the Interact API . . . . . . . . 20 To add or modify a treatment rule . . . . . . 56
Use interactive channels to coordinate your To add or modify treatment rules with the Rule
touchpoint resources . . . . . . . . . . . 22 Wizard . . . . . . . . . . . . . . . 62
Restrict how often an offer is presented . . . . 22 To enable and disable treatment rules. . . . . 63
Creating an interactive channel to coordinate To delete treatment rules . . . . . . . . . 64
your interactive campaign resources . . . . . 23 About deploying interaction strategy tabs . . . 64
About table mapping . . . . . . . . . . 24 Exporting an interactive channel . . . . . . 66
Interactive Channel Summary page . . . . . 28 Interaction strategy reference . . . . . . . 67
Group your interaction points into zones . . . . 30 (Optional) Assign target and control cells . . . . 67
Adding zones for your interaction points to the To override cell codes . . . . . . . . . . 68
interactive channel . . . . . . . . . . . 30 Deploy the Interact configuration . . . . . . . 68
Create interaction points for the visitor to interact
with your touchpoint . . . . . . . . . . 32
Adding visitor interaction points to your
Chapter 3. About interactive flowcharts 69
touchpoint interactive channel . . . . . . . 32 Building interactive flowcharts . . . . . . . . 70
Interaction point tab reference . . . . . . . 33 To create interactive flowcharts . . . . . . . . 70
Define the events that are triggered by visitor Interactive flowcharts and data sources . . . . . 71
actions . . . . . . . . . . . . . . . . 33 The test run profile table . . . . . . . . . 71
Events tab reference . . . . . . . . . . 35 Dimension tables . . . . . . . . . . . 72
© Copyright IBM Corp. 2001, 2014 iii

Configuring interactive flowcharts . . . . . . 72 Viewing Interact reports . . . . . . . . . . 103
Queries and Interact . . . . . . . . . . 72 To view reports from the interactive channel
About data types and stored objects . . . . . 73 Analysis tab . . . . . . . . . . . . . 103
Derived fields, user variables, macros, and To view Interact reports from the Campaign
Interact . . . . . . . . . . . . . . . 74 Analysis tab . . . . . . . . . . . . . 104
Using EXTERNALCALLOUT . . . . . . . 75 To view Interact reports from Analytics Home 105
About the Interaction process . . . . . . . . 75 About the Interaction Point Performance report
About the Decision process . . . . . . . . . 75 portlet . . . . . . . . . . . . . . . . 105
To configure the Decision process . . . . . . 76 About the Channel Deployment History report
To configure Decision process branches . . . . 76 (interactive channel) . . . . . . . . . . . 106
About the PopulateSeg process . . . . . . . . 77 About the Channel Event Activity Summary
To create smart segments . . . . . . . . . 77 report . . . . . . . . . . . . . . . 106
About the Sample process in interactive flowcharts 78 About the Channel Interaction Point
To configure the Sample process . . . . . . 78 Performance Summary report . . . . . . . 106
About the Select process in interactive flowcharts. . 79 About the Channel Treatment Rule Inventory
To configure the Select process . . . . . . . 80 report . . . . . . . . . . . . . . . 106
About the Snapshot process in interactive flowcharts 80 About the Interactive Segment Lift Analysis
To configure the Snapshot process . . . . . . 81 report . . . . . . . . . . . . . . . 107
Understanding interactive flowchart test runs . . . 82 About the Channel Deployment History report
To configure the test run size . . . . . . . 83 (campaign) . . . . . . . . . . . . . . 107
To perform a test run . . . . . . . . . . 83 About the Interactive Offer Learning Details
About deploying interactive flowcharts . . . . . 84 report . . . . . . . . . . . . . . . 107
To deploy an interactive flowchart. . . . . . 84 About the Interactive Cell Performance reports 107
To cancel a deployment request. . . . . . . 85 About the Interactive Offer Performance reports 108
To undeploy an interactive flowchart . . . . . 85 About the Interactive Cell Lift Analysis report 108
About the Channel Learning Model
Chapter 4. About the Interact List Performance Over Time report . . . . . . 108
process in batch flowcharts . . . . . 87 About the Zone Performance Report by Offer . . 108
About the Event Pattern report . . . . . . . 108
Interact List process box . . . . . . . . . . 87
To filter by interaction point . . . . . . . . 109
To configure the Interact List process . . . . . . 87
To filter by event or category . . . . . . . 109
To filter by offer . . . . . . . . . . . 109
Chapter 5. Understanding deployment To filter by target cell. . . . . . . . . . 109
to runtime servers . . . . . . . . . . 91 To filter by time . . . . . . . . . . . 110
Understanding runtime servers . . . . . . . . 92 To filter the Channel Deployment History report 110
Deployment and delete . . . . . . . . . . 93 To filter the Channel Treatment Rule Inventory
To delete an interactive channel . . . . . . 94 report . . . . . . . . . . . . . . . 110
About deployment versioning . . . . . . . . 94
To deploy to a runtime server group . . . . . . 95 Before you contact IBM technical
To undeploy . . . . . . . . . . . . . . 96
support . . . . . . . . . . . . . . 113
To view the deployment tab . . . . . . . . . 97
Filtering tables in IBM products . . . . . . 99
Notices . . . . . . . . . . . . . . 115
Chapter 6. About Interact reporting 101 Trademarks . . . . . . . . . . . . . . 117
Privacy Policy and Terms of Use Considerations 117
Interact reports data . . . . . . . . . . . 101
Interact Reports and Reporting Schemas . . . . 101
iv IBM Interact: User's Guide

Chapter 1. IBM Interact
IBM® Interact is an interactive engine that targets personalized offers to visitors of
inbound marketing channels. You can configure Interact to be behavioral, strictly
event-based, situational, strategic, and so on. Interact is a module within the IBM
suite of Enterprise Marketing Management tools, and is integrated with IBM EMM.
What Interact does
Interact uses both online and offline data, including in-depth historical knowledge
of customers plus current customer activities, to create real-time customer
interactions. These interactions increase sales, build relationships, generate leads,
increase conversion rates, optimize channel usage, and lower attrition. You can
establish the business rules and sales or service strategies that drive real-time
interactions, and modify them to reflect the continuous learning from your
marketing efforts.
Use Interact to enhance your marketing efforts
Use Interact to give your marketing organization the ability to coordinate real-time
inbound customer treatment strategies with your traditional outbound campaigns.
With Interact, you use the power of IBM EMM to enhance your real-time
marketing efforts in several ways:
v Use your multi-channel operations.
Use information from your customer touchpoints, including web, call center,
in-store, branch, to develop knowledge of customers and prospects, create a
consistent brand, and maximize customer communications.
v Create leading-edge website personalization.
Engage known and anonymous visitors, consider behavior, and personalize
interactions with them by making cross-sell offers, selecting editorial content,
offering appropriate service options, and coordinating banner messages.
v Optimize contact center interactions.
Use the power of your contact center for increased revenue generation and
customer retention. Provide better interactive voice response (IVR) navigation,
on-hold message selection, instant offers for retention and cross-selling,
prioritization of offers, and website intervention (such as chat or VoIP).
Use Interact to refine your marketing strategies
You use Interact to control and fine-tune the real-time, analytical content that is
delivered to your touchpoint systems. Your strategies can include factors that you
consider important. These strategies can drive the response to specific customer
actions, driving personalized content from an instant offer link on a website, to a
cross-sell opportunity at a call center. Interact gives you control over critical online
selling, marketing, and service strategies, and the ability to respond quickly to
opportunities or changes in your marketplace.
© Copyright IBM Corp. 2001, 2014 1

Understanding Interact
Interact integrates with your customer facing systems-such as websites and call
centers-and allows you to retrieve optimal personalized offers and visitor profile
information in real-time to enrich the interactive customer experience.
For example, a customer logs into a book store website and peruses the site.
Interact recalls the customer's prior purchasing habits (Japanese literature and
books by a certain author). When the customer goes to a page you have integrated
with Interact, Interact chooses what offers to present to the customer (a retelling of
a famous Japanese story by the same author) based on the previous interactions.
You configure Interact to integrate with your touchpoints using an application

programming interface (API). Using this API, you configure Interact to gather a
customer's information, add data to that information, and present offers based both
on actions taken by the customer in the touchpoint and the customer's profile
information.
Interact is closely integrated with Campaign to define which offers are assigned to
which customer. Because of this integration, you can use the same offers across all
of your campaigns, along with all of Campaign's offer management tools. You can
also integrate all the contact and response history across all of your campaigns
and, for example, use email and direct mail contacts to influence offers presented
to the user in real time.
The following sections describe the different components of Interact and how they
work together.
Interact architecture
Understanding Interact architecture helps you understand how Interact
communicates with the customer-facing touch point, the runtime servers, and IBM
Campaign. Interact architecture uses the Interact API to closely work with the
design environment, the runtime environment, and sometimes the testing runtime
environment to meet your performance requirements.
Interact consists of at least two major components, the design environment and the
runtime environment. You may have optional testing runtime environments as
well. The following figure shows the high-level architecture overview.
2 IBM Interact: User's Guide

Profile Profile
PRODUCTION DB DB TEST
RUNTIME RUNTIME
Runtime Runtime
Interact Runtime Tables Tables Runtime Interact
API Server Server API
Customer Interact Test

Facing Deployment Touch
Touch
Point
Point
Campaign
System Customer
Tables DB
DESIGN ENVIRONMENT
The design environment is where you perform the majority of your Interact
configuration. The design environment is installed with Campaign and references
the Campaign system tables and your customer databases.
After you design and configure how you want Interact to handle customer
interactions, you deploy that data to either a testing runtime environment for
testing or a production runtime environment for real-time customer interaction.
In production, the architecture may be more complicated. For example, a runtime

environment may have several runtime servers connected to a load balancer to
meet your performance requirements.
The following figure shows the Interact environment in more detail.
Chapter 1. IBM Interact 3

In the design environment, you define what Interact does at certain points in your
touchpoint by configuring interactive channels. You then divide your customers
into segments by creating interactive flowcharts. Within interactive flowcharts, you
can perform test runs to confirm that your customer data is segmented correctly.
Next, you must define offers. You then assign the offers to segments within an
interaction strategy. Once you have configured all of the Interact components, you
are ready to deploy the configuration to a staging runtime environment.
Interact deployments consist of the following:

v Interact configuration data including interactive channels and interaction
strategies
v a subset of Campaign data including smart segments, offers, and interactive
flowcharts
While not part of your Interact deployment, your customer data may be required
in the runtime environment. You must ensure this data is available to the runtime
environment.
In the staging runtime environment-which is the same as a production runtime

environment except that it is not customer-facing - you can test the entirety of your
Interact configuration, including the API integration with your touchpoint. During
runtime, a customer-or in the case of a staging server, someone testing the

system-takes actions in the touchpoint. These actions send events or requests for
data to the runtime server by means of the Interact API. The runtime server then
responds with results, such as presenting a set of offers (data) or re-segmenting a
customer into a new segment (event). You can continue modifying your Interact
configuration in Campaign and re-deploying it to the runtime environment until
you are satisfied with the behavior. You can then deploy the configuration to the
production runtime environment.
The production runtime servers record statistical and historical data such as
contact history and response history. If configured, a utility copies the contact
history and response history data from staging tables in the production runtime
server group to your Campaign contact and response history. This data is used in
reports that you can use to determine the effectiveness of your Interact installation
and revise your configurations as necessary. This data can also be used by
Campaign and other IBM products such as Contact Optimization, integrating your
real time campaigns with your traditional campaigns. For example, if a customer
has accepted an offer on your website, you can use that data in Campaign to
ensure either that the same offer is not sent by mail, or that you follow up the
offer with a telephone call.
The following sections describe important terms and concepts in both Campaign
and Interact.
Campaign key concepts

Interact integrates with IBM Campaign to define the offers that are assigned to
customers. Integration between Interact and Campaign ensures that you can use
the same offers across multiple campaigns, and integrate all the contact and
response history across all your campaigns.
Before you use Interact, there are several Campaign concepts you should be
familiar with. These are brief descriptions of the concepts. For more information,
see the Campaign User's Guide.
About Campaign
Campaign is a web-based Enterprise Marketing Management (EMM) solution that
enables users to design, execute, and analyze direct marketing campaigns.
Campaign provides an easy-to-use graphical user interface that supports the direct
marketing processes of selecting, suppressing, segmenting, and sampling lists of
customer IDs.
Once you have selected your targets, you can use Campaign to define and execute
your marketing campaign by assigning offers, sending e-mails, and so on. You can
also use Campaign to track the response to the campaign, creating output lists and
logging contacts to contact history, and use that information in your next
campaign.
Audience levels
An audience level is a collection of identifiers that can be targeted by a campaign.
You can define audience levels to target the correct set of audiences for your
campaign.
For example, a set of campaigns can use the audience levels "Household,"
"Prospect," "Customer," and "Account." Each of these levels represents a certain
view of the marketing data available for a campaign.

Audience levels are typically organized hierarchically. Using the examples above:
v Household is at the top of the hierarchy, and each household can contain
multiple customers and one or more prospects.
v Customer is next in the hierarchy, and each customer can have multiple
accounts.
v Account is at the bottom of the hierarchy.
Other, more complex examples of audience hierarchies exist in business-to-business

environments, where audience levels can exist for businesses, companies, divisions,
groups, individuals, accounts, and so on.
These audience levels can have different relationships with each other, for example
one-to-one, many-to-one, or many-to-many. By defining audience levels, you allow
these concepts to be represented within Campaign so that users can manage the
relationships among these different audiences for targeting purposes. For example,
although there might be multiple prospects per household, you might want to
limit mailings to one prospect per household.
Campaigns
In marketing, a campaign is a selection of related activities and processes that are
performed to achieve a marketing communication or sales objective. Campaign
also contains objects called campaigns which are representations of marketing
campaigns that facilitate design, testing, automation, and analysis.
Campaigns include one or more flowcharts that you design to perform a sequence
of actions on your data for executing your campaigns.
Cells
A cell is a list of identifiers (such as customer or prospect IDs) from your database.
In Campaign, you create cells by configuring and running data manipulation
processes in flowcharts. These output cells can also be used as input for other
processes in the same flowchart (downstream from the process which created
them).
There is no limit to the number of cells you can create. Cells to which you assign
one or more offers in Campaign are called target cells. A target cell is a distinct
group of homogeneous audience members. For example, cells can be created for
high-value customers, customers who prefer to shop on the web, accounts with
on-time payments, customers who opt to receive email communications, or loyal
repeat buyers. Each cell or segment you create can be treated differently, with
different offers or contact channels, or tracked differently, for comparison in
performance reporting.
Cells containing IDs qualified to receive an offer but that are excluded from
receiving the offer for analysis purposes, are called control cells. In Campaign,
controls are always hold-out controls.
The term "cell" is sometimes used interchangeably with "segment." Strategic

segments are cells that are created in a session rather than in a campaign
flowchart. A strategic segment is no different from other cells (such as cells that are
created by a Segment process in a flowchart) except that it is available globally, for
use in any campaign. A strategic segment is a static list of IDs until the flowchart
that created it originally is rerun.

Flowcharts
In Campaign, flowcharts represent a sequence of actions that you complete on
your data, as defined by building blocks called processes. Flowcharts can be run
manually, by a scheduler, or in response to some defined trigger.
You use flowcharts to accomplish particular marketing goals, such as determining

qualified recipients for a direct mail campaign, generating a mailing list for this
group of recipients, and associating each recipient with one or more offers. You can
also track and process respondents to your campaign, and calculate your return on
investment for the campaign.
Within each of your campaigns, you design one or more flowcharts to implement
the campaign, configuring the processes that make up the flowchart(s) to complete
the required data manipulation or actions.
Each flowchart has the following elements:

v Name
v Description
v One or more mapped tables from one or more data sources
v Interconnected processes that implement the marketing logic
Offers
An offer represents a single marketing message, which can be delivered in various
ways.
In Campaign, you create offers that can be used in one or more campaigns.
Offers are reusable:

v In different campaigns
v At different points in time
v For different groups of people (cells)
v As different "versions" by varying the offer's parameterized fields
You assign offers to interaction points in the touchpoints that are presented to
visitors.
Sessions
A session is a construct in Campaign where fundamental, persistent, global data
constructs (such as strategic segments and cubes) are created by Campaign
administrators and then made available to all campaigns.
Like campaigns, sessions are also composed of individual flowcharts.
Interact key concepts

IBM Interact is an interactive engine that targets personalized marketing offers to
various audiences.
This section describes some of the key concepts you should understand before you
work with Interact.

Design environment
Use the design environment to configure various Interact components and deploy
them to the runtime environment.
The design environment is where you complete most of your Interact

configuration. In the design environment, you define events, interaction points,
smart segments, and treatment rules. After you configure these components, you
deploy them to the runtime environment.
The design environment is installed with the Campaign web application.
Interactive channels
Use interactive channels in Interact to coordinate all the objects, data, and server
resources that are involved in interactive marketing.
An interactive channel is a representation in Campaign of a touchpoint where the

method of the interface is an interactive dialog. This software representation is
used to coordinate all of the objects, data, and server resources that are involved in
interactive marketing.
An interactive channel is a tool that you use to define interaction points and
events. You can also access reports for an interactive channel from the Analysis tab
of that interactive channel.
Interactive channels also contain production runtime and staging server

assignments. You can create several interactive channels to organize your events
and interaction points if you have only one set of production runtime and staging
servers, or to divide your events and interaction points by customer-facing system.
Interactive flowcharts
Use interactive flowcharts to divide your customers into segments and assign a
profile to a segment.
An interactive flowchart is related to but slightly different from a Campaign batch

flowchart. Interactive flowcharts perform the same major function as batch
flowcharts: dividing your customers in to groups known as segments. For
interactive flowcharts, however, the groups are smart segments. Interact uses these
interactive flowcharts to assign a profile to a segment when a behavioral event or
system event indicates that a visitor re-segmentation is needed.
Interactive flowcharts contain a subset of the batch flowchart processes, and a few
interactive flowchart-specific processes.
Note: Interactive flowcharts can be created in a Campaign session only.
Interaction points
An interaction point is a place in your touchpoint where you want to present an
offer.
Interaction points contain default filler content in cases where the runtime
environment does not have other eligible content to present. Interaction points can
be organized into zones.

Events
An event is an action that is taken by a visitor and that triggers an action in the
runtime environment. Examples of an event can be: placing a visitor into a
segment, presenting an offer, or logging data.
Events are first created in an interactive channel and then triggered by a call to the
Interact API by using the postEvent method. An event can lead to one or more of
the following actions that are defined in the Interact design environment:
v Trigger Re-segmentation. The runtime environment runs all the interactive
flowcharts for the current audience level that is associated with the interactive
channel again, by using the current data in the visitor's session.
When you design your interaction, unless you specify a specific flowchart, a
resegmentation action runs all interactive flowcharts that are associated with this
interactive channel with the current audience level again, and that any request
for offers waits until all flowcharts are finished. Excessive resegmentation within
a single visit can affect the performance of the touchpoint in a customer-visible
way.
Place the customer in new segments after significant new data is added to the
runtime session object, such as new data from requests from the Interact API
(such as changing the audience) or customer actions (such as adding new items
to a wish list or shopping cart).
v Log Offer Contact. The runtime environment flags the recommended offers for
the database service to log the offers to contact history.
For web integrations, log the offer contact in the same call where you request
offers to minimize the number of requests between the touchpoint and the
runtime server.
If the touchpoint does not return the treatment codes for the offers that Interact
presented to the visitor, the runtime environment logs the last list of
recommended offers.
v Log Offer Acceptance. The runtime environment flags the selected offer for the
database service to log to response history.
v Log Offer Rejection. The runtime environment flags the selected offer for the
v Trigger User Expression. An expression action is an action that you can define by
using Interact macros, including functions, variables, and operators, including
EXTERNALCALLOUT. You can assign the return value of the expression to any
profile attribute.
When you click the edit icon next to Trigger User Expression, the standard User
Expression editing dialog is displayed, and you can use this dialog to specify the
audience level, optional field name to which to assign the results, and the
definition of the expression itself.
v Trigger Events. You can use the Trigger Events action to enter an event name
that you want to be triggered by this action. If you enter an event that is already
defined, that event is triggered when this action is run. If the event name you
enter does not exist, this action causes the creation of that event with the
specified action.
You can also use events to trigger actions that are defined by the postEvent
method, including logging data to a table, including data to learning, or triggering
individual flowcharts.
Events can be organized into categories for your convenience in the design
environment. Categories have no functional purpose in the runtime environment.

Profiles
A profile is the set of customer data that is used by the runtime environment. This
data can be a subset of the customer data available in your customer database,
data that is collected in real time, or a combination of the two.
The customer data is used for the following purposes:

v To assign a customer to one or more smart segments in real-time interaction
scenarios.
You need a set of profile data for each audience level by which you want to
segment. For example, if you are segmenting by location, you might include
only the customer's postal code from all the address information you have.
v To personalize offers
v As attributes to track for learning
For example, you can configure Interact to monitor the marital status of a visitor
and how many visitors of each status accept a specific offer. The runtime
environment can then use that information to refine offer selection.
This data is read-only for the runtime environment.
Runtime environment
The runtime environment connects to your touchpoint and performs interactions.
The runtime environment can consist of one or many runtime servers that are
connected to a touchpoint.
The runtime environment uses the information that is deployed from the design
environment in combination with the Interact API to present offers to your
touchpoint.
Runtime sessions
A runtime session exists on the runtime server for each visitor to your touchpoint.
This session holds all the data for the visitor that the runtime environment uses to
assign visitors to segments and recommend offers.
You create a runtime session when you use the startSession call.
Smart segments
A smart segment is similar to a strategic segment in that it is a group of customers
with defined traits. Instead of a list of IDs, however, a smart segment is the
definition of what IDs are allowed in the list.
For example, a smart segment would be "All customers living in Colorado with an
account balance greater than $10,000 who have applied for a car loan in the last 6
months." These definitions are represented by interactive flowcharts. Smart
segments are only available in Interact.
Touchpoints
A touchpoint is an application or place where you can interact with a customer. A
touchpoint can be a channel where the customer initiates the contact (an "inbound"
interaction) or where you contact the customer (an "outbound" interaction).

Common examples are websites and call center applications. Using the Interact
API, you can integrate Interact with your touchpoints to present offers to
customers based on their action in the touchpoint. Touchpoints are also called
client-facing systems (CFS).
Treatment rules
Treatment rules assign an offer to a smart segment. These assignments are further
constrained by the custom-defined zone you associate with the offer in the
treatment rule.
For example, you have one set of offers you assign a smart segment in the "login"
zone, but a different set of offers for the same segment in the "after purchase" zone.
Treatment rules are defined on an interaction strategy tab of a campaign.
Each treatment rule also has a marketing score. If a customer is assigned to more
than one segment, and therefore more than one offer is applicable, the marketing
scores help define which offer Interact suggests. Which offers the runtime
environment suggests can be influenced by a learning module, an offer
suppression list, and global and individual offer assignments.
Interact API
Use the Interact application programming interface (API) to integrate Interact with
your touchpoints.
The Interact API can work as Java™ serialization over HTTP or as a SOAP
implementation to integrate Interact with your touchpoints.
Zones
Interaction points are organized into zones. You can limit a treatment rule to apply
to a certain zone only.
If you create a zone that contains all of your "welcome" content, and another zone
for "cross-sell" content, you can present a different set of offers to the same
segment based on where the customer is in your touchpoint.
Interact users
In Interact, you can create user roles, and add single or multiple users for each
user role. Users can be common across user roles.
Interact is used by many people within your organization. Because Interact is a

connection point between your touchpoints and your marketing campaigns, the
people that are involved with both parts of your organization will either be using
or affected by Interact.
The following list describes potential Interact user roles. These duties may be
divided among several individuals in your organization, or a few people may
perform multiple roles.
v A user who oversees all of the infrastructure that surrounds a touchpoint. While
this user may not actively touch any configuration in the design environment,
this person is in charge of making sure the touchpoint stays up and running,
and writes the integration between the touchpoint and the runtime environment
with the Interact API. This user approves deploying new configurations to

production runtime servers. This user may also review statistics and reports
from staging servers to analyze the effect of deploying new configurations to
production runtime servers.
v A user who installs and configures Marketing Platform, Campaign, and Interact.
This user also installs and configures the runtime server groups, and might also
perform the steps to deploy new configurations. This user could be considered
the Interact administrator.
v A user who designs real-time interactions. This user defines offers and which
customers should receive them by working with interactive channels and
campaigns. While this user may not perform the actual steps of configuration in
the runtime environment, this user defines what the configurations are and
spends a lot of time reviewing reports detailing performance and ROI.
v A user who designs segmentation logic for interactive channels by creating
interactive flowcharts.
v A user who manages the data used by Interact. This person may not ever 'use'
Interact, but is integral to your design team. This person must work with the
user who designs the segmentation logic and the user managing the touchpoint
to ensure that the correct data is where it needs to be, and is formatted and
indexed properly to meet all performance requirements.
Interact workflow for implementing the marketing plan

When you configure Interact, you use a workflow to outline the process from an
idea to deployment in detail. Configuring Interact is a multi-step, multi-person,
iterative process. The process from an idea to deployment involves: design,
configuration, testing, review, and deployment.
Workflow process
There are several steps in the workflow to implement the marketing strategy in
Interact:
1. Design the interaction. During the design step, the team identifies the
interaction points, zones, events, and categories in the interactive channel. The
Interact administrator uses the names of the interaction points and events and
configures the touchpoint with the Interact API. The Interact user uses the user
interface to enter the components into the system.
2. Configure the interaction. The design is configured in Campaign and Interact.
The using interactive flowcharts in Campaign, the Interact API, and the Interact
user interface. The Campaign and Interact users are involved in the
configuration as sell as the Interact administrator, who works with the Interact
API.
3. Test the interaction. The Interact user and administrator create the interaction
components in Interact. Then, the Interact administrator deploys them to a
staging server for testing.
4. Review the interaction. After the interaction is tested, review it again before
deployment.
5. Deploy the interaction. The administrator deploys the interaction to the
production server.

Design the interaction
During the design phase, you brainstorm about what kinds of interactive
marketing strategies you would like to use. When you have a strategy for how you
want the visitor to interact with your touchpoint, you need to determine how to
implement that strategy with Interact.
This brainstorming is a cooperative effort between the person who:

v Manages the touchpoint with the Interact API
v Works with the Interact user interface
v Designs the marketing plan
Using business goals and target metrics, they can create a list of interaction points
and zones, and a rough list of segmentation and suppression strategies. These
design meetings also identify the data that is required to do the segmentation.
Configure the interaction
During the configuration phase, the touchpoint administrator and an Interact user
implement the design. The Interact user defines offer-to-segment assignments and
configures the interactive channel with the user interface in the design
environment. The Interact administrator configures the Interact API to make the
touchpoint work with the runtime server. The data administrator configures and
creates the data tables that are required for both testing and production.
Test the interaction
After the interaction is configured in the Interact design environment, you mark
the various components for deployment to staging runtime environments. The
Interact administrator deploys the configuration to the staging servers and the
testing can begin.
All members of the team that is involved with designing the interaction review the
results to confirm that the:
v Configured interaction is working as designed
v Performance of the runtime environment is within tolerable limits for response
time and throughput
The designers might need to change the design and more testing might need to be
done. After everyone is pleased by the results, the manager can mark the
configuration for deployment to production servers.
Review the interaction
After testing, the touchpoint manager can review all the results as well to ensure
that the configuration will have no adverse effects on the customer-facing system.
Deploy the interaction
After the configuration has approval from all parties, it can be deployed to
production runtime servers.

Design workflow diagram
This diagram shows a sample design workflow.
While this diagram shows a linear progression, in practice, many people are
working on different components at the same time. It is also an iterative process.
For example, to use Interact API to configure the touchpoint to work with Interact,
the administrator must reference events that are created in the interactive channel.
As the Interact administrator configures the touchpoint in the runtime
environment, the administrator might realize that more events are needed. After
they are approved by the design team, the Interact user creates these events in the
design environment.

Planning your visitor interaction
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 the Interact
implementation requires the coordination of several components.
Determine how to interact with the visitors
The first step of designing the implementation is asking, "How and where do I
want to interact with my customers?"
This question has an almost unlimited number of answers, for example:

v Are you considering integrating with a website, an interactive voice response
(IVR) system, or a point of sale (POS) system?
v Do you want to display banner ads that are based onsite 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
might need to ask this question several times.
Define the components you configure in Interact
After the team identifies the strategy, you list and define what configuration
components the Interact user creates in Interact. The Interact user must coordinate
with the Interact administrator to define what interaction points and events must
be created with the Interact API.
The team must also consider what offers to present, how you segment the visitors,
and what sampling, integration, or tracking strategies to use. The answers to these
questions help define what information to create in the profile database. At the
same time, consider how to organize the interaction points into groups or zones
that are meant to serve a common purpose to fine-tune your offer presentation.
Evaluate extra options
There are several optional features, including offer suppression, learning,

individual offer assignments, and score override, which the team might 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.
Consider performance
Since performance is a part of Interact, the team must consider the data that is
required to segment the customers. Since there is a performance impact each time
data is retrieved from the database, carefully design the information that is
provided for the runtime environments. For more information about designing and
maintaining customer data, see the Interact Administrator's Guide.
Logging in to IBM EMM

Use this procedure to log in to IBM EMM.

Before you begin
You need the following.

v An intranet (network) connection to access your IBM EMM server.
v A supported browser installed on your computer.
v User name and password to sign in to IBM EMM.
v The URL to access IBM EMM on your network.
The URL is:
http://host.domain.com:port/unica
where
host is the machine where Marketing Platform is installed.
domain.com is the domain in which the host machine resides
port is the port number on which Marketing Platform application server is

listening.
Note: The following procedure assumes you are logging in with an account that
has Admin access to Marketing Platform.
Procedure
Access the IBM EMM URL using your browser.

v If IBM EMM is configured to integrate with Windows Active Directory or with a
web access control platform, and you are logged in to that system, you see the
default dashboard page. Your login is complete.
v If you see the login screen, log in using the default administrator credentials. In
a single-partition environment, use asm_admin with password as the password. In
a multi-partition environment, use platform_admin with password as the
password.
A prompt asks you to change the password. You can enter the existing
password, but for good security you should choose a new one.
v If IBM EMM is configured to use SSL, you may be prompted to accept a digital
security certificate the first time you sign in. Click Yes to accept the certificate.
If your login is successful, IBM EMM displays the default dashboard page.
Results
With the default permissions assigned to Marketing Platform administrator

accounts, you can administer user accounts and security using the options listed
under the Settings menu. To perform the highest level administration tasks for
IBM EMM dashboards, you must log in as platform_admin.
Setting your start page

The start page is the page that displays when you log in to IBM EMM. The default
start page is the default dashboard, but you can easily specify a different start
page.

If you do not want a dashboard page to display when you first log in to IBM
EMM, you can select a page from one of the installed IBM products as your start
page.
To set a page you are viewing as your start page, select Settings > Set current
page as home. Pages available for selection as a start page are determined by each
IBM EMM product and by your permissions in IBM EMM.
On any page you are viewing, if the Set current page as home option is enabled,
you can set the page as your start page.
Interact documentation and help

Interact provides documentation and help for users, administrators, and
developers.
Use the following table to get information about how to get started with Interact:
Table 1. Get up and running
Task Documentation
View a list of new features, known issues, IBM Interact Release Notes
and workarounds
Learn about the structure of the Interact IBM Interact System Tables and Data Dictionary
database
Install or upgrade Interact and deploy the One of the following guides:
Interact web application v IBM Interact Installation Guide
v IBM Interact Upgrade Guide
®
Implement the IBM Cognos reports IBM EMM Reports Installation and
provided with Interact Configuration Guide
Use the following table to get information about how to configure and use Interact:
Table 2. Configure and use Interact
Task Documentation
v Maintain users and roles IBM Interact Administrator's Guide

v Maintain data sources
v Configure Interact optional offer serving
features
v Monitor and maintain runtime
environment performance
v Work with interactive channels, events, IBM Interact User's Guide

learning models, and offers
v Create and deploy interactive flowcharts
v View Interact reports
Use Interact macros IBM Macros for IBM EMM: User's Guide
Adjust components to obtain optimal IBM Interact Tuning Guide
performance
Use the following table to get information about how to get help if you face issues
when you use Interact:

Table 3. Get help
Task Instructions
Open online help 1. Choose Help > Help for this page to
open a context-sensitive help topic.
2. Click the Show Navigation icon in the
help window to display the full help.
Obtain PDFs Use either of the following methods:
v Choose Help > Product Documentation
to access Interact PDFs.
v Choose Help > All IBM EMM Suite
Documentation to access all available
documentation.
Get support Go to http://www.ibm.com/support to
access the IBM Support Portal.

Chapter 2. Create the marketing campaign in the design
environment
Designing the Interact configuration is a multi-step process that involves many
people in your organization. You work with theInteract user interface, the Interact
API, and Campaign flowcharts to configure your interactive marketing campaign.
Workflow diagram
This diagram is an extract from the full design workflow, and shows only the
configuration tasks that you do in the design environment.
Interaction Create Interaction
Interactive Channel
Zones
Points Points
Campaign
Categories Events Create Events
Session
Smart Create Interactive
Segments Flowchart
Interact
API
Touchpoint
Offers Define Offers

Strategy tab
Interaction
Create Treatment
Rules
Cells
campaign
Task Flow
Override Target
Cells tab
Target
Campaign and Interact

and Control Cells
component creation Codes (optional)
and use
The diagram shows a linear progression even though several people can be
working on different components at the same time. It is also an iterative process.
For example, as you work with treatment rules, you might discover that you need
to reorganize your interaction points and zones. Working with Interact
configurations is also related to creating and working with traditional campaigns.

Sample workflow
A sample workflow can contain the following steps:

1. Create an interactive channel to hold the resources for your touchpoint with the
visitor.
2. Create interaction points that the visitor uses to interact with the touchpoint.
3. Create events that trigger actions when the visitor makes selections in the
touchpoint.
4. Use interactive flowcharts to define smart segments to assign offers to visitors.
5. Define offers to present to the visitor.
6. Define treatment rules to refine the offers that are presented to the visitor.
7. (Optional) Override the content of the target and control cells that are assigned
to segments.
8. Deploy the interaction.
After the Interact administrator deploys the configurations to the runtime servers,
and the touchpoint is integrated with the Interact API, your Interact
implementation is complete.
Configuration information shared by the user interface and the Interact

API
Configuring Interact to work with your touchpoint involves two Interact
components. The Interact user interface where you define the configuration in the
design environment. The Interact API that the Interact administrator configures for
the touchpoint to work in the runtime environment.
While these two components of configuration take place in two different areas,
they are related. The Interact API must reference several of the configuration
elements within the design environment. You and the person who works with the
Interact API must work together to agree on naming conventions, element
purpose, and so on. The design is an iterative and collaborative process. As the
person works with the Interact API and the touchpoint, you might have to create
more events and interaction points. As you design the interaction in the design
environment, you might have more requirements for the person who works with
the API.
Element shared by name
Several elements of the Interact configuration are referenced by the Interact API.
However, only the following three elements are referred to by name:
v Interactive channels
v Interaction points
v events
When you work with the Interact API, you must reference these elements by name.
These names must match and they are case insensitive. The names myinteract,
myInteract, and mYiNtErAcT all match.
Interact API and runtime information requests
During runtime, the Interact API does request information from interactive
flowcharts and treatment rules, however the API calls for that information

indirectly. For example, the API never calls an interactive flowchart. However, the
API does call an event that requests a resegmentation, which runs all of the
interactive flowcharts that are associated with the interactive channel. Likewise,
when the API requests offers with the getOffers method, that starts a sequence of
events that includes referencing the treatment rules.
Shared Campaign elements
Several Campaign elements can be used in your Interact configuration. You can
use these elements in the Interact API to enhance your interaction, including smart
segments, campaign start and end dates, offers, and interactive flowcharts.
Use the Interact API to reference these Campaign elements:

v Audience ID
v Audience level
v Custom offer attributes
v Offer code
v Offer description
v Offer effective date
v Offer expiration date
v Offer name
v Offer treatment code
Since these elements are shared across the whole of the design environment, you
must decide standards for these elements across your organization. Some of this
information you must provide to properly call the Interact API, such as audience
ID, and some you request with the API, such as offer attributes.
You can also reference the score for an offer with the Interact API. In general, this
score is the marketing score that is assigned to an interaction strategy. This score is
relevant for Interact only, not your entire Campaign environment. You can modify
or override the marketing score. For more information about the Interact API, see
the Interact Administrator's Guide.
Interact API interactions in the runtime environment
When a runtime session starts, that is, when the visitor initiates a contact, the
Interact API triggers a startSession. This call can include:
1. Creating a runtime session.
A runtime session is an instance on the runtime server, which contains all data
that is associated with the visitor. This instance includes all known profile data
and the results of any requests to the runtime server, such as segment
membership or a list of offers.
2. Loading the visitor profile data into the runtime session.
3. Running all interactive flowcharts that are associated with the interactive
channel and places the visitor into segments.
As the visitor interacts with the touchpoint, the Interact API can complete several
actions that include triggering events, requesting profile information, and changing
the audience level of the visitor. When the visitor reaches an interaction point in
the touchpoint, the Interact API can request one or more offers or trigger an event.
When the visitor leaves the touchpoint by logging out, hanging up, or timing out,
the runtime server ends the runtime session.
Chapter 2. Create the marketing campaign in the design environment 21

Use interactive channels to coordinate your touchpoint resources
An interactive channel is a representation of a client-facing touchpoint that is used
to coordinate all of the objects, data, and server resources that are involved in
interactive marketing.
Guidelines
In general, create one interactive channel for each touchpoint you are integrating
with Interact. For example, if you have a website and a call center to integrate
withInteract, create two interactive channels, one for each type of touchpoint.
You might also want to create different interactive channels for representing
same-type touchpoints. For example, if you have different websites for your
company's different brands, create an interactive channel for each brand, even if
each site is hosted on the same server.
Interactive channels and the other components

Interactive channels are where you organize and configure several components of
the interaction configuration, including interaction points, zones, events, and
categories. The interactive channel is also where you map profile tables and deploy
the interaction's processes and strategies to the runtime servers. You can find links
to the other components of the interaction configuration (interactive flowcharts and
treatment rules) on the Interactive Channel page in the user interface.
Interactive channels and the Interact API
Interactive channels are one of the three elements of the Interact configuration in
Campaign that interacts directly with the Interact API. You must use the exact
name of the Interactive channel when you use the startSession method in the
API. This name is case insensitive.
Number of interactive channels used
You can have as many interactive channels as required for your organization.
Different campaigns can reference the same interactive channel for the interaction
strategy. The interaction strategies for the interactive channel are accessed from the
Interactive Channel page.
For example, you have one campaign for new cell phones and another campaign
for new calling plans and each campaign has an interaction strategy for the
website interactive channel. The same campaign can have several interactive
strategies, each referencing a different interactive channel. Therefore, the new cell
phone campaign can have an interaction strategy for the website and an interaction
strategy for the call center.
Restrict how often an offer is presented

You can set the maximum number of times an offer is presented to a visitor in a
single runtime session. Default strings that you enter for offers that are presented
to everyone regardless of their actions are not counted.

Set the maximum number of times an offer is presented
You can set the number of times your touchpoint can display a single offer to a
single visitor during a single runtime session. This number is tracked by the
number of times the offer is logged as a contact, not by the number of times the
runtime environment recommends an offer. If you never log offer contacts, the
runtime environment assumes that the offer is not presented, and therefore
continues to recommend the offer, even if the maximum is exceeded.
Default strings not counted as offers
The runtime environment also does not consider default strings as offers for
calculating the maximum number of times an offer can be shown. For example, all
your interaction points have the same default string that presents the same default
offer and something happened on your network so that the touchpoint cannot
reach the runtime server. Therefore, the touchpoint displays the default string from
the interaction point. Although the touchpoint is presenting the same offer multiple
times, none of the times the offer is presented are counted.
Creating an interactive channel to coordinate your interactive

campaign resources
Use an interactive channel to coordinate all the objects, data, and server resources
that are involved in interactive marketing. You specify a security policy for the
channel. You can create a security policy or you can use the default security policy.
Before you begin

Before you begin this task, you must have this information:
1. Name of the interactive channel.
2. Description for the interactive channel.
3. Security Policy for the interactive channel. If you did not create any security
policies, the default global policy is selected for you, and you cannot change it.
You cannot edit the security policy for the interactive channel after you create
the interactive channel.
4. Server group for the interactive channel.
5. The production server for the interactive channel.
6. Maximum number of times you want to show an offer to a visitor in a single
session on this interactive channel.
About this task
You create an interactive channel to coordinate the resources for your interactive
campaign strategy. You create the interactive channel before you create any of the
other resources for the interactive campaign strategy. You can edit or delete any
interactive channels that you created.
To edit the interactive channel, click the Edit Summary icon on the Interactive
Channel Summary page.
To delete an interactive channel, select the check box next to the interactive channel
on the All interactive channels page and click the Delete Selected icon. When you
delete an interactive channel, you delete all interaction points and events that are
associated with it. Whether you can delete the interactive channel, depends on the
deployment status of the interactive channel.

Procedure
1. Select Campaign > Interactive Channels.
The All interactive channels page opens.
2. Click the Add an Interactive Channel icon on the All interactive channels page.
The Add/Edit Interactive Channel page opens.
3. Enter a Name and Description for the interactive channel. The name and
description you enter here are for your reference, and is displayed in windows
and reports.
4. Select the Security Policy for the interactive channel.
5. Select the server groups that you want to associate with this interactive channel
from the Runtime Server Groups list.
You can select multiple server groups by using Shift+Click or Ctrl+Click.
6. Select the production server from the Production Runtime Server Groups list.
7. Enter the Maximum # of times to show any offer during a single visit.
8. Click Save Changes.
About table mapping

Mapping tables is the process of making external customer or system tables
accessible in IBM Campaign.
A table mapping is the metadata that is used to define a base, dimension, or

general table. It contains information on the data source, the table name and
location, the table fields, audience levels, and data. Table mappings can be stored
for re-use in table catalogs.
Accessing the audience levels defined in Campaign in your

interactive strategy
To access the audience levels that are defined in Campaign in your interactive
strategy, you map the profile table to the interactive channel. Use the Interactive
Channel Summary page on to map the profile table for the interactive channel. You
use the "Map profile tables for Audience Level" wizard to complete this task.
Before you begin
Before you begin this task, you must have this information for the "Map profile
tables for Audience Level" wizard:
1. Name of the table you want to map. This table contains the audience identifier
that is defined in the Campaign > partitions > partitionN > Interact >
flowchart > datasource category
2. Whether to load the data into memory when a visitor interactive session starts.
3. IBM Table Name of the table as it appears in the Interactive Flowcharts.
4. Table details field name that is displayed in the Interactive Flowcharts.
About this task
You must map a profile table before you can map any dimension tables.
When the "Map profile tables for Audience Level" wizard validates the table
mapping, it references the data source that is defined in the Campaign > partitions
> partitionN > Interact > flowchart > datasource property. All interactive
channels must reference the same data source. This data source is for test runs
only.

To edit the profile table mapping, click the name of the Mapped Profile Table and
complete the "Map profile tables for Audience Level" wizard.
Procedure
1. In the Interactive Channel window, on theInteractive Channel Summary page,
click unmapped for the audience level you want to map under Mapped Profile
table.
The "Map profile tables for Audience Level" wizard opens.
2. Complete the "Map profile tables for Audience Level" wizard.
Accessing a dimension table from Campaign in your interactive

strategy
To access a dimension table from Campaign in your interactive strategy, you map
the dimension table joined to the profile table to the interactive channel. Use the
Interactive Channel Summary page to map the dimension table for the interactive
channel. You use the "Map profile tables for Audience Level" wizard to complete
this task.
Before you begin
You must map the profile tables for the interactive channel before you can map the
dimension tables.
Before you begin this task, you must have this information for the "Map profile
tables for Audience Level" wizard:
1. Name of the dimension table you want to map.
2. Name of the table to which you are mapping the dimension table.
3. Fields in the base table to which you are mapping the dimension table key
fields.
4. Join type for the tables. Either auto-selected, inner join, or outer join.
About this task
The "Map profile tables for Audience Level" wizard uses the data source that is
defined in the Campaign > partitions > partitionN > Interact > flowchart >
datasource property.
All interactive channels must reference the same data source.
Procedure
1. In the Interactive Channel window, on the Summary tab, click the name of
profile table under Mapped Profile table.
The "Map profile tables for Audience Level" wizard is displayed.
2. Click Map a new Dimension table.
3. Complete the Map Profile tables for Audience Level wizard.
Map Profile Tables for Audience Level wizard

Use the Map Profile Tables for the Audience Level wizard to map profile and
dimension tables from Campaign to your interactive channel.
Requirements
When you are working with the wizard and you:

v Validate mapping, Interact uses your test run Interact server. Your test run
runtime server must be running for Check Syntax to function.
v Add or edit a dimension table, the schema must match the profile table schema.
Available tasks
Use the wizard to complete table mapping tasks:
Tasks Flow
Map a profile table 1. Click Unmapped for the audience level
that you want to map.
2. Complete the fields for the profile table.
3. Select Validate mapping to validate the
mapping.
4. Select Complete the change to finish the
mapping.
Map a dimension table You can map dimension tables only after
you define a profile table for the audience
level.
1. Click Map a new Dimension Table.
2. Complete the fields for the dimension
table.
3. Select Complete the change to finish the
mapping.
You do not validate this mapping.

Edit a table mapping When you edit a profile table mapping and
change the table or field names, Interact
unmaps all dimension tables that are
associated with the profile table.
1. Select the table that you want o edit.
2. Modify the fields for the table.
3. If you modify a profile table, Select
Validate mapping to validate the
mapping.
4. Select Complete the change to save the
mapping changes.
Unmap a table 1. Select the table that you want to unmap.
2. Click Unmap.
3. Select Complete the change to save the
changes.
Fields used when you select a profile table to map
This table lists and describes the fields that you use when you select a profile table
to map:

Table 4. Select a table to map
Field Description
Select a table to map This list is a list of all the tables in the data source that is
defined by the Campaign > partitions > partitionN >
Interact > flowchart > dataSource property.
If you are mapping the profile table, you must select a

table that contains the audience ID defined in the Campaign
> partitions > partitionN > AudienceLevels category.
Each audience ID column maps name for name.
Load this data in to memory Select this check box to load the record that is associated
when a visit session starts with the Audience member into the runtime session when
the session starts. If you select this feature for all
dimension tables in the interactive channel, all database
reads for the selected audience level occur at the start of a
runtime session. The process of reading a database at the
start of a runtime session so that all subsequent data
requests during the runtime session are faster can improve
overall runtime performance. You can reload data from
tables by using the setAudience method. If you load all
data in to memory, while it can improve performance, it
also increases the memory requirements for the system.
IBM Table Name The name of the table as it is displayed in Interactive
flowcharts. You can change how the table name displays in
interactive flowcharts to make it easier for your flowchart
designers to select the correct tables. The name cannot be
empty, must begin with a letter, and can contain only
alphanumeric characters and underscores. The IBM table
name must also be unique within the table mapping, per
audience level, per interactive channel.
Table details The Table details field displays information for the field:
v The field name as it is displayed in the real data source,
v The IBM Field Name as it is displayed in the Interactive
flowcharts,
v The field Type,
v Whether this field is a Audience Key field.
If you are mapping a profile table, most of this table is

disabled. The fields that match the audience ID fields have
Audience Key selected. You can define Default values for
every field.
If you are mapping a dimension table, the Audience Key

column is enabled. Select the Audience Key check box for
the fields upon which you want to join the dimension table
to the base table.
Fields used when you map a dimension table to a base profile table
This table lists and describes the fields that you use when you select a table to
map:
Table 5. Map Dimension to Base
Field Description
The dimension table relates to Select the table to which you want to join this dimension
the following base table table.

Table 5. Map Dimension to Base (continued)
Field Description
Matching base table field Select the fields from the base table to which the Key fields
in the dimension table map.
Join type Select how you want to join the tables. Valid choices are
Auto-selected, Inner Join, and Outer Join.
Interactive Channel Summary page

Use the Interactive Channel Summary page to view a summary of the settings for
the interactive channel.
The Interactive Channel Summary page contains two main sections: the
Interactive Channel Summary and the Flowcharts and Strategies.
Interactive channel summary
This table lists and described the summary section of the Interactive Channel
Summary page:
Table 6. Description of the Interactive Channel Summary section
Heading Description
Description The description for the interactive channel. The more detailed
the description, the better other design environment users
understand the purpose of this particular interactive channel.
You can change this value by clicking the Edit icon and
modifying the description in the dialog that is displayed.
Security Policy The security policy applicable for this interactive channel. This
value is specified when you create the interactive channel. You
cannot change the security policy on an existing interactive
channel.
Runtime Server Groups A list of the runtime server groups available for this interactive
channel.
modifying the runtime server groups in the dialog that is
displayed.
Production Runtime The runtime server group that you chose for your live,
Server Group customer-facing touchpoint.
modifying the production runtime server group in the dialog
that is displayed.
Maximum # times to An integer that defines the maximum number of times to show
show any offer during a a particular offer during a single visit. The runtime
single visit environment uses this number along with treatment rules and
the learning engine when you choose offers to display.
modifying the value in the dialog that is displayed.
Learning Mode Whether the interactive channel uses the global learning
model, uses the marketer's scores only for offer weighting, or
uses the custom learning model that you specified in the New
Interactive Channel or Edit Interactive Channel dialogs.

Table 6. Description of the Interactive Channel Summary section (continued)
Heading Description
Mapped Profile Table Displays the IBM name and actual name for the profile table
for each audience level that is defined in Campaign.
If no profile tables are defined, this displays unmapped.
The name of the table or unmapped is a link to the "Map

Profile Table for Audience Level" wizard, where you can map
profile and dimension tables for the interactive channel.
The number of profile tables that you mapped is listed as the

number of supported audience levels. You might have more
audience levels that are defined in Campaign than you require
for your touchpoint. You do not have to define profile tables
for all audiences, only the audiences you use with your
interaction on your touchpoint.
Flowcharts and Strategies
The Flowcharts and Strategies section the flowcharts and interactive strategies that
are defined and associated with this interactive channel. This table lists and
describes the flowchart and strategy information that is shown:
Table 7. Description of the Flowcharts and Strategies section
Heading Description
Associated Flowcharts A listing of all flowcharts that are associated
with this interactive channel.
Each flowchart that is listed here is a link

that opens the flowchart where you can
view or edit it as needed.
Associated Strategies A listing of all strategies that are associated
with this interactive channel.
Each strategy that is listed here is a link that

opens the interactive strategy where you can
view and edit the treatment rules. You can
also mark or unmark the interactive strategy
for deployment.
View the treatment rule inventory A link that displays the Channel Treatment
Rule Inventory report, which is filtered for
this interactive channel.
View Deployment History A link that displays the Channel
Deployment History report for this
interactive channel. You can also view the
interactive channel's deployment history in a
different format on its deployment tab.
Edit Summary Displays the Interactive Channel Summary
dialog where you can modify most of the
information in the Interactive Channel
Summary section. Clicking Edit Summary is
the same as clicking the Edit icon at the top
of the Summary tab.

Group your interaction points into zones
You use zones to divide your interaction points into similar areas in your
touchpoint. You can use zones to make your treatment rules more specific. You can
move interaction points between zones. An interaction point can be a member of
only one zone at a time.
For example, if you divide your website into sections by product type such as
calling plans and phones for a telecommunications company. You organize your
interaction points into zones that are related to the product type. In your treatment
rules, you assign different offers to the same segment, depending on which zone
the customer is viewing. When the visitor is in the calling plans zone, the visitor
sees offers relating to new calling plans with better rates only. When the visitor
moves to the phones zone of the touchpoint, all the offers are targeted for new cell
phones.
Adding zones for your interaction points to the interactive

channel
When you define interaction points for your visitors, you can further specialize
those interaction points by adding them to zones. Each zone can have its own set
of rules that determine how offers are presented to visitors. Use the Add Zone icon
on the Interaction Points tab of the Interactive Channel window to add a zone.
About this task
Procedure
1. Click the Add Zone icon on the Interaction Points tab of the Interactive
Channel window.
The Add/Edit Zone dialog is displayed.
2. Enter a Name for the zone.
3. Enter a Description for the zone.
This description that you enter here is displayed on the Interaction Points tab
of the Interactive Channel window after you save the zone.
4. Optional: Click the Advanced Features link to display more settings that you
can apply to the zone.
If you display the advanced features, you can determine the following settings
for the zone you are adding or editing:
Learning Mode. The Learning Mode section specifies the rules by which
learning is applied to the zone you are creating or editing. You can choose any
of the following settings:
v Inherit from Interactive Channel is the default setting, and tells Interact to
use the learning mode that is specified for the interactive channel.
v Use Marketer's Scores Only indicates that Interact uses only the marketer's
scores for offer weighting.
v Use Custom Learning Model uses a custom learning model that you can
specify from the drop-down by name. If no custom learning models are
defined for this interactive channel, this option is dimmed and cannot be
selected.
For rule groups in this zone, resolve non-uniform learning rules by handles a
situation where there is a conflict between how offers are sorted in a
mixed-learning scenario, such as when some offers are suggested by sources in
which learning is enabled, and other offers are suggested from sources where

learning is disabled. For example, because each zone and each treatment rule
group can define its own learning rule, and the rule that is defined for a
treatment rule group can be different from the rule that is defined for the zone,
the choices here determine how Interact resolves that conflict.
There are several different levels in Interact at which learning can be enabled or
disabled: globally, for each interactive channel, for each treatment rule group,
and for each zone. The choices in the For rule groups in this zone, resolve
non-uniform learning rules by section provide the following solutions to the
conflict:
v Intermixing - Use Learning Mode for this zone (Default) indicates that the
sequence of offers is selected based on the highest score first, regardless of
the built-in learning score.
v Prioritizing Non-learning Offers indicates that the sequence of offers selects
non-learning offers first, followed by learning-based offers.
v Prioritizing Learning Offers indicates that the sequence of offers selects
learning offers first, followed by non-learning-based offers.
v Prioritizing Non-learning Offers: Dedupe provides the same results as the
Prioritizing Non-learning Offers option, but with duplicate offers removed
when the same offer is provided by learning and non-learning sources.
v Prioritizing Learning Offers: Dedupe provides the same results as the
Prioritizing Learning Offers option, but with duplicate offers removed when
the same offer is provided by learning and non-learning sources.
%Random specifies the chance that the returned offer is randomly selected,
without considering scores.
5. Click Save and Return to go back to the Interaction Points tab or Save and
Add Another to continue adding interaction points.
Results
To edit the name or description of a zone, click the name of the zone on the
Interaction Points tab.
To delete a zone, select the check box next to the zone on the Interaction Points tab
and click the Delete Selected icon. You cannot delete a zone while it is used in a
treatment rule.
Example
For example, suppose that you have a zone with four rule groups:
v Rule group Group1 has a learning module that is named LM1. LM1 contains
offer1 with a score of 50%, and offer2 with a score 60%.
v Rule group Group2 has no learning module.
v Rule group Group3 is inheriting for the zone.
v Rule group Group4 contains offer3 with a score of 65%, and offer4 with a score
of 45%. No learning model is assigned to this rule group. The Use marketer
score option is selected for this rule group.
In this example, offers for each particular zone have a mix of offers presented after
evaluating the score, using learning or no learning, depending on the
configuration. The following list describes some scenarios:
v If you select Intermixing - Use Learning Mode for this zone (Default) for this
zone, the sequence of offers to be selected are based on the highest score first,
regardless of the built-in learning score. Using the rule groups above, the

sequence would be Offer3 weighted at 65%, Offer2 weighted at 60%, Offer1
weighted at 50%, and Offer4 weighted at 40%.
v If you select Prioritizing Non-learning Offers for the zone, the sequence of
offers is based on non-learning offers being selected first, so the sequence that
uses the example rule groups would be offer3 non-learning, offer4 non-learning,
offer1 with learning, and finally offer2.
v If you select Learning - Prioritizing Learning Offers for this zone, the sequence
of offers to be selected are based on selecting the learning offers first, so the
sequence that uses the example rule groups would be offer1 Learning, offer2
Learning, offer3 non-learning, and finally offer4.
v If you select Non learning - Prioritizing Non-learning Offers: Dedupe for the
zone, the results would be the same as when you select Prioritizing
Non-learning Offers; however, the results would remove duplicate offers.
v If you select Prioritizing Learning Offers: Dedupe for the zone, the results
would be the same as when you select Prioritizing Learning Offers; however,
the results would remove duplicate offers.
v If you specify a value for the Related to % Random field, that value would be
used only when the learning mode is enabled. Offers other than the high
priority would be prioritized according to the specified percentage.
Create interaction points for the visitor to interact with your

touchpoint
An interaction point is how you identify where in your touchpoint you request
information. You organize all of your interaction points in zones. When you define
which offers go to which segments in your treatment rules, you can also define
these rules by zone. Therefore, you can have different types of offers available for
different sections of your touchpoint.
Every interaction point must contain some default string that the touchpoint can
use if there are no offers available.
Interaction points and the Interact API
An interaction point is one of the three elements of the Interact configuration in

the design environment that interacts directly with the Interact API. Whenever you
use the getOffers or postEvent methods in the Interact API, you must reference an
interaction point. The name of the interaction point that is used in the Interact API
must match the name of the interaction point as configured in the design
environment.
Adding visitor interaction points to your touchpoint interactive

channel
Use this task to add a place for the visitor to interact with your touchpoint. Use
the Add Interaction Points icon on the Interaction Points tab of the Interactive
Channel window to add an interaction point.
About this task
You can edit an interaction point by clicking the name of the interaction point on
the Interaction Points page.
You can move an interaction point to another zone after it is created by selecting
the check box next to the interaction point and clicking the Move to icon.

You can delete an interaction point by selecting the check box next to the
interaction point and clicking the Delete Selected icon.
Procedure
1. Click the Add Interaction Points icon on the Interactive ChannelInteraction
Points page.
The Add/Edit Interaction Point dialog is displayed.
2. Enter a Name for the interaction point.
3. Select a Zone.
4. Enter the Default String to return.
5. Enter a Description for the interaction point.
This description displays on the Interaction Points page.
6. Click Save and Return to go back to the Interaction Points tab or Save and
Add Another to continue adding interaction points.
Interaction point tab reference

There are several icons on the Interaction point tab that you use to manage
interaction points.
This table lists and describes the icons used to manage interaction points:
Icon Name Description

Add Zones Click to add a zone to this interactive channel.
Add Interaction Points Click to add an interaction point to this interactive channel.
Move to Select interaction points then click this icon to move the
selected interaction points to a new zone.
Delete Selected Select interaction points or zones, then click this icon to
delete them.
Define the events that are triggered by visitor actions

An event is an action, which is taken by a visitor, that triggers an action in the
runtime environment. The action might place a visitor into a segment, present an
offer, or log data. Within the Interact design environment, you can create an event
as one of the elements of configuration that interacts directly with the Interact API.
Example events
For example, you might create any of the following events:

v End Session. Mark the end of a visitor's interactive session.
v Get Offer. Request a list of recommended offers to serve to a visitor.
v Get Profile. Request visitor profile data that is stored in the session, including
includes temporal data and data read in from the profile table.
v Set Audience. Change a visitor's audience level within the interactive session.
v Set Debug. Override the current logging level for a visitor's interactive session.
v Start Session. Mark the start of a visitor's interactive session.

Event naming and the Interact API
When you are coding your touchpoint to work with the Interact API, you use the
postEvent method to reference events. The name of the event that is used in the
Interact API must match the name of the event as configured in the design
environment. This name is not case-sensitive.
Monitor events
To monitor how often all of these events occur on your touchpoint, see “About the
Channel Event Activity Summary report” on page 106.
Pre-defined actions
An event triggers one or more of the following pre-defined actions:
v Trigger Re-segmentation. The runtime environment runs all the interactive
flowcharts for the current audience level that is associated with the interactive
channel again, by using the current data in the visitor's session.
When you design your interaction, unless you specify a specific flowchart, a
resegmentation action runs all interactive flowcharts that are associated with this
interactive channel with the current audience level again, and that any request
for offers waits until all flowcharts are finished. Excessive resegmentation within
a single visit can affect the performance of the touchpoint in a customer-visible
way.
Place the customer in new segments after significant new data is added to the
runtime session object, such as new data from requests from the Interact API
(such as changing the audience) or customer actions (such as adding new items
to a wish list or shopping cart).
v Log Offer Contact. The runtime environment flags the recommended offers for
the database service to log the offers to contact history.
For web integrations, log the offer contact in the same call where you request
offers to minimize the number of requests between the touchpoint and the
runtime server.
If the touchpoint does not return the treatment codes for the offers that Interact
presented to the visitor, the runtime environment logs the last list of
recommended offers.
v Log Offer Acceptance. The runtime environment flags the selected offer for the
v Log Offer Rejection. The runtime environment flags the selected offer for the
v Trigger User Expression. An expression action is an action that you can define by
using Interact macros, including functions, variables, and operators, including
EXTERNALCALLOUT. You can assign the return value of the expression to any
profile attribute.
When you click the edit icon next to Trigger User Expression, the standard User
Expression editing dialog is displayed, and you can use this dialog to specify the
audience level, optional field name to which to assign the results, and the
definition of the expression itself.
v Trigger Events. You can use the Trigger Events action to enter an event name
that you want to be triggered by this action. If you enter an event that is already
defined, that event is triggered when this action is run. If the event name you
enter does not exist, this action causes the creation of that event with the
specified action.

Events, logging, and the Interact API
If you create an event with more than one log offer action, the Interact API
completes the same action for the associated offer. For this reason, do not create an
event that logs both offer acceptance and offer rejection since they contradict each
other. However, creating a single event to log offer contact and acceptance or offer
contact and rejection can be useful in your environment.
By default, the runtime environment can track two types of responses, offer
acceptance and offer rejection. You can modify the response types that the Log
Offer Acceptance and Log Offer Rejection events record by setting the accept and
reject configuration properties.
The Interact API can also use events to trigger actions that you define by using
event parameters in the API. These events include logging to a custom table,
tracking multiple response types, and specifying a specific flowchart to run. You
might have to create some events with no defined System Reaction, or several with
the same System Reaction, such as Log Contact, for use with the reserved event
parameters.
You might want to create several events with the Log Offer Acceptance action, one
for every response type you want to log, or a single event with the Log Offer
Acceptance action you use for every postEvent call you use to log separate
response types.
For example, create an event with the Log Offer Acceptance action for each type of
response. You define the following custom responses in the UA_UsrResponseType
table [as Name (code)]: Explore (EXP), Consider (CON), and Commit (CMT). You
then create three events and name them LogAccept_Explore, LogAccept_Consider,
and LogAccept_Commit. All three events are the same (have the Log Offer
Acceptance action), but the names are different so that the person who works with
the Interact API can distinguish between them.
Or, you might create a single event with the Log Offer Acceptance action that you
use for all custom response types. For example, name it LogCustomResponse.
When you are working with the Interact API, there is no functional difference
between the events, but the naming conventions can make the code clearer. Also, if
you give each custom response a separate name, the Channel Event Activity
Summary report displays more accurate information.
For more information about reserved parameters and the postEvent method, see
Events tab reference

There are several icon on the Events tab that you can use to manage events.
You can move the mouse cursor over each icon to see its name. This table lists and
describes the icons used to manage events:

Add Events Click to add an event to this interactive channel.
Add Event Patterns Click to define a new event pattern to this interactive
channel.
Move selected items to the Select one or more events or event patterns, then click this
following category icon to move the selected items to a new category.
Copy selected items Select one or more events or event patterns, then click this
icon to duplicate the selected items. Interact automatically
adds a numeric suffix to the names of each copy.
Delete Selected Items Select events or event patterns, then click this icon to delete
them.
Manage Categories Click to open a dialog box in which you can create, delete,
and edit categories in this interactive channel.
Adding an event and pre-defined action to your touchpoint

Use this task to add an event and the predefined action to take when the visitor
triggers the event.
About this task
You can edit an event by clicking the name of the event on the Events tab.
You can move an event to another category by selecting the event and clicking the
Move selected items to the following category icon.
You can delete an event by selecting the event and clicking the Delete selected
items icon.
Procedure
1. Click the Add Events icon on the Interactive Channel Events tab.
The Add Event dialog appears.
2. On the General tab, provide a name and description for this event that helps
you identify it.
The description appears on the events tab and is intended for your reference
only.
3. Optional: Choose a category in which you want to organize this event.
Categories are for your organizational purposes only, and do not affect the
operation or use of the event. You can move events to other categories after
they are created.
4. Click the Actions tab to continue defining this event.
5. On the Actions tab, select the Action that you want to associate with this event.
6. Click Save and Return to return to the Events tab or Save and Add Another to
continue adding events.
Use categories to group events

Categories are an organization tool for your events and event patterns. Categories
have no effect on your Interact configuration, other than to make it easier for you
to manage what can be hundreds of events or event patterns.

You create categories to organize your events and event patterns in whatever
groups make sense for your organization. For example, you can create categories
that are based on event purpose (such as "resegment" or "logContact") or where the
event pattern is used in the touchpoint (such as "cellPhoneCatalogPage" or
"newCallPlanScript").
You can move events and event patterns between categories. Each event or event
pattern can be a member of one category only.
Creating a category to group events

Use the Interaction Channel Events tab to add a category.
About this task
To edit the name or description of a category, select the category in the Manage
Categories dialog and click Edit.
To delete a category, select the category in the Manage Categories dialog and click
Delete.
Note:
If you delete a category that contains events or event patterns, all the events and
event patterns in the category are also deleted. Use the Delete button with caution.
Procedure
1. Click the Manage Categories icon on the Interactive Channel Events tab.
The Manage Categories dialog is displayed.
2. Click New to open the New Category dialog.
3. Enter a Category Name and Description.
4. Click OK to return to the Manage Categories dialog.
5. Click Close to return to the Events tab or click New to add more categories.
Use event patterns to personalize offers to the visitor

An event pattern is a flexible way to personalize offers that are based on patterns
of visitor activity. When the visitor's behavior matches the event patter that you
create, it triggers specific actions. Event patterns are sometimes referred to as
behavior triggers.
Event patterns identify visitor activity and behavior patterns
Event pattern data is audience identifier specific and spans interactive sessions.
Event pattern statuses are loaded at the beginning of each visitor interactive
session and stored at the end of each interactive session.
Event pattern types and interactive flowcharts
When you define an event pattern, you associate it with a single Interactive
Channel. After you define the event patterns that are available for an Interactive
Channel, you can use the patterns on your interactive flowchart.

You can define process boxes in the flowchart so that when an event pattern is
matched, the visitor is included in a predefined segment to which specific offers
are then assigned.
Examples
Here are some examples of events you might use in event patterns that result in
presenting relevant offers to your customers.
v A website visitor views a specified combination of pages, or visits certain pages
the specified number of times.
v A website visitor downloads specified documents or views specified media.
v A call center representative enters a specified reason for the call or a specified
service request that results from the call.
Event pattern types

You use event patterns to test whether one or more events occurred during an
interaction. When the specified event pattern is met, one or more actions are
triggered in response. Event patterns are optional.
Pattern types
The following types of event pattern are available.

v Match All. If all of the specified events occur, the pattern is true.
With this option, you can add one or more events to the Selected Events list.
v Counter. If the specified incoming events occur a specified number of times, the
pattern is true.
For example, you might require that the visitor generates a reject event 10 times,
or that the visitor requests contact one time.
v Weighted Counter. You assign a score to each event you specify, and the pattern
is true if a specified total score is reached.
Unlike the Match All option, all of the specified events do not have to occur; the
total score is what determines whether the pattern criteria are met.
Example
For example, suppose you configure the pattern as follows.

v You select firing conditions and assign the following scores.
– Firing condition 1 has a score of 1.
– Firing condition 2 has a score of 2.
v You specify a Weighted Counter value of 10.
The event pattern would be true in any of the following cases.

v Firing condition 1 occurs 10 times.
v Firing condition 1 occurs two times and Firing condition 2 occurs four times.
v Firing condition 2 occurs five times.
How Interact processes event pattern states and statuses

Event patterns respond to a visitor's interactive session with the runtime
environment by updating their states and statuses and passing them to the runtime
environment for processing.

Interact loads, tracks, and stores event pattern information:
v At the start of the session, Interact tries to load any previous event pattern states
that are associated with the current visitor's audience identifier, if event pattern
states exist.
v During the session, as an event is posted, Interact updates the states and statuses
of any event patterns that use the event. If an event pattern is used during the
session, such as during execution of an interactive flowchart, the status of the
event pattern is retrieved and updated.
v At the end of the session, the statuses are either stored or discarded. If the
audience identifier is found in the profile data source, the statuses of all the
updated event patterns that are associated with the visitor's audience identifier
are stored. Otherwise, the event pattern states are discarded.
Store states for unknown audience identifiers
The event pattern states for unknown users are discarded by default at the end of
the session. To change the default, set one of these values to TRUE:
v Configuration property interact | services | eventPattern |
persistUnknownUserStates
v Session parameter UACISavePatternStates
When the audience identifier changes in a session
If the audience identifier changes in the middle of a session, Interact tries to load
the saved event pattern states for the new audience identifier.
In some situations, the audience identifier changes during the session from
unknown to known. For example, a person enters a website, adds items to the cart,
then logs in to place the order. In these cases, the event activities that belong to the
initial audience identifier can be merged into the event activities that belong to the
new audience identifier. To merge the statuses, one of these values must be set to
TRUE:
v Configuration property interact | services | eventPattern |
persistUnknownUserStates
v Session parameter UACISavePatternStates
Event pattern states and statues are session independent
Event pattern states and statuses are stored by the visitor's audience identifier.
Event activities from one user session are reflected in another session, when the
audience identifier matches and both sessions are active when those events occur.
Creating an event pattern to identify visitor behavior patterns

You create event patterns to identify patterns of visitor activity and behavior, and
to complete specific actions when those patterns are identified. Use the Add Event
Pattern icon on the Interactive Channel toolbar to add an event pattern.
About this task
After you create event patterns, they become available within the design
environment, appearing in interactive flowcharts in Select, Decision, and
PopulateSeg process boxes, and in the Interact List process box in batch
flowcharts. In those flowchart processes, you can define your queries to run the

action you define when the event patterns are identified and the visitor is
presented with the appropriate offers.
Procedure
1. Click the Add Event Pattern icon on the Interactive Channel toolbar.
2. On the General page, give the pattern a name, description, and start and end
dates, and specify whether it is enabled.
3. On the Pattern page, specify the pattern type and select one or more events
that must occur to fulfill the event pattern and set its state to true.
offerAccepted, offerContacted, offerRejected, offerAcceptedInCategory,
offerContactedInCategory, and offerRejectedInCategory are predefined events
that are also available. If you add offerAccepted, offerContacted, or
offerRejected, you are prompted to select an offer that triggers the macro. If
you add offerAcceptedInCategory, offerContactedInCategory, or
offerRejectedInCategory, you are prompted to set attribute values of the offers
that triggered the macros. You can add each of these macros multiple times
with different offers or offer attributes and values for each event pattern.
You can edit eventInCategory macros by double-clicking the macro in the
Selected Events list.
Note: The predefined events are not available for POST events.
Specify an extended time span during which the pattern retains its true state
before it resets and begins evaluating events again.
4. On the Actions page, specify which actions you want to occur when the event
pattern criteria are met.
5. Click Save and Return to close the Event Pattern dialog, or click Save and Add
Another to save the event pattern and create an event pattern.
Fields you use to configure event patterns

You use the Interactive Channel Events page to configure event patterns.
Some pattern types and fields are available only when advanced patterns are
enabled by integrating Interact with Interact Advanced Patterns.
See the IBM Interact Advanced Patterns and IBM Interact Integration Guide for details.
This table lists and describes the fields on the Event Patterns page.
Table 8. Fields in the Event Patterns definition window
Fields Description
General page
Name Enter a descriptive name for the event pattern. This name appears
in the Event Patterns list on the Events page.
Enable check box Select this check box when the event pattern is ready to be used.
Category Optionally, enter a category for this event pattern. The category has
no effect on how the event pattern operates; it is used solely for
your organizational purposes.
This category appears in the Event Patterns list on the Events page.
Description Optionally, enter a description for this event pattern.
This description appears in the Event Patterns list on the Events

page.

Table 8. Fields in the Event Patterns definition window (continued)
Fields Description
Start Date Time and Optionally, specify the date range during which you want the event
End Date Time pattern to be valid. The date fields are used in the following ways:
v If no dates are specified, the event pattern is valid while it is
deployed.
v If you specify only a start date, the event pattern is valid from
that date and time until it is no longer deployed.
v If you specify only an end date, the event pattern is valid from
the time it is deployed until the end date and time.
v If you specify both a start and end date, the event pattern is
valid only during the specified range.
The following applies to the advanced patterns.

v If no end date is specified, January 30, 2099 is used as the end
date.
v If no start date is specified, December 26, 2000 is used as the
start date.
Pattern page
Pattern Type Select how the event pattern is evaluated. Options are Match All,
Counter, and Weighted Counter. For the Counter and Weighted
Counter pattern types, you set more fields:
v Counter
For the Pattern fires when the occurrences of the select Event
are >= field, set the number of times the events must occur for
the pattern to become true.
v Weighted Counter
For the Pattern fires when TOTAL score = field, set the total
score that the weighted event or events must reach for the
pattern to become true.
Rolling time and Time bound versions of each of the three basic
patterns are available when advanced patterns are enabled.
Available Event and Select from the list of events you defined in Interact design time.
Selected Event Click the arrow buttons to add the events as criteria or remove
them from criteria.
Extend true state for Optionally, use this field to specify how long the pattern state
additional: time span remains true after its conditions are met. After the specified time
span is over, the pattern status is set to false and the pattern begins
evaluating events again.
Events must occur Specify the time span for which events are evaluated.
within time span
This field applies only to the advanced patterns.
Actions page
Actions list Select one or more actions to complete. Optionally, use the
Conditions feature to test values against your pre-defined event
parameters.
See “Define the events that are triggered by visitor actions” on

page 33 for a description of the events in this list.

Use constraints to limit the number of times an offer is presented
Offer constraints are a way to limit the number of times an offer or a collection of
offers can be presented over defined periods of time. For example, you might want
to suppress an offer after a predefined number of impressions in one day or to
distribute offers on a webpage among different product lines.
By using the Constraints tab in Interact, you can create, delete, enable, or disable
an offer constraint.
Creating a constraint for an offer

Use this task to set a time and date range for presenting an offer. You can also set
the number of times an offer is shown in a specified time and date range. Use the
Constraints page to add an offer constraint.
About this task
You can edit a constraint by clicking the name of the constraint on the Constraints
tab.
You can delete an offer constraint by selecting the check box next to its name and
clicking the Delete Selected icon.
Procedure
1. Click the Add Constraints icon on the Constraints tab of an Interactive
Channel.
The Add/Edit Constraints dialog appears.
2. Enter a Name for the offer constraint.
3. Enter a Description for the constraint.
This description appears on the Constraints tab to identify this offer constraint.
4. Specify the offers to which to apply the constraint by selecting in Folder or in
Offer List. Use the accompanying drop-down list to select the folder or offer
list that you want.
You can specify that the offers be available during a specific range of dates and
times, be available up to a maximum number of times within a specific period,
or both.
5. Specify the range of dates during which the offers can be made available:
a. Click Start serving offers after and use the calendar tool that opens to
specify the earliest date on which the offers can become available. Use the
drop-down list next to the Start serving offers after field to select the
earliest time that the offers can become available.
b. Click Stop serving offers by and use the calendar tool that opens to specify
the last date on which the offers can become available. Use the drop-down
list next to the Stop serving offers by field to select the time they stop
being available.
6. Optional: Complete the Distribute evenly with fields to specify the maximum
number of impressions you want the offers to be displayed within a single time
period.
v Enter the maximum number of times you want the offers to be displayed in
the at most <number> impressions field (replacing <number> with the
actual maximum number you require).

v Use the per drop-down list to specify the time period in which you want the
maximum number of impressions to be served to visitors. For example, per
hour, per day.
If you do not complete the Distribute evenly fields, the Interact server makes
the offers available as usual for this interaction channel.
7. Optional: Enter the maximum overall number of times you want the offers to
be served in the Impressions field.
If you do not enter a value in this field, no maximum number of offers
constraint is applied.
8. Click Enable to make this offer constraint active within the parameters you
defined.
9. Click Save and Return to go back to the Constraints tab or Save and Add
Another to continue adding offer constraints
Modifying a constraint to change when an offer is presented

You can modify the name, description, or the definition settings of a constraint.
Procedure
1. Click the Constraints tab of an interactive channel to view the list of
constraints.
2. Click the name of the constraint you want to edit.
The Add/Edit Constraints window opens.
3. Modify the Name, Description, or definition settings of the constraint.
4. Click Save and Return to go back to the Constraints page or Save and Add
Another to save your changes and add another constraint.
Enabling or disabling an offer constraint

Sometimes you want to run offers without any constraints or restrictions for
limited duration. In this case, you can disable and enable constraints.
About this task
Offer constraints are defined with a range of time during which it is used.
However, there might be times when you want to prevent the offer constraint from
being:
v Used without redefining its operating range
v Considered at all
You can disable and enable offer constraints with the Add/Edit Constraint
window.
Procedure
1. Click the name of the constraint you want to edit on the Interactive Channel
Constraints page.
The Add/Edit constraint window appears.
2. To disable the offer constraint so that the selected offers are served without the
restrictions that are defined here, click Disable.
3. To enable the offer constraint, click Enable.
4. Click Save and Return to return to the Constraints tab, or click Save and Add
Another to add another constraint.

Deleting a constraint that is no longer needed
You can delete an offer constraint if you do not need it.
About this task
Note: You cannot recover a constraint after you delete it.
Procedure
1. Select the check box next to the constraints you want to delete.
2. Click Delete Selected.
3. Confirm the deletion.
Use learning models to select offers

Interact has a built-in learning module that monitors the real-time behavior of your
visitors to influence your interactive flowcharts and help select the offers to
present. You can also configure the learning settings to assign attributes at the
interactive channel level so that each interactive channel can have its own set of
customized learning models. Using customized learning models is also referred to
as "self learning."
Before you can use the Self Learning feature, you must enable built-in learning
globally for your Interact environment. For information about enabling the
learning module and more information about learning in general, see the IBM
Interact Administrator's Guide.
By using the Self Learning page in Interact, you can create, delete, edit, enable, or
disable a learning model for an interactive channel.
Adding a learning model to customize offers for a visitor

You can add learning models to monitor the actions of the visitors that visit your
website. Based on the previous actions of the visitors, you can determine the best
offers for them.
About this task
You can edit a learning model by clicking the name of the learning model on the
Self Learning tab.
You can delete a learning model by selecting the check box next to its name and
clicking the Delete Selected icon.
Procedure
1. Click the Add Model icon on the Self Learning page of an Interactive Channel.
The Add/Edit Learning models window opens.
2. Enter a Name for the learning model.
3. Enter a Description for the learning model.
This description is displayed on the Self Learning page to identify this learning
model.
4. Complete the definition for the learning model by adding visitor attributes to
the Predictive Attributes of Interest list.

This list specifies which visitor attributes you want Interact to monitor to
determine the best offers to present to visitors. For a detailed description of
learning and learning attributes, see Interact built-in learning overview in the IBM
Interact Administrator's Guide.
5. Click Enable to make this learning model active within the parameters you
defined.
6. Click Save and Return to go back to the Self Learning page or Save and Add
Another to continue adding learning models
Editing a learning model

You can edit learning model parameters, such as name, description, and visitor
attributes.
Procedure
1. Click the Self Learning tab of an interactive channel to view the list of learning
models.
2. Click the name of the learning model that you want to edit.
The Add/Edit Learning Model dialog is displayed.
3. Optional: Modify the Name, Description, or definition settings of the learning
model.
4. Click Save and Return to go back to the Self Learning page or Save and Add
Another to save your changes and add another learning model
Deleting a learning model

Delete learning models that you no longer use. You cannot recover a learning
model after you delete it.
About this task
You cannot recover a learning model after you delete it.
You cannot delete a learning model that is in use.
Procedure
1. Select the check box next to the learning model that you want to delete. You
can select multiple learning models.
2. Click Delete Selected.
3. Confirm the deletion.
Enabling and disabling a learning model

Instead of deleting a learning model, you can disable it so that it is not available in
a learning channel. You can enable the learning model when you require it to be
available in the learning channel again.
Procedure
1. Click the name of the learning model that you want to enable or disable on the
Interactive Channel Self Learning page.
The Add/Edit Learning Model window opens.
2. Optional: Click Disable to disable the learning model so that it is no longer
available in the interactive channel.
3. Optional: Click EnableTo enable the learning model.

4. Click Save and Return to return to the Self Learning page, or click Save and
Add Another to create a customized learning model.
Use with smart segments to refine offers

Interact uses smart segments in treatment rules to assign offers to visitors. Unlike
strategic segments, you can create smart segments in Campaign sessions only. To
create smart segments, you must use interactive flowcharts.
After you create the smart segments, you can organize them just as you organize
strategic segments.
When you work with segments on the Segments page of Campaign, you can
distinguish smart segments by the following icon: .
Create a Campaign session for interactive flowcharts

Interactive flowcharts are only available in Campaign sessions. You must create at
least one session for your interactive flowcharts. Use the same security policy for
the session as for the interactive channel that is associated with the flowcharts in
the session.
Sessions can contain a combination of batch and interactive flowcharts. If your

session contains both types of flowcharts, and you click the Run icon and select
Run All from the Session Summary page, only the batch flowcharts run.
You cannot run interactive flowcharts from the design environment, you can
perform only test runs.
Define an interactive flowchart to segment your visitors

Interactive flowcharts provide the segmentation logic for your interaction. When a
visitor's runtime session is created, the runtime environment takes all available
profile information for the visitor and runs it through all interactive flowcharts that
are associated with the interactive channel. This filtering places the visitor into zero
or more smart segments. The runtime environment then uses these segments to
present offers as defined by the treatment rules.
You can rerun the profile information through all of the flowcharts by using an
event with the Trigger Re-segmentation action.
You can create interactive flowcharts inside of Campaign sessions only.
See Chapter 3, “About interactive flowcharts,” on page 69 for details about creating
interactive flowcharts.
Define real-time interactive offers for visitors

Based on offer templates you define in Campaign, you can set up real-time
interactive offers that Interact presents to visitors.
Important: Interact does not currently support offer lists.

Offer template requirements for Interact
When you define offer templates to use when you create interactive offers, be
aware of these requirements:
v You must enable the Interaction Point (IP) ID and Interaction Point Name offer
attributes for all offers that are used by Interact. These attributes must exist, and
are automatically populated during run time, overwriting any default IP ID or
IP Name attributes you defined. The IP ID is the internal ID and the IP Name
the name for the interaction point that is associated with the offer. This data is
required for reporting.
v If you do not enable Allow offers created from this template to be used in
real-time interactions when you define the offer template, you can still use the
offers that are defined from this template with treatment rules. Offer suppression
is available for use with the offers. However, Interact is unable to include those
offers in reports.
v If your offer template contains the offer effective date and offer expiration date,
you can define the dates relative to the Flowchart run date. For example, you
can define the Offer Effective date to be the Flowchart run date. The offer can
then expire some number of days after the effective date. For interactive
flowcharts, the Flowchart run date is the time at which the runtime environment
recommends the offer to the touchpoint for presentation.
Offers and naming conventions
As you map offers in Campaign to offers on your touchpoint, keep in mind the
information that is available to use as part of your naming conventions. For
example, for easy reference you might want to save all the banner ads in files that
have the same name as the offer code.
Offers and treatment rules
When you change offers used in treatment rules, including retiring offers, you
must redeploy all the interactive channels that are associated with the server
group. The changes take effect when the interactive channels on the server group
are redeployed.
Offers and the Interact API
As you create your offers, the Interact API can reference the following information
from the offer:
v Custom offer attributes
v Offer code
v Offer description
v Offer effective date
v Offer expiration date
v Offer name
v Offer treatment code
When you create a postEvent call that logs offer acceptance or rejection, you must
include the offer treatment code. However, if you enable cross-session response
tracking, you can match on the treatment code, offer code, or a custom code
particular to your environment. For more details about cross-session response
tracking, see the Interact Administrator's Guide.

You can use nameValuePair class of the Interact API to define or retrieve data from
custom offer attributes.
Creating offer templates for Interact

Use offer templates to create real-time offers that contain consistent information an
audience segment. You create the offer templates in Campaign and use them in
Interact.
Procedure
1. Follow the instructions in the Campaign Administrator's Guide with the following
exceptions.
2. In Step 1 of 3: Metadata, select the Allow offers created from this template to
be used in real-time interactions check box.
3. In Step 3 of 3: Default Values, define default values for Interaction Point ID
and Interaction Point Name.
You can enter any integer for the Interaction Point ID default value, and any
string for Interaction Point Name. The values are automatically populated with
the correct data by the runtime environment; however, the design environment
requires a default value.
Use real-time offer suppression to fine-tune visitor offers

Offer suppression is another way to fine-tune the offers that Interact presents to
visitors. Define offer suppression rules when you want to prevent an otherwise
eligible offer from being seen by a visitor again because they: accepted or rejected
the offer; or are presented with the offer more than a specified number of times.
For example, you might present an offer for a discounted price on tablet computers
to a visitor who rejects the offer. If you concluded that the visitor is no longer
interested in tablet computers, you could suppress that offer for that visitor for the
next 30 days. If you also determined that a user who rejects tablet computers also
has no interest in smart phones, you could suppress related offers for the same
time period.
You can also provide a time period after which the offer should once again be
eligible for that visitor. A time limit for the suppression ensures that, after a certain
amount of time has passed, the offer will again be eligible to be seen by the visitor.
Interact applies offer suppression in real-time, after offer personalization for the
visitor is complete. Each eligible offer is checked against the offer suppression list
before being presented, and any offers that match are omitted from the eligible list
for that visitor.
You can define offer suppression rules for any offer based on an offer template
where Allow offers created from this template to be used in real-time
interactions is selected.
Rules for suppressing offers in real time

Configuring real-time offer suppression in IBM Interact involves defining some
combination of how to handle the offer if the visitor has accepted it before, rejected
it before, has been presented with the offer more than a specific number of times,
or is related to an offer that is already being suppressed.
When Interact evaluates an offer for presentation to a visitor, offer personalization

is performed as usual, and then each eligible offer is compared to the offer

suppression list to see whether it matches. If the offer matches, it is not presented
to the visitor, and instead another matching offer is presented instead.
The following table describes the methods by which Interact can suppress an offer:
Table 9. Offer suppression rules
Rule Description
Offer acceptance An offer acceptance is an offer that has
received any response that is recorded as an
acceptance response. By default, a visitor
response can trigger an "accept" action for
an offer, but you can specify other response
types as acceptance actions.
When you are defining an offer for real-time

interaction, suppressing the offer that is
based on acceptance is defined in the On
Offer Acceptance section.
The complete list of response types available

for rule suppression is defined in the
UA_UsrResponseType table in theIBM
Campaign system tables. See the IBM
Campaign Administrator's Guide for details.
Offer rejection An offer rejection is an offer that has
received any response that is recorded as a
rejection response. By default, a visitor
response can trigger an "reject" action for an
offer, but you can specify other response
types as rejection actions.

based on rejection is defined in the On
Offer Rejection section.
The complete list of response types available

for rule suppression is defined in the
UA_UsrResponseType table in theIBM
Campaign system tables. See the IBM
Campaign Administrator's Guide for details.
Offer fatigue When an offer has been presented to a
visitor a specific number of times, the offer
is suppressed to prevent offer fatigue, where
an offer is seen so many times it is no longer
noticed.

based on the number of times it has been
presented is defined in the On Offer
Presentation section.

Table 9. Offer suppression rules (continued)
Rule Description
Related offer suppression For any offer suppression (On Offer
Acceptance, On Offer Rejection, or On
Offer Presentation), you have the option of
also suppressing other offers that are related
to the current offer. An offer is related if the
offer attribute (as defined on the offer
template) has a matching value to the offer
that is being suppressed.
For example, you might be suppressing an

offer that has been accepted by visitors
where the attribute "Average response
revenue" is less than $100. By suppressing
other offers that are based on this attribute
having the same value, you can suppress
other low-value offers to the same visitor.
If an offer is related to other offers that have

been accepted, rejected, or presented too
many times, the offer is no longer presented.
Be aware of the following practices

concerning attribute matching:
v If an offer rule defines both an attribute
name and an attribute value, then offers
with the same attribute whose value
matches the configured value are
suppressed for the configured duration.
v If an offer rule has only an attribute name,
then all offers with the same attribute
whose value matches the value of the
offer being posted against are suppressed
for the configured duration.
For each of the rules described above, you can optionally apply a time limit to the
offer suppression so that the offer is suppressed for a specified number of days. If
you do not supply a time limit, the offer is permanently suppressed for that visitor.
Working with treatment rules

Treatment rules are the main guidelines that are used by Interact to present offers.
The treatment rules are where you assign offers to smart segments by zone. You
can also add a marketing score to each rule to add weight to the offer within the
learning engine.
There are several optional features you can use to further influence or override
treatment rules. For more information about Interact offer serving, see the Interact
Administrator's Guide.
Treatment rules are organized by smart segment. You assign any number of offers
to each segment. After assigning offers to a segment, you can define a zone where
that offer is applicable. You can assign the same offer to the same segment multiple
times and assign them to different zones.

If you delete a smart segment or retire an offer, Campaign disables any treatment
rule that contains the segment or offer.
The smart segments are mapped to cells within a campaign. You can edit the cell
codes that are associated with each smart segment from the interaction strategy
tab.
You must select offers that are created from an offer template with Allow offers
created from this template to be used in real-time interactions. enabled only. If
you do not, inaccurate report data is generated.
Treatment rules are defined on the interaction strategy tab of a campaign. You can
copy interaction strategies from one campaign to another using the Copy
Interaction Strategy icon at the top of the tab.
Offer eligibility
Treatment rules are the first level of methods Interact uses to determine which
offers are eligible for a visitor. Interact has several optional features that you can
implement to enrich your offer-to-visitor assignments.
The following list displays the optional features in Interact that you can use to
enrich your offer-to-visitor assignments:
v Offer suppression
v Global offers
v Individual offer assignments
v Score overrides
v Learning
Before you create your treatment rules, confirm with your Interact administrator
the offer eligibility features that are available to you. For example, if you are using
a score override table to override the marketing score, it might not be necessary to
change the marketing scores from the default for all of your treatment rules.
For more information about offer eligibility features, see the Interact Administrator's
Guide.
Marketing score
Every treatment rule contains a marketing score that is represented by the slider.
The default score is 50. The higher a score, the more likely it is that Interact selects
the offer to recommend. Depending on how you configure your treatment rules
across multiple campaigns, you can have multiple offers that are assigned to the
same smart segments.
Interact uses the marketing score to help determine which offer displays if multiple
offers are available for a single request. For example, if a request for offers must
choose between offer A with the marketing score of 30 and offer B with the
marketing score of 80, Interact presents offer B.
If two or more of the highest-scoring offers have the same score, Interact breaks
the tie among the offers by making random selection from the matching offers.
This helps to ensure that a single visitor interacting in the same zone multiple
times is more likely to see different offers on each interaction.You can change this
behavior, if wanted, by modifying the Interact | offerServing |

offerTieBreakMethod configuration property. See the "Interact Runtime
Configuration Properties" appendix of the Interact Administrator's Guide for details.
If you assign the same offer to the same segment with different scores, for
example, two different campaigns might create treatment rules for the same
interactive channel, Interact uses the higher score.
You can also define the marketing score by using advanced options for the
treatment rule. You can build an expression by using IBM macros, offer attributes,
session variables, dimension tables, and any value in a customer's profile to define
the marketing score.
You can override any changes to the marketing score made on the interaction
strategy tab by providing data in a score override table. Using a score override
table, you can easily import scores that are generated in IBM PredictiveInsight,
Contact Optimization, or some other modeling software. In the Score Override
table, you can define scores greater than 100.
If you enable built-in learning, the marketing score is used in the learning
algorithms.
For details about working with the score override table, see the Interact
Administrator's Guide.
Treatment rule advanced options

You can enhance your treatment rules with advanced options. You can add an
expression to either determine whether the treatment rule is applicable or to
override the marketing score.
Treatment rules for offers outside of interactive flowcharts
You write expressions for offer eligibility directly inside treatment rules to control
how you target offers from outside of interactive flowcharts. Some rules might be
easier to manage at this level rather than at the segmentation level.
For example, you might write the expression offer.dynamic.ownProductX='yes',

that is, if the offer attribute ownProductX is yes, use this treatment rule. In this
example, you might include a specific offer or you might have a different score for
the offer for people who already own product X. You can build specific treatment
rules, for example, assigning specific offers that are based on offer attributes or the
day of the week.
Treatment rules to adjust marketing scores
You can also write expressions to define or adjust the marketing score.
For example, profileTable.dimensionTable.scoreAdj * MarketerScore, which

multiplies the value of the scoreAdj column to the current marketing score defined
by the slider for the treatment rule.
Working with the Interaction Strategy tab

The interaction strategy tab is the place in your campaign where you assign offers
for the real-time interactions. When you create the interaction strategy tab, you
assign it to an interactive channel.

You can create as many campaigns that contain interaction strategy tabs as
required for your organization. For example, if you have a campaign for new
checking accounts and another for auto loans, both can reference the same
interactive channel for the call center. You cannot copy or move interaction strategy
tabs.
Note: You can have one interaction strategy tab per interactive channel per
campaign. If you have three interactive channels, you can have no more than three
interaction strategy tabs in a single campaign, and each of these tabs must be
assigned to a different interactive channel.
The interaction strategy tab contains two major sections, the deployment area and
the treatment rules area. The deployment area shows the deployment status of the
treatment rules. The treatment rules are where you assign offers to segments.
Campaigns with interaction strategy tabs
The summary tab of campaigns displays the segments and offers associated with
the campaign. Offers added to the campaign by treatment rules display on the
campaign summary tab only if three conditions are met. First, you must deploy the
interaction strategy. Second, you must configure the contact and response history
module to transfer data from the runtime environment to the design environment.
Third, the data transfer from the runtime environment to the design environment
must be complete. For example, you configure the contact and response history
module to run every two hours. You then add an interaction strategy tab to the
campaign. The offers do not is displayed on the campaign Summary tab. You then
deploy the interaction strategy tab. The offers are still not displayed on the
campaign Summary tab. Two hours later after the contact and response history
module finishes the next data transfer, the offers is displayed on the campaign
Summary tab.
Smart segments do not display on the campaign Summary tab.
To create an interaction strategy tab

You can create an interaction strategy tab while creating a campaign or while
viewing the Summary tab of an existing campaign.
Before you begin
You must create an interactive channel before creating interaction strategy tabs.
Procedure
1. You can add an interaction strategy tab to a campaign in one of two ways:
v When creating a campaign, click Save and Add an Interaction Strategy.
v When viewing the Summary tab of an existing campaign, click the Add an
Interaction Strategy icon.
The new interaction strategy page is displayed.
2. Enter a Name and Description for the interaction strategy tab.
3. Select the Interactive Channel for the interaction strategy tab.
4. Click Save and Create Treatment Rules. Clicking the Save and Create
Treatment rules button places you in the interactive strategy in edit mode,
where you can make and save changes. See “To add or modify a treatment
rule” on page 56 for information about adding and modifying treatment rules.

5. Click Save and Exit when you are finished creating treatment rules, or click
Cancel to exit interactive strategy edit mode and return to the view-only
interaction strategy tab.
Results
You can edit the name and description of the interaction strategy tab later by
clicking the Edit Properties icon. You cannot change the Interactive Channel with
which the interactive strategy is associated.
You can modify an interaction strategy tab later by clicking the Edit Strategy icon.
You can delete an interaction strategy by clicking the Delete Interaction Strategy
icon. Whether you can delete the interaction strategy depends on the deployment
status of the interactive channel that is associated with this interaction strategy tab.
To view the interaction strategy tab

Whenever a campaign has one or more interaction strategy tabs that are associated
with it, you can view each tab to see the current, detailed settings and deployment
status of the interaction strategy, and you can also mark the interaction strategy for
deployment without entering edit mode. This section describes the information
that you can see while in view-only mode.
Interactive channel information
The For The Interactive Channel field displays the interactive channel with which
this interaction strategy tab is associated. Click the name of the interactive channel
to go directly to the Summary tab of the associated interactive channel.
Deployment information
There are two fields on the interaction strategy tab that provide you with
deployment information:
v Deployment status. The Deployment Status button indicates the current status
of the interaction strategy tab, such as Not Yet Deployed, Deployed, the last
deployment date, last undeployment date, and so on.
v Deployment action. Click the deployment action button to specify an action to
take with this interaction strategy, depending on its current state. The choices
include:
– Mark for deployment. If the status is "Not Yet Deployed," you can click this
button to mark the interaction strategy for deployment.
– Mark for undeployment. If the status is "Deployed," you can click this button
to mark the interaction strategy for undeployment.
– Cancel Deployment Request. If you have clicked Mark for Deployment, you
can undo that request by clicking this button.
– Cancel Undeployment Request. If you have clicked Mark for
Undeployment, you can undo that request by clicking this button.
Viewing the treatment rules
The interaction strategy tab contains a complete list of the treatment rules available
for the strategy. You can use this list to view treatment rules in the following ways:

Table 10. Interaction strategy view options. Interaction strategy view options
Viewing option Description
View by menu Allows you to view the list of treatment
rules grouped by segment (along with the
zones, offers, and other options for that
segment), or grouped by zone (along with
the segments, offers, and other options for
that zone).
Click this icon to see a read-only view of the
Cell Self-Learning Settings icon ( self-learning settings for that segment.
This icon is available in view-only mode

only when you are viewing by segment.
View Interactive Cell Performance report Click this icon to see the Interactive Cell
Performance by Offer report for that
icon ( ) segment.
Filtering columns to omit specific values By default, the table shows all values for the
specific segments or zones. If a column
heading is accompanied by the filter icon (
), you can click the icon to select only the
specific items of that type you want to
display. See “Filtering tables in IBM
products” on page 99 for more information
about using column filters.
View-only treatment rule settings. For all other treatment rule information,
including enabled/disabled, Marketers
Score, Advanced Options, and
Parameterized Offer Attributes, you can
view the information (or click the icons to
view additional information) just as you can
when you are creating treatment rules, with
the restriction that all information is
view-only and cannot be changed.
To modify any information on the Interaction Strategy tab, click the Edit Strategy
icon to enter edit mode.
Related tasks:
“Sorting tables in IBM products”
Sorting tables in IBM products:
When you are viewing a table of information in IBM products, features might be
available that allow you to customize the table view to sort the information in
ascending or descending order, based on one column value or based on
combinations of column values. This section describes how to identify and use
sorting options, when they are available in a table.
About this task
The steps described here apply only to tables where sorting by column heading is
supported. To identify a table where this feature is supported, move your mouse
pointer onto a column heading. If a sort control is displayed, as shown in the
following example, the table supports sorting by column heading:

The control to the right of the column heading indicates the sort order for this
column, which described in the table in the following procedure.
Procedure
1. To determine the sort order of a table using a single column, click one of the
following controls in the column heading:
Sort icon Description

Sorts the table by using the selected column
in ascending order.
Sorts the table by using the selected column

in descending order.
Cancels the sorting of the table by using this

column.
2. Optionally, move the mouse over one or more additional columns, and click the
ascending or descending icon to sort by additional column values ("2"
indicating secondary sort, "3" indicating a tertiary sort, and so on). Each level of
sorting you add is applied to the data in the table in the order in which you
assign it. For example, if you selected Date as the primary sort column and
Time as the secondary sort column, all rows in the table would be sorted by
date, and within identical date values, each row would be sorted by time.
3. To clear a column from affecting the table sort order, click the sort icon on the
column until the "x" is displayed, then click the "x".
To add or modify a treatment rule

Use the Add Rules on an interaction strategy tab to add or modify a treatment
rule.
Before you begin
You must create smart segments and offers before you create treatment rules.
You must also be viewing an interactive strategy tab in edit mode. To enter edit
mode, click the Edit Strategy icon on the interactive strategy tab.
Note: You cannot edit a strategy if it is marked for deployment.
Procedure
1. On an interaction strategy tab, click the Add Rules ( ) icon.

The Add Rules panel is displayed.
Note:
As you drag an object from the Add Rules panel onto the table that defines
the treatment rule, the color of the object you are dragging changes from red
to green. Green indicates that you can drop the segment at the specific

location on the list; red indicates that you cannot drop the segment at that
location. See the descriptions for each object for an explanation of where you
can drop objects on the treatment rule.
2. Add a segment to a rule by selecting a segment from the Available Segments
tab of the Add Rules panel and dragging it to the rules table. If you drag
multiple segments to the rules table, multiple rules are created for you
automatically.
You can drop segments only onto the Eligible Segments column. The order of
the rules does not matter.
After you add a segment to the rule, you can click the following icons next to
the segment name:
v Use the Self-Learning Settings icon ( ) to determine the learning model

that applies to this segment in the treatment rule. By default, the learning
model is inherited from each zone, but you can use this dialog to specify
that the marketing scores or a custom learning model can be applied
instead. See “Use learning models to select offers” on page 44 for details.
You can also view and change the Self-Learning settings by clicking the
name of a segment and selecting Override Self-Learning for this Segment
from the menu that is displayed.
v If the View Report icon ( ) is visible, you can view the Interactive Cell
Performance by Offer report for this strategy.
3. To add zones to the treatment rule, click the Available Zones tab in the Add
Rules panel.
The Available Zones tab that contains zones to which you can assign the
offers in specific segments.
4. Add a zone to a rule by selecting one or more zones from the Available
Zones tab of the Add Rules panel and dragging it to the rules table.
If you select multiple zones, each zone you drop into the table creates a
unique treatment rule.
You can drop offers into the Eligible Zones column for a particular segment,
or onto the segment itself to accomplish the same action. The order of the
zones does not matter.
You can modify the zones in a segment at any point by clicking the name of
the zone in the Eligible Zones column and selecting the check box next to
each zone you want to include, or by selecting All Zones to modify the
selected zone to encompass all zones. When you modify an All Zones entry
to select individual zones, individual treatment rules are created automatically
for the specific zones you selected.
5. To add offers to the treatment rule, click the Available Offers tab in the Add
Rules panel.
The Available Offers tab that contains offers that you can recommend as part
of this treatment rule is displayed.
6. Add an offer to a rule by selecting an offer from the Available Offers tab of
the Add Rules panel and dragging it to the rules table.
You can also select multiple offers and drag them to the rules table.
You can drop offers into the Recommended Offers column for a particular
zone, or onto the zone itself to accomplish the same action. The order of the
rules does not matter; however, dragging to an offer already in the list inserts
the rule below that offer.

You can add multiple offers to a treatment rule, and Interact duplicates the
treatment rule for each offer automatically.
7. To modify the marketing score for a specific treatment rule, adjust the slider in
the Marketers Score column. To modify the marketing score for multiple
treatment rules at once, select the check box next to each treatment rule you
want to modify, then choose Edit Selected Rules > Advanced Options.
8. To add an advanced option to define rule eligibility or override the marketing
score, click the advanced options icon ( ), located to the right of the score
slider, in a treatment rule, or select multiple zones whose advanced options
you want to modify, then choose Edit Selected Rules > Advanced Options.
Use the slider to assign a marketing score to treatment rule. Click the radio
buttons next to Consider this rule eligible if the following expression is true
or Use the following expression as the marketing score to see the options for
defining advanced rule eligibility options. For information about defining
advanced rules, see “To add advanced options to a treatment rule.”
9. To specify parameterized offers for a treatment rule, click the Parameterized
Offer Attributes icon ( ) in the Off Attr column, or select the check box
next to one or more treatment rules and choose Edit Selected Rules >
Parameterized Offers. Use the dialog box that is displayed to specify the
parameterized offer attribute names and values as described in “To add
parameterized offer attributes to a treatment rule” on page 60.
10. When you are done editing the interaction strategy tab, click Save and Exit to
return to view-only mode, or click Save to save your changes and continue
editing.
You can discard your changes and return to view-only mode by clicking
Cancel at any time.
What to do next
You receive a warning if you add the same offer to the same segment for the same
zone, other than All Zones, to prevent duplication. You can choose to ignore this
warning.
You can view segments and offers either in the tree view or list view. The tree
view displays the segments or offers in the folder structure you create on the
respective segment or offer page. The list view displays the segments or offers in
alphabetical order by name. The Source Flowchart and Last Run columns are
empty for all smart segments. You can also search for segments and offers by
name, description, or code. The search for segments can display smart segments
only.
You can view the Interactive Cell Performance by Offer report for a segment by
clicking the View link under Performance Statistics. If you select offers that do not
have Allow offers created from this template to be used in real-time interactions
enabled, no data is collected for reporting.
To add advanced options to a treatment rule

Use the Edit Interaction Strategy tab icon on an interaction strategy tab to add
advanced options to a treatment rule.
About this task
You can write an expression to define treatment rule eligibility or to override the
marketing score.

Procedure
1. If you are not already editing an interaction strategy tab, click the tab and click
the Edit Interaction Strategy tab icon to enter edit mode. When you are in
view-only mode, you can view, but not change, advanced options following the
steps below.
2. Select one or more treatment rules for which you want to add advanced
options, then complete one of the following steps:
a. Click the advanced options icon ( ), located to the right of the score
slider, in a treatment rule to add advanced options.
Note:
The Enabled, Marketers Score, Adv. Opt (Advanced Options), and Off Attr
(Parameterized Offer Attributes) columns and icons are not visible when the
Add Rules panel is visible. To see these columns when you are editing a
rule, click the Close icon ( ).

b. Select the name of one or more eligible zones, then click Edit Selected
Rules > Advanced Options.
The Advanced Options panel is displayed. By default, Do not use advanced
options is selected, indicating that the Marketing Score values should be used.
However, you can override that setting by following the steps here.
3. Select Consider this rule eligible if the following expression is true to create
an eligibility rule or Use the following expression as the marketing score to
override the marketing score.
Select Do not use advanced options to disable the advanced options. This does
not delete any expressions.
4. Write your Expression.
All available functions, variables, and operators are listed to assist you building
your expression.
You can click Check Syntax to determine whether your expression is valid.
Note: Check Syntax uses your test run Interact runtime server for validation.
Your test run runtime server must be running for check syntax to function.
5. Click OK when you are finished editing the advanced options to close the
dialog and save your changes.
Treatment rule advanced option expressions:
You can write either a Boolean expression to filter treatment rules, or an expression
to calculate an override for the marketer's score. However, you have a limited
number of expression building blocks.
Important: Custom macros, derived fields, and user variables are not available for
treatment rule advanced options.
The following building blocks are available to you.

v IBM macros that are supported by Interact
For a list of the IBM macros that are supported by Interact, see the IBM Macros
User's Guide.
v Offer attributes
v Session variables

v Dimension tables
v Profile data
v Marketers score
If you define a Boolean expression for a marketing score, true becomes 1 and false
becomes 0. If you define a numeric expression for a Boolean expression, 0 is false
and all other values are true.
Here are several examples of expressions for both rule filtering and score
calculation using the various building blocks available to you.
Consider this rule eligible if the following expression is true

profileTable.accountType != ’Gold’ ||
profileTable.dimensionTable.accountBalance > 5000
Offer.Static.EffectiveDateFlag = 0
Offer.Dynamic.OfferColor = ’Blue’
EXTERNAL_CALLOUT(’GetPrimeRate’) <= 6.9
In this example, the GetPrimeRate external callout is a Java program which goes to
a website and collects the current prime interest rate.
Use the following expression as the marketing score

AVG(profileTable.dimensionTable.accountBalance)
MarketerScore + STDEV(profileTable.dimensionTable.accountBalance)
In the following example, the marketer's score takes into account the customer's
lifecycle (which represents the marketer's overall likelihood to be responsive to
offers and the company's desire to market to this customer), the predetermined fact
that the company wants to market certain classes of products to this specific
individual, and the overall value that accepting the offer would add to the
customer's account in the eyes of the company.
Calculated Marketer’s Score =
[sLifeCycle] *
[wClassA] *
[(wShortTermVal * vShortTerm) + (wLongTermVal * vLongTerm)]
Customer Attributes:
wShortTermVal = global weighting towards short term value = 1
wLongTermVal = global weighting towards long term value = 0.7
wClassA = customer weighting towards product class A = 1.2
sLifeCycle = customer life cycle score = 1.5
1 - Onboarding
1.5 - Settled
0.2 - At Risk
0 - Leaving
Offer Attributes:
vShortTerm = offer short term value gain = 250
vLongTerm = offer long term value gain = 150
To add parameterized offer attributes to a treatment rule

For any treatment rule or set of treatment rules, you can parameterize the values of
some offer attributes at run time based on the profile data. Using a dialog available
from the strategy tab, you can create mappings that parameterize offer attributes

with constants or expressions. After the strategy is deployed successfully, the
mappings you created are used in the runtime environment to override the offer
attribute values of the returned offers.
Before you begin
Make sure that you have defined offers with attributes that you can parameterize
from the strategy tab, and that you have assigned one or more offers to the
treatment rules you are defining.
About this task
When offers are requested, the Interact runtime processes the requests as usual, but
before those offers are about to be returned, the run time determines whether any
attributes of those offers can be parameterized based on the strategy treatment
rules that apply. For parameterized offers, the run time retrieves the appropriate
attribute mappings, evaluates them, and returns the results as the return values.
Note: If the run time determines that an offer attribute is parameterized based on
both the treatment rule setting and a table-driven feature (such as the Interact
Process Box on the batch flowchart), the order in which they are evaluated are
white list first, then strategy treatment rules, then offerBySQL query results, and
then, if the preceding criteria are not available, the default offers.
You can create, view, and edit parameterized offer attribute settings by using one
of two methods on the strategy tab.
Procedure
1. If you are not already editing an interaction strategy tab, click the tab and click
the Edit Interaction Strategy tab icon to enter edit mode. When you are in
view-only mode, you can view, but not change, offer attribute parameterization
settings by following the steps that are described here.
2. Select one or more treatment rules for which you want to add offer attribute
parameterization settings, then complete one of the following steps:
a. Click the offer attribute parameterization icon ( ), located to the right

of the score slider and advanced options icon, in a treatment rule.
Note:
(Parameterized Offer Attributes) columns and icons are not visible when the
Add Rules panel is visible. To see these columns when you are editing a
rule, click the Close icon ( ).

b. If you are viewing the strategy tab in edit mode, select the name of one or
more eligible zones, or one or more eligible segments, then click Edit
Selected Rules > Parameterized Offers.
The Parameterized Offer Attributes panel is displayed, showing each attribute
in the Attribute Name column, and the current value to be used for that
attribute in the Attribute Value column. By default, the default values for the
attributes are displayed. However, you can override those values by following
the steps here.
3. In the Attribute Value column, click the value currently displayed.

4. Use the dialog that is displayed to enter a literal constant for that offer attribute
or to create an expression by using the provided expression builder.
All available functions, variables, and operators are listed to assist you building
your expression.
You can click Check Syntax to determine whether your expression is valid.
Note: Check Syntax uses your test run Interact runtime server for validation.
Your test run runtime server must be running for check syntax to function.
5. Click OK when you are finished editing the advanced options to close the
dialog and save your changes.
To add or modify treatment rules with the Rule Wizard

Use the Rule Wizard on an interaction strategy tab to add or modify treatment
rules. You can add multiple treatment rules at once using this method.
Before you begin
You must create smart segments and offers before you create treatment rules.
You must also be viewing an interactive strategy tab in edit mode. To enter edit
mode, click the Edit Strategy icon on the interactive strategy tab.
Procedure
1. On an interaction strategy tab, click the Rule Wizard.
2. Select offers to be included in the rules you generate through the Rule Wizard.
You can search for offers or browse through the list of available offers. Click
Next after you selected offers to include.
3. Select segments to be included in the rules you generate. You can search for
segments or browse through the list of available segments. Click Next after you
selected segments to include.
4. Associate zones with each selected segment to be included in the rules you
generate. By default All Zones is selected. You can assign different zones to
any single or group of selected segments. You should select in the segments list
the wanted items in the segments list and then associate the wanted zones.
Click Next after you associated zones to each selected segment.
5. Under Edit rule advanced options, you can adjust the marketing score. You
can also enable and add rule expressions. Click Check Syntax to validate any
expression before proceeding. Then, click Next. Changes are applied to all
created and modified rules.
6. Modify parameterized attributes that are common to your selected offers. Click
each value to edit the offer attribute. Click Check Syntax to validate any
expression before proceeding. Then, click Next. Changes are applied to all
created and modified rules.
7. Set the wizard behavior for the rule generation process. You can choose to
update the existing rules with your changes. You can also change the wizard
result view and show only the rules that are created or updated by the Rule
Wizard.
8. Click Done to apply your rules.
What to do next
You can view segments and offers either in the tree view or list view. The tree
view displays the segments or offers in the folder structure you create on the

respective segment or offer page. The list view displays the segments or offers in
alphabetical order by name. The Source Flowchart and Last Run columns are
empty for all smart segments. You can also search for segments and offers by
name, description, or code. The search for segments can display smart segments
only.
You can view the Interactive Cell Performance by Offer report for a segment by
clicking the View link under Performance Statistics. If you select offers that do not
have Allow offers created from this template to be used in real-time interactions
enabled, no data is collected for reporting.
To enable and disable treatment rules

You can enable and disable treatment rules without deleting them. You cannot
enable or disable rules until the interaction strategy tab finishes loading.
About this task

You can view the menus by clicking the segment or offer.
Note:
(Parameterized Offer Attributes) columns and icons are not visible when the Add
Rules panel is visible. To see these columns when you are editing a rule, click the
Close icon ( ).
Procedure
1. Open the interaction strategy tab that contains the treatment rules that you
want to modify.
2. Click the Edit Strategy icon to enter edit mode.
3. Modify the treatment rules by using any of the following methods.
Action Procedure
Enable a single rule Click the Enable Rule icon until the check mark is
green (and not dimmed).
Enable all rules that contain a Click an offer and select Enable all Rules involving
particular offer this Offer.
Enable all rules that contain a Click a segment and select Enable all Rules for this
particular segment (cell) Segment.
Disable a single rule Click the Enable Rule icon until you see a gray
(dimmed) check mark.
Disable all rules that contain a Click an offer and select Disable all Rules
particular offer involving this Offer.
Disable all rules that contain a Click a segment and select Disable all Rules for
particular segment (cell) this Segment.
4. When you are finished enabling or disabling treatment rules, click Save to save
your changes and remain in edit mode, or Save and Exit to save your changes
and return to view-only mode.

To delete treatment rules
You can delete treatment rules you no longer need. You can open the menus by
clicking the segment or offer. Deleting all the rules for a segment also removes the
segment from the treatment rules table.
Procedure
1. Open the interaction strategy tab that contains the treatment rules that you
want to modify.
2. Click the Edit Strategy icon to enter edit mode.
3. Delete the treatment rules by using any of the following methods.
Action Procedure
Delete a single rule Click an offer and select Delete this Rule.
Delete all rules that involve an offer Click an offer and select Delete all Rules Involving
this Offer.
Delete all rules for a segment (cell) Click a segment and select Delete all Rules for this
Segment.
4. When you are finished deleting treatment rules, click Save to save your
changes and remain in edit mode, or Save and Exit to save your changes and
return to view-only mode.
About deploying interaction strategy tabs

After you configure the interaction strategy tab, the next step is to mark the
strategy tab for deployment. When you mark an interaction strategy tab for
deployment, a notification is displayed on the interactive channel that is associated
with this interaction strategy tab that it can be deployed to a runtime server group
for testing or production.
When an interaction strategy tab is marked for deployment, you cannot edit the
strategy tab. If you need to make more changes before the interaction strategy tab
is deployed, you can cancel the deployment request. This removes the strategy tab
from the list of items that are pending deployment, at which point you can modify
it as needed.
When an interaction strategy tab is no longer needed, you can mark it to undeploy.
This adds the retirement request to the deployment queue. The next time that all
changes are deployed, the interaction strategy tab and all its treatment rules are
removed from the runtime server.
To mark an interaction strategy tab for deployment

After you create and modify an interactive strategy as needed for an interactive
channel, you can mark it for deployment.
Before you begin
An interaction strategy must be created for an interactive channel.
Procedure
1. View the summary page for the interaction channel that is associated with the
interaction strategy you want to mark for deployment.
2. In the Associated Strategies area on the summary page, click the interactive
strategy that you want to mark for deployment.

The interactive strategy tab is displayed.
3. Click the Mark for deployment button.
Results
The interaction strategy is marked for deployment. The interaction strategy is

added to the list of items that are waiting to be deployed on the interactive
channel summary page.
Note:
You cannot edit an interaction strategy that is marked for deployment.
The next time that you deploy the interactive channel, the changes to this
interaction strategy tab are included.
If you have reports that are installed and click View Deployment History at the
bottom of the interactive channel summary tab, you can view the Interactive
Channel Deployment History report to see the results of the deployments.
To cancel a deployment request

Use an interaction strategy tab to cancel a deployment request.
Procedure
1. View the interaction strategy tab for which you want to cancel deployment.
2. Click Cancel deployment request.
Results
The interaction strategy tab is no longer marked for deployment. The interaction
strategy tab is removed from the list of items that are waiting to be deployed on
the interactive channel summary tab. You can now edit the interaction strategy tab.
If you click View Deployment History, you can view the Interactive Channel
Deployment History report if you have reports installed.
To mark an interaction strategy tab for undeployment

If you no longer require the smart segments that are created by an interaction
strategy tab, you can undeploy the strategy tab. This removes all references of the
strategy tab from the runtime server. This option is available only if you have
previously deployed the interaction strategy tab.
Procedure
1. View the interaction strategy tab that you want to mark for undeployment.
2. Click Mark for undeployment.
Results
The interaction strategy tab is marked for undeployment. The data removal request
is added to the list of items that are waiting to be deployed on the interactive
channel summary tab. You cannot edit an interaction strategy tab which is marked
for undeployment.
The next time that you deploy the interactive channel, all references to this
interaction strategy tab are removed from the runtime servers.

If you click View Deployment History, you can view the Interactive Channel
Deployment History report if you have reports installed.
Exporting an interactive channel

In Interact, you can export a previous interactive channel deployment version.
When you export a deployment version, you can send this export to IBM technical
support to troubleshoot any problems with your deployment.
You can export an interactive channel deployment version from the Deployment
History section of the Deployment tab in your Interactive Channel. When you
export an interactive channel, it is saved as ExportIC.exp by default.
Any objects that are disabled are not exported as part of the export package.
The interactive channel is exported in the following structure.

v Dependent objects
– Campaigns
– Offers
v Global data
– Custom macros
– Audience levels
– Offer attribute def map
– Learning configuration
– CH RH tables map
– Event patterns
– Interactive flowcharts
– Strategies
– Inherited global events reference
– Profiles
– Offers by SQL
– Learning module
– Interact flowcharts
– zones
– Deployment information
– Constraints
– Offers by table
– Server groups
v Other exported objects
– Offer references
– Campaign references
– Offers by SQL default cells
– Segments
– Default offers default cells
– Detect configuration
– Target cells

Interaction strategy reference
Use the table in this section to understand the icons on the Strategy tab.
The interaction Strategy tab uses the following icons.
The icons, left to right, are described in the following table.

Edit Strategy Click to add new treatment rules to this interaction
strategy.
Edit Properties Click to edit the name and description of the interaction
strategy. You cannot change the interactive channel.
Delete Interaction Strategy Click this icon to delete this interaction strategy tab.
Add a Flowchart Click this icon to add a batch flowchart to this campaign.
Remember, to add interactive flowcharts, you must create
them in a session.
Add an Interaction Strategy Click this icon to add an interaction strategy to this
campaign.
Copy Interaction Strategy Click this icon (in view-only mode) to create a copy of this
interaction strategy. When you click this icon, a dialog is
displayed where you can specify the destination for the
copy.
(Optional) Assign target and control cells

Since the interaction strategy tab is part of a campaign, you can also take
advantage of the target cell spreadsheet. The target cell spreadsheet (TCS) is a
spreadsheet-type feature for each campaign that displays all cells within that
campaign, and their details, including assigned offers.
The TCS functions a little differently with interaction strategies than with batch
flowcharts. You can use both the top-down and bottom-up approaches. Cells that
are generated by treatment rules in the interaction strategy tab become bottom cells
in the TCS. You can use the top-down approach the same as with batch flowcharts.
However, currently, the offer to the cell assignment from the interaction strategy
tab do not display in TCS. Also, you cannot assign an offer to a cell on the TCS for
use in treatment rules; you must use the interaction strategy tab to assign offers to
cells for real-time interactions.
You do not need to approve cells that are used in interaction strategies in a
Marketing Operations TCS.
Control cells also work differently for real-time interactions. For example, on a
website, you must always present an "offer," otherwise the page layout might be
broken. The offer for a control cell might be a simple branding image instead of a
traditional offer. The reports available if you have reports installed do not report
on control cells for real-time interactions.
For more information about the target cell spreadsheet, see the Campaign User's
Guide.

To override cell codes
When you create a treatment rule, Campaign maps the segments to cells. If
necessary, you can override the cell name or cell code.
Procedure
1. Click the segment for which you want to edit the cell code.
2. Select Override this Cell Name or Code.
The Override Cell Name and Code dialog is displayed.
3. Edit the Target Cell Name.
4. Change the Cell Code as follows:
v Generate a new cell code by using the Campaign cell code generator by
selecting Use an auto-generated or hand entered code created just for this
rule and clicking Auto-generate.
v Enter a cell code by selecting Use an auto-generated or hand entered code
created just for this rule and entering a new Target Cell Code.
v Select a cell code that is created in the Target Control Spreadsheet (TCS) with
the top-down method by selecting Select or type a pre-created target cell
code and selecting the code from the list.
The list filters by what you enter. For example, if you enter ABC, the list
displays the cell codes that start with "ABC" only.
5. Click Save and Return to close the Override Cell Name and Code dialog, or
click Save and Edit Next to edit the cell name and code of the next segment.
Deploy the Interact configuration

When you configured the Interact configuration, you had to mark the interaction
strategy tab and all interactive flowcharts for deployment. After all configuration
for your Interact implementation is complete in the design environment, you are
ready to deploy the configuration to a runtime server.
See Chapter 5, “Understanding deployment to runtime servers,” on page 91 for

details about deploying interactive channels.

Chapter 3. About interactive flowcharts
Interactive flowcharts are similar to Campaign batch flowcharts when used to
create strategic segments.
You use batch flowcharts in Campaign to complete a sequence of actions on your

data for executing your campaigns. Batch flowcharts are made up of processes,
which you configure to perform the actual data manipulation that is required for
your campaign. When you use batch flowcharts in sessions, you create persistent
data constructs, such as strategic segments, that are available globally to all
campaigns. A strategic segment is a list of IDs created in a session and made
available to all campaigns. A strategic segment is no different from other segments
(such as those created by the Segment process) except that it is available globally,
for use in any campaign.
Interactive flowcharts fulfill a similar purpose to assign visitors to your

touchpoints into segments. Each interactive flowchart is made up of processes,
which you configure to assign visitors to segments. Interactive flowcharts also
create segments that are available globally to any interaction strategy for a
corresponding interactive channel in any campaign. However, segments that are
created by interactive flowcharts are different from those created in batch
flowcharts. Segments that are created by batch flowcharts are a list of IDs.
Segments that are created by interactive flowcharts, called smart segments, are the
definition of which customers must be in the segment.
Interactive flowcharts are meant to function in real time, working with one visitor
at a time. After deploying the interactive flowchart to a runtime server, an instance
of each flowchart exists for every active visitor to your touchpoint. Each visitor
runs through the interactive flowcharts to be assigned to smart segments in real
time. You can configure interactive flowcharts to reference data in your production
data source and data that is collected in real time from the touchpoint.
Interactive flowcharts can have one audience level per flowchart. You can,
however, have many interactive flowcharts per audience level.
As you design your interactive flowcharts, you must remember that interactive
flowchart performance is different from batch flowchart performance. These
flowcharts are run in real time. If it takes too long for the perfect advertisement to
load on your website, your customer might go to a different site. When designing
flowcharts, you must work in tandem with your touchpoint administrator,
balancing your segmentation requirements with your touchpoint performance
requirements. Some design considerations that you should discuss with your
touchpoint administrator include the number of interactive flowcharts to run per
audience level and the number of times you require a database lookup.
Since interactive flowcharts run on the runtime server and not within the design
environment, you cannot run an interactive flowchart in Campaign. You can,
however, perform a test run of an interactive flowchart within Campaign.

Building interactive flowcharts
Typical interactive flowcharts start with an Interaction process, go through data
manipulation processes, and end in at least one PopulateSeg process. The data
manipulation processes, Decision, Select, and Sample, can be used to create
detailed segments. The Decision and Sample processes can be used to create
branching logic, while the Select process can be used to enrich the data that is
considered in making decisions and segmentation. The Snapshot process can be
used to persist profile data, session data, or real-time calculated data to a database.
All interactive flowcharts must start with an Interaction process. The Interaction
process also defines the number of audience records that are processed during a
test run of the flowchart.
The Decision process can be used to divide the input into different cells by creating
branches that are based on condition expressions.
After separating the input into flowchart cells, use the PopulateSeg process to
designate the members of the cells as members of smart segments.
You can use the Select process to access advanced queries to augment the visitor
selection. The Select process gives you access to user variables, derived fields,
custom macros, and web callouts. You can also include data from dimension tables
available in your data source.
The Sample process gives you a limited selection of the sample configurations
available in a batch flowchart. As with batch flowcharts, use the Sample process to
create one or more cells for different treatments, control groups, or a subset of data
for modeling.
Use the Snapshot process to write data to a table in your data source. For example,
if you use a Select process to access real-time data by web callouts and custom
macros, use the Snapshot process to add that data to your customer profile.
To create interactive flowcharts

Use the Summary tab of a session to add an interactive flowchart.
Before you begin
Important: When you create interactive flowcharts, remember that you must
define the audience level for the flowchart. You cannot change the audience level
of the flowchart after you create it.
Procedure
1. Open the Summary tab of the session to which you want to add an interactive
flowchart.
2. Click the Add a Flowchart icon.
The New Flowchart page is displayed.
3. Enter a name and description for the flowchart.
4. Select the Interactive Flowchart flowchart type.
When you select Interactive Flowchart, configuration settings for interactive
flowcharts are displayed.
5. Select the Interactive Channel for this interactive flowchart.

6. Select the Audience Level for this interactive flowchart.
7. Click Save and Edit Flowchart.
The Edit Interactive Flowchart page displays the process palette and a blank
flowchart workspace.
Results
You can now edit the interactive flowchart.
Interactive flowcharts and data sources

Similar to batch flowcharts, use interactive flowcharts to define the segments that
the audience members belong in, based on characteristics of the data that is
associated with the segments. However, the data that you use in an interactive
flowchart is different from the data that you use in batch flowcharts.
Batch flowcharts use data available in databases. Interactive flowcharts also use
persisted profile data from a database, but they can also use real-time session data.
The real-time session data can include anything that you can extract from your
touchpoint. You can include how long a caller has been on hold, track the website
from which the visitor came from, determine the weather at the visitor's location,
and so on. The persisted profile data comes from database tables, similar to batch
flowcharts. The data can include all the traditional data that you have about your
visitors: name, account number, address, and so on.
The test run profile table

During design-time, you have access only to persisted profile data. Campaign is
not connected to a touchpoint and therefore cannot collect real-time session data.
To create interactive flowcharts that reference real-time session data and to
complete test runs of interactive flowcharts, you must have sample real-time
session data in a 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 that is 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 that a visitor came from, and stores it
with the name linkFrom, there is a column that is called linkFrom in the test run
profile table.
The test run profile table might 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 who designs interactive flowcharts, the person who designs and codes
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 must 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 might 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 data is in dimension tables.
Dimension tables
You can map dimension tables for interactive flowcharts. However, you must map
the tables in the Interactive Channel, and not within the Campaign table mapping
that is available in Campaign Settings.
Dimension tables must have a column that maps to the profile table. You can map
a dimension table to another dimension table. A dimension table that is mapped to
another dimension table must have a column that maps to the other dimension
table. A chain of dimension tables must eventually map to the profile table. For
example, dimension table A must share a column with dimension table B,
dimension table B must share a column with dimension table C, and dimension
table C must share a column with the profile table.
You can have many dimension tables, however, they all must exist in the same
data source. All dimension tables must be mapped in the interactive channel before
you start to work in an interactive flowchart. You cannot map tables to retrieve
data within an interactive flowchart. (You can map a general table for use with a
Snapshot process.)
While you can have many dimension tables, work with your touch point
administrator to confirm you are meeting performance requirements.
Configuring interactive flowcharts

In general, interactive flowcharts are configured the same way as batch flowcharts.
While you need consider the different concepts behind interactive flowcharts
compared to batch flowcharts, you add and edit processes in an interactive
flowchart in the same way as you do in a batch flowchart.
Unless an exception is mentioned here, for details about general flowchart creation,
such as adding processes, renaming processes, and so on, see the Campaign User's
Guide.
v Remember that you cannot change audience level in an interactive flowchart.
v Whether you can delete an interactive flowchart depends on its deployment
status.
v If you access the Table Mappings dialog, clicking Load loads only general tables.
You must complete all table mapping for an interactive flowchart in the
interactive channel that is associated with the flowchart.
v Stored table catalogs are not used in interactive flowcharts.
Queries and Interact

Several processes in Interactive flowcharts and advanced options in treatment rules
can be used to create queries to select data from your data source. These are, in
general, the same queries as Campaign.
You can use any of the following methods to create a query in interactive
flowcharts or treatment rule advanced options.
v Point & Click
v Text Builder

v Macros
For details about these methods, see the Campaign User's Guide.
v Event pattern matching, which provides access to the state of every event
pattern that is defined for the interactive channel (including out of date range
event patterns). You can including event patterns in your query to combine
other segmentation logic with behavioral logic, or you can use the pattern state
alone to define a behavioral segment.
The potential values for an event pattern state are provided as an integer with
one of the following values:
Table 11. Event pattern states
Event
pattern state Description
1 Pattern condition has been met (the pattern is true)
0 Pattern condition has not been met (the pattern is false)
-1 Pattern is expired (outside of the valid date range)
-2 Pattern is not enabled (the Enabled check box is not selected in the event
pattern definition dialog)
Interactive flowcharts and treatment rule advanced options do not support raw
SQL.
The following sections describe any differences in the options available in

interactive flowcharts and advanced options in treatment rules.
About data types and stored objects

Like Campaign, Interact supports several data types for stored objects. User
variables, derived fields, and macros can all use Number, String, and Date data
types. Date constants are interpreted by using the date format settings of
Campaign.
Interact also supports the Vector data type. Vectors are similar to arrays, except
that the number of elements is variable. All operators available to Interact can have
a Vector for at least one of its arguments.
Given the following:

v X [operation] Y = Z where X, Y, and Z are vectors
v Sx, Sy, Sz are the size of each vector
v Dx, Dy, Dz are the data types for each vector, and X and Y must contain the same
data types.
Then the following is true:

v Sz = Sx * Sy
v Dx = Dy = Dz
Take the following two examples.
The following table shows how Interact evaluates the expressions IF((X+Y)==10)
and IF(NOT((X+Y)==10)) where X={1,2,3} and Y={9,10,11}.

X Y X+Y (X+Y)==10? NOT((X+Y)==10)?
1 9 10 True False
1 10 11 False True
1 11 12 False True
2 9 11 False True
2 10 12 False True
2 11 13 False True
3 9 12 False True
3 10 13 False True
3 11 14 False True
Since the equation must evaluate to either true or false, and at least one of the
operations evaluates to true, the result of both the expressions IF((X+Y)==10) and
IF(NOT((X+Y)==10)) is true.
Derived fields, user variables, macros, and Interact

While you can create expressions in interactive flowcharts and advanced options
for treatment rules, all of the building blocks are not available in both query
builders. The table in this section describes the query building block, whether it is
available in interactive flowcharts or advanced options, and any special notes.
Unless otherwise described in the following table, see the Campaign User's Guide
for more details about building queries.
Available in Available in
interactive advanced
Object flowchart options Notes
Derived fields Yes No You can use derived fields, persistent
derived fields, stored derived fields, and
user variables in interactive flowcharts with
the Decision, Select, and Snapshot
processes. Derived fields can contain
constants, user variables, other derived
fields, and macros. If you are creating a
derived field in an interactive flowchart
that you want to be available as a
name-value pair in the Interact API, you
must preface the name with the prefix
defined in the SessionVar configuration
property, for example,
SessionVar.DerivedFieldName.
User variables Yes No User variables can contain only numerics or
strings. Interactive flowcharts do not
support the None data type.

Available in Available in
interactive advanced
Object flowchart options Notes
IBM Macros Yes Yes A select list of IBM macros are available for
use in interactive flowcharts and advanced
options for treatment rules. The design
environment lists the available IBM macros
in the query builder. For details about
using macros, see the IBM Macros User's
Guide.
Note: NUMBER, IS, and IN behave
differently in interactive flowcharts and
advanced options than Campaign.
EXTERNALCALLOUT is only available for

interactive flowcharts. This function can be
used to make synchronous callouts to
external services.
Custom Yes No Raw SQL selecting ID list or Raw SQL
Macros selecting ID list + value custom macro
types are not supported in interactive
flowcharts.
Using EXTERNALCALLOUT
EXTERNALCALLOUT is a function available to you when working with custom macros
in Decision, Select, and Snapshot processes in interactive flowcharts.
EXTERNALCALLOUT can be used to make a synchronous call to an external service, for
example, to request the credit score for a particular audience level.
To use external callouts, you must write the external service in Java by using the
IAffiniumExternalCallout interface. For more details about the
IAffiniumExternalCallout, see the Interact Administrator's Guide.
About the Interaction process

All interactive flowcharts must start with the Interaction process. You can use the
interaction process to start an interactive flowchart, and to define the size of the
test profile sample that Interact uses when performing a test run of interactive
flowcharts.
About the Decision process

The Decision process is the workhorse of the interactive flowchart. The Decision
process divides the cells that are passed into the process into new cells that are
based on configurable criteria. Each new cell creates a branch, like a decision tree.
An interactive flowchart can contain as many Decision processes as necessary. For

example, the first Decision process in an interactive flowchart might create the cells
HighValue, MediumValue, and LowValue. You can then have three more Decision
processes, one for each of the first segments to divided them into more refined
segments, for example FrequentShopper, Shopper, and RareShopper.
When an interactive flowchart runs on the runtime server, only one customer at a
time goes through the flowchart. If a branch is empty, the runtime environment
does not process that branch nor its child branches.

The Decision process can take input only from a process which creates cells, such
as an Interaction, Decision, Sample, or Select process.
Configuring the Decision process is a two-step process. First, you must select the
input cells, second, you must configure the branches.
To configure the Decision process

Configuring the Decision process is a two-step process: first, you must select the
input cells, and second, you must configure the branches.
Procedure
1. In an interactive flowchart in Edit mode, add a Decision process to the
2. Provide input to the Decision process by connecting it to one or more data
manipulation processes.
Data manipulation processes include Interaction, Decision, Sample, or Select.
3. Double-click the Decision process.
The Process Configuration window appears displaying the Decision tab.
4. Select a source cell from the Input drop-down list.
5. Select Create Mutually Exclusive Branches if you want the created segments to
be mutually exclusive.
If you want a branch to contain all the remaining customer IDs, you must
select Create Mutually Exclusive Branches.
6. Configure the branches.
7. (Optional) Click the General tab to assign a name and notes to the process.
The name appears on the process in the flowchart. The notes appear when you
point to the process in the flowchart.
8. Click OK.
Results
The process is configured and appears enabled in the flowchart.
To configure Decision process branches

Configure a branch in a Decision process to use an interactive flowchart. The
Decision process creates branches by dividing the cells that are passed into the
process into new cells that are based on configurable criteria.
Procedure
1. In the Decision process on the Decision tab, complete one of the following
actions:
v Select a branch and click Edit to edit the branch condition.
v Click Add Branch to create a branch.
v Select a branch and click Remove to delete a branch.
2. In the Edit or Add a Branch window, enter a Branch Name.
3. If you do not want to create a query, or to select all remaining customers,
choose Select All Customer IDs.
Choosing Select All Customer IDs is useful if this Decision process is after
several data manipulation processes and the Customer IDs have already been
filtered by previous processes.

Note: To select all remaining customers, you must select Mutually Exclusive
Branches on the Decision Process Configuration dialog. If you do not select
Mutually Exclusive Branches, this branch selects all customer IDs connected to
the Decision process.
Select Customer IDs With is selected by default, and the query builder is
active.
4. Select a table from the Select Based On drop-down list.
5. Create a condition for the branch by using queries.
6. Click OK.
Results
The Add or Edit a Branch window closes and you return to the Decision tab of the
Decision process. You can continue to configure branches or finish configuring the
Decision process.
About the PopulateSeg process

The PopulateSeg process performs a similar function as the CreateSeg process in
batch flowcharts; the PopulateSeg process takes the input cells and makes them
smart segments. The segments that you create with the PopulateSeg process are the
smart segments you use in treatment rules. The PopulateSeg process is a terminal
node of interactive flowcharts.
Remember that only smart segments can be used in interaction strategies. You
cannot use strategic segments in interaction strategies.
To create smart segments

You must create smart segments for interaction strategies. You cannot use strategic
segments in interaction strategies.
Procedure
1. In an interactive flowchart in Edit mode, add a PopulateSeg process to the
2. Provide input to the PopulateSeg process by connecting it to one or more data
Data manipulation processes include Decision, Sample, or Select.
3. Double-click the PopulateSeg process.
The Process Configuration window is appears displaying the Define Segments
tab.
4. Select one or more source cells from the Input drop-down list.
5. In the Result Segments area, select an input cell and select a Segment Name.
If you want to create a segment, select New Segment and complete the New
smart segment dialog. Enter a Name and Description and select the segment
folder under which you want to create the segment. You can organize your
smart segments the same as you organize strategic segments.
Note: Special characters should not be used in smart segment names.

The name is displayed on the process in the flowchart. The notes are displayed
when you point to the process in the flowchart.
7. Click OK.

Results
About the Sample process in interactive flowcharts

The Sample process in interactive flowcharts fills the same purpose of Sample
processes in batch flowcharts, to create one or more cells for different treatments,
control groups, or a subset of data for modeling. However, the interactive
flowchart Sample process contains only a subset of the features in the Sample
process in batch flowcharts. The Sample Size Calculator and Maximum Cell Size
are removed. Interactive flowchart Sample processes also have a new method for
selecting the sample, the Deterministic Hash Function.
In a batch flowchart, the Sample process randomly selects some number of

customers to be in a sample cell. In an interactive flowchart, however, during run
time, the Sample process works with a single customer at a time. When you define
the % for a sample, you are defining the probability that a visitor becomes a
member of that cell.
When defining sample cells, you must create at least two. Define a % for one
sample, and select All Remaining for the other. If you do not do this, you will
have undefined results. For example, if you create one 30% sample only, the
remaining 70% of visitors are not assigned to any cell.
You must connect the Sample process to a PopulateSeg process to complete

creating a smart segment that you use for sampling.
The Deterministic Hash Function assigns visitors to samples randomly. However, if

the same visitor passes through the interactive flowchart more than once, the
visitor is placed in the same cell. If you want to ensure that visitors are eligible to
be sampled differently after they have been placed in the same cell repeatedly, you
can configure a time period for the Deterministic Hash Function. (Adjust the Date
of first reset and Number of days between resets.)
If you are creating a flowchart that copies the functionality of another flowchart,
you can ensure that the Sample process uses the same Deterministic Hash Function
as the original interactive flowchart by using the Hash Seed field. To place visitors
in the same sample group, use the same number of cells, Hash Seed, Date of First
Reset, and reset period in both Sample processes. Interact uses the value of the
Hash Input seed and the reset date to determine which cell the visitor is placed in.
To configure the Sample process

Use an interactive flowchart in the Edit mode to configure a Sample process.
Procedure
1. In an interactive flowchart in Edit mode, add a Sample process to the
2. Provide input to the Sample process by connecting it to one or more data
Data manipulation processes include Decision, Sample, or Select. You can
connect the Sample process to an Interaction process also.
3. Double-click the Sample process.

All output cells from any process that is connected to the Sample process are
listed in the drop-down list. To use more than one source cell, select the
Multiple Cells option. If more than one source cell is selected, the same
sampling is completed on each source cell.
5. Determine the number of samples that you want to create for each of your
input cells, and enter that number in the # of Samples/Output Cells field.
By default, three samples are created for each input cell, with default names
"Sample1", "Sample2" and "Sample3."
6. Select each sample under the Output Name column and complete the
following actions:
The Edit Output Cell section is enabled.
a. Place your cursor in the Cell Name text box and type to modify the
sample name.
You can use any combination of letters, numbers, and spaces. Do not use
any periods (.) or slashes (/ or \).
b. Enter the probability that a visitor is assigned to the sample in the % field,
or select the All Remaining check box.
The % must be less than 100.00.
7. (Optional) Change the Hash Seed under the Deterministic Hash Function.
You must change the Hash Seed only if you want this Sample process to
assign visitors to cells the same way as another Sample process. The Hash
Seed must be an alphanumeric value.
8. (Optional) Enter the Date of first reset under the Deterministic Hash
Function.
Click the ellipsis button for a calendar to select the date.

9. (Optional) Enter the number of days between resets.
The name is displayed on the process in the flowchart. The notes are
displayed when you mouse of the process in a flowchart.
11. Click OK.
Results
You must connect the Sample process to a PopulateSeg process to complete

creating a smart segment that you use for sampling.
About the Select process in interactive flowcharts

The Select process in interactive flowcharts fills the same purpose of Select
processes in batch flowcharts to specify the customer data that you want to use in
your interactive flowchart. The interactive flowchart Select process contains a
subset of the batch flowchart Select process, it only contains the Source and
General tabs.
You can use the Select process to select data from your data source to augment the
profile table you referenced in the Interaction process. You also have access to user
variables, derived fields, and macros. Remember that interactive flowcharts are
limited to one audience level. However, you can use the Select process to reference
data in a dimension table at a different audience level. For example, you might

reference a table with household transaction data in an interactive flowchart with
the customer audience level to sort by information in the household data.
To configure the Select process

Use an interactive flowchart in the Edit mode to configure the Select process.
Procedure
1. In an interactive flowchart in Edit mode, add a Select process to the flowchart
workspace.
2. Provide input to the Select process by connecting it to one or more data
Data manipulation processes include Decision, Interaction, Sample, or Select.
3. Double-click the Select process.
All output cells from any process that is connected to the Select process are
Multiple Cells option. If more than one source cell is selected, the same select
actions are completed on each source cell.
5. Determine whether you want to select all rows from the data source or whether
you want to filter the rows that are based on specified criteria. Select one of the
following options.
a. Select All IDs to include all the rows of data from the data source in the
Input drop-down list.
b. Select IDs With to create a query to select only certain IDs based on criteria
you define.
6. If you use the Select IDs With option to select only certain IDs based on
specified criteria, create a query.
7. (Optional) Click the General tab to add a name and notes to the process or to
configure the Output Cell name or Cell Code.
when you mouse of the process in a flowchart.
8. Click OK.
Results
About the Snapshot process in interactive flowcharts

The Snapshot process in interactive flowcharts fills the same purpose of Snapshot
processes in batch flowcharts to capture a list of IDs and associated data, and
export them to a table. The interactive flowchart Snapshot process contains a
subset of the batch flowchart Snapshot process. You can save to a table only. You
also cannot order or skip duplicate entries in the table, however, since interactive
flowcharts only handle one record at a time, these features are not necessary.
Snapshot and data formats
When saving to an existing table from the Snapshot process, Interact saves data as
described in the following table.

to Number
From to Text (String) (Double) to Date (Date)
Text (String) Original Value Double SimpleDateFormat as
defined in
defaultDateFormat
configuration property
Number (Double) String Original Value Throws exception
Date (Date) SimpleDateFormat as Throws Original Value
defined in Exception
defaultDateFormat
configuration property
When writing to a table that does not already exist, the Interact runtime
environment dynamically creates a table using default data types. You can override
these default data types by creating a table of alternate data types. For details, see
To configure the Snapshot process

Use an interactive flowchart in the Edit mode to configure the Snapshot process.
Procedure
1. In an interactive flowchart in Edit mode, add a Snapshot process to the
2. Provide input to the Snapshot process by connecting it to one or more data
Data manipulation processes include Decision, Interaction, Sample, or Select.
3. Double-click the Snapshot process.
All output cells from any process that is connected to the Snapshot process are
Multiple Cells option. If more than one source cell is selected, the same
snapshot actions are completed for each source cell.
5. Select a table from the Export to list.
If a table does not exist, select New Mapped Table and follow the instructions
for creating a table in the Campaign Administrator's Guide.
6. Select an option to specify how updates to the output table are handled:
a. Append to Existing Data. Append the new information to the end of the
table. This is the recommended method for database tables.
b. Replace All Records. Remove any existing data from the table, and replace
it with the new information.
c. Update Records. All fields that are specified for snapshot are updated with
the values from the current run of the process.
7. Specify the fields that are written out by the Snapshot process.
a. The fields in the table are displayed in the Export Fields list under the
Table Field column. You can automatically find matching fields by clicking
Match>>. Fields with exact matches for the table field names are
automatically added to the Export Fields list. If there are multiple matching
fields, the first match is taken.
b. You can manually select the fields to include.

a. Select the fields that you want to include in your output from the
Candidate Fields list.
You can select multiple fields at one time by using Ctrl+Click or a
contiguous range of fields by using Shift+Click.
b. Move selected fields to the Fields to Snapshot list by clicking Add>>.
c. You can manually modify the pairings by clicking <<Remove or Add>>.
d. If wanted, reorder the fields in the Fields to Snapshot list by selecting a
field and clicking Up1 or Down1 to move it up or down in the list.
8. (Optional) Click the General tab to add a name and notes to the process or to
configure the Output Cell name or Cell Code.
when you point to the process in a flowchart.
9. Click OK.
Results
Understanding interactive flowchart test runs

Interactive flowchart test runs check the segmentation logic of an interactive
flowchart. Interactive flowcharts are intended to run on a runtime server with one
visitor at a time. However, you can test them in Campaign to ensure that the
interactive flowchart creates and assigns visitors to the segments you expect. For a
complete test of your interactive flowcharts and how it interacts with your
touchpoint, you must deploy the interactive flowchart to a test runtime server.
The method of testing interactive flowcharts is the same as testing batch

flowcharts, that is, complete a test run. While the results might seem similar (each
segment is assigned some number of members), the way the flowchart assigns the
members is different. When you complete a test run of an interactive flowchart, the
design environment uses a runtime environment. The runtime environment treats
each row in your profile table as a visitor, running each visitor one at a time
through the flowchart.
The runtime environment references the customer data that is supplied in tables
that are referenced in interactive flowcharts and all real-time data available from
event parameters, external callouts, and so on. During a test run, the design
environment does not have access to actual real-time data. The design environment
uses the data available in your test run table. You must work with your Interact
administrator to add sample data into the test run profile that can properly test
your interactive flowcharts. For example, if you define segmentation logic that
separates audience members that are based on the first digit of their postal code,
make sure that you have one entry in your test run profile for each possible first
digit.
By default, the Interaction process limits the number of input records in your
profile table that is used in a test run, but you can adjust the number of records
that are used as needed. The design environment selects the first number of
records in audience ID order. For example, if you limit your test run to five
records, the design environment uses the first five records in your test run profile
table, which is sorted by audience ID.

Note: Interactive flowcharts are not optimized to run with thousands of records. If
you start a test run to process a high number of records, the test run might take
several minutes to complete.
You can view the results from the last test run only. the design environment
deletes all data from the previous test run when starting a new test run. If there
are over 1000 entries in your test run, or to view test run data after closing the test
run window, the test run data is stored in the following tables in the database that
is defined by the testRunDataSource.
v TestAttr_n. Contains the data for the Test Run Attribute Data report, that is, all
the data in the profile table for each audience ID.
v TestCount_n. Contains the data for the Test Run Cell Counts report, that is, the
number of members in each cell.
v TestError_n. Contains the data for the Test Run Errors report, that is, any errors,
if they occurred, in the test run.
v TestSeg_n. Contains the data for the Test Run Segment Data report, that is, the
audience ID and the assigned segment.
The suffix _n indicates the flowchart ID. You can determine the flowchart ID by
examining the UA_Flowchart table in the Campaign system tables.
To configure the test run size

Use an interactive flowchart in the Edit mode to configure the test run size.
Procedure
1. In an interactive flowchart in Edit mode, double-click the Interaction process.
The Process Configuration window appears displaying the Input tab.
2. Select Limit input records to and enter the number of records.
3. Click OK.
To perform a test run

Use an interactive flowchart in the Edit mode to perform a test run.
About this task
Interactive flowcharts test runs function differently than batch flowchart test runs.
You cannot pause and restart or stop an interactive flowchart test run.
Procedure
1. In an interactive flowchart in Edit mode, click the Run and select Test Run
Flowchart.
The design environment uses the runtime environment defined in the
serverGroup configuration property with all the data in the test run data source
to test the interactive flowchart.
A test run status dialog opens.
2. When the test run completes, click View Results to view the results.
Results
The test run results consist of four tables:

v Test Run Segment Data. Displays the audience ID and the assigned segment.

v Test Run Attribute Data. Displays all the data in the profile table for each
audience ID.
v Test Run Cell Counts. Displays the number of members in each cell.
v Test Run Errors. Displays any errors, if they occurred, in the test run.
Similar to batch flowcharts, the test run also populates the number of members in
each cell output by the process. Since processes without successors do not output
cells to another process, the numbers are not populated. For example, create a
simple flowchart, Interaction > Decision > PopulateSeg. After a test run, the
Interaction process displays the number of members in its output cell below the
blue checkmark indicating the process ran successfully. This number should be the
same as the Test Run Size. The Decision process displays the number of members
in each cell. If the Decision process creates three cells, there will be three numbers,
separated by semicolons (;), for example 29;11;10. Because the PopulateSeg process
does not output cells to another process, it does not display any members.
About deploying interactive flowcharts

When you configure the interactive flowchart, you must mark the flowchart for
deployment. When you mark an interactive flowchart for deployment, a
notification is displayed on the interactive channel that is associated with this
interactive flowchart that it can be deployed to a runtime server group for testing
or the production runtime server group.
When an interactive flowchart is marked for deployment, you cannot edit the
flowchart. If you have to make more changes before the interactive flowchart is
deployed, you can cancel the deployment request. This removes the flowchart from
the list of items that are pending deployment.
When an interactive flowchart is no longer needed, you can mark it for

undeployment. This adds the retirement request to the deployment queue. The
next time that all changes are deployed, the interactive flowchart is removed from
the Interact server. Treatment rules that contain the smart segments that are created
by the flowchart you removed still exist, however, since there is no interactive
flowchart to assign a visitor to that segment, no visitor is assigned to the segments
created by the flowchart that you removed.
To deploy an interactive flowchart

You can deploy an interactive flowchart while you are viewing the flowchart.
Before you begin
Make sure that the flowchart is not in the Edit mode.
Procedure
1. View the interactive flowchart that you want to mark for deployment.
You must view the flowchart. You cannot mark a flowchart for deployment in
edit mode.
Interactive flowcharts are available only in sessions.
2. Click Mark for deployment.

Results
The interactive flowchart is marked for deployment. The interactive flowchart is

channel summary tab. You cannot edit an interactive flowchart which is marked
for deployment.
The next time that you deploy the interactive channel, the changes to this
interactive flowchart are included.
To cancel a deployment request

By canceling a deployment request, you can remove an interactive flowchart from
the list of items that are waiting to be deployed. You can then edit the flowchart.
Procedure
1. View the interactive flowchart for which you want to cancel deployment.
You must view the flowchart. You cannot cancel a flowchart's deployment in
edit mode.
Interactive flowcharts are available in sessions only.
2. Click Cancel deployment request.
Results
The interactive flowchart is no longer marked for deployment. The interactive

flowchart is removed from the list of items that are waiting to be deployed on the
interactive channel summary tab. You can now edit the interactive flowchart.
To undeploy an interactive flowchart

If you no longer require the smart segments that are created by an interactive
flowchart, you can undeploy the flowchart. This removes all references of the
flowchart from the runtime server.
Before you begin

v You have an interactive flowchart that is deployed.
v The interactive flowchart is not in the Edit mode.
Procedure
1. View the interactive flowchart that you want to mark for undeployment.
You must view the flowchart. You cannot mark a flowchart for undeployment
in edit mode.
Interactive flowcharts are available in sessions only.
2. Click Mark for undeployment.
Results
The interactive flowchart is marked for undeployment. The data removal request is
channel summary tab. You cannot edit an interactive flowchart which is marked
for undeployment.
The next time that you deploy the interactive channel, all references to this
interactive flowchart are removed from the runtime servers.

Chapter 4. About the Interact List process in batch flowcharts
When Interact is installed, the Interact List process is available in batch flowcharts.
Similar to the Call List and Offer List processes, the Interact List process allows
you to specify which offers are served to which visitors to your interactive site.
This provides you with the ability to target offers to entire audience levels, target
specific individual audience members, or suppress offers from specific audience
members using table-driven features.
You use batch flowcharts in IBM Campaign to complete a sequence of actions on

your data for executing your campaigns. Batch flowcharts are made up of
processes, which you configure to perform the actual data manipulation that is
required for your campaign. IBM Interact provides integration with Campaign
batch flowcharts to help determine the list of offers that might be served to a
specific audience or type of audience.
Interact List process box

The Interact List process box is a batch flowchart process that is available only
when IBM Interact is installed on your Campaign server.
Use the Interact List process box on a batch flowchart to determine the offers that
are served to customers by the Interact runtime server, including the following
choices:
v Offer suppression at an individual level (a "black list")
v Offer assignment at an individual level (a "white list," or score override)
v Offer assignment at an audience level (global, or default, offers)
v Offer assignment by custom SQL query
The runtime server has access to the output from this process when you deploy
the interactive campaign. A batch flowchart might contain multiple instances of the
Interact List process box.
When you are working with the Interact List process, you must be familiar with
the following concepts:
v Chapter 4, “About the Interact List process in batch flowcharts”
Tasks that you can complete from this page:

v “To configure the Interact List process”
To configure the Interact List process

Use a batch flowchart in the Edit mode to add an Interact List process to the
Procedure
1. In a batch flowchart in Edit mode, add an Interact List process to the flowchart
workspace.
The Interact List process is available on a batch flowchart if IBM Interact is
installed on your Campaign server.

2. Provide input to the Interact List process by connecting it to one or more data
manipulation processes, such as Sample or Select.
3. Double-click the Interact List process in the flowchart.
The process configuration dialog is displayed.
4. On the Fulfillment tab, specify the fulfillment details of your list output.
a. Use the OfferList type drop-down list to specify the type of offer filter you
are configuring this process to use:
v Black list (Offer Suppression) - indicates offers to suppress from being
served to a specific audience. This allows you to prevent offers from
appearing for specific visitors, based on the segment of the audience into
which the visitor falls.
v White list (Score Override) - indicates that Interact must always serve an
offer to a particular audience regardless of whether the marketing score
would otherwise cause Interact to make the offer available.
v Global Offers (Default Offers) - defines offers that can be offered
(similar to White list) for an entire audience type; that is, a default offer
that every visitor in a specified audience can see, regardless of the
segment of which they might otherwise be a part.
v Offer Filters (Offers by SQL) - Allows you to provide a SQL query to
determine which offers are served to the specified visitors. This option
allows you, for example, to serve up an offer that is based on a specific
visitor preference.
If you select this OfferList type, the input for this process is determined
by your SQL query and the Input/Audience drop-down list is dimmed
and cannot be selected.
The OfferList Type you specify here determines the behavior of the Interact
List process, and the options available to you in this configuration dialog, as
noted below:
b. From the Interactive Channel drop-down list, choose the interactive
channel that specifies the interaction points, events, and other settings that
can apply to the Interact List process you are defining.
This drop-down list automatically lists the interactive channels that you
already defined within the Interact design time environment.
c. (White list or Black list only) From the Input drop-down list, specify the
input cells (to use as the data source for the contact list. To use more than
one cell (such as multiple input segments), click the ellipses ( ) button
next to the Input field, then use the Select Cells to Use dialog that is
displayed, select the input cells to use.
If you select multiple input cells in this step, all of the input cells you select
must have the same audience level.
Note: If the contact process is not connected to a process that provides

output cells, there are no cells to select from in the Input drop-down list. To
correct this, close the process configuration dialog and connect the Interact
List process to an output process, then begin the configuration process
again.
d. (Global Offer only) Use the Audience drop-down list to specify the
audience type for which you want this Interact List process to apply.
e. Use the Target Data Sourcedrop-down list to indicate the data source to
which you want to write the output from this process.

f. Enter the database table to which you want to write the output from this
process in the Table name field.
The table that you specify is created automatically when the process runs, if
it does not exist.
g. To specify the fields that are written to the specified OfferList table each
time this process runs, click the ellipses ( ) button next to the Table name
field.
The Personalization Options dialog is displayed. The predefined set of fields
that is written to the table is displayed in the Fields to Log list.
v Select the fields that you want to include in your output from the
Candidate Fields list.
You can use IBM Campaign Generated Fields by expanding the IBM
Campaign Generated Fields list, or use derived fields by clicking the
Derived Fields button.
v To pair a candidate field to a field already listed in the Fields to Log list,
select the candidate field, then select a field in the Fields to Log list, then
click Add>>.
v To add a candidate field to the Fields to Log list without pairing it with
an existing field, click the blank line after the last entry in the Fields to
Log list, then click Add>>.
v Remove fields from the Fields to Log list by selecting them and clicking
<<Remove.
v If wanted, reorder the fields in the Fields to Log list by selecting a field
and clicking Up1 or Down1 to move it up or down in the list.
v If wanted, click the Derived Fields button to create a variable for
providing output to the table.
h. Select an option to specify how updates to the output table are handled:
v Append to Existing Data - Each run of this process adds its output data
to the table you specified in the Table name field
v Replace All Records - Each run of this process removes any data from
the table before you write the new output data.
5. To assign one or more offers or offer lists to each target cell defined in this
process, click the Treatment tab.
The Assign offers to cells interface is displayed.
How you configure the output on the Treatment tab depends on the OfferList
type you selected on the Fulfillment tab.
a. Black Lists (Offer Suppression) - For each target cell displayed in the table,
click the Offer column to select from a drop-down list of available offers, or
click Assign Offers. Use the Assign Offers dialog to select one or more
offers that you want to suppress for the input cells (visitors) specified on
the Fulfillment tab of this process.
b. White Lists (Score Override) - For each target cell displayed in the table,
click the Offer column to select from a drop-down list of available offers, or
click Assign Offers. Use the Assign Offers dialog to select one or more
offers that you want to serve for the input cells (visitors) specified on the
Fulfillment tab of this process, even if the marketing score would not
otherwise serve that offer to the visitor.
c. Global Offers (Default Offers) - For each target cell displayed in the table,
click the Offer column to select the wanted offers from a drop-down list, or
click Assign Offers. Use the Assign Offers dialog to select the offers that
Chapter 4. About the Interact List process in batch flowcharts 89

you want to serve to all visitors of the audience type that is selected on the
Fulfillment tab for this process, regardless of the segment into which they
fall.
d. Offer Filter (Filter by SQL) - Click the Offer by SQL button to create a SQL
expression that allows the Interact runtime server to select the offers that
you want to serve to a set of visitors. Use the Create Offer by SQL dialog
that is displayed in the following ways:
v Select an existing SQL template name from the SQL drop-down list, or
enter a new name in this field for the template if you are defining a new
template.
v Provide the contents of the SQL query in the SQL template field.
v Click Check Syntax to determine if your expression is valid. Check
Syntax uses your test run Interact runtime server for validation. Your test
run runtime server must be running for check syntax to function.
Note: If you use the SQL Server, Check Syntax does not show errors in
your expression even when your expression is invalid. If your expression
is invalid, the flowchart test run fails even if it passed when you used
Check Syntax.
For more information about using the Create Offer by SQL dialog, see the
"Creating queries using SQL" section in the IBM CampaignUser's Guide.
6. (Optional) Click the General tab to assign a name or notes to the process.
when you point to the process in the flowchart.
7. Click OK to complete the Interact List process configuration.
Results
The process is configured and appears enabled in the flowchart. You can test the
process to verify that it returns the results you expect.

Chapter 5. Understanding deployment to runtime servers
Deployment is how you transfer all the configuration that you define in the design
environment to the runtime server groups. Deployment is grouped by interactive
channel. When you deploy an interactive channel, you are sending all the data that
is associated with an interactive channel to the selected runtime server group. This
is why, when you are creating interactive channels, you must define the production
runtime servers and the non-production (testing) runtime servers.
The first deployment contains the following data:

v All interactive flowcharts that are associated with the interactive channel that are
marked for deployment.
This includes the smart segments.
v All interaction strategies that are associated with the interactive channel that are
marked for deployment.
This includes the treatment rules, which also include offers.
v All events, zones, and interaction points that are defined in the interactive
channel.
v Other required data not specific to interactive channels including audience level
definitions, built-in learning configuration, offer attribute definitions, custom
macro definitions, contact and response history mapping information, and
campaign start and end dates.
On all subsequent deployments of the interactive channel, Interact sends the

following to the selected runtime server.
v All data that is associated with the interactive channel including interaction
points and events.
v All edited interactive flowcharts and interaction strategies that are associated
with the interactive channel that are marked for deployment.
v The last deployed version of all interactive flowcharts and interaction strategies
that are contained in previous deployments which are not marked for
undeployment.
v All other required data not specific to interactive channels.
If an interactive flowchart or interaction strategy is marked for undeployment,

Interact disables all data and references to the undeployed flowcharts and
strategies from the runtime server.
Note: After you deploy an interactive channel to a Interact runtime server, the
runtime server is now associated with that particular design environment,
including the Campaign partition. If you attempt to reuse the same runtime server
by associating it with a new design environment, deployment fails. This scenario
might occur if you have a staging Campaign installation and a production
Campaign installation.
Deployment is a four-step process.

1. Configure and mark all interactive flowcharts that are associated with an
interactive channel for deployment.
2. Configure and mark all strategy tabs that are associated with an interactive
channel for deployment.

3. Configure the events and interaction points tab of the interactive channel.
4. Deploy the data from the interactive channel deployment tab.
When you mark an interactive flowchart or interaction strategy for deployment or

undeployment, it remains marked and locked against editing until you deploy to a
production server. The following table shows the marked for deployment status of
an interaction strategy as you take actions in the design environment.
Step Marked status Action in design environment

1 Marked for deployment Mark an interaction strategy for deployment.
and locked for edit.
2 Marked for deployment Deploy elsewhere to a staging server group.
and locked for edit
Testing on the staging server shows that your
treatment rules need changes.
3 Available for edit Cancel the deployment request for the interaction
strategy to make your changes.
4 Marked for deployment After you make your changes to the interaction
and locked for edit strategy, mark it for deployment again.
5 Marked for deployment Deploy elsewhere to a staging server group again.
and locked for edit
Testing with your revised treatment rules is successful
and you determine the interactive channel is ready for
production.
6 Available for edit Deploy to the production server group.
When to deploy
You must deploy your interactive channel when you change any of the following
data.
v Interactive flowcharts
v Interaction strategies
v Audience level definitions
v Built-in learning configuration
v Offer attribute definitions
v Custom macro definitions
v Contact and response history mapping information
v Campaign start and end dates
v Retiring offers
If you change any of the other required data not specific to interactive channels,
you must redeploy all the interactive channels that are associated with the server
group for the changes to take effect.
Understanding runtime servers

Runtime servers are the workhorses of your Interact implementation. The runtime
servers listen and respond to requests from the touchpoint through the Interact
API. When your touchpoint requests an offer, it is the runtime server that responds
with the offer.

Interact works with server groups. A server group contains one or more runtime
servers. If you have multiple runtime servers, you can configure them to work
with a load balancer for better performance. Your touchpoint must be configured
to communicate with these runtime servers.
You can have multiple server groups. You might have one group for your call
center and one for your website. You might also have one group that is for testing
and one that is working with a live, customer-facing touchpoint. Each interactive
channel can have one production server group only.
After you finish designing and configuring your interaction in the design
environment and completed the Interact API code work with your touchpoint, you
are ready to send, or deploy, the interaction data to the runtime server. After you
deploy the interaction data to the runtime server, you can start testing how the
touchpoint works with Interact.
Deployment and delete

To ensure that you do not accidentally remove data that is required for a Interact
runtime server to run correctly, deploying an interaction configuration locks
Interact objects so you cannot delete them. After you deploy an interaction
configuration, you cannot delete any interaction strategy tab, interactive flowchart,
or interactive channel that is associated with the interaction configuration until you
remove the object from all server groups.
If you mark an interaction strategy or an interactive flowchart to be removed, and

then deploy the interactive channel to all server groups which contained the
interaction strategy or interactive flowchart, you can delete the interaction strategy
or interactive flowchart.
If you remove an interactive channel from all server groups to which you deployed
the interactive channel, you can delete any of the interaction strategies, interactive
flowcharts, or interactive channels.
For example, you have interactive channel A which contains interactive flowchart
A and interaction strategy A. You deploy interactive channel A to the server group
Test and the server group Production. You realize that interactive flowchart A is
inadequate, so you make interactive flowchart B. You mark interactive flowchart A
to be removed, and mark interactive flowchart B for deployment. You deploy the
flowchart to server group Test. You cannot delete interactive flowchart A because it
is still deployed to server group Production. After you deploy to server group
Production, you can delete interactive flowchart A. Over time, you realize you
must restructure your interaction configuration. You create interactive channel B,
interaction strategy B, and interactive flowchart C. You deploy this interaction
configuration to server group Test and server group Production. You also remove
interactive channel A, interaction strategy A, and interactive flowchart B from
server group Production. You cannot delete any objects because all objects are
deployed somewhere. After you remove interactive channel A, interaction strategy
A, and interactive flowchart B from server group Test, you can delete interactive
channel A, interaction strategy A, and interactive flowchart B.
Chapter 5. Understanding deployment to runtime servers 93

To delete an interactive channel
After you deploy an interaction configuration, you cannot delete an interactive
channel that is associated with the interaction configuration until you remove the
object from all server groups to ensure that you do not accidentally remove
required data from the runtime server.
About this task
Therefore, before you can delete an interactive channel, you must undeploy any
associated objects.
Procedure
1. Click the associated strategy on the interactive channel summary tab. Mark the
associated interaction strategy for undeployment.
2. Click the associated flowchart on the interactive channel summary tab. Mark
the associated Interact flowchart for undeployment.
3. Click View Deployment History on the interactive channel summary tab. If all
pending changes are marked with an X, click Redeploy. Continue to the next
step when the redeploy is successful.
4. Highlight the server group, click Undeploy. Undeploy is only enabled if the
previous steps were completed successfully. Continue to the next step when the
undeploy is successful.
5. Delete the associated interactive channel.
6. Delete the associated flowchart.
7. From the All Interactive Channels list, highlight the interactive channel and
delete it.
About deployment versioning

IBM Interact retains information about every deployment and assigns a version
number to it, along with any description or name you provide, for several reasons.
First, to ensure that the deployment record is maintained for future reference, so
that you can track when the deployment occurred, which user deployed the data,
whether the deployment was successful or not, and so on. Second, Interact
preserves the state of the deployment to ensure that it is available in the future for
redeployment or for loading back into the design time to use as the basis for
further modifications.
Information about each version
When you deploy an interactive channel or settings, you are required to name the
version you are deploying, such as SalesPortal_1, SalesPortal_2, and so on. A
sequential version number is also assigned automatically. You can also optionally
provide a description of the deployment. All of this information, along with more
status information such as the type of deployment and its status, are all available
in the Deployment History section of the interactive channel deployment tab.
At any point, you can select a deployment version in the Deployment History
section and either redeploy it as-is (which allows you to revert to an earlier
deployment if necessary), or to reload elements from that deployment to the
design time environment as a starting point for further modifications.
Note: Redeploying a version (rolling back to a deployment version) must be used

with care. For example, campaign objects or offers that existed at the time of the

original deployment might no longer exist, or might no longer be valid. Test the
behavior of the previous version of the deployment before using it in a production
environment.
Versioning actions
In addition to viewing the historical information about each deployment, there are
two actions you can take on past deployment versions:
Table 12. Version actions on the deployment tab
Action Description
Redeployment Allows you to deploy the specific version of
a past deployment to the specified server
group, following the same steps and
providing the same information as for
deploying a pending interactive channel.
Reloading individual flowcharts and Lets you reload the specified flowcharts and
strategies to the design time environment interactive strategies to the design time, so
you can use them as the basis for more
changes. You can select individual
flowcharts or strategies to reload, or reload
the entire interactive channel.
To deploy to a runtime server group

This procedure deploys to a runtime development, test, or production server group
for the Interactive Channel.
Before you begin
Before deploying to a live, customer-facing production runtime server group, you

must confirm that all interactive offers, interactive flowcharts, interaction strategy
tabs, interaction points, zones, and events are tested and approved.
Also, after you create a stable deployment, do not make any changes to the
Interactive channel, interactive flowcharts, and interaction strategies that are
associated with this deployment to ensure that you send the same configuration
when you deploy to the next group of servers (such as the production servers).
If you have any new or modified flowcharts or sessions, you have to navigate to
those flowcharts or sessions and manually mark them for deployment before
deploying the rest of the channel. If you do not, your modifications will not be
included in this deployment.
Procedure
1. Navigate to the deployment tab of the interactive channel that you want to
deploy.
The interactive channel deployment tab is displayed.
2. Click Deploy Interactive Channel Changes.
The Deploy Interactive Channel Changes dialog is displayed.
3. Use the Select a server group where changes will be deployed drop-down list
to specify the development, test, or production server group on which you
want to deploy.

4. Enter a version name for this deployment version, such as
Portal_CustomerCheck_6 or another value that is meaningful to you in the
deployment history and other reports.
5. Optionally, enter a description for this deployment that is meaningful to you in
the deployment history and other reports to help track the decisions and
purpose behind this deployment.
6. Optionally, select or clear the Also deploy current global settings check box.
This check box is selected by default, and deploys global settings that include
learning configuration settings, offer attribute definitions, audience level
mappings, and custom macros. Because deploying these settings might affect
other interactive channels that are already deployed in the same server group,
you might want to clear this check box to leave existing settings in server
group as they already are configured.
7. Confirm you have verified the prerequisites by selecting the check boxes.
The Deploy the Changes button does not become active until you confirm all
the prerequisites.
8. Click Deploy the Changes.
9. Enter the user name and password for the Interact user on the runtime server
and click Login to Server.
If you complete multiple deployments during the same IBM EMM user session,
the login data for the runtime server is cached, so you do not have to enter it
again.
Also, be aware that the credentials you enter here must be defined within IBM
Marketing Platform, even if Windows Integrated Login is enabled for your
installation. Windows Integrated Login credentials are not used to authorize
deployments.
Results
The data is deployed to the selected runtime server group. You can view the
results in the Deployment History section of the deployment tab, and with the
Interactive channel deployment history report.
To undeploy
Use the following steps to undeploy a deployment.
About this task
If you are bringing an interactive channel or touchpoint offline, you can undeploy
a deployment.
When you undeploy, Interact disables the data from the previous deployment from
the selected runtime server.
Note: In most cases, avoid undeploying from a production server, because

undeploying effectively turns off the rules for the interactive channel. Instead,
correct the data and deploy your changes, or use the Redeploy feature in the
Deployment History section to replace the deployed settings with a prior version.
Procedure
1. In Campaign, navigate to the deployment tab of the interactive channel you
want to undeploy.

2. In the Active Deployments section, select a deployment to a specific server
group and click Undeploy.
Clicking Undeploy starts the process to remove the interaction configuration
from the runtime server group. If the deployment was to a production server
group, there are safeguards to confirm that you are ready to send the changes
to a production server because this is a customer-facing system. A red warning
icon on this button indicates that there are changes that have not been
deployed to the production server group.
3. Optionally, provide an explanation of the reasons for undeploying in the
Deployment Description field.
4. Confirm you have verified the consequences by selecting the check box.
The Undeploy the Interactive Channel button does not become active until
you confirm the consequences.
5. Click Undeploy the Interactive Channel.
6. Enter the user name and password for a valid Interact user on the Interact
runtime and click Login to Server.
If you complete multiple deployments during the same Campaign user session,
the login data for the Interact run time is cached, so you do not have to enter it
again.
Results
The data is disabled on the selected Interact runtime server group. You can view
the results in the Deployment History section of the deployment tab, or in the
Interactive channel deployment history report. Undeploy does not remove data
that is used in reports.
If you undeploy all interactive channels and their associated data from a Interact
runtime server, it does not disassociate the runtime server from the design
environment.
To view the deployment tab

Each interactive channel includes a tab where you can see detailed information
about any active deployments of this interactive channel, view any pending
changes to the deployment status of the interactive channel, and see the history of
past deployments. You can also use the deployment tab to deploy, redeploy, and
undeploy interactive channel settings. This section describes what you can view on
the deployment tab.
Active Deployments
This section contains information about which deployments are active in each
server group you defined. For example, you might have one version of the
interactive channel that is deployed to your test server group, while another, fully
tested version of the interactive channel is deployed on your production servers
group.
Pending Changes
These are the components that are marked for deployment but are not deployed
yet. The title of the Pending Changes section indicates how many objects are
changed by the pending deployments.

This section only lists pending flowcharts and strategies, and does not include
entries for interaction points or other settings pending deployment. You can deploy
here, or deploy the global settings only. This table includes the following
information:
Type Indicates the type of change that this entry in the table represents, such as
flowchart, interactive strategy, and so on.
Change Waiting for Deployment
a link to the interactive flowchart or interaction strategy that contains the
change.
Source of Change
A link to the session or campaign that contains the change.
Change Type
Whether the change is new (Addition/Update) or a retraction
(Undeployment).
Date Requested
The date and time the change was marked for deployment.
Wait Time
The time that passed since the change was marked for deployment. This
value does not refresh automatically, but is updated when you reload the
page or click the Refresh button.
Requester
The user name of the Interact user who marked the change for
deployment.
If the item is disabled, the item was in the previous deployment but is not marked
for deployment. For example, your original deployment contained interactive
flowcharts A and B, and interaction strategies C and D. You can change interaction
strategy C and mark it for deployment. The Change Waiting for Production
Deployment list displays A, B, C, and D, but only C is black. A, B, and D are
disabled. You change interactive flowchart B, but do not mark it for deployment. If
you deploy now, Interact deploys the original A, B, and D, and the new version of
C. Interact does not use the new version of flowchart B because it was not marked
for deployment.
Deployment History
All of the deployment history that is captured in Interact can be viewed here and
sorted by any of the column types shown. You can also filter the information that
is shown here by server group and by status. For example, you might use the
column filter to show only the interactive channels that are deployed to your
production server group.
The Deployment History section contains the following information:

Version name
The name you assigned to this version of the deployment, in the Deploy
Interactive Channel Changes or Deploy Global Settings Only dialogs.
Version number
The number assigned to this version of the deployment.
Operation
The type of deployment, such as deploying the interactive channel with all
global settings, deploying only the global settings, and so on.

Global Settings
Whether global settings were included in the deployment or not (a
checkmark indicates that they were). Note that you cannot sort on the
Global Settings status.
Deployment Description
The description you entered into the deployment dialog at the time of
deployment.
Date The date and time of the deployment.
Server Group
The name of the server group to which the deployment was sent.
User The name of the user account that requested the deployment.
Status Whether the deployment was successful or failed. Deployments with a
status of "Failed" cannot be redeployed or reloaded to the design time.
Interactive Channel Name
The name of the interactive channel at the time it was deployed. If you
have renamed the interactive channel since the deployment, this name is
not updated.
There are also page controls that determine the maximum number of rows to show
per page of this list (5, 10, 20, and so on), and links to go to the start of the list,
previous and next pages of the list, and the end of the list.
Related tasks:
“Filtering tables in IBM products”
“Sorting tables in IBM products” on page 55
Filtering tables in IBM products

When you are viewing a table of information in IBM products, features might be
available that allow you to include or omit specific information (filter) the table
view, based on one column value or based on combinations of column values. This
section describes how to identify and use filtering options, when they are available
in a table.
About this task
The steps described here apply only to tables where filtering by column heading is
supported. To identify a table where this feature is supported, look for the
following icon in any column heading:
When this icon is gray, it indicates that filtering is available but not currently in
use for this column. The following table describes the different states of this icon:
Table 13. Column filter status icons
Filter icon Description
When this icon is displayed next to a
column heading, it indicates that no filter
that uses that column or its values is active
on the table. Click the icon to begin filtering.

Table 13. Column filter status icons (continued)
Filter icon Description
When this icon displayed next to a column
heading, it indicates that a filter that uses
that column or its values is active on the
table. Click the icon to view, modify, or
remove the filter.
Procedure
1. To filter a table by using a single column, click the filter icon in the column
heading. When you click the icon, the filter dialog is displayed with all of the
values on which you can filter the table. By default, all of the values are
selected, indicating that no information that is based on this filter criterion is
omitted from the table .
2. Use this dialog box to select the values that you want to display in this table,
and clear the check box next to the values you want to omit from the display.
For example, if you were filtering the Status column, you might select the
Failed check box, and clear the remaining check boxes, to display only items
with a status of "Failed" in the table.
3. To select all of the values to show in the table at one time, select the Filter By
check box at the top of the dialog.
4. To clear all of the values available to display in the table, clear the Filter By
check box.
This is useful if you want to display only a small number from a long list of
possible values; you can clear all of the check boxes at once, then select only
those you want to display.
5. To accept the changes you made and see the table that is filtered as specified,
click Filter.
6. To remove the column's filter from the table completely, click Remove Filter.
This has the same effect as selecting all of the check boxes.
Results
When you filter on more than one column, the filters are combined. For example, if
you were to filter out some server groups and also filter out some status values,
the results would be combined to show only the server groups that you chose to
display that have the specified status values.

Chapter 6. About Interact reporting
Interact is integrated with IBM EMM reporting to deliver comprehensive Cognos
reports in Interact.
The IBM EMM reports provide reporting schemas and related maintenance tools
that are required to integrate Interact with the supported version of IBM Cognos
BI, and to run and maintain the Cognos reports available in Interact.
Interact reports data

Interact reporting requires three sets of data to report on: the data from your
design environment, data from your production runtime environment, and data
from the learning module. For example, the Channel Offer Performance Summary
report requires data from the Campaign data source for data about offers, and data
from the contact and response history from the production runtime server.
The runtime environment stores all contact and response history in staging tables
to avoid impeding the performance of the production environment. Interact
provides a contact and response history module which copies data from the
runtime server to the design environment for your reports to have the correct data.
If you do not configure this utility, the reports cannot have the correct data.
Several reports require specific data about offers. To ensure that the reports contain
the correct data, you must use offers that are created with an offer template with
Allow offers created from this template to be used in real-time interactions
enabled.
Interact Reports and Reporting Schemas

The Interact Report Package reports are supported by IBM reporting schemas. You
can customize the schemas to specify time periods, configure audience levels, and
create extra performance reporting schemas.
You can customize the reporting schemas in the Interact Report Package in the
following ways:
v Specify calendar time periods for performance reports
v Configure the audience level for performance reports
v Create extra performance reporting schemas for extra audience levels
The following table maps the individual IBM Cognos BI reports provided in the
Interact Reports Package to the IBM reporting schemas that support them.

Interactive
Channel /
Interact Campaign Interact Interact
Interactive Performance Deployment Runtime Learning
View schema View schema History View schema View schema
Campaign - X X
Interactive
Channel
Deployment
History
Campaign - X X X
Interactive
Cell
Performance
Over Time
Campaign - X X X
Interactive
Cell
Performance
by Offer
Campaign - X X X
Interactive
Offer
Performance
Over Time
Campaign - X X X
Interactive
Offer
Performance
by Cell
Campaign - X X
Interactive
Offer
Learning
Details
Interactive X X X X
Cell Lift
Analysis
Interactive X X
Channel -
Channel
Deployment
History
Interactive X X
Channel -
Channel
Event
Activity
Summary
report

Interactive
Channel /
Interact Campaign Interact Interact
Interactive Performance Deployment Runtime Learning
View schema View schema History View schema View schema
Interactive X X X
Channel -
Channel
Interaction
Point
Performance
Summary
Interactive X
Channel -
Channel
Treatment
Rule
Inventory
Interactive X X X
Segment Lift
Analysis
Interaction X X X
Point
Performance
Viewing Interact reports

Interact integration with reports can be used to run Cognos reports from within
Campaign. Some reports contain links to other reports to provide more
information.
As the Interact reports exist within Campaign, see the Campaign User's Guide for
generic instructions on viewing reports.
You can customize all the example reports available with the Interact Reports
Package, for example, add more audience levels. For details about how to
customize Interact example reports, see the Marketing Platform Administrator's
Guide.
To view reports from the interactive channel Analysis tab

You can use the Interactive Channel Analytics area to view several Interact reports.
About this task
The following reports are available from the Interactive Channel Analytics tab:
v Channel Deployment History
v Channel Event Activity Summary
v Channel Interaction Point Performance Summary
v Channel Interactive Segment Lift Analysis
v Channel Learning Model Performance Over Time
v Interactive Channel Treatment Rule Inventory
Chapter 6. About Interact reporting 103

Procedure
1. Select a Report Type from the Interactive Channel Analysis tab.
If no additional configuration is needed, the report is displayed.
2. If there are configuration options after the report is displayed, select filters for
the report, then click Refresh.
For example, select the interaction point or an end date and time to view for
the Channel Interaction Point Performance Summary report. On other reports,
you might select date ranges, or specific channel data to use for filtering.
3. If you are required to enter configuration options before the report is generated,
as might be the case with the Channel Learning Model Performance Over Time
report, select the required report filters and options, then click the Next or
Finish buttons at the bottom of the report.
Results
The selected report is displayed.
To view Interact reports from the Campaign Analysis tab

You can use the Campaign Analytics tab to view several Interact reports.
About this task
The following reports are available from the Campaign Analysis tab:
v Event pattern
v Interactive Cell Lift Analysis
v Interactive Cell Performance by Offer
v Interactive Cell Performance Over Time
v Interactive Offer Learning Details
v Interactive Offer Performance by Cell
v Interactive Offer Performance Over Time
Procedure
1. Select a Report Type from a Campaign Analysis tab.
the report, then click Refresh.
For example, select the cell to view for the Interactive Cell Performance by
Offer report.
Results

To view Interact reports from Analytics Home
You can use the Interact Reports folder of the Campaign Analytics area to view
several Interact reports.
About this task
The following reports are available from the Interact Reports folder of the
Campaign Analytics area:
v Event Pattern
v Interactive Cell Lift Analysis
v Interactive Cell Performance by Offer
v Interactive Cell Performance Over Time
v Interactive Offer Learning Details
v Interactive Offer Performance by Cell
v Interactive Offer Performance Over Time
In addition, the Zone Performance Report by Offer report is available when you
click the Zone Performance folder in the Interact Reports folder of the Campaign
Analytics area:
Procedure
1. Select Analytics > Campaign Analytics
2. Select the Interact Reports folder. Optionally, click the Zone Performance
folder to view the zone performance reports list.
3. Select the report that you want to view.
The Report Parameters window is displayed.
4. Select the campaign for which you want to view data, then click Generate the
Report.
the report, then click Refresh
For example, select the cell to view for the Interactive Cell Performance by
Offer report.
Results
About the Interaction Point Performance report portlet

The only Interact specific report available in the Dashboard is the Interaction Point
Performance report portlet. This portlet shows the number of offers accepted per
interaction point over a seven day period. By analyzing this report, you can
determine the peak marketing locations on your interactive channel to help design
future campaigns.

This dashboard report is defined to point to the interactive channel with the ID of
1. To change the ID of the interactive channel this report points to, see the
Marketing Platform Administrator's Guide.
About the Channel Deployment History report (interactive channel)

The Channel Deployment History report is an audit log for tracing changes to all
runtime servers, and is available from the interactive channel Analysis tab. You
can filter this report by runtime servers, campaigns, or the user who performed the
deployment.
The campaign, interaction strategy, session, and flowchart names are links to the
campaign, interaction strategy, session, and interactive flowchart. To return to the
report, use the Back button of your browser.
This report is also available from the campaign Analysis tab and the Interact
Reports folder in Analytics Home.
About the Channel Event Activity Summary report

The Channel Event Activity Summary report can be used to track the activity of
deployed events for an interactive channel.
You can filter the report by all categories, a particular category, all events, or a
single event. You can compare how often an event occurred over the last
twenty-four hours, or the last seven days. The report also points out the peak hour
or day and the slowest hour or day for an event. You can use the peak data to help
determine the best ways to optimize your processing resources, or plan your
marketing strategies around expected traffic. By knowing when the slowest times
are, you can plan your deployments to occur when they will be the least
disruptive.
About the Channel Interaction Point Performance Summary

report
The Channel Interaction Point Performance Summary report measures the
performance of each interaction point in the interactive channel across all offers
and segments. By analyzing this report, you can determine the peak marketing
locations on your interactive channel to help design future campaigns.
You can filter this report by all interaction points or a single interaction point. The
report displays the number of offers displayed, accepted, and rejected for that
interaction point.
About the Channel Treatment Rule Inventory report

The Channel Treatment Rule Inventory report is a list of all the treatment rules that
are associated with an interactive channel. You can filter this list by a combination
of target cells, zones, and campaigns. You can use this report as a diagnostic tool
when investigating the marketing behavior around a specific cell, zone, or
campaign.
The campaign and interaction strategy names are links to the campaign or
interaction strategy. The offer name is a link to the Interactive Offer Performance
Over Time report, which is filtered by that offer. To return to the Channel
Treatment Rule Inventory report, use your browser's Back button.

About the Interactive Segment Lift Analysis report
Lift analysis reports show the performance improvement that is created by using
Interact built-in learning. The Interactive Segment Lift Analysis report shows the
acceptance rate of offers by smart segment, comparing offers presented randomly
and offers presented by Interact built-in learning. This report shows these values
over time, so you can see trends for the better, or worse, and use that information
to refine your marketing strategies.
This report is populated only if you use Interact built-in learning.
About the Channel Deployment History report (campaign)

The Channel Deployment History report displays the deployment data for all
interaction strategies and the interactive channels that are associated with a
campaign. Use the Analysis tab of the Campaign to view this report.
The campaign, interaction strategy, session, and flowchart names are links to the
campaign, interaction strategy, session, and interactive flowchart. To return to the
report, use the Back button of your browser.
This report is available from Analysis of the interactive channel.
About the Interactive Offer Learning Details report

The Interactive Offer Learning Details report displays all the learning attributes
that you are tracking with the built-in learning module.
Each chart in the report shows the likelihood of a visitor to respond to the
specified offer if they have a specific value for an attribute of interest. You can use
this report to analyze what the learning module is learning and use that to modify
what attributes you track or your offer-to-segment assignments.
You must select an offer to display data in the Interactive Offer Learning Details
report. By default, no data displays.
This report is not available if you are using external learning.
About the Interactive Cell Performance reports

The Interactive Cell Performance reports have two variations: Over Time and by
Offer. These reports measure the performance of target cells in their inbound
marketing scenarios for a campaign. When you filter by target cell, you are
filtering by the cell that is assigned to the smart segment in your treatment rule.
You can sort these reports by all cells or a specific target cell. These reports display
the number of offers that are presented, accepted, and rejected by a target cell over
time or by offer. These reports cover all target cells that are associated with the
treatment rules in an interaction strategy within a campaign.
If you display these reports by clicking a link on the Interaction Strategy tab, the
report is automatically filtered by target cell. When you display these reports by
using a link under the Analytics > Campaign Analytics menu, the report covers
all target cells, but can be filtered for specific cells after it is displayed.

About the Interactive Offer Performance reports
The Interactive Offer Performance reports have two variations: Over Time and by
Offer. These reports measure the performance of offers in their inbound marketing
scenarios for a campaign. You can sort these reports by all offers or a specific offer.
These reports display the number of times that an offer was presented, accepted,
and rejected over time or by target cell (segment). These reports cover all offers
that are associated with the treatment rules in a campaign.
About the Interactive Cell Lift Analysis report

Lift analysis reports show the performance improvement that is created by using
Interact built-in learning. The Interactive Cell Lift Analysis report shows the
acceptance rate of offers by cell, comparing offers that are presented by random
and offers that are presented by Interact built-in learning.
This report shows these values over time, so you can see trends for the better, or
worse, and use that information to refine your marketing strategies. This report is
populated only if you use Interact built-in learning.
About the Channel Learning Model Performance Over Time

report
The Channel Learning Model Performance report compares the performance of
two channel learning models over a certain time period to help you determine the
effectiveness of each learning model in specific time periods.
If you select this report from the Analysis tab of an interactive channel, the report
is automatically generated for the current interactive channel. If you generate the
report by selecting Analytics > Campaign Analytics > Interact Reports, you can
select the interactive channel to which you want the report to apply. You can filter
this report for a specific date range, and you can filter the report for specific
click-through/accept properties, and no response/reject properties as wanted.
About the Zone Performance Report by Offer

The Zone Performance Report by Offer is an interactive cell performance report
that is filtered by interaction point. You can use this report to see how offers are
performing by zone.
You can view the Zone Performance Report by Offer by selecting Analytics >
Campaign Analytics, then clicking Interact Reports, and then Zone Performance
Reports. When you open the report, you can use the Zone drop-down list to
specify the zone for which you want to view the performance charts. After the
report is generated, you can select different Interaction Points and resubmit the
report to update the performance data.
About the Event Pattern report

The Event Pattern report shows you event pattern activity across interactive
channels and their categories.
You can use this report to analyze how personalized offers were presented to
visitors through event patterns. You can also analyze how many event patterns are
triggered to visitors in the interactive channels you report on.

To run an Event Patter report, you can select which interactive channels you want
to analyze. Then, you can select categories in those interactive channels to also
appear in your report.
This report is available from the Interact Reports folder of the Campaign Analytics
area.
To filter by interaction point

Filter the Channel Interaction Point Performance Summary report by interaction
point to view data only for the interaction point that is required.
About this task
To filter a report by interaction point, select the interaction point by which you
want to filter data from the Interaction Point list. To select all interaction points,
select Interaction Point.
The report automatically reloads, displaying only the data you selected.
To filter by event or category

You can filter the Channel Event Activity Summary report by event and category.
About this task
To filter a report by category, select the category by which you want to filter data
from the Select Category list. To select all categories, select Category.
To filter a report by event, select the event by which you want to filter data from
the Select Event list. To select all events, select Event Name. If you have selected a
category, when the report reloads, the Select Event list displays the events in the
selected category only.
To filter by offer
You can filter the following reports by offer: Interactive Offer Learning Details,
Interactive Offer Performance by Cell, and Interactive Offer Performance Over
Time.
About this task
To filter a report by offer, select the offer by which you want to filter data from the
Offer list. To select all offers, select Offer ID.
To filter by target cell

You can filter the following reports by target cell: Interactive Cell Performance by
Offer, and Interactive Cell Performance Over Time

About this task
When you filter by target cell, you are filtering by the cell that is assigned to the
smart segment in your treatment rule.
To filter a report by target cell, select the target cell by which you want to filter
data from the Target Cell list. To select all cells, select Cell ID.
To filter by time
You can filter the following reports by time: Interactive Cell Performance Over
Time, Interactive Offer Performance Over Time, Channel Event Activity Summary,
and Channel Interaction Point Performance Summary
About this task

To filter a report by date, select end date for the Last 7 Day range and click
Refresh. You can enter a date or select one from the calendar list.
To filter a report by time, select end time for the Last 24 hour range and click
Refresh. The default is 12:00 AM. This displays yesterday's data. If you clear the
check box, the report uses the current time on the Cognos report server.
If there is no data for a particular date or time, the graph does not display any
data. In line graphs, if there is no data, the trend goes across dates that contain
data only. For example, you have the following data points: 6/1 (100), 6/2 (no
data), and 6/3 (50). The line goes from 100 on 6/1 to 50 on 6/3. The line may pass
through ~75 on 6/2 but that is not an actual data point. Also, if there is only one
data point, no line displays, as there is nothing to connect.
To filter the Channel Deployment History report

To filter the Channel Deployment History report, select the criteria by which you
want to filter data and click Refresh. You can select multiple criteria per list by
using CTRL+click. To select all criteria, click Select all. Selecting Deselect all
indicates no filter, which shows the same data as Select all.
About this task
You can filter the Channel Deployment History report on the interactive channel
analysis tab by the following criteria:
v Deployment Destination. The server groups to which you have deployed this
interactive channel
v Campaigns Updated by Change. The campaigns that contain the interaction
strategies that are associated with this interactive channel
v Deployment Owner. The IBM users who deployed this interactive channel
The report does not load until you click Refresh. when it reloads, the report
displays only the data you selected.
To filter the Channel Treatment Rule Inventory report

You can use multiple criteria to filter the Channel Treatment Rule Inventory report.

About this task
You can filter the Channel Treatment Rule Inventory report by the following
criteria:
v Target Cells. The cells that are assigned to the smart segments in your treatment
rules associated with this interactive channel
v Zones. The zones in this interactive channel
v Campaigns. The campaigns that contain interaction strategies that are associated
with this interactive channel
To filter the report, select the criteria by which you want to filter data and click
Refresh. You can select multiple criteria per list by using CTRL+click. To select all
criteria, click Select all. Selecting Deselect all indicates no filter, which shows the
same data as Select all.
The report does not load until you click Refresh. When it reloads, the report
displays only the data you selected.

Before you contact IBM technical support
If you encounter a problem that you cannot resolve by consulting the
documentation, your company's designated support contact can log a call with
IBM technical support. Use these guidelines to ensure that your problem is
resolved efficiently and successfully.
If you are not a designated support contact at your company, contact your IBM
administrator for information.
Note: Technical Support does not write or create API scripts. For assistance in
implementing our API offerings, contact IBM Professional Services.
Information to gather
Before you contact IBM technical support, gather the following information:
v A brief description of the nature of your issue.
v Detailed error messages that you see when the issue occurs.
v Detailed steps to reproduce the issue.
v Related log files, session files, configuration files, and data files.
v Information about your product and system environment, which you can obtain
as described in "System information."
System information
When you call IBM technical support, you might be asked to provide information
about your environment.
If your problem does not prevent you from logging in, much of this information is
available on the About page, which provides information about your installed IBM
applications.
You can access the About page by selecting Help > About. If the About page is not
accessible, check for a version.txt file that is located under the installation
directory for your application.
Contact information for IBM technical support
For ways to contact IBM technical support, see the IBM Product Technical Support
website: (http://www.ibm.com/support/entry/portal/open_service_request).
Note: To enter a support request, you must log in with an IBM account. This
account must be linked to your IBM customer number. To learn more about
associating your account with your IBM customer number, see Support Resources
> Entitled Software Support on the Support Portal.

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
170 Tracer Lane
Waltham, MA 02451
U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not

been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.
Privacy Policy and Terms of Use Considerations

IBM Software products, including software as a service solutions, ("Software
Offerings") may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user or for other purposes. A cookie is a piece of data that a web site can
send to your browser, which may then be stored on your computer as a tag that
identifies your computer. In many cases, no personal information is collected by
these cookies. If a Software Offering you are using enables you to collect personal
information through cookies and similar technologies, we inform you about the
specifics below.
Depending upon the configurations deployed, this Software Offering may use
session and persistent cookies that collect each user's user name, and other
personal information for purposes of session management, enhanced user usability,
or other usage tracking or functional purposes. These cookies can be disabled, but
disabling them will also eliminate the functionality they enable.
Various jurisdictions regulate the collection of personal information through

cookies and similar technologies. If the configurations deployed for this Software
Offering provide you as customer the ability to collect personal information from
end users via cookies and other technologies, you should seek your own legal
advice about any laws applicable to such data collection, including any
requirements for providing notice and consent where appropriate.
IBM requires that Clients (1) provide a clear and conspicuous link to Customer's
website terms of use (e.g. privacy policy) which includes a link to IBM's and
Client's data collection and use practices, (2) notify that cookies and clear gifs/web
beacons are being placed on the visitor's computer by IBM on the Client's behalf
along with an explanation of the purpose of such technology, and (3) to the extent
required by law, obtain consent from website visitors prior to the placement of
cookies and clear gifs/web beacons placed by Client or IBM on Client's behalf on
website visitor's devices
For more information about the use of various technologies, including cookies, for
these purposes, See IBM's Online Privacy Statement at: http://www.ibm.com/
privacy/details/us/en section entitled "Cookies, Web Beacons and Other
Technologies."
Notices 117

Printed in USA

IBMInteract911UsersGuide en Us

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IBMInteract911UsersGuide en Us

Uploaded by

Copyright:

Available Formats

IBM Interact

Version 9 Release 1.1

© Copyright IBM Corp. 2001, 2014 iii

iv IBM Interact: User's Guide

What Interact does

Use Interact to enhance your marketing efforts

Use Interact to refine your marketing strategies

© Copyright IBM Corp. 2001, 2014 1

You configure Interact to integrate with your touchpoints using an application

2 IBM Interact: User's Guide

Customer Interact Test

In production, the architecture may be more complicated. For example, a runtime

The following figure shows the Interact environment in more detail.

Chapter 1. IBM Interact 3

Interact deployments consist of the following:

In the staging runtime environment-which is the same as a production runtime

4 IBM Interact: User's Guide

Campaign key concepts

Chapter 1. IBM Interact 5

Other, more complex examples of audience hierarchies exist in business-to-business

The term "cell" is sometimes used interchangeably with "segment." Strategic

6 IBM Interact: User's Guide

You use flowcharts to accomplish particular marketing goals, such as determining

Each flowchart has the following elements:

Offers are reusable:

Like campaigns, sessions are also composed of individual flowcharts.

Interact key concepts

Chapter 1. IBM Interact 7

The design environment is where you complete most of your Interact

The design environment is installed with the Campaign web application.

An interactive channel is a representation in Campaign of a touchpoint where the

Interactive channels also contain production runtime and staging server

An interactive flowchart is related to but slightly different from a Campaign batch

Note: Interactive flowcharts can be created in a Campaign session only.

8 IBM Interact: User's Guide

Chapter 1. IBM Interact 9

The customer data is used for the following purposes:

This data is read-only for the runtime environment.

10 IBM Interact: User's Guide

Interact is used by many people within your organization. Because Interact is a

Chapter 1. IBM Interact 11

Interact workflow for implementing the marketing plan

12 IBM Interact: User's Guide

This brainstorming is a cooperative effort between the person who:

Configure the interaction

Test the interaction

Review the interaction

Deploy the interaction

Chapter 1. IBM Interact 13

This diagram shows a sample design workflow.

14 IBM Interact: User's Guide

Determine how to interact with the visitors

This question has an almost unlimited number of answers, for example:

Define the components you configure in Interact

Evaluate extra options

There are several optional features, including offer suppression, learning,

Logging in to IBM EMM

Chapter 1. IBM Interact 15

You need the following.

The URL is:

host is the machine where Marketing Platform is installed.

domain.com is the domain in which the host machine resides

port is the port number on which Marketing Platform application server is