Changelog
Intempt SDKs
Back to All

December 31, 2024

6 months ago by Svitlana Rudenko

We’ve launched a new Product Block in the Visual Editor, making it easier than ever to embed product recommendations directly into your emails, web personalizations, and experiments. Whether you want to highlight best sellers, recently added items, or personalized picks—this block has you covered.

You can choose between dynamic blocks (powered by behavioral and predictive data) and static blocks (where you hand-pick the products yourself). Dynamic blocks automatically surface trending items or personalized suggestions based on each user’s journey. Static ones let you stay in full control of what’s shown.

Each block is fully customizable—adjust fonts, colors, product titles, CTA buttons, and layout. You can even style them as sliders to better showcase collections like “New Arrivals” or “Popular Right Now.”

To get started, just open the Visual Editor, drag in the Product Block, choose your type, and fine-tune the layout under the Styles tab. That’s it.



🛠 Improvements & Fixes 🛠

  1. Force deletion issue resolved for Likelihood, Next Best Action, and RFM

The issue where force deletion did not work for Likelihood, NBA, and RFM has been resolved. Users can now successfully delete models without errors, ensuring a smoother workflow when managing these features.

  1. Error with attribute data type changes fixed

Attribute changes, such as switching from "phone" (string) to "synced" (boolean), now fail as expected to maintain datatype consistency and prevent schema mismatches.

  1. Enabled all sources for Stripe account processing

The system now enables all sources attached to a Stripe account when handling the "account.application.authorized" event. This fix ensures seamless processing and proper synchronization across all connected sources for Stripe accounts.

  1. Custom events foreign properties fix

Custom events now properly handle foreign properties. For custom events with sessionId, session attributes are correctly included in the /event-attributes request. For custom events with pageId, page attributes are also included in the /event-attributes request. This fix ensures that all relevant attributes are accurately associated with custom events, improving data integrity and usability.