Enhanced recommendation capabilities with the addition of a Product Block feature in the Visual Editor. This update improves personalization options in both Personalizations and Experiments, enabling dynamic or static content integration.
✨ New Features ✨
1. Product Block in Visual Editor
What it is:
The Product Block feature allows users to create dynamic or static product recommendations directly as part of site personalization or experimentation.
Key details:
Dynamic product blocks show items based on business trends (e.g., best sellers in the last 90 days) or personalize recommendations based on individual user behavior and predictive analytics.
Static product blocks allow users to manually select specific items to display.
Users can customize the appearance of the blocks (e.g., product title, price, CTA button) using the Styles tab for font, size, and color adjustments.
Product blocks can also be styled as sliders for showcasing the newest products, most popular items, or personalized recommendations.
Why it matters:
This update enhances Intempt's personalization capabilities by providing an intuitive and visually engaging way to integrate product recommendations into various marketing campaigns and user experiences.
How it works:
Open an email, website, or experiment in the Visual Editor.
Drag and drop the Product Block into the canvas.
Choose between a dynamic or static product block type.
Fill out the necessary fields and adjust product details using the Styles tab.
🛠 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.
2. 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.
3. 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.
4. 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.