Use the installation roadmap to quickly find the information that you need for installing Campaign.
HCL® Campaign allows you to define inbound and outbound triggers that can be used in all flowcharts in a partition.
You must have permissions to use triggers in a flowchart.
The Settings menu provides access to most of the tasks that Campaign administrators typically perform.
Security policies control user access to the objects and features in HCL® Campaign.
HCL® Campaign administrators must perform initial one-time tasks and routine administration tasks that pertain to database tables.
Administrators can customize campaigns by using custom campaign attributes, initiatives, and products.
Before administrators perform offer template management tasks, there are several important concepts to understand.
HCL® 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.
Contact history is stored in the HCL® Campaign system database in separate tables by audience level. Therefore, you need to set up audience levels before you begin working with contact history.
Before you begin working with response history, you should read the audience level administration topics and set up required audience levels.
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.
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.
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.
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.
You define triggers when editing a flowchart. A trigger that you define in one flowchart is available to all flowcharts in the same partition.
You can create inbound and outbound triggers and organize them in folders.
Three processes can execute outbound triggers when they run.
You can set up a flowchart to execute selected triggers when the flowchart runs successfully, on both production and test runs.
You can set up a flowchart to execute selected triggers when the flowchart encounters an error when running, on both production and test runs.
You can configure a Windows machine to send triggers to a Campaign installation on UNIX. Follow these steps to set up the unica_actrg utility and required files on a remote Windows machine.
Tokens can be used in the command line of an outbound trigger to pass specific information from the running flowchart.
The trigger utility (unica_actrg) supports the following syntax and options.
HCL® Campaign records information in several different log files.
Each campaign, cell, offer, and treatment in Campaign has an identifying code that is generated by code generators, and conforms to a specified format.
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.
HCL® Campaign optionally integrates with a number of other HCL products.
The listener is a key component of HCL® Campaign. It provides an interface between front-end clients and back-end analytical server processes.
Administrators use the Campaign utilities to manage listeners, sessions, and flowcharts, and perform other important administrative tasks.
Campaign supports the use of localized data and non-United States locales, including multiple user-preferred locales within the same installation of the HCL® application.
The configuration properties for HCL® Campaign are located at Settings > Configuration.
Some special characters are not supported in any HCL® Campaign object names. In addition, some objects have specific naming restrictions.
This section provides information on character encodings and language-sensitive database considerations, and lists the encodings supported by Campaign.
Campaign notifies users of error events when they occur with error messages that consist of a code number and error text.
Help Center