Product Update 11.18 makes message management easier, improves reporting and Media Assets, and includes several reliability and usability improvements. Most changes require no action.
Release overview
| Release item | Category | What changed | Why it matters |
|---|---|---|---|
| Media Assets | Improvement | Media Assets have moved to Content and reused files can share central storage, with a clear distinction between Campaign and Overall assets. | Less duplication and clearer access scope. |
| Message management | Improvement | SMS and WhatsApp messages can be copied, and the message preview again shows the ID, creation date and change history. | Content can be reused more quickly and changes are easier to trace. |
| Bulk SMS reporting | Improvement | Bulk Message sends are registered as campaigns in Spotler Message. | Bulk sends can be reported on as campaigns instead of grouped altogether |
| Login | Improvement | Two-factor authentication and failed-login messages are clearer and appear at the correct time. | Users receive clearer guidance during login. |
| Contact and import integrity | Bug fix | Uniqueness checks use complete field values, and groups used by automated imports cannot be deleted. | Prevents overwritten contacts and broken scheduled imports. |
| Platform cleanup | Maintenance | Outdated and unused technology has been removed. | A simpler platform is easier to secure, maintain and improve. |
Highlighted changes
Clearer and more efficient Media Assets
Media Assets are moved from Setup to Content and distinguish between Campaign assets and Overall assets. The existing Overall Assets can be found at Overall. Campaign assets belong to a specific campaign; Overall assets are available across the licence and require Overall permissions.
When you edit your mailing and insert an image, you will now see an extra Campaign tab:
Copying a mailing no longer creates a separate physical copy of every image and file. Reused assets can share the same centrally stored file, reducing duplicate storage and keeping reused content consistent.
Copy messages and review their history
Users with permission to edit messages can copy both SMS and WhatsApp messages from the Messages screen. The content is copied to a new message with its own ID and creation date. The original history is not copied; the new message receives a history entry showing that it was copied.
The message preview once again includes the message ID, creation date and change history, with one line for each adjustment.
Improved reporting in Spotler Message
New bulk Message sends are now registered as campaigns in Spotler Message instead of grouped together. This makes campaign-level reporting possible. The sending workflow in Spotler MailPro does not change.
A simpler, more maintainable platform
The end-of-life Email Wizard, Slurp and legacy filter editor have been removed. Removing these older components reduces technical complexity and allows improvements to focus on the current, supported functionality. Unused SOAP actions for SMS and the remaining backend components for Push Notifications have also been removed. No customer action is expected for these technical cleanups.
Full release notes
Media Assets
- Media Assets has been moved from Setup to Content
- Media Assets now distinguishes between Campaign assets and Overall assets.
- Existing license wide assets are available at Overall
- A new empty campaign specific location for media assets is available in each campaign
- Copied mailings can reuse centrally stored assets instead of creating physical duplicates.
SMS and messaging
- SMS and WhatsApp messages can be copied again.
- The message preview shows the ID, creation date and change history again.
- Messaging Senders no longer shows an SMS sender when SMS is unavailable.
- Date fields in SMS messages can follow the configured locale.
- Copying field definitions between campaigns retains the
mobile_nrfield. - Bulk message sendouts are registered as campaigns in Spotler Message
Other improvements
- The two-factor authentication message more clearly tells users to check their email and verify the login.
- The “too many failed login attempts” message is shown at the correct time.
- A group used by an automated import can no longer be deleted.
- For new campaigns, uniqueness checks compare the complete value of unique fields and email addresses.
- Improved certificate reissuance in line with updated standards.
Technical cleanup
- The end-of-life Email Wizard, Slurp and legacy filter editor have been removed, reducing platform complexity.
- Unused SOAP actions for SMS and the remaining components for Push Notifications have been removed.
- The remaining legacy Webpower interface has been removed; all users now see the Spotler-branded interface.
Related documentation
FAQ
My Media Assets are no longer visible. Why is that?
You are probably viewing the newly introduced location for campaign-specific media assets. This location only contains files for the current campaign and may therefore still be empty.
Existing license-wide media assets have been moved to Overall.
Will links to media assets in previously sent emails continue to work?
Yes. These changes do not affect links to existing media assets in previously sent emails. Recipients can therefore continue to access these files and older newsletters.
Do I need to make any changes to existing or new emails?
No, existing emails do not need to be updated. When creating or editing an email, you can choose between campaign-specific files and the existing shared files in Overall.
Can I copy both SMS and WhatsApp messages?
Yes. Users with permission to edit messages can copy both message types. The content is copied into a new message with a new ID, creation date and history entry.
Does sending bulk SMS change in MailPro?
No. The sending workflow is unchanged. New bulk SMS sends are registered as campaigns in Spotler Message, which makes campaign-level reporting possible there.
Do I need to take action because of the removed features?
No. The removed technical components were mostly unused and customers that were affected by removed features we informed beforehand. No further action is expected.