New features and changes in version 12.1.7

In Unica Journey 12.1.7, we have introduced some new features, and we have made changes to some existing features or functionality.

The following list mentions the new features, and the changes to existing features, in Unica Journey 12.1.7:

Journey to support multiple partitions

Unica Journey introduces support for Multi Partition. Partitions provide a way to secure data associated with different groups of users and Business Units. Once Unica Journey is configued to operate with multiple partitions, each partition appears to application users as a separate instance of the application and they can view and manage data and resources associated with their partition.

Journey-Support for additional REST elements in Journey UI

Unica Journey now supports adding additional elements dynamically while configuring REST API requests providing a way to add custom name/value pairs and QUERY PARAMETERS, HEADERS, etc

Confluent Kafka with Unica Journey

Unica Journey now supports Confluent Kafka as part of its technology stack.

As a journey designer, I should be able to specify the variable or place holder for data definiiton fields in query parameters, headers and url path in the rest touch point configuration

This feature now allows specifying the variable or place holder for data definition fields in query parameters, headers and url path in the rest touch point configuration. The placeholders will be replaced by actual values during Journey Execution - providing a way to customize the query parameters, headers and url paths for each audience.

Journey-Integrate Mobile Push Channel with Link

Unica Journey introduces Mobile Push messaging using Unica Link connector leveraging third party vendors like With this new feature, Journey now supports Push Messaging through Unica Deliver or using the Unica Link connector.

Journey-Full PII data Masking and Data Logs masking

Journey now provides a way to mask/hide the personal identifiable information data (PII) for a regular user from viewing it. Once configured, details page with processing details showing audience data is blocked completely along with disabling of deep links in the popups showing stats.

Journey-Establish a Secure REST API Connection

Unica Journey now supports Secure REST API connections

Journey-Delete Journey

Unica Journey now supports deleting Completed journeys - this allows removing completed journeys and associated audience data and responses.

[Performance] Ability to flag if the audience is to be considered New / Update / as per dedup check

With the intention to optimize audience deduplication process, Journey engine supports certain optional hints, which can be supplied along with the audience message. With this - both at data level and at audience level - Journey optimizes Dedup to handle only Inserts or Updates based on user setting in the json.

Journey-Duplicate data definition DD

Unica Journey now supports creating a new copy of an existing Data Definition.

Journey-Support for additional Methods in REST touchpoint

REST API touchpoint now supports PUT/PATCH methods

Journey-Support to add headers in REST

Support for adding Headers to REST calls is now available

Journey-Support for custom request query parameters in REST

REST API touchpoint now supports customer Request Query parameters.

Journey-Show Data Definition and Entry Source codes in Journey

Data Definition and Entry Source codes are now displayed along with their names making it easier to track them where names are similar. Hyperlinks of these codes makes it easy to navigate to their details page

Journey - Unica products communication with internalServer URL from Platform

Unica supports using Internal URL for Platform now providing a more secure way of communication with Unica products including Unica Journey

User data (audience + response) cleanup on live journey

Audience data can now be purged from the database based on configurations in the Journey application. When enabled, audience data older than the configured days will be purged from the system thus providing a way to maintain the data growth in the backend database.