Improved

• Braze User Aliases: We've added support for user aliases within our Braze integration. When syncing to Braze from Simon, if an external_id does not exist for a contact, we will now fall back to a user alias if it exists in the Simon account.

Added

• Amazon Ads Integration: This integration allows you to sync contact audiences directly to Amazon Marketing Cloud (AMC), where they will appear as Advertiser Uploaded Audiences. With this, you can create lookalike audiences in Amazon DSP, suppress existing customers from acquisition campaigns, target high-LTV customers with personalized ads, and retarget churn-risk users across Amazon-owned properties.

Improved

• AI Model Upgrade: All GenAI features (e.g. Jinja Generator, Segment Descriptions, etc.) have been upgraded from Claude 3.5 Sonnet to Claude 4 Sonnet, providing enhanced performance and capabilities across the platform.
• Klaviyo API Enhancement: We've enhanced our Klaviyo trait syncing operations to provide improved performance for large-scale profile updates and backfills.

Added

• Journey Campaign Metrics Filtering: Added toggles to help users focus on relevant data by only viewing rows for nodes in the current live journey version and excluding non-sending nodes like branching and joining steps. This enhancement makes campaign performance analysis more streamlined and targeted.

Fixed

• Resolved a bug in sorting functionality on the Flows index table, as well as normalized the column widths for better readability.

Improved

• Improved the search interface on both the Flow and Journey index pages for better usability.

Improved

• Increased the property threshold to 150 for trait syncing to Klaviyo
• Improved the isolation of Journeys execution to provide more consistent journey launch / entry timing

Added

• Programmatic Updates to the Subscription Center: You can now programmatically update the membership of individual contacts to lists in Simon's Subscription Center by sharing files containing email addresses to add / remove from the given list.

Improved

• Updated time zone formatting across both Flow Builders & Journeys to be consistent & clear relative to UTC.

Added

• New Salesforce Marketing Cloud Channel Action: We've added the Add to and Update Data Extension to the Flows - Beta flow builder.

Fixed

• When using Simon Webhooks, the UI would crash if sampling a contact failed to return a contact. Now, the failure is displayed gracefully in the form of a user-friendly validation error.

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.