Added

We now support building one-time segment-triggered journeys! Select the "Drain immediately after sending" option on your journey's entry criteria to stop the journey from capturing new contacts beyond the initial membership of the underlying segment. Read more here.

Improved

• Proactively scaled data pipe and message sending infrastructure, both for Simon Mail specifically but also generically across channels, to improve message throughput for Black Friday + Cyber Monday season.

Fixed

• Ensured subject line character count limits don't take into account extra characters from Jinja personalization.
• Fixed a bug where emojis weren't rendering appropriately in subject lines.

Added

• Engagement Index in Simon Predict: We've introduced the Engagement Index, a brand-specific metric for measuring customer engagement. Use it to identify top prospects for campaigns, build lookalike audiences, or replace outdated engagement criteria. This flexible tool helps you tailor marketing strategies based on real engagement insights.
• 1:1 Couponing Assignment: You can now perform per-contact coupon or voucher assignment within Simon. This allows you to send contact-specific coupon codes that are assigned at the time of send. It's also compatible with Journeys branching, allowing you to send different lists of coupon codes to different groups of contacts in different variants of your campaign. Read more about it here.
• Custom Headers in Simon Mail: Simon Mail now supports custom headers (also known as x-headers)! These can be leveraged for a variety of use cases -- for example, managing your deliverability by integrating with ISP-specific deliverability insight tools. Check out some of our sample use cases and how to configure x-headers for your Simon Mail campaigns here.

Added

• New Journey Version Transition: We've added a new way for you to transition between versions of a journey! When publishing a new version of a journey, you can now choose to transfer contacts in the current version of the journey to the new version you're publishing! This allows your changes to take affect sooner, rather than waiting for the old version of the journey drain entirely. Read more here.
• Attentive Trigger Journey Action: We've updated our Attentive integration to allow users to trigger their Attentive Journeys from Simon. This is great news for customers who rely on Attentive to manage orchestration and on Simon mainly as an upstream data layer. This is also an excellent option for customers who use Attentive's reporting and are frustrated that our existing Trigger SMS action does not show up in Attentive’s reporting. This action is available in both Simon Journeys and Flows.
• RFM Model in Beta We now offer an RFM, or Recency, Frequency, and Monetary, which is a data-driven model that helps a brand’s segmentation strategy across several use cases, from identifying fraudulent purchasers to finding high-intent, high-value customers.

Improved

• Drag-and-Drop Journeys: We've made it clear where all the “Drop Zones” are for the selected step for easier and quicker iteration when using the drag-and-drop functionality to build and edit journeys.

Fixed

• Resolved an issue with the Event Visibility dashboard that prohibited users from seeing events being streamed to Simon via Simon Signal due to changes in Google's third-party cookie handling.
• Fixed an issue where alerts for Journeys under review in the Action Panel were not being sent to Slack.

Documentation Updates

• We've updated our fair use policies to include reasonable limits on individual Contact Event and Object dataset sizes.
• Check out our guide to building performant datasets within Simon Data! These include tips to consider when writing SQL, configuration suggestions, and our suggested dataset development workflow.

Added

• Journey Delay Editing: We've made it possible to edit a delay node in a live journey to better support changes you may need to make to your customer experience without publishing a new version.
• Optimized Send Time Model: We now provide an Optimized Send Time model to enable you to reach our customers at the time they are most likely to engage. This model is available for use in Journeys if you have Simon Mail or Sendgrid as your ESP.

Improved

• Journey Editing: We've made it easier to navigate to edit mode for nodes in a live journey so you can easily make changes to sends or delays without needing to publish a new version.

  

• Journey Entry Segment Search: When searching for an entry segment for a journey, we will now let you know if there is no segment that matches the name you're searching for.

• Contact Journey History: We have surfaced an additional field (FRONTEND_JOURNEY_ID) in the Contact Journey History data to make it easier to search for a specific journey.

• Webhook Action: We've added a validation to prevent saving or launching Flows and Journeys using the Webhook action if the domain configured in the Webhook Request Details has not yet been authorized for your account to avoid flow failures.

  

• Content Preview: We've added a spinner when in preview mode so if a template preview is taking a while to render, you know we're working on it!

  

Documentation Updates

• Search Bot: Our documentation site now uses a bot powered by OpenAI to help find the answers you're looking for and summarize learnings across our docs site. Now, you'll receive an AI-generated response in addition to surfacing any helpful documentation based on your search terms.
• Trait Syncing: This page was updated to remove references to this product being in Beta, as it is Generally Available to all customers that use the supported destinations (Braze, Klayvio, Iterable).

Improved

• Journey Split Navigation: We've made it easier to understand and edit branching and experiments journeys! Now, you are able to click into the configuration for any node within a split rather than only the top-level split step.

• Contact Journey History: We have surfaced additional fields to the Contact Journey History data we share for easier and more robust reporting. Read more about Journey History and these fields here (new fields are: CAMPAIGN_ACTION_ID, CAMPAIGN_SYNC_ID, JOURNEY_STATUS, JOURNEY_VERSION_STATUS, JOURNEY_TRIGGER, VARIANT_ID, JOURNEY_CREATED_AT, JOURNEY_LAUNCHED_AT, JOURNEY_ENDED_AT, JOURNEY_VERSION_CREATED_AT, JOURNEY_VERSION_LAUNCHED_AT, JOURNEY_VERSION_ENDED_AT, EMAIL).
• Criteo Integration: We've updated our Criteo integration to use their updated APIs for outbound syncing.
• Content Index Page: We have adjusted the spacing on our content index page to account for longer template and block names, requiring less text wrapping.

Fixed

• Facebook Match+ Configuration: We adjusted our Facebook actions in both Flows and Flows Beta to no longer allow users to uncheck the "Use Multi-key Fields to Increase Match Rate" box if the "Amplify your Audience Using Match+" box is checked. Match+ requires the use of Multi-key, so this action can no longer be misconfigured.

Documentation Updates

• Sub-processors and Supporting Services: This page has been updated with to include Zendesk as a sub-processor, Datadog as a supporting service, and to clarify both AWS and Snowflake are located in Europe in addition to their United States locations.
• Attentive Quiet Hours: This page has been updated to add considerations for use of Quiet Hours when sending SMS or MMS via Simon and Attentive.
• Journey Experiments: This page has been updated to clarify why experiment distributions not matching configurations while population size is small.

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.

Added

• Login Page: There is now a redirect to request a demo for folks that may navigate to the Simon Data login page from our website that are not yet Simon users.

Improved

• Slack Alerts: Alerts are updated to display the instance name they're related to. If you have multiple Slack channels for different instances, it might be a good time to consider consolidating to streamline workflow depending on your team's structure.

• Content Index Page:The edit date year now displays on the content index page for both templates and content blocks

• SMS Integrations:Attentive and Twilio Send SMS to Contact actions in both Flows and Journeys, now have a dynamic approximate character count to help track if you're within downstream requirements for character limits per message. Refer to your SMS provider's documentation for further detail on character count limits and how special characters like emojis impact character count.

Fixed

• Experiment Details: Experiments with very long names no longer cause difficulty for users to properly view experiment details for a given flow. Previously, there were cases where experiment names were covering conversion criteria.

• You can now use multiple Braze accounts when you add the destination to a Beta Flow. To add multiple business units to your authentication, first contact your account manager to enable multiple sub-accounts, then follow the steps here.

• The counts for entries to individual nodes in Journeys metrics now include all live versions. We've updated our reporting to properly capture all historical entries to a given node:

  

📚 Documentation updates

• Your documentation site looks a little different! Developer guides are now available on docs.simondata.com, consolidated in the API reference:

• We updated the permissions required for Braze authentication and added details about how to enable multiple sub-accounts.
  • We updated how to choose from multiple sub-accounts when syncing a Simon segment attribute in Braze.
• We added Flow ID information to the Flows - Beta guide.

✅

Thanks for reading!

We look forward to updating you every week with new and improved product features as part of our release cycle. Any questions or comments? We want to hear them! Feel free to leave feedback directly on the documentation page or via the Support Center.

• Webhook authentication was updated to allow for 15 domains maximum (previously 5 maximum). You can now view all existing, connected domains from the integrations page.

• You can now send a webhook test in Flows - Beta.

• You can now download a CSV with all your dataset names and details from the Datasets Dashboard.

• Three new columns were added to the Datasets Dashboard: Last Row Count, Last Runtime, and Last Completion:

  

• The X-axis in Flow Delivery Metrics was updated to reduce the number of dates and improve all-time metrics legibility:

  

• You can now sync to SFTP-based SFMC channel actions using SSH to authenticate rather than OAuth credentials. This is configured in the SFMC SFTP form on the integrations page. Learn more here.

• The Jinja Generator is now available in the Simon Mail Drag and Drop editor and for use in custom contexts in Beta Flows. To access it from a Beta flow, add a field then click the book icon to open the full editor.

  

• Simon Mail Drag and Drop editor updates are live to all. You can now:

  • Reuse content blocks (great for headers and footers)

  • Preview templates with dynamic content and send test emails

  • Convert Simon Mail Drag & Drop templates to HTML

  • Pick custom contexts from any segment, not just your "All Contacts" segment.

  • Make a Drag and Drop template available in Event Triggered flows