In Interact, you can use the postEvent method in the Interact API to trigger an event which logs an "accept" or "reject" action for an offer. You can also augment the system to allow the postEvent call to record additional response types, such as Explore, Consider, Commit, or Fulfill. All of these response types must exist in the UA_UsrResponseType table in the Campaign system tables. Using specific event parameters to the postEvent method, you can record additional response types and define whether an accept should be included in learning.
To log additional response types, you must add the following event parameters:
UACIRESPONSETYPECODE — a string representing a response type code. The value must be a valid entry in the UA_UsrResponseType table.To be a valid entry in the UA_UsrResponseType you must define all of the columns in the table, including CountsAsResponse. Valid values for CountsAsResponse are 0, 1, or 2. 0 indicates no response, 1 indicates a response, and 2 indicates a reject. These responses are used for reporting.
UACILOGTOLEARNING — A number with the value 1 or 0. 1 indicates Interact should log the event as an accept for learning. 0 indicates Interact should not log the event for learning. This parameter enables you to create several postEvent methods logging different response types without influencing learning. If you do not define UACILOGTOLEARNING, Interact assumes the default value of 0.You may 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 exactly the same (have the Log Offer Acceptance action), but the names are different so that the person working with the API can distinguish between them.
First, set up all the name-value pairs
This first example shows using the individual events.
IBM Unica Interact
8.5.0
|
Copyright IBM Corporation 2011. All Rights Reserved.
|
For more information, see our support and community site: Customer Central
|
|