Overview
This release introduces enhancements to the Batch Communication Engine (BCE) to improve campaign automation, user authentication, and data handling. Key updates include support for File-Triggered Campaigns, Single Sign-On (SSO), and improvements to Profile Import/Export Processes. These changes streamline workflows, strengthen security, and improve data consistency.
File-Triggered Campaigns
BCE introduces file-triggered campaigns that allow users to initiate campaign sends by simply dropping files into a configured SFTP location, eliminating the need for manual uploads and simplifying execution. Users can run campaigns immediately upon file delivery or use files for scheduled runs, with profiles in the file automatically used as the campaign audience. After each run, files are automatically moved to processed or error folders to prevent duplicate sends and improve visibility into file status, making this feature especially useful for teams that rely on external systems to generate audience files and want a streamlined, file-driven workflow.
Single Sign-On (SSO)
The SSO feature significantly simplifies how users access BCE by removing the need to remember and manage separate login credentials. Users can log in more quickly using their existing organizational account, and if they already have an active session, they can access BCE without any additional authentication steps, saving time and reducing friction.
It also improves productivity by allowing users to switch between authorized organizations or brands within the same session, eliminating repeated logins. From an access management perspective, users benefit from more secure and consistent permissions, with default roles automatically assigned and elevated access controlled by administrators, ensuring appropriate access without manual setup.
Overall, the feature enhances ease of use, speed, security, and access control, leading to a smoother and more efficient user experience.
Continuous Improvements
Profile Import/Export Enhancements
This release enhances the profile import and export experience to better handle real-world data issues while maintaining data quality and improving visibility into profile and subscription information. During import, undefined columns are ignored and labeled in the preview, and all column names are standardized to lowercase to prevent confusion and duplicate attributes. Import rules have changed, requiring, at minimum, the Profile Id to update existing records. New records require both the Profile Id and at least one valid channel address. If other channel address fields fail validation, the address will be replaced by "N/A". Profile exports now include active Subscription IDs for better context, and failed import files are automatically moved to an error folder with alerts to help teams quickly identify and resolve issues.