Highlights in Engage
January 2025
Versions 5.79 - 5.86
Shared Audience List Filtering Options
BACKGROUND:
Previously, when sharing an Audience List with other organizations in your brand, filters could be applied to narrow down the records being shared. However, these filters were limited to fields from the main Audience List only. Filtering on Data from a 1-1 linked list was not possible.
SOLUTION:
You can now share Audience Lists with other organizations while applying filters based on 1:1 linked lists. For example, if a linked list called "Loyalty Cards" contains loyalty card information across multiple organizations, you can filter and share only the contacts associated with a specific organization's loyalty card. This functionality enhances targeted sharing and helps ensure data privacy.
What this looks like in Engage (Selligent):
Upon sharing an Audience List, a filter can be added to limit the records shared with the other organization. Now, in the Filter dialog you have the option to select fields from a 1:1 linked list.
List Enhancements
BACKGROUND:
When linked lists are used, for example, in imports or exports, it was previously not possible to delete these relationships, though modifications were still allowed. Going forward, modifications to these relationships will no longer be permitted. Allowing such changes could lead to inconsistencies, especially if the relationship is referenced in a stored procedure. If the relationship is altered while the stored procedure continues to use the old definition, it could cause discrepancies, errors, or unexpected behavior.
SOLUTION:
Now, relations can no longer be altered once they are in use.
What this looks like in Engage (Selligent):
Upon accessing a relation that is in use, all properties are non-editable:
Mobile In-App Styling Improved Workflow 
BACKGROUND:
Previously, marketers had to create a journey with a dedicated page before they could use that page as a content source for an in-app notification, making the process cumbersome and inefficient. Within the in-app notification setup, they were required to manually select the journey's input component and then choose the page, which added complexity and made the workflow time-consuming and not very intuitive.
SOLUTION:
Now, marketers can enjoy an improved workflow, and select a page from the asset selector, without going first through the process of creating a journey, saving time while at the same time making it more intuitive and user-friendly.
What this looks like in Engage (Selligent):
In the configuration of the in-app notification a new Page option has been added. When selected, an asset selector is available to select a page and use it as a source in the in-app notification:
Note: The option previously labeled as Page, which allowed marketers to select the journey and then the page, has now been renamed to Journey.
Users who were using the old Page option will now see that these are renamed to Journey.
Sender Information in SMS, MMS and RCS
BACKGROUND:
Upon designing an MMS, SMS or RCS, the brand name or sender displayed in the mobile notification and app is currently based on the organization you are creating the message for. However, this is not always the same as the sender of the message.
SOLUTION:
Now, the sender of mobile messages is based on the sender configured in the mobile endpoints.
What this looks like in Engage (Selligent):
In Engage, when configuring an SMS, MMS, RCS channel endpoint, the sender of the message needs to be provided:
Now, upon designing an SMS, MMS, RCS message a mobile endpoint is selected.
The sender information for the selected channel is used in the message notification and content:
When no mobile endpoint has been selected yet for the message, the sender will be filled out with the name of the current organization.
Content Blocks Wizards and UI Enhancements
BACKGROUND:
Content Blocks are a key element of efficient content creation, allowing marketers to create content once and re-use this in multiple messages, speeding up the creation process as well as guaranteeing consistency across messages. Up till now, the creation of such a Content Block was a rather technical matter in a not so user-friendly interface.
SOLUTION:
Now, a wizard guides the user through the creation process and aligns the creation of a Content Block with the creation of all other content types. Also, UI changes have been made for improved user experience.
What this looks like in Engage (Selligent):
Upon creating a new Content Block from the Library section, a wizard allows you to first select the type of element you want to create, in this case a Content Block:
The Content Block basic fields and all fields are shown on 2 distinct tabs, mirroring the way in which content properties are shown elsewhere in the application.
When all details are filled out, click the Create button. This will take you to the Content Block Source tab where you can create and edit the HTML code:
An auto-complete function is available in the code editor:
Once a Content Block has been created, a Usage panel becomes available, replacing the former Linked content tab, listing all messages where the Content Block is in use. Again, these changes align the Content Block creation and editing with the other content sections in the application.
In addition, personalization through emojis, personalization and data selection fields have been slightly revamped as well as the locking mechanism when another user is editing the Content Blocks.
(More details in this subject can be found the this dedicated topic on Content Blocks.)
SG tags in Content Blocks Enhancement
BACKGROUND:
SG-tags are Engage specific HTML tags that allow configuration of the layout and content through a properties panel and make it language dependent. Previously, SG-tags were supported in Content Blocks created directly in the Library chapter. It was not supported yet when importing HTML messages.
SOLUTION:
Now, SG-tags are also supported when importing HTML messages via the Create email API. Note that it is not yet supported when importing HTML messages via the Engage interface.
Enhanced Workflow for Grow Integration
BACKGROUND:
Previously, when wanting to use a Grow experience (of type microsite) in an Engage message, marketers had to first manually copy the experience’s URL from Grow and then paste this as an external url in the Links configuration dialog in their Engage message. This required marketers to navigate two different tools which were time consuming and could be quite tricky to keep the overview.
SOLUTION:
Now, marketers can add an experience easily. In the Link configuration of an Engage message, they can now choose Grow as a destination and select an experience via an asset selector. This simplifies the process and speeds up the inclusion of an experience in a message.
What this looks like in Engage (Selligent):
When configuring a link to a Grow experience, marketers are now presented with an additional option as the destination of the link: Experience from Grow.
Once that option is selected, an additional field is listed to choose the appropriate experience.
Click the field to call the experience dialog. All experiences are listed by default, but only the Live ones can be used in a message. Use the Filter button to filter out the other ones.
You can click an experience to display a preview.
The eye icon shows the preview in full screen on a separate browser tab.
When you are happy with your choice, click Select.
The link to the Grow experience is listed in the Links dialog and once saved it is shown in the Links section of your message. It can now be added to your message like any other link.
(More details on using Grow experience in content can be found in this dedicated topic.)
AI Assistant in Dashboard Creation
BACKGROUND:
AI is a powerful tool that assists marketers in creating high-quality content. It is already available in Engage for subject line suggestions and content creation in messages (text, buttons). However, the potential of AI extends beyond content creation, including areas such as report generation.
SOLUTION:
Engage Data Studio has now introduced AI to help dashboard creators find the right graphs for their data and needs.
What this looks like in Engage (Selligent):
When creating or updating a dashboard, marketers can now add new graphs either manually or with the help of a Marigold AI assistant. New tabs are available that allow users to access suggested graphs or request AI recommendations by simply entering a question or use case, which will generate a series of relevant graph suggestions.
Suggestions:
The Suggestions tab provides a series of suggested graphs, based on the dataset that is listed at the top.
You can choose a different dataset from the drop-down and get suggestions that apply to that dataset. Using a suggested graph in your dashboard is done by an easy drag and drop from the graph onto the dashboard.
Ask AI
The Ask AI tab gives you the opportunity to ask a question or make a request, in simple terms.
As a result, AI will propose graphs, using the dataset listed at the top. Again, this dataset can be changed easily.
(More details on this subject can be found in the dedicated topic.)
Journey Reporting
BACKGROUND:
The current journey reports are not aligned with other UI elements in the application and are rather static, creating a mismatch between the application and the reporting.
SOLUTION:
Journey reports have been revamped and offer a more dynamic way of displaying results, resulting in better data representation, improved usability and a more modern UI.
What this looks like in Engage (Selligent):
Before:
After:
Although journey reports do look different in this new release, the data contained in them is to a high degree aligned with the old reports.
General journey information as well as message specific information is accessible through the horizontal tabs at the top of the report. Once a message tab has been selected, a left menu is shown giving access to a series of charts for the selected message including an overview for the message, detailed stats, delivery data, email clients(for email only), Device type (for mobile push messages), and the heatmap (email only).
Example of a report for a Single Batch journey, with a general tab and a single tab for the message sent:
Example of a report for a Custom Journey. In the General tab there is general journey information plus an overview of all content in the journey:
Here’s an example of a custom journey with multiple channels, where a dedicated tab displays reporting details for a specific content within the journey:
Additional functionality:
- The entire journey report can now be exported in PDF or PNG format, while individual widgets in a report can be exported to CSV, XLSX and PNG (when applicable). Previously, only export to CSV was offered.
- Data in widgets can be filtered, dynamically changing the data in other widgets as well.
(All details on the Journey reports can be found in this dedicated topic.)
Mandatory Google Consents for Google Customer Match
BACKGROUND:
Google Customer Match is an Engage feature that allows marketers to update Google audiences with Engage contacts. Google now mandates explicit consent before a contact can be added or updated in the Google Audience.
SOLUTION:
The Engage Google Customer Match feature now includes additional fields to capture and store a contact's consent for using their data for advertising purposes.
What this looks like in Engage (Selligent):
Upon adding the Google Customer Match Component to a Custom Journey, a properties panel is displayed, now listing additional fields to store the contact’s consent.
Ad Userdata stores a contact’s consent for using their data in ad targeting, while Ad Personalization tracks consent for utilizing their data in ad personalization. The possible consent values are: granted, denied, unknown, and unspecified. In the cases of "unknown" and "unspecified," Google determines whether the contact is added or removed from the relevant targeting audience.
(More details on this can be found in the dedicated Google Customer Match topic.)
