Home
Administrator Guide
Unica Interact provides documentation and help for users, administrators, and developers.
Managing Unica Interact data sources
Unica Interact requires several data sources to function properly. Some data sources contain the information Unica Interact requires to function, other data sources contain your data.
About cross-session response tracking
Visitors may not always complete a transaction in a single visit to your touchpoint. A customer may add an item to their shopping cart on your web site and not complete the sale until two days later. Keeping the runtime session active indefinitely is not feasible. You can enable cross-session response tracking to track an offer presentation in one session and match it with a response in another session.
Configuring contact and response history tables for cross-session response tracking
Whether you create a copy of the contact history tables, or use the actual tables in the Unica Campaign system tables, you must perform the following steps to configure the contact and response history tables.
UACI_TrackingType table
The UACI_TrackingType table is part of the runtime environment tables. This table defines the tracking codes used with cross-session response tracking. The tracking code defines what method the runtime environment uses to match the current offer in a runtime session with the contact and response history.

Administrator Guide
Unica Interact provides documentation and help for users, administrators, and developers.
- Administering Interact
  When you administer Unica Interact you configure and maintain users and roles, data sources, and optional product features. You also monitor and maintain the design and runtime environments. Product-specific application programming interfaces (APIs) are available for you to use.
- Security Management
  Access to the Unica Interact runtime User Interface requires authentication. Only the Login IDs defined in Unica Platform and having Unica Interact admin role can access the pages.
- Configuring users
  Unica Interact requires you to configure two sets of users, runtime environment users and design environment users.
- Managing Unica Interact data sources
  Unica Interact requires several data sources to function properly. Some data sources contain the information Unica Interact requires to function, other data sources contain your data.
  - Interact data sources
    Unica Interact requires several sets of data to function. The sets of data are stored and retrieved from data sources, and the data sources you set up depend on the Unica Interact features you are enabling.
  - Databases and the applications
    The data sources that you create for use by Unica Interact might also be used to exchange or share data with other Unica applications.
  - Campaign system tables
    When you install the Unica Interact design environment, you also create new, Unica Interact-specific tables in the Unica Campaign system tables. The tables that you create depend on the Unica Interact features you are enabling.
  - Runtime tables
    If you have more than one audience level, you must create staging tables for the contact and response history data for each audience level.
  - Test run tables
    The test run tables are used for test runs of interactive flowcharts only. Test runs of interactive flowcharts should test your segmentation logic. You only need to configure one test run database for your Unica Interact installation. The test run tables do not need to be in a stand-alone database. You could, for example, use your customer data tables for Unica Campaign.
  - Profile database
    The contents of the profile database depend entirely on the data you need for configuring your interactive flowcharts and Unica Interact API. Unica Interact requires or recommends that each database contain certain tables or data.
  - Learning tables
    If you are using Unica Interact built-in learning, you must configure the learning tables. These tables contain all the data the built-in learning feature learns on.
  - Contact history for cross-session response tracking
    If you enable the cross-session response feature, the runtime environment needs read-only access to the Unica Campaign contact history tables. You can configure the runtime environment to view the Unica Campaign system tables, or you can create a copy of the Unica Campaign contact history tables. If you create a copy of the tables, you must manage the process of keeping the copy up to date. The contact and response history module will not update the copy of the contact history tables.
  - Running database scripts to enable Unica Interact features
    To use the optional features that are available in Unica Interact, run database scripts against the database to create tables or update existing tables.
  - About Cross Session Contact Tracking
  - About contact and response history tracking
    You can configure runtime environment to record contact and response history in the Unica Campaign contact and response history tables. The runtime servers store contact and response history in staging tables. The contact and response history module copies this data from the staging tables to Unica Campaign contact and response history tables.
  - About cross-session response tracking
    Visitors may not always complete a transaction in a single visit to your touchpoint. A customer may add an item to their shopping cart on your web site and not complete the sale until two days later. Keeping the runtime session active indefinitely is not feasible. You can enable cross-session response tracking to track an offer presentation in one session and match it with a response in another session.
    - Enable duplicate detection and suppression
    - Cross-session response process
    - Cross-session response tracking data source configuration
      Unica Interact cross-session response tracking matches session data from the runtime environment with the Unica Campaign contact and response history. By default, cross-session response tracking matches on treatment code or offer code. You can configure the runtime environment to match on a custom, alternate code.
    - Configuring contact and response history tables for cross-session response tracking
      Whether you create a copy of the contact history tables, or use the actual tables in the Unica Campaign system tables, you must perform the following steps to configure the contact and response history tables.
      - UACI_TrackingType table
        The UACI_TrackingType table is part of the runtime environment tables. This table defines the tracking codes used with cross-session response tracking. The tracking code defines what method the runtime environment uses to match the current offer in a runtime session with the contact and response history.
      - UACI_XSessResponse
        The UACI_XSessResponse table is part of the runtime environment tables. This table is used for cross-session response tracking.
    - Enabling cross-session response tracking
      Use this procedure to enable cross-section response tracking.
    - Cross-session response offer matching
      By default, cross-session response tracking matches on treatment codes or offer codes. The crossSessionResponse service uses SQL commands to match treatment codes, offer codes, or a custom code from session data to the Unica Campaign contact and response history tables. You can edit these SQL commands to match any customizations you make to your tracking codes, offer codes, or custom codes.
  - Using a database load utility with the runtime environment
    By default, the runtime environment writes contact and response history data from session data into staging tables. On a very active production system, however, the amount of memory required to cache all the data before runtime can write it to the staging tables may be prohibitive. You can configure runtime to use a database load utility to improve performance.
  - Event pattern ETL process
    To process large amounts of Unica Interact event pattern data and to make that data available for queries and reporting purposes, you can install a stand-alone Extract, Transform, Load (ETL) process on any supported server for optimal performance.
- Offer serving
  You can configure Unica Interact in many ways to enhance how it selects offers to present. The following sections describe these optional features in detail.
- Understanding the Interact API
  Unica Interact serves offers dynamically to a wide variety of touchpoints. For example, you can configure the runtime environment and your touchpoint to send messages to your call center employees informing them of the best up sell or cross sell prospects for a customer who has called with a specific type of service inquiry. You can also configure the runtime environment and your touchpoint to provide tailored offers to a customer (visitor) who has entered a particular area of your Web site.
- Managing the Unica Interact API
  Whenever you use the startSession method, you create a Unica Interact runtime session on the runtime server. You can use configuration properties to manage the sessions on a runtime server.
- Classes and methods for the Unica Interact API
  The following sections list requirements and other details you should know before you work with the Unica Interact API.
- Classes and methods for the Interact JavaScript API
  The following sections list requirements and other details you should know before you work with the Unica Interact JavaScript API.
- About the ExternalCallout API
  Unica Interact offers an extensible macro, EXTERNALCALLOUT, for use with your interactive flowcharts. This macro enables you to perform custom logic to communicate with external systems during flowchart runs. For example, if you want to calculate the credit score of a customer during a flowchart run, you can create a Java™ class (a callout) to do so and then use the EXTERNALCALLOUT macro in a Select process in your interactive flowchart to get the credit score from your callout.
- Unica Interact utilities
  This section describes the administrative utilities available with Unica Interact.
- About the Learning API
  Unica Interact offers a learning module which uses a naive-bayesian algorithm to monitor visitor actions and propose optimal offers (in terms of acceptance). You can implement the same Java™ interface with your own algorithms using the Learning API to create your own learning module.
- Interact WSDL
  The Unica Interact installation includes two WDSL (Web Services Description Language) XML files that describe the available web services and how to access them. You can view these files in your Unica Interact home directory, and an example is shown here.
- Interact runtime environment configuration properties
  This section describes all the configuration properties for the Unica Interact runtime environment.
- Unica Interact Simulator
  This section describes all the configuration properties for the Unica Interact simulator.
- Interact design environment configuration properties
  This section describes all the configuration properties for Unica Interact design environment.
- Real-time offer personalization on the client side
  There may be situations where you want to provide real-time offer personalization without implementing low-level Java™ code or SOAP calls to the Unica Interact server. For example, when a visitor initially loads a web page where Javascript content is your only extended programming available, or when a visitor opens an email message where only HTML content is possible. Unica Interact provides several connectors that provide real-time offer management in situations where you have control only over the web content that is loaded on the client side, or where you want to simplify your interface to Unica Interact.
- JVM parameters
- Unica Interact and Digital Recommendations integration
  Unica Interact can integrate with IBM Digital Recommendations to provide Unica Interact-driven product recommendations. Both products can provide product recommendations for offers, but using different methods. Digital Recommendations uses a visitor's web behavior (collaborative filter) to build correlations between visitors and recommended offers. Unica Interact is based on customer's past behavior, attributes, history, and less on view-level offers, learning which offers best match a customer's behavior profile (based on demographics and other information about the customer). Offer acceptance rates help to build a predictive model through self-learning. Using the best of both products, Unica Interact can use a personal profile to define offers that will pass a category ID to Digital Recommendations and retrieve recommended products based on popularity (the "wisdom of the crowds") for display to the visitor as part of the selected offers. This can provide better recommendations for customers that will result in more click-throughs and better outcomes than either product acting alone.
- Interact and DDX integration
  With Digital Data Exchange, your website can link to Unica Interact to provide a powerful omni-channel execution engine that delivers the best offers to the optimum channels and evolves (learns) from the offer feedback to continuously increase marketing effectiveness.
- Unica Interact and Unica Journey integration
- Unica Interact and Unica Deliver integration
- Configure gateways
  Use triggered message gateways to send offer information from outbound channels.

UACI_TrackingType table

The UACI_TrackingType table is part of the runtime environment tables. This table defines the tracking codes used with cross-session response tracking. The tracking code defines what method the runtime environment uses to match the current offer in a runtime session with the contact and response history.


Column	Type	Description
`TrackingCodeType`	int	A number representing the tracking code type. This number is referenced by the SQL commands used to match information from the session data to the contact and response history tables.
`Name`	varchar(64)	The name for the tracking code type. This is passed in to session data using the `UACI_TrackingCodeType` reserved parameter with the `postEvent` method.
`Description`	varchar(512)	A brief description of the tracking code type. This field is optional.

By default, the runtime environment has two tracking code types defined, as shown in the following table. For any alternate code, you must define a unique TrackingCodeType.


TrackingCodeType	Name	Description
1	Treatment Code	UACI Generated Treatment Code
2	Offer Code	UAC Campaign Offer Code

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.