When a Custom Journey begins with a Recurring Batch Input and includes an Event Data Component, users are now able to choose if the event is created once or every time the journey is executed.
This new configuration has been added to the properties of the Event Data Component, as a toggle to enable if desired.
In some cases when creating a Custom Journey, a marketer may discover a needed message is not yet created. To accommodate this workflow, a new shortcut to create new content has been added to the Interaction components for email, SMS, mobile messages and pages.
To use this shortcut, right click on a component placed on the canvas, or select the option in the component’s properties panel to the right.
Marketers often need to store and use more complex data types. For example, at a car exhibition visitors can provide their interest in one or more car models and types. When they leave their feedback, they will be contacted with personalized communications regarding their models of interest.
To support this, the user can now create JSON fields in Custom Events lists. A maximum of 5 JSON fields per Custom Events list is allowed. These JSON fields will be available in the Personalization dialog and the Visibility Constraint Editor to allow for the personalization of messaging.
In addition to the new functionality delivered in the Umbu Release, this release extends further on the multiple mobile apps per organization feature. This enhancement is also supported by the API.
Now, when creating a mobile message for a specific Devices list (Mobile app) linked to the audience of the message, the marketer can directly access the personalization fields for that mobile app.
Also, additional validation is added to ensure that each mobile endpoint can only be used in one organization and one audience. The reason why this is important is that when using the expression MobileValue (instead of a fixed scope) to personalize the mobile message, there is no need to duplicate the message when changing apps. The expression will always point to the right app. For example, when changing from test app to production app, you simply change the selected app in your message and the personalization will still work correctly.
The Vanilla release introduces Selligent Data Studio (SDS), our dashboard creation tool that allows users to create customized reporting of Selligent data and make them available in SMC. Standard datasets currently available for use, including communication and consumer stats, allow users greater visibility of their data to improve their marketing strategies.
Communication stats contain all the communications delivered and interactions with communications per contact. Common fields in this dataset include messages (emails, SMS, mobile) sent, delivered, viewed, clicked, etc.
Consumer engagement stats provide information on contacts and their engagement. This dataset currently supports the standard fields in an Audience list, such as email, language, optout, maildomain, etc.
Selligent Data Studio comes in two versions. SDS, available now in the Vanilla release, and SDS Pro, which will be released later this year. With SDS, marketers can create a dashboard based on the standard datasets provided. SDS Pro will allow the use of data from external sources and give the marketer the ability to create static and dynamic segments in SMC lists based on the dashboard filters. Selligent Data Studio is accessible from the Modules entry, via SSO. A maximum of 10 SDS users can be given rights to create dashboards. However, all SMC users with the necessary access rights to the dashboards chapter in SMC may view the dashboards created in SDS and published to SMC.
In addition to custom dashboard creation, a series of standard dashboards have been provided by Selligent. These dashboards can be viewed in the SDS but cannot be edited or deleted. Standard dashboards can also be duplicated and then edited to meet marketers needs. Selligent Data Studio or SDS offer an easy to use, drag-and-drop interface, where marketers can create their dashboards using common report components: bar, line, column, filters …
Every component on the dashboard can be configured. Depending on the type of component, different options are available such as the color theme, if a legend needs to be displayed, how data is ordered, if data should be limited when there are too many values, and many more. Filters, static or dynamic, allow limiting the data in the dashboard. Static filters are applied by default, either for the full dashboard or for a specific component. Dynamic filters give the marketer the possibility to filter on the spot. These filters can then be applied to all dashboard components or to a specific selection of components. Once dashboard design is complete, it can be published and made available from the Dashboards entry in SMC.
As a marketer, targeting visitors that are NOT on a certain page of their website can be advantageous. For example, if the website has a daily promotions page, you may want to draw visitors who have not viewed the page to do so and view these limited time promotions. To accommodate this need, a new constraint to target visitors who are not viewing a certain URL, has been added to the Constraint editor. The constraint ‘URL does not contain’ allows you to create these audiences.
This new constraint is available in the constraint editor in segments, offers and exports.
Marketers are often looking for new ways to retain visitors to their website. The Vanilla release introduces the ability to identify visitors who have been inactive or have shown an intent to exit a web page. To save these potentially lost visitors, a pop-in offer (or any other placement type) can be configured targeting this specific group. To support this new feature, new settings can be defined at universe level: one that sets the time period after which a website visitor is perceived as inactive (default 30 sec), and one that sets the minimum time before any exit offer can be triggered (default 10 sec).
The inactivity and intent to exit settings allow you then to create offers that target these specific audiences by creating a constraint in the WHO section when creating a new offer.
As a first step in the integration of Site into SMC, the configuration of the user rights has been moved to SMC. The Permissions section in the Admin Configuration now also contains an entry for Site. A matrix allows defining detailed rights for the different entities within the Site tool: Carts, Exports, Offers, Reporting Segments, Tags. Marketers with access to these sections have the right to Create, Update and Delete the different assets, Clear tag values (to allow clearing previously collected tag values) and Queue exports (to start exports manually). All users that can access segments or offers can also create labels for segments/offers.
It is now possible to enter a custom Reply address in the header when designing email messages. Prior to the Vanilla Release, Reply addresses could only be selected from a pre-defined list linked to the maildomain.
To use a custom Reply address, users can type a custom value in the Reply field. Pressing Enter will save the configuration. Personalization fields and expressions can be added manually to custom Reply addresses for even more individualized results.