An event is one of the three elements of the Interact configuration in the design environment that interacts directly with the
Interact API. When coding your touchpoint to work with the
Interact API, you use the
postEvent method to reference events. The name of the event used in the
Interact API must match the name of the event as configured in the design environment. This name is not case-sensitive.
If you create an event with more than one log offer action, remember that the Interact API performs the same action for the associated offer. Therefore, you should not create an event which 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 may be useful in your environment.
The Interact API can also use events to trigger actions that you define 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 may need 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.
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
Interact API can distinguish between them.
When working with the Interact API, there is no functional difference between the events, but the naming conventions may make the code clearer. Also, if you give each custom response a separate name, the Channel Event Activity Summary report displays more accurate information.