Users can now leverage a barcode component to add either barcodes or QR codes to their messages. Support is provided for type EAN13 and Code39 barcodes. The selected type defines the structure of the bar code. When the type is defined as QR Code, the user specifies a correction level (which establishes how usable it is, even if parts of it are missing and a version (which is how much data the QR code can contain). A higher correction level requires more space, and thus a higher version number. Both barcodes and QR codes are generated using one or more fields from your audience list and the size can also be defined within the available user settings.
Smart Content, which provides product recommendations courtesy of Selligent Cortex, our purpose-built AI powered engine includes an enhancement to track which recommendation leads to a purchase. Existing functionality included attribution, in terms of which Smart Content blocks that led to an ‘add to cart’ action, but this release extends to attribute the conversion for increased understanding of Smart Content performance.
Several enhancements were made to the use of lists within Selligent Marketing Cloud. The first, now allows users to share a specific list with other organizations (subject to the appropriate user permissions and access rights to the destination organization). Filters can be applied, to share only a sub-set of the list, if required. Shares can also be edited (subject to user permissions) and validation ensure shares cannot be removed for organizations the user had not been granted access to.
Additional expression capabilities have been added now to support the following: Hash, Search, Find, ReverseSearch, as well as IF and CASE functions, e.g.
Reporting enhancements for Recurring Batch Journeys were made to provide performance per run of the journey. This gives insight in how a single Recurring Batch execution performs compared to other executions of that same journey. The information available from a chart, as well as via a accumulative report.
The Data Search API has been updated to include the filter on a list of for an organization when a filter exists, as well as support for deduplication of messages via the API.
Integration with CRM solutions has been fully tested and we now support the following versions for the different connectors:
As different integrations require different throughputs, in this release users can now define the interval and batch size for any channel inputs, for example, Facebook Custom Audience, Google customer Match or any Custom Channels.
The Facebook Plugin Version has been upgraded to 3.3. As covered under Data Synchronization Enhancements within this release, you can now also define a batch size and time interval for Facebook Custom Audience and Google Customer Match channels.
Within the Damson release there are several enhancements to the Custom Channel such as the support of custom parameters in the Custom Channel definition and the support of Option Lists for these parameters. As covered under Data Synchronization Enhancements within this release, you can now also define a batch size and time interval for Custom Channels.
This release includes the introduction of Cadence Management to Selligent Marketing Cloud. Previously available to Campaign, this release provides a radically redesigned user experience to control the channel frequency, prioritization of journeys and channel communications. This is differentiating against competitors which provide only email centric controls, or frequency caps for channels with no way of prioritization journeys to control the orchestration of channel communications and control marketing pressure. This can reduce data fatigue, which is a typical of over-solicitation of marketing communications to consumers. Marketers define plans, to which journeys are added to limit the number of outgoing messages. Rules help to determine frequency, and priorities can be set across multiple journeys by simply dragging to define the priority order. Intra journey touches can also be taken into account, for example in lifecycle journeys where someone may receive multiple messages. Reporting provides details of targets that have been excluded and which journey, message or rule is responsible for the reduction to provide full visibility to the user.
Sometime, when a journey is designed you may want to avoid duplication of a marketing message, but you might be using different audiences which contain the same email address (or perhaps even telephone number). Within the Damson release we are introducing the Deduplication Component to resolve this very issue. Users are able to perform such deduplication with Single Batch, Recurring Batch and AB Journeys. All they need to do is select either one, or several unique keys that identify the individual uniquely, e.g. customer id, email address, etc. and then a field to sort the result by, and preferred sort order (i.e. Ascending / Descending). Where duplicates are detected, users can choose which record to keep, and which to discard, for example the most recently updated record may prove the most common use case. This also allows for more advanced use cases, which is great for industries like Telco’s that have multiple product lines e.g. Digital TV, Broadband, Telephone, Mobile, etc. Specific products can be targeted to the head of household (by deduping on account number) but for promoting movies or television programs can be personalized to each family member. Customer Journeys also support this functionality for every Bulk Component added, including Email, SMS, Mobile Push, Facebook Customer Audience or Google Customer Match as well as Customer channels.
Users looking to reduce the number of contacts within a Custom Journey can now leverage the Top Component to do so and can also use in conjunction with the Single Batch and Recurring Batch Components. Users specify the number of records that should be selected as well as whether it will be applied to each, or across all executions. The latter ensures that the volume is reached, by sending additional batches until the target is met. The earlier will send less messages, where the volume of records in the audience is less than the defined threshold. Compatibility also enables the Top Component to be used in conjunction with the wave component for single batch execution to support even more advanced use cases.
An enhancement was made to allow for multiple Audience Filter Components to be added after the same Event within a Custom Journey. This allows for more advanced use cases, whereby you want to pivot the path of different audience groups within a single journey.
Several content enhancements were made to enhance the user experience within Selligent Marketing Cloud within the Damson release. Firstly, users can now convert messages to templates, and templates to messages. This creates efficiencies, whereby the user wants to leverage an existing message as a starting point for a new template, or accidentally creates a message, instead of a template. Secondly, duplication of emails to folders in other organizations was extended for SMS and Mobile Messages. Validation checks for missing assets, such as access to the content section in the target organization, a language does not exist, or there is no access to a Content Block leveraged within the target organization. Users can also force a copy if there are errors, so they can manually select the assets in the destination organization.