Capabilities rolling out in October 2023

Summary

• You can now clone and rename fields in the flow of a rule.

• Personas now allows you to disable a Persona, allowing it to be removed for some key views, simplifying usage.

• New feature to include KPI stats of Conversion, Service Cost, and CSat score in Journey Analytics as a new tab on Journey Visualizations.

• Enhancement to Journey Visualizations, adding the attribute filtering to all other analytics tabs.

Rule Designer

Testing Rules

Display Logs Associated with a Tile

In the Test Runner screen, you can now access logs generated by a specific tile by clicking on the tile within the main Rule Designer canvas. This feature simplifies the process of tracing changes to fields and their values throughout the rule flow, greatly enhancing testing and rule troubleshooting.

Improved JSON Presentation and Auto-Repair in Test Runner

JSON data added to the test runner will now be displayed in a more user-friendly format. We've introduced a JSON editor that enhances the formatting, provides better visibility into nested JSON structures, and offers an auto-repair function to address minor JSON irregularities.

Check for new template versions as you work on your rules

We now automatically check for new template versions while you're working on your rules. This enables you to promptly adopt these new versions as soon as they become available.

Streamlined Template Selection Screen

We've simplified the template selection screen by removing extraneous functions that were distracting from its core purpose. The ability to delete a template and change its icon has been removed.

Support for Multiple Inputs in Recently Used Templates

When selecting a template from the recently used templates screen, you can now choose the input to use, providing more flexibility in your rule creation process.

Clone and Rename Fields

You can now clone and rename fields within the rule flow. This is especially useful when you need to utilize the same field value for multiple field mappings or when the original field name does not align with the expected values in your templates. Note that some system fields cannot be renamed.

Improved understanding of Output Fields

In Rule Designer, output fields now offer the following features:

1. Search functionality to easily locate specific fields of interest and hide unrelated ones, simplifying the tracking of specific fields in your rule.

2. Display of fields for each distinct output, where applicable. Tiles may have multiple outputs with different associated fields, and now you can specify the one you want to view.

3. Indication of how far back in the rule flow a field was created, including a tile-based distance measurement. This helps you understand where the field originated.

4. Ability to click on tiles in Rule Designer to focus your view, allowing for a more detailed examination of specific elements.

Personas Management

Enable and Disabling of Personas

While working with personas, you may find that some no longer align with your customer experience (CX) or marketing requirements. You can now disable personas, which offers the following benefits:

1. Removal of the disabled persona from the selection wizard in the switch case functionality within Rule Designer. Any existing switch cases containing the disabled persona will be retained.

2. Hiding the disabled persona from the default view in the Personas screen. It remains available if you change the filter to "All," ensuring a streamlined view of active personas during your daily work.

3. Removal of the disabled persona from steps within Journey Playbooks.

Monitor Persona Activity

A new activity counter in the Personas screen will indicate how many events have been created for a specific persona. Personas with low or no activity are likely inactive and may necessitate adjustments to the data you are loading.

Steps/API

Support for other fields in Real time Input step

You can now pass fields from headers or parameters into the Realtime Input as other fields.

Process Future Events Step now accepts API keys for added security

To provide essential security for your rules you can choose to require the calling solution to provide a known API key to ensure only known systems can call the rule.

Rules can also start with Process Future Event steps and these did not support the use of a key. These have now been updated to also support the use of an API key.

Public Templates

We need to ensure that the data being pushed into Journey Analytics is accurate and will create useful learnings for our users. If the data used to trigger a rule is invalid this is likely to have an adverse impact on data quality. and a linked impact on accuracy of learnings.

The GET CXID Public template will now no longer pass any events to the queue where the row is found to be invalid. The row will currently continue to flow through the rule so should be removed with a Invalid Data S3 Output before it gets to any other queue steps.

Data retention improvements for Alterian internal fields

Data stored in the Alterian Cache is used for varied purposes; it could be your current favourite category, your churn risk, your email address or your preference information.

Alterian also write many fields to the cache to service our solution though our Public Templates. We have not historically added expiry times to this data.

The Public Templates that create and update these fields have now been configured to read and then rewrite the value therefore renewing the expiry time each time a field is used. This means that fields that are read will persist and those that are never used will be purged after the alloted time. The fields that we have set to be purged are highlighted out below along with their chosen expiry times.

Journey Analytics

Journey Visualisations

KPI Journey Stats display have been added to standard (non Journey Discovery) Journey Visualisations.

This feature is dependent on the use of Location Mapping & Journey Exploration to define the Journeys present in the data, as well as ensuring the correct and full data is being collected for those stats within the rules in Rule Designer.

Journey Stats are displayed as a new tab in the Journey Visualisations screen, to allow the standard stats of Conversion, Service Cost and CSat to be displayed for each Journey.

This gives the CX Analyst more control in gathering KPI stats, by control of both the Date Range in Journey Visualisation, and filtering by any Attribute filtering in place. Using side-by-side Sankey Flow diagrams, CX Analysts can now review and compare stats across different time periods, as well as analysing if the stats are in line with expected values.

Journey Visualisations

Previous to this release, only the Flow, Distribution and Relationship tabs respected the Attributed filtering on the Journey Visualisation screen. This has now been enhanced to Visitor Stats and the newly added Journey Stats

Fixes

Known Issues

Report Issue

To report an issue with the application not detailed here, please contact Technical Support. Please use our Service Desk to report issues.