Home
Administrator Guides
Administrator Guide
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.
Writing to contact history
To record contact history, users configure one or more contact processes, such as a Call List or Mail List, then run a flowchart in production (not test) mode. Contact history is written to the tables related to the audience levels that are used in the 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.
    - Contact history concepts
      Contact history is maintained in the base contact history and detailed contact history tables in the Unica Campaign system database. Contact history is maintained separately for each audience level. Offer history and treatment history are used together with contact history to form a complete historical record of offers that are sent.
    - Creating contact history tables for new audience levels
      When you create a new audience level, you might need to create a table in the Unica Campaign system table database to store contact history and detailed contact history for targets and controls in that audience level.
    - To add a contact status code
      You can add your own contact status codes to supplement the contact statuses that are delivered with Unica Campaign. Define new contact status codes in the UA_ContactStatus table in the Unica Campaign system database. A contact status indicates the type of contact made (for example, Delivered, Undelivered, Control).
    - Deleting contact status codes
      You can delete contact status codes that you do not intend to use. However, you should not delete a contact status that is in use.
    - Writing to contact history
      To record contact history, users configure one or more contact processes, such as a Call List or Mail List, then run a flowchart in production (not test) mode. Contact history is written to the tables related to the audience levels that are used in the flowchart.
    - Updating contact history
      To update contact history that has already been recorded, users configure the Track process and run it in production mode. Updating contact history is necessary, for example, to update contact status or add additionally tracked fields.
    - Clearing contact history
      Users can clear the contact history generated by a contact process while configuring it. They are also prompted to select run history options when re-running processes or branches that have existing contact history, as these types of runs do not increment flowchart Run IDs.
    - Default contact status codes
      Unica Campaign is delivered with the following contact statuses, defined in the UA_ContactStatus table.
  - 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.
  - 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

Writing to contact history

To record contact history, users configure one or more contact processes, such as a Call List or Mail List, then run a flowchart in production (not test) mode. Contact history is written to the tables related to the audience levels that are used in the flowchart.

Note: The settings discussed in this topic do not affect Unica Deliver and Unica Interact. Those products use their own ETL processes to extract, transform, and load data into the Unica Campaign contact and response history tables.

The ability to write to contact history depends on the contact history logging options, which administrators can use to either allow or prohibit logging. These global configuration settings affect the contact processes as well as the Track process:

The logToHistoryDefault configuration setting determines whether the Log to contact history tables option is checked or cleared by default in a contact or Track process box. If logToHistoryDefault is enabled, Log to contact history tables is checked by default, meaning contact history updates are allowed.
The overrideLogToHistory configuration setting controls whether users with the appropriate permissions can change the Log to contact history tables setting when they configure a contact or Track process.

To make all flowchart production runs always write to contact history, enable logToHistoryDefault and disable overrideLogToHistory.

When contact history is logged, offer and treatment history are written as well.

Note: If a process is configured to log contact history, but the process runs on a cell with no selected targets, history records are not written.

For more information, see the Unica Campaign User's Guide.

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.