New features and changes in version 12.1.4

Personalization Playback – Phase 2

Introduced additional capabilities for the Personalization Playback feature, introduced in version 12.1.3. In this release, the Personalization Playback feature provides retrospective views of the activities from more perspectives and presents them in a better way.

Added the view type of Offers. This provides a view of the sessions and users associated with selected offers. Additionally, you can see the top three offers Interact presents the most at every aggregation unit (hours, days, or months).
Added the view type of Segments. This provides a view of the sessions and users associated with selected segments. Additionally, you can see the top three segments that are eligible the most at every aggregation unit (hours, days, or months).
Capabilities of selecting any past date range, in addition to several preset ranges, for both of the newly added view types.
In both Offers and Segments view types, you can drill down to individual API request level.
Improved user interface for smoother and convenient user interaction.
A new batch that runs once a day for purging the playback data older than the retention period.

Enhancements to Smart Strategy UI

Smart strategies have the following new enhancements:

The performance data of A/B testing is retrieved and displayed only on demand in order to decrease the initial load time of the smart rule list.
If Centralized Offer Manager is integrated, the details of offers can be displayed with a simple click when selecting offers in the edit mode, and for the offers already added to smart rules.
Some optimization is added to the cache used behind the strategy page.

Tighter integration with Contact Central

An option is added to each outbound endpoint (outbound gateways and channels) to honor the customer consents stored in Contact Central.

Reusable Events and Patterns

An interactive channel can be configured to have another interactive channel as its parent. When it is done, the events and event patterns defined in the parent channel can be used in the child channel as if they were defined in the child channel.

More Options for Handling Duplicate Offers

It is not uncommon that an offer is used in multiple rules with different ways of personalization, which makes a same offer to be eligible with different versions. It is sometimes desired to return multiple of those versions. As a response to this, the following methods of de-duplication are introduced:

De-duplication by offer codes, which means only a single version of an offer can be returned.
De-duplication by treatment codes, which means multiple versions of an offer can be returned, while a same version can be returned only once.
No de-duplication, which means even a same version of an offer can be returned multiple times.

Options for Capturing more Analysis Data

With easy configuration changes, the following detailed data can be captured:

Log individual API request with its parameter.
Log the completion of individual API request with its duration of processing.
Log the completion of individual profile loading with its duration of processing.
Log the completion of individual flowchart execution with its duration of processing.
Log the completion of individual flowchart process box execution with its duration of processing.
Enable the recording of detailed metrics of API processing to JMX.
Enable the recording of detailed metrics flowchart execution to JMX.
Enable the recording of detailed metrics related to cache operations to JMX.

Miscellaneous Enhancements

The date values defined with campaigns and offers are adaptable on the timezone of the Interact run time instances. For example, if a campaign is configured to be effective on August 1st, then it will be effective from 00:00:00 on August 1st in the timezone configured with the Interact run time server group.
It can be enabled to connect to Unica Deliver via SOCKS proxy, in both Interact design time and run time.
Integer attributes are better handled. Specifically, if an offer attribute is defined as an integer, its value is handled and returned as an integer number, and if a profile attribute is defined as an integer, its value is retrieved and returned as an integer number, unless it is overwritten.
In order to more easily integrate with Interact run time instances with security, a Unica Manager based token authentication is supported.