Capabilities rolling out in August 2022

Home / General

We have reduced the situations where new tabs are created by Alterian CX. In general tabs are now only automatically created when you click to create a “New” item and this creates a new tab.

Rule Designer

Open in New Window

We now allow a Rule to be opened directly into a new window to allow easy comparison.

Simply right click on the Rule and select “Open in new window” from the “Open” options.

Understand clearly the fields flowing through each Tile

When you are building your Rules it is useful to understand the fields you have available at any given point. Now by selecting and right clicking on the Tiles in your Rule you can “Show Output Fields” to see the fields flowing out of each Output Connector.

Switch Case Values can now be edited

Switch Case values added by a user to a Switch case can now be edited. Cases set in the underlying template are still locked from editing.

Public Rules in Rule Designer

Public Rules are “working examples” we provide to our customers and will never be run within the Public Client in which they sit. We have made a series of changes to Rule Designer to restrict changes to Public Rules. For example, they cannot now be started, copied or deleted while within the Public Client.

Rules

Data Health

The current Rule Health visualisations in the Rules screen provide the user with an indication on whether a Rule is performing correctly.

We have now added a Data Health visualisation that shows where Invalid Data is flowing through your Rules allowing you to assess your tagging and integrations and fix your data issues.

Three Data Health visualisations can show:

• Green Icon “Good”- Less than 0.5 % Rule issues over the reporting period

• Amber Icon “Concern”- 0.5% - 2% Rule issues over the reporting period

• Red Icon “Warning” - Greater than 2% Rule issues over the reporting period

Alongside the visualisations a Data Health column is now available showing the full number of invalid data rows identified by a rule over the last full hour.

Help Links

Rules can now be saved with a Help link. The help link will show in the Rules screen allowing users quick access to help on what Rules do and how they should be used.

Filter Reset

We now have a filter reset button in the Rules screen. Clicking on this will reset any filters currently applied.

This filter reset is also available in the logs screen.

Templates

Filter Reset

We now have a filter reset button in the Templates screen. Clicking on this will reset any filters currently applied.

Cache Report

The Cache report now shows the default Expiry Time (TTL) set for the Table being examined. The Expiry time will show how long data is held before being automatically rolled off.

The Table Expiry Time is the default set for the Table. It’s possible that data fields in the table may have different Expiry times if these values were set independently within the Cache steps.

Rule API Testing

Rule Group Testing - Specify number of results and dedupe

When testing Rule Groups, you now have two new options.

Top allows you to specify how many results from the Rule Group you want to return back. This is useful when you only want the top one result to select a banner or the top three for three elements of content on an email.

By default a Rule Group will not provide back all of the possible results if some or all of the the values in the decisions are identical. If you would like to see all of the values as part of your testing process use Dedupe to allow all the values to be passed back.

Journey Analytics

Data Transformation Function

Note: This feature is available for administrative users to provide analysts with an agreed and defined Location format.

The number of unique Location values in data being collected from website tags in particular, or other integration code via DDE, can be an issue to give useful Insights and Analytics to Alterian Customers due to extended URL strings.

Items in the full URL such as GUID’s, #fragments, sessionid’s etc, can cause “like” Locations to become unique due the addition of these items in the URL.

For example in the URL

AcadianFinance/myportal/myaccount/paycreditcard/#Z7_31MEH4C0NGQ450QO24SVRO1SI2

the /# section is for session identification, which within the Locations column, is not desired as it makes the /paycreditcard unique for every Bank Customer and therefore cannot be used to analyse common behaviour. To facilitate analysis of, for example, behaviour leading up to, or after the /paycreditcard Location, it must be a common Location across all Bank Customers.

Therefore the URL above needs to be “transformed” to simply

AcadianFinance/myportal/myaccount/paycreditcard

This feature will allow the definition of a comprehensive Data Transform against the Location column that can be inserted into the execution of both Journey Visualisation (Sankey) and JA Dashboards to give more power to the Location analytics

For more information see - https://alteriandocs.atlassian.net/wiki/spaces/PD/pages/1781628935

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.