Several enhancements have been made to the Send-Time Optimization (STO) feature in order to improve the calculation and use of the optimized send-time for a contact.
The activation and configuration of STO for a journey has been moved from the Advanced section of the journey properties to the Basic properties. The option ‘Send at optimal (predicted) time for each consumer’ can be found in the Scheduling section.
When activated, an Advanced link is shown and when expanded, a drop-down allows users to set the time zone, indicating midnight in the time zone for which emails will go out for same day delivery. Unless modified, this drop down now defaults to the time zone of the marketer enabling the setting. This section previously existed, but is now only available from the Advanced link.
An STO profile is now available for all contacts that have at least one interaction. Previously, profiles were only created for contacts having a minimum number of interactions over a given time period.
Also, a fallback STO time has been introduced and is visible from the journey STO settings. The fallback STO will be used for contacts who have had no interactions and therefore do not have an STO profile. The fallback STO time is based on the best send-time for the audience.
Whether a contact has an STO profile or not can now be used when filtering an audience. When STO is activated for an environment, the STO scope becomes available in the Audience filter.
The STO profile for a contact is based on a weighted combination of the best send-time for the contact and the best send-time for the audience. This improves the functionality of the feature in cases where:
On the Products Insights tab, when searching for items in the product catalog, users can specify a number of catalog properties. Within the Satsuma (v5.1) Release, the “item_url” property is added to the list of properties that can be searched.
When defining a Smart Audience, it is possible to set the maximum size of the audience, as well as limit the targeted audience based on filter criteria. This ensures you target only the contacts with the best match. This feature was introduced in the Riberry (v5.0) Release.
In the Satsuma (v5.1) Release, the size of the potential audience is calculated and displayed when configuring the audience filter, providing more insight on the effectiveness of the filter. Based on the filtered audience, an indication is also given of how many of those contacts have interacted with the brand and what the size of the expected output segment will be.
Using this information, the marketer can adapt the filters and see the result of their changes before launch.
Rich push messages are push messages that contain an image or Smart Content. Now, similar to the behavior on iOS, images in rich push notifications are also visible as a thumbnail in the Android notification banner. Once clicked, a full version of the image is shown.
To improve the preview of messages using Custom Events data for personalization, it is now possible to select a specific Custom Events record after selecting a test user for the preview. This allows the preview to better represent what the final message will look like by taking into account personalization values.
When Custom Events records are available for the selected test-user, they are listed below, with a maximum of 25 records. Note that only the most recent 25 records are shown. When no Custom Events records exist, the user is informed.
In the Riberry (v5.) Release, data imports were enabled for imports into audience lists and 1:1 linked lists. When defining these recurring imports, the usage of this 1:1 linked list in the import is recorded, and the linked list will be unable to be deleted. The usage details are available from the Relations overview for an Audience list.
It is now possible to keep track of fields being used in imports & exports, and show this information when clicking the “Usage” button in the field properties in list design.
Custom Events lists contain a series of default system fields in addition to user defined custom fields. The State field is a system field and import into this field is no longer allowed.
Users cannot create a list field with name ‘USER_ID’. This is a reserved field name. This restriction applies to SMC as well as to the API. A warning will be displayed in the validation pane.
Non editable fields in lists are now displayed differently, making it clear to the user what fields can and cannot be edited. Editable fields are indicated by a grey line that turns blue when clicked. Non-editable fields have no lines.
When data synchronizations encounter problems, the Notifications center informs the user of the problem with the ability to click through to the history of the data sync. To make it clear there are unread notifications, the number of unread messages is now indicated.
Within the Satsuma (v5.1) Release, four new dashboards are introduced, replacing the existing dashboards and providing users with more concentrated and structured access to the different metrics. Filters will allow the marketer to drill down to the information required. The following dashboards will be made available:
New in these dashboards is the ability to filter on channel. This gives the marketer the opportunity to compare metrics over the different channels targeted in a journey.
Also, the Reporting section now includes a new metric: Open tracked count. This metric includes the number of messages that have been opened and for which the images have been downloaded. Opens without image download are not included.
The Pop-in Placements editor has been improved and now contains an additional option.
The Z-index field specifies the stack order of an element. An element with greater Z-index is always in front of an element with a lower Z-index.
Also, the ESC button now closes the pop-in.
In an effort to keep our audience up to date on any important new developments, additions to the web help or other changes, we have developed a newsfeed, visible on the landing page of the Online Help and from the Resources section.
Two new use case videos have been added to the library:
A new course has been added to the Site curriculum:
A new course has been added to the SMC curriculum: