v2023.13 Release Notes

Our July 6th 2023 release, v2023.13, introduces updates to your Playbooks, Customer Trail, and Data Automation . For Playbooks, you no longer need to click the Validate button once you have fixed any validation errors as they will automatically clear. For Customer Trail, you can now click View account details to see the current values of your Customer Attributes. Additionally , new properties have been added to allow you to see the cause of an account update in greater detail. Lastly, for Data Automation, we now support content timestamps for millisecond granularity in both Imports and Exports.

See the Playbooks, Customer Trail, Data Automation, and Bug Fixes sections of this article for additional information.

Note: A bug fix was introduced to Landing Pages that displays line breaks properly, previously they were not always displayed. It is recommended that you sanity-check your existing Landing Pages to ensure formatting has not changed.


Playbooks

Learn more - Playbooks

When editing your Playbooks with validation errors, it can be cumbersome to click the Validate button in the top-right regularly. We have introduced real-time updating of your validation errors to avoid these extra steps. Now they will disappear as you are making the changes.

Playbooks

Description

Playbooks

Description

What’s New

  • N/A

What’s Changed

  • Corrections to validation errors are displayed in real-time, instead of needing to click the Validate button again

What’s Removed

  • N/A


Customer Trail

Learn more - Customer Trail

Although Customer Trail is excellent at displaying the different Events that have occurred for your customers, viewing the current state of a customer through Customer Trail was difficult or potentially impossible and you would have needed to rely on Exports. Now you can see the current attributes for your customer directly when viewing their Trail by clicking View account details in the top-right of their Customer Trail screen.

Additionally , when investigating a customer, we have added additional clarity on what exactly is causing an account update. We have done so by adding the "Triggered By", "SourceName", and "SourceId" properties, the details of which you can read in the change table below.

Customer Trail

Description

Customer Trail

Description

What’s New

  • When viewing a Customer Trail you can now click View account details in the top-right to see the current Customer Attributes

What’s Changed

  • "Account Creation" and "Account Updated" now have properties of "Triggered By", "SourceName", and "SourceId"

  • "Triggered By" is the cause of the account update, which can be a data source import, modify attribute control, or landing page form submission "SourceName" and "SourceId" depend on the type of trigger, but will reference the campaign name and ID in the case of a Modify Attribute Control

What’s Removed

  • N/A


Data Automation

Learn more - Data Automation

Imports and exports both have the ability to display timestamps down to the second. In some instances, you may desire additional granularity. Therefore, we have added support for milliseconds allowing file content timestamps to have the format of HH:mm:ss.fff. If the fff is confusing, it stands for fraction. This is not to be confused with the file name timestamp, but the content within the file itself.

Data Automation

Description

Data Automation

Description

What’s New

  • Import and Export file content timestamps millisecond granularity via the HH.mm:ss.fff time format option

What’s Changed

  • N/A

What’s Removed

  • N/A


Bug Fixes

Platform Area

Description

Platform Area

Description

Playbooks

  • Viewing the entry and exit criteria of the published version of a Playbook, there would be a nonfunctional button to clear those criteria. The published version of a Playbook is intended to be view-only, and therefore this button is no longer visible

Content

  • Landing Pages were not displaying line breaks, which are now displayed

  • Note: It is recommended to go through some of your Landing Pages to check that you don't have line breaks that were not displaying, but are now displaying, therefore changing your formatting

Data Automation

  • When saving compression or encryption settings, our system would report that settings were saved, even though they were not, which now works as expected