Home
Administrator Guides
Administrator Guide
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.
About audience levels and system tables
If you require additional audience levels, you must create and map the equivalent set of system tables to support them as you did for the default Customer audience level.
Required fields in audience-level-specific tables
This section provides lists of the required fields in the system tables required for each audience level.
Required fields in the response history table
The response history table for each audience level in the Unica Campaign system database must minimally contain the fields described in this section.

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.
    - About audience levels
      An audience level is a collection of identifiers that can be targeted by a campaign.
    - Why different audience levels are needed in Unica Campaign
      Different audience levels enable flowchart designers to target and switch between specific identifiable groups in their campaigns, or to scope one audience level by another (for example, to target one individual per household).
    - The default Customer audience level
      Unica Campaign is delivered with a single audience level called Customer. You can define additional audience levels as required for your user tables and campaign needs.
    - About audience levels and system tables
      If you require additional audience levels, you must create and map the equivalent set of system tables to support them as you did for the default Customer audience level.
      - Default Customer audience level system tables
        Unica Campaign is delivered with system table ddl scripts to create the tables that support the default Customer audience level.
      - About audience levels and strategic segments
        For each audience included in a flowchart or Optimize session that uses strategic segments, you map the segment membership system table to a physical table that defines segment members.
      - Audience level unique identifiers
        When you create a new audience level, you must specify at least one field to be used as the unique identifier for members of that audience level. To uniquely identify each member of the audience, you might need to use multiple fields.
      - Required fields in audience-level-specific tables
        This section provides lists of the required fields in the system tables required for each audience level.
        Required fields in the contact history table
        The contact history table for each audience level in the Unica Campaign system database must minimally contain the fields described in this section.
        Required fields in the detailed contact history table
        The detailed contact history table for each audience level in the Unica Campaign system database must minimally contain the fields described in this section.
        Required fields in the response history table
        The response history table for each audience level in the Unica Campaign system database must minimally contain the fields described in this section.
        Required fields in the segment membership table
        If you are using strategic segments in Unica Campaign or Unica Optimize, you must create the segment membership table for each audience level that you use with strategic segments. At a minimum, the table must contain the fields described in this section.
    - About audience levels and user tables
      A user table can be associated with a single audience level or with multiple audience levels.
    - Workflow for setting up a new audience level
      The listed tasks provide the workflow for setting up a new audience level.
    - Removing an audience level
      When you remove an audience level, the system tables are removed, but the underlying database tables remain. Therefore, if you remove an audience level, any processes and flowcharts depending on that audience level (that is, that attempt to write to the audience level tables) will generate errors.
    - About global suppressions and global suppression segments
      Use the global suppression feature to specify a list of IDs (in a single audience level) that are automatically excluded from all cells in flowcharts in Unica Campaign.
  - 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.
  - 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

Required fields in the response history table

The response history table for each audience level in the Unica Campaign system database must minimally contain the fields described in this section.

Table 1. Required fields in the response history table
Key	Column Name	Data Type	Length	Allow Nulls
Yes	Identifier for audience level.	numeric or text		No
Yes	TreatmentInstID	bigint	8	No
Yes	ResponsePackID	bigint	8	No
No	ResponseDateTime	datetime	8	No
No	WithinDateRangeFlg	int	4	Yes
No	OrigContactedFlg	int	4	Yes
No	BestAttrib	int	4	Yes
No	FractionalAttrib	float	8	Yes
No	CustomAttrib	float	8	Yes
No	ResponseTypeID	bigint	8	Yes
No	DateID	bigint	8	Yes
No	TimeID	bigint	8	Yes
No	DirectResponse	int	4	Yes

Each response history table you create for a new audience level should have a foreign key constraint on the UA_Treatment table's TreatmentInstID field.

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.