Several enhancements were made in this release to Content Blocks. The user can now also add Content Blocks to reserved sections (placeholders) in their messages when building messages based on a template, e.g. to personalize the message, or add a brand specific footer.
In addition, it is now possible to define default values for variables used within content blocks, enabling users to select predefined variables, use default variables or define new ones, as required.
Enhancements have been made to Smart Content and the quality of recommendations made to the customer. To avoid recommending products that have already been viewed or added to the cart by the customer, an additional option is added to the Cortex algorithm configuration which enables exclusion of products that were visited, carted or recommended and clicked on by the user already. Users can use either one, or a combination of options, as required.
Messages that use repeaters to display items in the message and that allow marketers to manage these items, now automatically only display the fields to fill out for the selected layout instead of all available fields, with no manual configuration required by the user. This will speed up the process of adding items.
Within this release, enhancements were added so that all Mobile Push Notifications and In-App Messages must have a mandatory expiration date. By default, the date is set to Today +2 months. Users can change this by using the Date Picker Dialog to choose a new expiration date. This ensures that mobile users are never confronted with outdated messages and offers for a better customer experience.
Any type of Response page can now be generated based on data stored in Selligent. This is a unique selling point of Selligent as this allows you not only to generate personalized HTML pages but also XML, JSON, CSS and plain text pages that can be used through the API. Users can build their own APIs for other systems directly within Selligent Marketing Cloud and utilize all the data, without requiring involvement of developers for their use cases. This especially highlights our platform extensibility.
For example, if a user wants to display specific content on a website page, such as last ordered product, payment status, content recommendations, etc. for the logged in user, an API response page can be used to display the required data, then use our Journey API to retrieve the personalized response page in real-time. Unlike developer approaches, which require code changes for new data elements, users need only edit the page and it is up-to-date. Extremely, fast and powerful.
Several enhancements were made within the Cherimoya release. Now a dedicated user right has been added to give users the explicit right to define mediums. Users who do not have this right, but nevertheless have access to tasks and want to create/update a task will only be able to select a predefined medium.
In addition, in order to increase the flexibility of the import function, MS ExcelTM and RSS are now supported as a file type for Import tasks, which already provided support for JSON, XML and Delimiter file types.
This release includes a number of enhancements for AB Journeys. The number of messages that can be tested in an AB Journey has been increased from 5 to 7.
In addition, reporting on AB journeys now lets you analyse the individual messages sent out in your AB Journey. To achieve this, a message analytics tag is set on the individual messages ensuring the AB test details are included in Google Analytics reporting. The tags can be set at creation time of the journey, or afterwards in the properties of the journey.
In a Custom Journey, data can be updated in the list as the result of an event in the journey. This is done through the Data Component. This Component has been extended in this release to provide additional data handling, allowing to create or update records in all lists linked to the selected Audience list for this journey. This includes 1:1, 1:N and N:N linked lists. In case of a record update, you can set a filter to limit the number of records in the targeted list and sort the result ascending or descending, returning one single record to update in the linked list.
The lookup component for Custom Journeys has been extended to let you search for data in any list that exists for the current organization. Previously this was only possible on the master Audience list. The ‘Switch to profile’ is only available for the Audience list though. This option to switch to a record in any lookup list will be added in a following release. The result of the lookup can be sorted. If several records are returned by the filter, you can sort the records for example with the most recently updated at the top.
Sometimes labels and sentences can occur at different locations in your content or journeys and translation into the contact’s language might be required as well. Examples of this might be a company logo or legal disclaimer.
To tackle this in an easy way, you can store these labels in dictionaries and for each label add a translation for all desired languages.
Using and re-using these labels in content is easy by adding a dedicated function to retrieve the translated label: [%label(‚DictionaryName‘,’Labelname‘)%].
The right translation is automatically displayed based on the language of the message. For ease of use, labels are also available from the Personalization dialog. The dictionaries are stored under the Library section and can be shared among multiple organizations or attributed to only one organization. The languages available in a dictionary depend on the languages defined for the selected organizations.
Labels in a dictionary can be exported from the Dashboard to a CSV file. This allows you to have the labels translated and import them again into the dictionary. Inline editing or deleting a label can be done from the labels overview.
For easy access all recent dictionaries are also available from the Library fly-out menu.
Validation is performed when trying to delete a dictionary or label and deletion is not possible when the label or dictionary is used in content
For users with more complex layouts with editable content, they can continue to use content blocks to address these use cases.
In our Blueberry release, we added the capability to create text-based Computed Fields in Lists. With Cherimoya, we have now extended this to support all data types, including numbers, dates, etc.
The Field usage can be viewed directly from the Field properties in a List. A dedicated button is available to launch the dialog with the usage details. In addition, when trying to delete a field in use, the same usage overview will be displayed.
To simplify the use of data errors in content, they have been added to the Personalization dialog where they can be easily selected and added to your content. Data errors are for instance generated by the Validation Component.
A new capability has been added to the API Explorer, allowing the possibility to delete tasks via the API.
A minor change was made, so now when defining filters on audiences, in journeys, etc. the small Filter icon has been replaced with a bigger Edit Filter button for improved usability.