Home
Administrator Guides
Administrator Guide
Triggers administration
Unica Campaign allows you to define inbound and outbound triggers that can be used in all flowcharts in a partition.
Tokens supported by triggers
Tokens can be used in the command line of an outbound trigger to pass specific information from the running flowchart.

Administrator Guides
- Administrator Guide
  - Unica Campaign administration overview
    The Settings menu provides access to most of the tasks that Unica Campaign administrators typically perform.
  - Security in Unica Campaign
    Security policies control user access to the objects and features in Unica Campaign.
  - Database table administration
    Unica Campaign administrators must perform initial one-time tasks and routine administration tasks that pertain to database tables.
  - Customizing campaigns
    Administrators can customize campaigns by using custom campaign attributes, initiatives, and products.
  - Offer template concepts
    Before administrators perform offer template management tasks, there are several important concepts to understand.
  - About audience level administration
    Unica Campaign is delivered with a single audience level called Customer. You can define any additional audience levels that you need. Audience levels let flowchart designers target specific groups, such as Households, in marketing campaigns.
  - Before you begin working with contact history
    Contact history is stored in the Unica Campaign system database in separate tables by audience level. Therefore, you need to set up audience levels before you begin working with contact history.
  - Response history administration
    Before you begin working with response history, you should read the audience level administration topics and set up required audience levels.
  - Monitoring and controlling flowchart runs
    Choose Campaign > Monitoring and use the All monitored runs page to view the status of all active flowcharts and suspend, resume, or stop flowchart runs.
  - Dimension hierarchy concepts
    A dimension hierarchy is a data construct that groups data into bins based on value ranges. Dimension hierarchies are the basis for a variety of reports.
  - Triggers administration
    Unica Campaign allows you to define inbound and outbound triggers that can be used in all flowcharts in a partition.
    - What is an inbound trigger?
      An inbound trigger is a message that is broadcast to one or more campaigns. You can configure a flowchart to "listen" for a particular trigger to start the execution of one or more processes.
    - What is an outbound trigger?
      An outbound trigger is the execution of a command, batch file, or script that takes place after a flowchart or process is run. You can define triggers to perform virtually any action, such as opening an application, sending an email, or running a program.
    - How are triggers defined?
      You define triggers when editing a flowchart. A trigger that you define in one flowchart is available to all flowcharts in the same partition.
    - Working with trigger folders and triggers
      You can create inbound and outbound triggers and organize them in folders.
    - Setting up outbound triggers
      You must have permissions to use triggers in a flowchart.
    - Setting up inbound triggers
      You must have permissions to use triggers in a flowchart.
    - Setting up the trigger utility on a remote Windows machine
      You can configure a Windows machine to send triggers to a Unica Campaign installation on UNIX or Windows. For Windows installation, ensure that the listener port is open for incoming traffic on the Campaign listener machine. Follow these steps to set up the unica_actrg utility and required files on a remote Windows machine.
    - Tokens supported by triggers
      Tokens can be used in the command line of an outbound trigger to pass specific information from the running flowchart.
    - Unica Campaign trigger utility syntax
      The trigger utility (unica_actrg) supports the following syntax and options.
  - Unica Campaign log files
    Unica Campaign records information in several different log files.
  - JVM Parameters
  - About codes in Unica Campaign
    Each campaign, cell, offer, and treatment in Unica Campaign has an identifying code that is generated by code generators, and conforms to a specified format.
  - Accessing the Advanced settings
    When a flowchart is open for editing, administrators can choose the Advanced settings option on the Admin menu to make administrative changes that affect only the current flowchart.
  - Unica Campaign integration with other products
    Unica Campaign optionally integrates with a number of other products.
  - Unica Campaign listeners
    The listener is a key component of Unica Campaign. It provides an interface between front-end clients and back-end analytical server processes.
  - Unica Campaign utilities
    Administrators use the Unica Campaign utilities to manage listeners, sessions, and flowcharts, and perform other important administrative tasks.
  - Configuring the ACOOptAdmin tool
    Configure the ACOOptAdmin tool to run Unica Optimize sessions from the command line.
  - Non-ASCII data in Unica Campaign
    Unica Campaign supports the use of localized data and non-United States locales, including multiple user-preferred locales within the same installation of the application.
  - Configuration properties for Unica Campaign
    The configuration properties of Unica Campaign are located at SettingsConfiguration. For more details on the configuration properties, see the Campaign Administrator Guide.
  - About special characters
    Some special characters are not supported in any Unica Campaign object names. In addition, some objects have specific naming restrictions.
  - Introduction to character encodings
    This section provides information on character encodings and language-sensitive database considerations, and lists the encodings supported by Unica Campaign.
  - About Unica Campaign Error Codes
    Unica Campaign notifies users of error events when they occur with error messages that consist of a code number and error text.
  - Troubleshooting
- System Tables

Tokens supported by triggers

Tokens can be used in the command line of an outbound trigger to pass specific information from the running flowchart.

The following table lists the tokens supported by triggers and the processes where specific tokens are available.

Table 1. Tokens supported by triggers
Token	Description	Where Used
`<AMUSER>`	The Unica user name of the user running the flowchart.	Processes that support outbound triggers.
`<CAMPCODE>`	The campaign code associated with the current campaign.	Processes that support triggers, trigger on failure, trigger on success.
`<CONTACTLIST>`	Contact list specified in a contact process. If the Contact List is written to a file, the appropriate full path name and file name replace the trigger token. If the Contact List is written to a database table, the token is simply removed.	Call list and Mail list processes.
`<CONTACTLOG>`	The log of the particular contact process. When the Log is written to a file, the appropriate full path name and file name replace the trigger token.	Call list and Mail list processes.
`<FLOWCHARTFILENAME>`	Full path name of a flowchart's `.ses` file	Processes that support outbound triggers.
`<IXUSER>`	The user name of the Unica Collaborate user.	Processes that support triggers, trigger on failure, trigger on success.
`<OUTPUTTEMPTABLE>`	A token for use in raw SQL in pre- and post-processing under the Advanced window to create a temp table. For example:`Create <OUTPUTTEMPTABLE> as SELECT CustIDs from CustomerTable WHERE ...`	Select process.
`<OWNER>`	The Unica Platform security user name of the user who created the flowchart.	Processes that support triggers, trigger on failure, trigger on success.
`<PROCESSNAME>`	The name of the current process box.	Processes that support triggers.
`<PROCESSID>`	The ID of the current process box.	Processes that support triggers.
`<SESSIONID>`	The ID of the current flowchart.	Processes that support triggers, trigger on failure, trigger on success.
`<SESSIONNAME>`	The name of the current flowchart.	Processes that support triggers, trigger on failure, trigger on success.
`<UserVar.UserVarName>`	Any user variable value. The user variable must be defined in current flowchart.	Processes that support triggers, trigger on failure, trigger on success.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.