In this release of Spotler Mail+, new features have been added and various bugs have been fixed. We highlight two updates in particular: the ideas forum is now accessible to all users regardless of their language profile, and a third answer option has been added to the Gender question in the forms module.
In this article, you can read more about:
Ideas forum available to everyone
Until recently, the ideas forum was only available to Dutch-speaking users. If your profile was set to English or another language, you previously couldn't submit an idea. From now on, the ideas forum is accessible regardless of the language set in your profile.
Want to know more about the ideas forum?
- Introduction to the ideas forum
- How do I get to the ideas forum?
- How does the ideas forum work?
- How we keep the ideas forum up to date
Good to know
The version of the ideas forum you see depends on the language in which your environment was created. If you are an English-speaking user in a Dutch-configured environment, you will see the Dutch ideas forum. The ideas in this forum are not translated into English. If your Mail+ environment is set to English, you will see the English ideas forum. This ensures you and your colleagues view the same forum and can see and vote on each other’s ideas.
Third option in form question 'Gender'
In the Forms module, a third option has been added to the standard Gender question: Prefer not to say. Previously, only the options for Male and Female were available. The new option supports inclusivity and is customizable: the label can be edited or removed.
This addition also changes the default setting for personalized salutations. If the third option is selected, only the name will be used. If Male is selected, Mr. is used; for Female, it will be Ms.; and for 'Prefer not to say', only the last name is used.
Good to know
- Existing forms that already use this question will not be updated
- Existing (API) connections may not be able to process this option
- If you’ve previously created a custom gender question, the salutation setting will not be updated and can continue to be used as is
Full release notes
API updates
The API for mailing interactions has been extended. It is now possible to retrieve SMS interactions and mailing IDs when calling the mailing interaction endpoints.
SMS interactions
SMS interactions can now be found in the mailing interaction calls. This means sent SMS messages and possible bounces are now visible via the API. This was previously not possible.
The following API endpoints now include SMS interactions:
Mailing or automation ID
It is now also possible to link an interaction to a specific automation. Two new IDs have been added:
- publishedAutomationId – Similar to the existing mailing ID, but specifically for automations
- automationContactId – A unique ID per contact in an automation
These IDs are available in the following API endpoints:
- GET /mailing-interaction/bounced
- GET /mailing-interaction/clicked
- GET /mailing-interaction/opened
- GET /mailing-interaction/sent
Improvements in the Editor
Element selection for RSS items
You can now choose which type of element you want to use for RSS items. Previously, a text element was used by default for the "description" field, but now you can easily change this to, for example, a heading.
This improvement is particularly useful for personalized RSS feeds. The editor automatically detects the content type and suggests suitable elements such as text, images, or links.
In future updates, this will be further extended with element selection for custom recommendation items and more element types for personalized product blocks.
Accessibility – Language selection
Previously, you had to adjust the SPML code to set a screen reader language. That is no longer necessary: the editor now includes a convenient input field allowing users to easily set the message language.
This is essential for better accessibility of your messages, especially for users who rely on screen readers.
Bug fixes
-
Ticket number: 2378637 | Forms | Read-only field values are hidden
The read-only email address field was not displayed in forms. This made it unclear to users which email address was being used on unsubscribe pages. -
Ticket number: 2370533 | Required symbol missing in editor
In required questions in forms (V2), the asterisk (*) was not shown. Error messages were also missing due to a specific HTML structure that made the symbol invisible. -
Validation added to ‘Resend’ in Mailing Wizard
If the “Automatically resend to new contacts” option was not selected, users could still proceed without any warning. A validation message now appears and the radio buttons are marked in red. -
Brands were not applied in forms
When assigning a brand to a form, it did not appear in the form itself. The correct brand was shown in the preview. -
Ticket number: 2360693 | Column spacing missing in advanced content elements
In product and recommendation blocks, the configured column spacing was not applied. This affected both the preview and the final message. -
Anchor tags with spaces didn’t work in some email clients
Anchor links with spaces in their names didn’t function correctly. Some email clients (such as Outlook) were unable to convert ‘%20’ back into a space. -
Ticket number: 2375134 | Image alignment differs on mobile
Images aligned to ‘center’ could appear left-aligned on mobile in the toolbar, even though the settings were correct. -
Focus remained on anchor name input
When adding an anchor, the focus didn’t move to the input field for the anchor name. -
Labels clarified for button link options
The first two options in the button link settings now clearly show the terms _blank and _self. The ‘frame’ option will likely be removed, as email does not support frames.