Release-20230131 Release Notes

Owned by Priya Tiwari (Deactivated), created
Jan 15, 2024
3 min read

Our 2023 February 1st release introduces: Email and Text Message sending "as soon as possible" in your Playbooks; event-based filtration in your Customer Trails; Symend Analytical Data availability in your Data Sources if you are using a Data Workspace; and a Landing Page Viewed event available in your Customer Trail and Exports.

Playbooks

If you are designing a Playbook in a way where you would like a customer to receive an outreach ASAP, even if it's midnight on Christmas, then you will now find that capability in our platform. This is important because previously the only way to send a message was with a scheduled send, and that would still adhere to your send window. An example use case would be an immediate message informing the user they have gone over the data plan on their phone.

Playbooks

Description

Playbooks

Description

What's New

  • An Email or Text Message Control can now be scheduled for "as soon as possible" instead of being scheduled for a specific time

  • The message will be sent as soon as the account reaches the control within the playbook

  • Restricted dates, send windows, or duplicate message checks do not apply

What's Changed

  • N/A

What's Removed

  • N/A

Customer Trail

Learn more - Customer Trail

Learn more - Events

We have expanded on our Customer Trail from the previous release by adding the capability to filter an individuals events based on the event category. Also, we have added an event for Landing Page Viewed in both Customer Trail and Exports.

Customer Trail

Description

Customer Trail

Description

What’s New

  • An event has been added for Landing Page Viewed in your Customer Trail, this will also be available in Exports

  • Viewing an individuals Customer Trail now has the capability to filter based on event types

  • Categories are the same across Customer Trail and Exports

What's Changed

  • Styling has been slightly modified for consistency on the "To" and "From" text when filtering based on a date range

What's Removed

  • N/A

 

Data Workspaces

Our previous release included an incremental release of Data Workspaces. Specifically, the ability to add a Data Workspace as a source. However, our Analytical Data was not included in that release.

Data Automation

Description

Data Automation

Description

What's New

  • Data Workspaces have had the Symend Analytical Data enabled

  • You can now find this information if you are directly connected to the Workspace

    • It can also be found in Data Source Mappings if you are utilizing a Data Workspace

What's Changed

  • N/A

What's Removed

  • N/A

Exports

Learn more - Events

As you would see in the Customer Trail, we have added a new event for Landing Page Viewed, to track when a customer navigates to your Landing Page.

Exports

Description

Exports

Description

What’s New

  • An event has been added for Landing Page Viewed in your Exports, this will also be available in your Customer Trail

What's Changed

  • N/A

What's Removed

  • N/A

Bug Fixes

Platform Area

Description

Platform Area

Description

Playbooks

  • Adding a restricted date for your outreaches would return the time of the restricted date as UTC in the UI, which could make it appear as though the date was incorrect, now the display is based off your local time zone

Landing Pages

  • Adding a divider and then modifying the styling without a CSS Class was unable to be saved because the CSS Class was treated as a mandatory field

Segments

  • Making an attribute-to-attribute comparison did not have the compared attribute marked as required in the UI, resulting in the ability to click Save, even though the save would be unsuccessful

  • Adding an attribute-to-attribute comparison and then changing the left hand attribute would allow a comparison to be made between attributes of different data types

Exports

  • Deprecated attributes were visible in the UI

  • Setting an export frequency for the first time was not immediately visible in the UI, resulting in the page needing to be refreshed before changes would be visibly represented