Home
Administrator Guide
Unica Interact provides documentation and help for users, administrators, and developers.
Interact design environment configuration properties
This section describes all the configuration properties for Unica Interact design environment.
InteractDT | partitions | partition[n] | Interact | dataGovernance
dataGovernance is used to configure the masking values to be used for Text/Numeric/Date data types. The values configured here shall be used to mask the profile attributes as per their data type.

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.
- 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.
  - InteractDT | general | logging
    The InteractDT | general | logging property defines the InteractDT logging related configuration.
  - InteractDT | general | monitoring
    Properties in this category are applicable when JMX connector needs to be enabled for Interact contact and response history module.
  - InteractDT | navigation
    Some of the properties in this category are used internally and should not be changed
  - InteractDT | partitions | partition[n] | Connections
    InteractDT|partitions|partition1|Connections configuration defines the Unica InteractDT optional communication with other Unica products like Unica Audience Central, Unica Segment Central, Unica Centralized Offers and Unica Campaign for access to Segments, Offers, Audience and flowcharts. The following are the categories along with their options:
  - InteractDT | partition | partition[n] | dataSources
    The properties in InteractDT|partitions|partition[n]|dataSources determine how Unica InteractDT interacts with databases, including its own system tables, for the specified partition.
  - InteractDT | partitions | partition[n] | internal
    Properties in this category specify integration settings and the internalID limits for the selected Unica InteractDT partition. If your Unica InteractDT installation has multiple partitions, set these properties for each partition that you want to affect.
  - Campaign | partitions | partition[n] | reports
    The InteractDT | partitions | partition[n] | reports property defines the different types of folders for reports.
  - InteractDT | partitions | partition[n] | systemTableMapping
    If Unica Campaign is not installed, Unica InteractDT refers systemTableMapping configuration to map the product entities like Offer, Segment, flowchart, folder etc to their respective base table. The default values of all the required entities are already mapped and do not require any modification.
  - InteractDT | partitions | partition[n] | UnicaInsightsReports
    The InteractDT | partitions | partition[n] | UnicaInsightsReports property defines the different types of folders for reports.
  - Campaign | partitions | partition[n] | Interact | contactAndResponseHistTracking
    These configuration properties define settings for the Unica Interact contact and response history module.
  - Campaign | partitions | partition[n] | Interact | report
    These configuration properties define the report names when integrating with Cognos®.
  - Campaign | partitions | partition[n] | Interact | learning
    These configuration properties enable you to tune the built-in learning module.
  - Campaign | partitions | partition[n] | Interact | deployment
    These configuration properties define deployment settings.
  - Campaign | partitions | partition[n] | Interact | serverGroups | [serverGroup]
    These configuration properties define server group settings.
  - Campaign | partitions | partition[n] | Interact | flowchart
    These configuration properties define the Unica Interact runtime environment used for test runs of interactive flowcharts.
  - Campaign | partitions | partition[n] | Interact | whiteList | [AudienceLevel] | DefaultOffers
    These configuration properties define the default cell code for the default offers table. You need to configure these properties only if you are defining global offer assignments.
  - Campaign | partitions | partition[n] | Interact | whiteList | [AudienceLevel] | offersBySQL
    These configuration properties define the default cell code for the offersBySQL table. You need to configure these properties only if you are use SQL queries to get a desired set of candidate offers.
  - Campaign | partitions | partition[n] | Interact | whiteList | [AudienceLevel] | ScoreOverride
    These configuration properties define the default cell code for the score override table. You need to configure these properties only if you are defining individual offer assignments.
  - Campaign | partitions | partition[n] | Interact | outboundChannels
    These configuration properties enable you to tune the outbound channels for triggered messages.
  - Campaign | partitions | partition[n] | Interact | Simulator
    These configuration properties define the server group you want to use to run API simulations.
  - InteractDT | partitions | partition[n] | Interact | dataGovernance
    dataGovernance is used to configure the masking values to be used for Text/Numeric/Date data types. The values configured here shall be used to mask the profile attributes as per their data type.
  - InteractDT | partitions | partition[n] | Interact | offerArbitration
    OfferArbitration allows you to make offers-related miscellaneous configurations for Interact Design time. It allows you make Campaign as an optional property of Strategy.
- 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.
- Interact Design Time Separation from Campaign
  Unica Interact 12.1.6 onwards, Interact Design Time is a standalone application under Unica suite, independent of Campaign. Interact Design Time has been part of the Unica Campaign product hence tightly coupled with Campaign and uses a lot of Campaign services. After separation, Interact Design Time can function properly irrespective of Campaign is installed or not. Interact Design Time is a new application under HCL Unica having its own configurations for Security, REST API Filter configuration, UI Navigation settings etc deployed with /InteractDT as context root.

InteractDT | partitions | partition[n] | Interact | dataGovernance

dataGovernance is used to configure the masking values to be used for Text/Numeric/Date data types. The values configured here shall be used to mask the profile attributes as per their data type.

There are no validations for these configurations while saving, but these values are validated every time when we need to mask any data. The parameters in the dataGovernance node are as follows:

maskTextDataAs: Accepts any text data and cannot be blank.; Default value is ****.

maskNumbericDataAs: Accepts only numeric data and cannot be blank.; Default value is 0.

maskDateDataAs: Allows any valid date in dd-MM-yyyy format or MM-dd-yyyy format. System interprets the input as dd-MM-yyyy first and then MM-dd-yyyy to convert this input to a valid date.; Default value is 01-01-2100.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.