June 2024: Pre-Headers, Journeys Improvements, Integration Updates
9 months ago
Added
- Pre-Header Support: You can now specify the preheader of your email in the configuration of your campaign instead of the HTML of your template. Read more here.
- Journeys Alerts: We've added alerts to Slack for Journeys that require review in Action Panel so your team can review any unexpected changes.
- Send Now Confirmation: We've added an extra validation step when sending one-time flows immediately - no more accidental sends when you meant to save!

- Salesforce Marketing Cloud Actions: Flows beta now supports the Sync Contact to Data Extension action for our Salesforce Marketing Cloud integration.

Improved
- Journeys Re-entry Criteria: Journeys now support more flexible re-entry criteria to better target customers at the right time in their lifecycle.

- Klayvio Integration: Our bi-directional integration with Klaviyo now uses their updated APIs for both data ingestion and outbound syncing rather than relying on their v1 / v2 APIs that were deprecated at the end of June.
- OneSignal Integration: We now have a native OneSignal integration that supports web and mobile push.
Fixed
- Journeys Copy Branching: You are now able to successfully copy a step from another branch of an Event Triggered Journey, even when the branching uses an Event Split.