In Spotler MailPro, release 11.16 introduces updates to the import scheduler, flow builder, mailing configuration, and data processing. These updates provide more control over imports, improve flow efficiency, and enhance export and anonymization capabilities within the software.
What is included in this release?
This release contains improvements to the import scheduler, new configuration options in mailings and flows, and optimizations in exports and performance. Several existing features have been expanded or simplified based on common usage.
On this page, the following topics are covered:
- Import scheduler features
- Flow builder updates
- Performance improvements
- Data processing and export
- Dynamic sending option
- Full release notes
- FAQ
Import scheduler features
The import scheduler is used to automatically import contact data from external sources such as SFTP or API connections. This release adds multiple options to improve control, flexibility, and error handling.
Manage contacts not in the source file
You can now automatically remove contacts from a group if they are not included in the import file. This ensures that the group always reflects the current state of the source system.
Optionally, these contacts can be moved to another group instead of only being removed. This enables use cases such as moving outdated contacts to a separate group for further processing, for example anonymization.
Use wildcard filenames for imports
It is now possible to use a wildcard (*) in the filename when retrieving files from an SFTP location. This allows the import scheduler to process files with dynamic naming patterns, such as batch numbers.
All files matching the pattern are processed. To prevent duplicate imports, it is recommended to enable archiving so processed files are moved after import.
Improved file path handling in external connections
The software now automatically adds missing forward slashes (/) to file paths in external connections. This prevents import failures caused by incorrect path formatting.
Return import error files to external connection
You can configure the import to return error files to the external connection. This allows external systems to automatically process import errors.
To use this functionality, configure both the return option in the import and a result path in the external connection. Error files can include dynamic naming, such as timestamps, to support tracking.
Name your import schedules
Import schedules can now be given a custom name. This makes it easier to identify and manage multiple scheduled imports.
Flow builder updates
Not in group option
A “Not in group” option has been added to flow start steps. This allows contacts to be excluded before the flow starts.
This prevents unnecessary processing inside the flow and improves performance, especially when large groups are involved.
Combined flow start steps
The “When Contact Matches Filter” start step has been removed and merged into the “Periodical with optional filter” start step.
This simplifies flow configuration by combining similar functionality into a single, more flexible option.
Performance improvements
Improved sendout speed for Single SMS
The sendout speed for Single SMS messages has been improved. This results in faster delivery of individual SMS messages.
Data processing and export
Select inactive groups in the anonymizer
The anonymizer now supports inactive groups. This allows you to anonymize contacts in custom groups that are no longer actively used.
This removes the need for workarounds using system groups and provides more flexibility in data management.
Sends as separate rows in advanced export
You can now include sends as separate rows in advanced exports. This aligns the export structure with raw data exports.
Each event, such as send, click, or bounce, can be exported as an individual row instead of combining multiple events into a single row. This improves clarity and makes the data easier to process externally.
Dynamic sending option
A new option has been added to control whether sender fields from the contact are used in a mailing.
If sender fields such as sender_email and sender_name exist on the contact, these can be used to personalize the sender. This enables use cases such as sending emails from individual account managers.
Previously, these fields were always used when available. You can now choose per mailing whether to use these contact-level fields or the default sender configured in the mailing.
This makes it possible to switch between personalized and generic sending within the same setup.
Full release notes
The overview below lists all changes included in this release, including smaller improvements and bug fixes.
Feature optimizations
- Ability to choose whether to use sender_email fields in the mailing settings
- Added “Not In Group” option in the Recurring Flow start step
- Removed “When Contact Matches Filter” Flow start step and renamed Periodical to “Periodical with optional filter”
- Improved the sendout speed for Single SMS
- Select inactive groups for the Anonymizer
- Optionally add Sends as separate rows in the Automated Export
Import scheduler
- Setting to move contacts not in source CSV file out of the import group
- Optionally move them to a different group
- Also available via REST API (RemoteCSVImport)
- Possibility to pick up dynamic file names from SFTP using a wildcard
- Automatically pre- and append missing /’s to the filepath in the External Connection
- Ability to return import error files towards the used External Connection
- Identify a scheduled import by its name
Bug fixes
- Fixed a bug where republishing a Flow too quickly after unpublishing failed
- Fixed a bug where access of Summary Export and Advanced Export wasn’t separately enforced
- Fixed inefficient queries in Automated Exports, especially with webversions
- Resolved several issues found in the yearly pentest
FAQ
When should I use the option to remove contacts not in the import file?
Use this option when your source system is leading and you want your group to always match the latest import data.
What is the benefit of using wildcard filenames?
Wildcard filenames allow flexible file handling when filenames change, such as when batch numbers are included.
Why would I return import error files to an external connection?
This allows automated systems to process errors and keeps error data available for a longer period.
What is the advantage of separate rows in exports?
Separate rows provide clearer event-level data and make it easier to analyse or process exports externally.