Unica Journey
Release Notes
System Requirements
Installation Guides
Upgrade Guide
Sizing Guide
Administrator's Guide
- An Introduction to Unica Journey
  Unica Journey is a goal-based orchestration solution to craft, execute, and visualize context-driven, personalized, multi-step omnichannel customer experiences.
- New navigation UI
  Unica has introduced New UI.
- Journey Multi Partition
- Clean-up Journey Audiences
- Unica Journey integrations
- Process of Starting and Stopping Journey
- Journey user roles and permissions
  Before you begin using Unica Journey, you should assign roles and permissions to users.
- Journey AI Support (Add Journey via MaxAI)
  Overview
- Apache Reverse Proxy Setup Steps for Microsoft Windows
  To setup Apache Reverse Proxy server on Microsoft Windows, complete the following steps:
- Journey interaction logging
  Interaction Logging for Journey is executed as a scheduled job. The scheduling parameters are set in application.properties file of the Journey Engine. The following is an example of the setting:
- Journey logging
  In Journey version 12.1.2 and earlier, the property JOURNEY_LOGGING, in the journey_master_config.properties file, was only used for tracing the audience.
- Configuring OptIn Optout functionality
- Journey GDPR
- Kafka authentication using SSL
- Kafka authentication using Kerberos
- Support for Kafka Topic Prefix
  In the 25.1.1 release, Journey has introduced support for adding a prefix to Kafka topics.
- Configure Web Application servers Tomcat for SSL
  On every application server on which a Unica application is deployed, configure the web application server to use the certificates you have decided to employ.
- Mailchimp Configuration
  Configuration of Mailchimp as external source with Journey.
- Settings
  Use the settings menu to manage the Journey integrations like Email connectors, SMS connectors, CRM connections, and REST integrations.
System Schema
Tuning Guide
Accelerators
User Guide
Superset Reports
Director
Licensing Guide
PDFs
Notices

Configuring OptIn Optout functionality

In 12.1.9 release, Journey supports opt out/in for Email, SMS and Whatsapp channels. Opt out/in is not supported for Push channel.

Journey touchpoint respect the contact central preferences before executing for Opt-in Opt-out specific to the channel and do not send communication if audiences are opted out. This should apply to both Link and Deliver type of touchpoint.

To enable the Opt-Out functionality in Journey, users must have Contact Central installed and enabled in Unica and along with Journey partition wise contact central flag should be enabled.

A scheduler is default configured to fetch audience data every 12 hours from Contact Central to Journey. Users can modify the schedule by updating below property available in the engine's application.properties file. Every time when jobs executed Journey will take only updated and delta audiences from Control Central to Journey.

engine.contactcentral.consent.data.cron=0 0 */12 * * ?

When above consent jobs executed by Journey engine at set frequency, opted out audiences data is retrieved from Contact Central and stored in the Journey channel wise consent database tables.

Database tables : journeyaudiencewhatsappconsent,journeyaudiencesmsconsent,JourneyAudienceEmailConsent.

Optional: The default page size for storing data in the Journey tables is 1,000 records per iteration. To change this, users can set engine.contactcentral.consent.pagesize=2000 (or another desired value) in the engine's application.properties file.

After making any changes to the application.properties file, users must restart the engine service for the changes to take effect.