Adding an action in Design Time UI

To add an action for an event or an event pattern, perform the following steps.

On the Events page, click Add events or Add event patterns.
Add/Edit event or Add/Edit event pattern dialog is displayed.
Click the Actions tab and click Add action.
Add/Edit action dialog is displayed.
Add/Edit action dialog for an event
Add/Edit action dialog for an event pattern

Common fields you use to define all types of actions

Interact supports eight different types of actions. There are common fields in Add/Edit action dialog that apply to all types of actions, and some fields that are only applicable to specific types of actions.

This table lists and describes common fields in the Add/Edit action dialog.

Common fields in the Add/Edit action dialog


Fields	Description
Action tab
Action type	Select one of the eight action types, which is invoked when an event occurs or when the conditions of an event pattern is met: Trigger re-segmentation Log offer contact Log offer acceptance Log offer rejection Trigger userexpression Trigger events Suppress offers Qualify segments For the first four action types, an event or event pattern can have atmost one of each. For remaining four action types, an event or event pattern can have as many as actions of each type.
Invoke action when pattern state	Only applicable and visible to Event Patterns. Met, invoke action when conditions of event pattern are met Not met, invoke action when conditions of event pattern are not met. Use this option to track visitors’ in-activities.
Check pattern state	It is only applicable to Event Pattern and is visible when “Invoke action when pattern state not met” option is selected. Specify the following when pattern state is evaluated for in-activities: At the end of cycle Evaluate at the end of pattern time span After first event occurs, wait X Days/Hours/Minutes/Weeks Evaluate after specified duration since the first event occurs After most recent event occurs, wait X Days/Hours/Minutes/Weeks Evaluate after specified duration since the most recent event occurs
Invoke action	Specify when action is invoked: Immediately Invoke action immediately With a delay of X Days/Hours/Minutes/Weeks When an event occurs or pattern conditions are met or not met, action is invoked after specified duration. On X Calendar days/Calendar weeks/Calendar months on at the time When an event occurs or pattern conditions are met or not met, action is invoked at a scheduled date and time Note: For a "Trigger re-segmentation" or a "Trigger user expression" action, although delayed option can be defined in UI, but invoking action in delay mode is irrelevant because "re-segmentation" or "calculate expression" must happen in session. Note: A "Suppress offer" or a "Enable segment" action can also only be invoked in "Immediately" mode, therefore no option of "Delayed" invoke is available in UI.
Conditions tab
Parameter name	Specify name of Name/Value pair as condition if an action is invoked or not. The Name/Value pair can be passed into postEvent API in Unica runtime environment.
Parameter value	Specify value of Name/Value pair as condition if an action is invoked or not. The Name/Value pair can be passed into postEvent API in Unica runtime environment.

Fields you use to define Trigger user expression action

In section of Define an expression to calculate, provide the following information:

Select an Audience level, the profile attributes will be updated for the selected audience level.
Optional. Under Field name to assign the result of expression, specify the field name.
Define an expression using functions, variables, operators and various attributes by selecting them from the list at right, and click Use.
1. Click Check Syntax to check the syntax of the expression you have created.
2. Click Clear to clear the expression.

Fields you use to define Trigger event action

Define events to trigger for an action in the section of Specify the events to trigger. You can either select from list of existing events in the Interactive Channel or create a new event.

Select Create new events option to create new events and trigger this action.
Select the option Select from existing events to pick the existing events to trigger this action. The events are grouped by their interactive channel, with the interactive channels’ hierarchy from top to bottom.
1. Under Available events, select events and click >> button, the selected events is displayed in Selected events list.

Granular suppression

Earlier, when offers were suppressed, via offer suppression rules, event/pattern actions, or black list, it was suppressed globally. This used to create a limitation because there were cases where marketers wanted to suppress an offer in only one channel while keepoing it eligible in others. Some scenarios are as follows:

Scenario 1: An offer was presented to a customer multiple times, implying that the customer was not particularly interested in those offers. However, such offers have a high value to the merchant. Therefore, the marketer wants such offers to be suppressed in the mobile channel, as there was limited space on a mobile app, while still keeping it available on the web channels as there was space for more offers.

Scenario 2: Customers rejected offers from the merchant’s website but later decided that they wanted to take advantage of it. However, it was no longer available on the website. Customers may call the customer service to get back the offer. This creates a situation where offers were not available on one channel had to be available on another channel (call center channel).

With the introduction of granular suppression in 12.1.7, marketers will be able to fine tune the scope of an offer suppression and Qualifying Segments to specific interactive channels and even specific zones.

Fields you use to define Suppress offer action

Define offers to suppress in the section of Select offers to suppress. You can suppress a single offer or all offers that have a same offer attribute value.

Select the Individual offer option to suppress a single offer.
1. Optional. In the Find/filter offers box, type to search offer by offer name.
2. Select the offer and offer is displayed in the Selected offer box.

Select the Offers with same attribute value option to suppress all offers with same offer attribute value.

In 12.1.7, we have introduced four built-in parameters which can be used for configuring the "Suppress Offer" action for an event or event pattern. The parameters are:

Table 1.
Parameter	Description
`UACIPOST_ActionForChannel`	A pipe delimited list of the names of interactive channels that will be suppressed.
`UACIPOST_ActionExceptChannel`	A pipe delimited list of the names of interactive channels that will not be suppressed.
`UACIPOST_ActionForZone`	A pipe delimited list of the names of zones that will be suppressed. Suppressed zones only apply to the concerned channel.
`UACIPOST_ActionExceptZone`	A pipe delimited list of the names of zones that will not be suppressed. Not suppressed zones only apply to the concerned channel.

For all the parameters, use the prefix _@_ (underscore)to denote the interactive channel in which the action is triggered.

If you do not set a value for any of the parameters, it is deemed as invalid and that parameter is ignored.

If you do not configure any of the parameters, the offers are suppressed globally.

For UACIPOST_ActionExceptZone and UACIPOST_ActionForZone to work, pass the parameter UACIZoneName as an API parameter when invoking postEvent with the event that triggers the event pattern.

Optional. In the Find/filter attributes box, type to search offer attribute by name.
Select an attribute. It is displayed in the Selected attribute box.
Provide value of the attribute.

Fields you use to define Qualify segment action

Define segment to enable in the section of Select segment to enable.

Select an audience level from Audience level list, the segment will be loaded for selected audience level.
Optional.In the Find/filter segments box, type to search by segment name.
Select a segment and the segment is displayed in the Selected segment box.

In 12.1.7, we have introduced four built-in parameters which can be used for configuring the "Suppress Offer" action for an event or event pattern. The parameters are:

Table 2.
Parameter	Description
`UACIPOST_ActionForChannel`	A pipe delimited list of the names of interactive channels that will be suppressed.
`UACIPOST_ActionExceptChannel`	A pipe delimited list of the names of interactive channels that will not be suppressed.
`UACIPOST_ActionForZone`	A pipe delimited list of the names of zones that will be suppressed. Suppressed zones only apply to the concerned channel.
`UACIPOST_ActionExceptZone`	A pipe delimited list of the names of zones that will not be suppressed. Not suppressed zones only apply to the concerned channel.

For all the parameters, use the prefix _@_ (underscore)to denote the interactive channel in which the action is triggered.

If you do not set a value for any of the parameters, it is deemed as invalid and that parameter is ignored.

If you do not configure any of the parameters, the offers are suppressed globally.

For UACIPOST_ActionExceptZone and UACIPOST_ActionForZone to work, pass the parameter UACIZoneName as an API parameter when invoking postEvent with the event that triggers the event pattern.