To configure a Response process

The Response process compares response information with contact history and logs information to the response history tables for the appropriate audience level.

For complete information, see About contact history.

Navigate to the list of campaigns where you created your contact flowcharts (the ones that assigned the offers you plan to analyze).

Typically, you would create a separate flowchart to handle the response process.

Drag the Response process from the palette to your flowchart.

Connect a Select or Extract process as input into the Response process. The Select or Extract process must read from an action table. An action table is a database file or table produced outside of IBM® Campaign. An action table contains response data collected after offers are presented to customers. Typically, this data includes customer identification, response codes, and attributes of interest.

Double-click the Response process in the flowchart.

The process configuration dialog opens.

Use the Source tab as follows.

If you followed the steps in this procedure, the Input list already displays the correct input. The input must originate from the mapped action table in your data mart that holds your customer response information.

If you are using a delimited flat file as input to the Response process, you must ensure that all data types in the input files are mapped appropriately, as this is not enforced by the Response process. Using a mismatched data type (for example, having a treatment code mapped as "numeric" when the UA_Treatment.TreatmentCode field is a "string" type) causes a database error on some databases (for example, system tables on DB2®).

For Response Date, select a date from your action table to associate with the records output by the Response process. By default, a value of "Today" is selected.

For Response Type Code, choose a field from your action table. The response type codes are globally defined and available for all campaigns. Response types are the specific actions that you are tracking, such as click-through, inquiry, purchase, activation, and use. Each response type is represented by a unique response code.

Use the Mapping to Treatments tab to select the fields to be tracked and match them to a list of offer and treatment attributes.

In the Candidate Action Fields list, expand the action table that you are using, so you can see the list of fields.

Use the Add button to match Candidate Action Fields to the corresponding attributes in the Matched Offer/Treatment Fields list. The Offer/Treatment Attribute column lists all offer or treatment attributes in the system.

It is best to match at least one Attribute of Interest and one Response Code.

Unmapped fields, and fields for which values not available (or NULL) are not used for response attribution. For a treatment instance to receive response credit, all populated fields must match, except for controls, for which all codes are ignored.

Click the Log tab to specify additional fields to log to response history.

Use the controls to match fields from the Candidate Fields list with fields in the Fields to Log list.

You can automatically match fields by clicking Match. Fields with exact matches for the Table Field names are automatically added to the Fields to Log list. If there are multiple matching fields, the first match is taken.

Click the General tab to assign a name and descriptive note to the process.

10.

Click OK.

The process is now configured. You can test run the process to verify that it returns the results you expect. When you save and run the flowchart, information is written to the response history system tables.