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.