Home
Administrator Guides
Administrator Guide
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.
Campaign | partitions
This category contains properties to configure Unica Campaign partitions, including the default partition, which is named partition1.
Campaign | partitions | partition[n] | validation
The Validation Plugin Development Kit (PDK), delivered with Unica Campaign, allows third parties to develop custom validation logic for use in Unica Campaign. Properties in the partition[n] > validation category specify the classpath and class name of the custom validation program, and an optional configuration string.

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.
  - 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.
    - Campaign
      To specify the locales and component applications that your installation supports, choose Settings > Configuration, then click the Unica Campaign category.
    - Campaign | collaborate
      The properties in this category pertain to Unica Collaborate configuration.
    - Campaign | navigation
      Some of the properties in this category are used internally and should not be changed.
    - Campaign | caching
      Certain objects, such as offers, are cached in the web application server to improve response times in the Unica Campaign user interface. The Campaign|caching configuration properties specify the length of time that cached data is retained. Smaller values result in more frequent cache updates, which can adversely affect performance by consuming processing resources on both the web server and the database.
    - Campaign | partitions
      This category contains properties to configure Unica Campaign partitions, including the default partition, which is named partition1.
      - Campaign | partitions | partition[n] | WatsonAssistant
        These properties control authentication between Unica Campaign and IBM WatsonAssistant if the products are integrated.
      - Campaign | partitions | partition[n] | Unica Deliver | contactAndResponseHistTracking
        Use the properties in this category to configure Unica Deliver offer integration with Unica Campaign for the current partition.
      - Campaign | partitions | partition[n] | Deliver | sendTimeOptimization
        Use the property in this category to run Deliver STO ETL which will determine the best time to send a message to users when they are most likely to open the message. Deliver STO ETL job determines optimal send time of all the recipients contacted based on their email open responses.
      - Campaign | partitions | partition[n] | Engage
        These properties control authentication and data exchange between Unica Campaign and Engage if the products are integrated.
      - Campaign | partitions | partition[n] | Engage | contactAndResponseHistTracking
        These properties specify the ETL of events that are downloaded from UBX in the Unica Campaign history tables.
      - Campaign | partitions | partition[n] | Coremetrics
        The properties in this category specify integration settings for Digital Analytics and Unica Campaign for the selected partition.
      - Campaign | partitions | partition[n] | reports
        The Campaign | partitions | partition[n] | reports property defines the different types of folders for reports.
      - Campaign | partitions | partition[n] | validation
        The Validation Plugin Development Kit (PDK), delivered with Unica Campaign, allows third parties to develop custom validation logic for use in Unica Campaign. Properties in the partition[n] > validation category specify the classpath and class name of the custom validation program, and an optional configuration string.
      - Campaign | partitions | partition[n] | audienceLevels | audienceLevel
        Do not edit properties in this category. These properties are created and populated when a user creates audience levels on the Administration page in Unica Campaign.
      - Campaign | partitions | partition[n] | audienceLevels | audienceLevel | field[n]
      - Campaign | Partitions | partition[n] | dataSources
        The properties in Campaign|partitions|partition[n]|dataSources determine how Unica Campaign interacts with databases, including its own system tables, for the specified partition.
      - Campaign | partitions | partition[n] | systemTableMapping
        Properties in the systemTableMapping category are populated automatically if you remap any system tables or map Contact or Response history tables. You should not edit properties in this category.
      - Campaign | partitions | partition[n] | server
        This category contains properties to configure the Unica Campaign server for the selected partition.
      - Campaign | partitions | partition[n] | offerCodeGenerator
        Properties in this category specify the class, classpath, and configuration string for the offer code generator, and also the cell code generator used to assign a contact process to a Target Cell Spreadsheet cell.
      - Campaign | partitions | partition[n] | UBX
        These properties control authentication and data exchange between Unica Campaign, Engage, and UBX if the products are integrated.
      - Campaign|partitions|partition[n]|Kafka|Journey
        This category contains properties to configure the kafka used in Journeys for the selected partition
      - Campaign | partitions | partition[n] | Link
        This category contains properties to configure the Link for the selected partition.
    - Campaign | monitoring
      Properties in the this category specify whether the Operational Monitoring feature is enabled, the URL of the Operational Monitoring server, and caching behavior. Operational Monitoring displays and allows you to control active flowcharts.
    - Campaign | ProductReindex
      The creator of an offer can specify the products that are associated with that offer. When the list of products available for association with offers changes, the offer/product associations must be updated. Properties in the Unica Campaign > ProductReindex category specify the frequency of these updates and the time of day that the first update runs.
    - Campaign | unicaACListener
      If you are configuring a single-node listener cluster, use this category, and only this category, to define configuration settings for your non-clustered listener. For clustered listeners, the properties in this category pertain to all listener nodes in the cluster, except for the following properties, which are ignored: serverHost, serverPort, useSSLForPort2, serverPort2. (Instead, set these properties for each individual node, under Campaign|unicaACListener|node[n].)
    - Campaign | campaignClustering
      Set these properties if you have a clustered listener configuration. Set these properties once per instance of Unica Campaign; you do not need to set them for every partition.
    - Campaign | unicaACOOptAdmin
      These configuration properties define settings for the unicaACOOptAdmin tool.
    - Campaign | server
      The property in this category specifies a URL that is used internally, and does not need to be changed.
    - Campaign | logging
      This category specifies the location of the Unica Campaign log4jConfig properties file.
    - Campaign | proxy
      The Unica Campaign, Acoustic Campaign, and UBX integration is supported with outbound proxy connections.
    - Campaign | flowchart events
      If you are configuring Unica Director with Unica Campaign, use this category and set "enableEvents" to "Yes". If this property is set to NO, Unica Campaign will not publish any flowchart execution details to Unica Director. These properties must be set only once per instance of Unica Campaign; they do not need to be set for every partition of Unica Campaign.
    - Report configuration properties
      The report configuration properties for Unica are available at Settings > Configuration > Reports.
  - 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

Campaign | partitions | partition[n] | validation

The Validation Plugin Development Kit (PDK), delivered with Unica Campaign, allows third parties to develop custom validation logic for use in Unica Campaign. Properties in the partition[n] > validation category specify the classpath and class name of the custom validation program, and an optional configuration string.

validationClass

Description

The validationClass property specifies the name of the class used for validation in Unica Campaign. The path to the class is specified in the validationClasspath property. The class must be fully qualified with its package name.

For example:

com.unica.campaign.core.validation.samples.SimpleCampaignValidator

indicates the SimpleCampaignValidator class from the sample code.

This property is undefined by default, which causes Unica Campaign to perform no custom validation.

Default value

No default value defined.

validationConfigString

Description

The validationConfigString property specifies a configuration string that is passed into the validation plugin when Unica Campaign loads it. The use of the configuration string may vary, depending on the plugin used.

This property is undefined by default.

Default value

No default value defined.

validationClasspath

Description

The validationClasspath property specifies the path to the class used for custom validation in Unica Campaign.

Use either a full path or a relative path. If the path is relative, the behavior depends on the application server that is running Unica Campaign. WebLogic uses the path to the domain work directory, which by default is c:\bea\user_projects\domains\mydomain.
If the path ends in a slash (forward slash / for UNIX™ or backslash \ for Windows™), Unica Campaign assumes that it points to the location of the Java™ plug-in class that should be used.
If the path does not end in a slash, Unica Campaign assumes that it is the name of a .jar file that contains the Java™ class. For example, the value /<CAMPAIGN_HOME>/devkits/validation/lib/validator.jar is the path on a UNIX™ platform that points to the JAR file that is provided with the plug-in developer's kit.

This property is undefined by default, which causes the property to be ignored.

Default value

No default value defined.

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.