November 5, 2024

Released a redesigned Messages tab with dynamic content support for emails and SMS, improved deletion confirmation for clearer object management, and advanced segmentation using account attributes for precise targeting. Introduced basic RECS project functionality for personalized product feeds. Key fixes include optimized logging to prevent system slowdowns, schema update corrections, improved journey tracking, enhanced reporting filters, and seamless email creation in the updated interface.

✨ New Features ✨

1. Updated Messages Tab

What it is:

We've redesigned the Messages tab to make it more user-friendly and efficient.

Why it matters:

This new design allows users to interact with messages more intuitively, enhancing the overall experience.

How it works:

The updated layout simplifies message creation and adds support for dynamic content with liquid variables not only in emails but also in sms messages. Now you can dynamically customize content, easily adapting it to your specific needs.

2. Enhanced Deletion Confirmation

What it is:

We've improved the deletion confirmation message, making it clearer which objects will be affected.

Why it matters:

This update ensures that users have full visibility into related objects that will be deleted along with the main object.

How it works:

When deleting an object, you’ll now see a detailed view of all related objects. This new interface provides confirmation steps, helping you review all affected items to avoid unintended deletions.

3. Segmentation Matching with Account Attributes

What it is:

This update introduces advanced filtering for user segmentation based on account-level attributes, such as company size, revenue, industry, and company name.

Why it matters:

With this feature, you can better target users who are associated with specific types of companies, enabling more precise and relevant outreach.

How it works:

Account-level attributes are now available in targeting. To create a robust filtering mechanism that leverages account-specific attributes to target individual users.

🚀 In-Progress 🚀

RECS Project

Right now, we're only implementing - Basic RECS flows, metadata, and feeds.

What it is:

This project is a major selling point for Intempt as a platform to get more use of journeys and personalizations products. The current personalization capabilities (attribute personalization) will not be sufficient to leverage the GrowthOS potential.

Why it matters:

The solution is - enable creating product feeds that would output product recomendations based on pre-set algorithms (like best-sellers) and product attribute filters. These feeds then should be selectable for product output via API or in personalizations and email builder.

🛠 Improvements & Fixes 🛠

1. Change Logging Settings

To prevent potential system slowdowns and avoid exceeding physical memory limits, we’ve optimized our logging configurations. This update ensures that log files are managed more effectively, reducing memory usage and maintaining smooth system performance, especially during peak operational times.

2. Schema Update Issue

An issue was identified where adding new properties to schemas caused errors, disrupting workflows. Fix ensures proper schema updates.

3. Integrations Deletion on Project Deletion

Previously, integrations connected to a project weren’t always removed when the project itself was deleted. We’ve implemented an automatic cleanup process to delete all unconnected integrations when a project is removed, ensuring that no unnecessary integrations are left behind, which contributes to better data hygiene and system organization.

4. Journey State Merging Logic

We fixed an issue related to users re-entering journeys set to a “once” frequency. Previously, re-entering a journey would sometimes merge a user’s state incorrectly, causing confusion in user tracking. This update ensures that re-entry rules are respected, providing accurate journey tracking and a consistent user experience within each journey.

5. User Attributes in Events

In some instances, user attributes like default_address were not appearing in events, such as “Product Ordered.” This fix ensures that all relevant user attributes are included in events, enabling more robust targeting and accurate user profiling for personalized communications.

6. Foreign Filters for Reports

We resolved an issue that was limiting the functionality of foreign filters in reports. With this fix, users can now apply target-specific filters across reports without issue, allowing for more granular reporting and the creation of insights that better match the organization’s targeting criteria.

7. Global Filters in Reports

Users encountered issues with global filters not functioning correctly, preventing the creation of accurate reports. We’ve resolved this bug to ensure global filters are applied properly in reports, making report creation smoother and enhancing the reliability of data insights.

8. Server-Side Personalization Segmentation Issue

There was a bug where segments wouldn’t appear in server-side personalization unless the “Segmentation” page had been accessed first. We’ve corrected this issue so that segments are now reliably available in personalization without the need to check the Segmentation page, improving efficiency and reducing the steps needed for segment configuration.

9. Email Message Creation Issue

During the implementation of the new Messages tab design, an issue arose with email message creation that could disrupt the user workflow. This fix aligns email creation with the updated design, allowing users to compose and manage emails without issues, providing a seamless experience with the new layout.