Added

  • Lookup Table Support: You can now create Lookup Tables to connect non-contact data (e.g. product catalogs, store locations, inventory data) to your Simon instance for use in personalization. As an example, you can now include a product recommendations module in your winback campaign to reduce customer churn
  • Action to Trigger an Attentive Journey: 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.

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.

Documentation Updates

Improved

  • Webhook Action: We've added a validation to prevent saving or launching Flows 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.

  • Multi-Value Identifier Support: We now have the ability to support an array of identifiers associated with a single contact (e.g. all_emails) in the Schema and Segment Builders. Joining tables on an array field results in a 1:many relationship between the tables. For example, if Jane Doe has 3 emails associated with their contact, any activity associated with any of these emails will be tied to Jane Doe.

  • Permissions: We've updated user roles to include permissions for Trait Syncing.

Fixed

  • Segment Copying: We fixed a bug that was occurring when copying segments where the copied segment was being properly created, but the UX was appearing not to save with an error.

Documentation Updates

  • IP Allowlist: This page was updated to include EU Service IP addresses.

Added

  • CSV Uploads: Instead of relying on data teams or Snowflake admins to create and connect a table to Simon for use in segmentation, marketers can use the Simon platform to upload a CSV for immediate activation. Simply upload a CSV, which creates a table in your organization's underlying Snowflake, and immediately activate those customers without writing a single line of code.
  • Trait Syncing: We've released trait syncing, a new integration approach that incrementally sends customer properties to supported marketing clouds to support best-in-class personalization downstream of Simon. With trait syncing, customers can see greatly increased syncing performance and dramatically reduced overage usage for platforms that charge on data consumption. Trait syncing is currently supported with Braze, Iterable, and Klayvio.
  • Support for ARRAY Data Types: We've added support for ARRAY data types throughout our composable application. With ARRAYs, marketers can create more nuanced segments based on multiple criteria. For example, it is now possible to segment customers who have purchased multiple specific products or engaged through various channels over time.

Improved

  • Unified Contact View Performance: We've made performance improvements to our Unified Contact View (UCV) feature, ensuring that both the index page and individual contact profiles load as quickly as possible. You will be able to see channel identifiers and multi-key fields immediately while all other contact properties will load in the background and will appear once they're available.
  • Criteo Integration: We've updated our Criteo integration to use their updated APIs for outbound syncing.

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.
  • Segmentation Unique Values: This page has been updated to clarify what to expect while building a segment with a property you are segmenting on contains more than 1,000 unique values.

Added

  • Datasets: Unlock the power of data transformation with Datasets; this feature allows you to write SQL to transform your data and create custom or calculated fields, even without direct access to Snowflake, enabling Marketers to drive personalized campaigns with ease and precision.
  • Query Tag: We added a Query_Tag to your Snowflake query history. This tag is for Simon internal use. It contains the application within Simon that generated our query. It's not backward compatible and subject to change without notice.

Improved

  • User Permissions: You can now choose from three pre-configured user roles or design custom permissions. Read our guide here for more detail.


  • Segmentation: For both property filters and event filters using the is and is not operators, there are now up to 1000 field values displayed regardless of how many distinct values exist for the attribute you are filtering on. You are no longer left guessing the format of any attribute while building segments, even if it has more than 1000 distinct values.

  • Privacy Requests: We have improved our backend processing of Privacy Requests to more quickly delete individual's data that have requested erasure.

✨ New


🔨 Improved

  • Flows reporting now includes reporting over unprocessed contacts. If contacts are skipped for any reason, you can see this detail in reporting to investigate any discrepancies between Simon and your downstream channels:

  • We added a drop-down box for fields with distinct values so you don't have to guess the syntax for the field value. This is available for both property filters and event filters using the is and is not comparisons. The list is populated with values from your data warehouse with values refreshing daily. Newly connected fields may take a few minutes for their values to be available. If there are more than 1000 unique values, you'll need to manually enter a value. Learn more here.

  • You can now use multiple Braze accounts when you add the destination to a Flow. To add multiple business units to your authentication, follow the steps here.

    From the Account ID drop-down, select the Braze account you want to trigger from.

    From the Account ID drop-down, select the Braze account you want to trigger from.

All accounts currently authorized display on the integration page

All accounts currently authorized display on the integration page



📚 Documentation updates

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.

  • The activity dashboard was removed and replaced with the Flows Index page to make way for future improvements.

  • AI powered segment descriptions are now available based on your property filters:

  • 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.

  • Data feed syncing is now available in flows. Contact data is sent downstream to your Snowflake instance. To enable or disable, from the left navigation expand Admin then click Settings, then Data Feed Configuration. When enabled, you'll see the Data Feed details at the bottom of the Flow creation screen:

  • From the segment details page, the number of live flows powered by that segment are now displayed:




New! AI powered Segment descriptions. Auto-generate your segment descriptions while selecting property filters.

Improved! We made enhancements to the query generator that powers the segmentation tool. You should notice that the views Simon maintains are a bit clearer and easier to read. Additionally, the top-level segment filter group option has now been fully superseded by the property filter group level segment filter; these two options are identical semantically, this is just UI consolidation providing users less ways to do the same thing.