December 24,2024

We’ve officially launched the Recommendations Project, a major upgrade that brings smarter product discovery into GrowthOS. This release sets the foundation for using journeys and personalization to drive actual revenue—not just engagement.

At the core is a new system for managing product feeds—dynamic collections powered by preset algorithms like “best sellers,” combined with custom filters like category, tags, or availability. These feeds can be used across web, email, or API to deliver relevant product recommendations at scale.

Under the hood, this includes new infrastructure for catalogs, feeds, and an updated Product Block in the Visual Editor—built to display personalized or trend-based items in real time. Whether you’re building a tailored email campaign or a dynamic site experience, you can now plug in feeds directly into your creatives and let the system do the heavy lifting.

This unlocks a key layer of GrowthOS: moving beyond attribute personalization to context-aware, behavior-informed product suggestions—right where your users are looking.

Catalogs

We’ve introduced Catalogs — a new way to view and manage your product data inside GrowthOS. Once your product feed is ingested (from your store or backend), Catalogs give you a central hub to organize, update, and validate every item.

This matters because personalized experiences are only as good as the data behind them. Catalogs ensure your product information is clean, consistent, and ready to power everything—from dynamic product blocks to automated recommendations in journeys and emails. It’s the foundation for delivering personalization that actually reflects what you sell, in real time.

Feeds

Added support for Product Feeds—dynamic collections built from your product catalog using custom rules you define in GrowthOS. You can filter products based on attributes like category, price range, stock availability, or even customer behavior signals.

This gives you full control over what gets shown to whom. Whether you’re building a “high-margin picks” feed for premium users or a “back-in-stock” set for returning visitors, feeds make personalization smarter and more targeted. The result: higher engagement, better conversion, and less manual work.

Product Block in Visual Editor

A product block is a type of block that can be used in personalizations. When added to a website, it allows you to select a specific product feed or manually choose products to display.

The product block provides a seamless way to integrate product recommendations into websites and other customer touchpoints. By leveraging feeds or manually curated selections, businesses can deliver highly relevant and visually appealing product suggestions, driving engagement and sales.

Hubspot Bi-Directional (backend)

Our new HubSpot Bi-Directional Integration ensures your CRM data stays fully in sync between HubSpot and GrowthOS. You can configure both one-way and two-way syncing with flexible field mappings and filters—so your customer data stays clean, unified, and always up to date.

This integration eliminates silos across marketing, sales, and product teams by creating a shared source of truth. Whether you're syncing lifecycle stages, lead scores, or custom fields, the data flows both ways—powering real-time personalization, reporting, and automation without messy exports or manual updates.

If you're running campaigns out of GrowthOS and managing contacts in HubSpot, this update just made your job way easier.

🛠 Improvements & Fixes 🛠

1. Java 21 Migration Completed

The migration from Java 11 to Java 21 is now complete. This ensures that all platform services are updated to leverage the latest advancements in performance, security, and language features introduced in Java 21.

The Java 11 to Java 21 migration project is important for several reasons. First of all, it ensures that the platform keeps up with the latest technological advances, benefiting from the increased performance, improved security, and new language features introduced in Java 21. Using an outdated version of Java can lead to technical debt, increased maintenance costs and potential vulnerabilities.
This project aimed to migrate all platform services to a modern and actively supported version of Java 21. This upgrade not only improves the overall stability and reliability of the platform, but also lays the foundation for more efficient implementation of future upgrades. By migrating to the latest version of Java LTS (Long-Term Support), the platform better meets the growing demands of users and stakeholders, ensuring long-term sustainability and competitiveness in the market.

2. Fixed stripe historical data sync

The issue with Stripe historical data sync, which was failing due to an improper serialization/deserialization mechanism, has been resolved. This fix ensures that all historical transaction data from Stripe is accurately imported and synchronized with the platform, providing users with a complete and reliable dataset. By addressing this problem, businesses can now seamlessly analyze past transaction trends and derive actionable insights without data discrepancies or gaps.

3. Console hyperlinks in an e-mail text editor

The issue where console hyperlinks in the email text editor redirected to an invalid URL has been resolved. This fix ensures that all hyperlinks within the editor now correctly redirect to their intended destinations, improving the workflow and usability for users. With this update, users can confidently embed and test links within email campaigns without disruptions or errors.

4. Fixed Variable Option in Visual Editor

The issue where the variable option in the Visual Editor was not functioning correctly has been resolved. This fix ensures that users can now seamlessly insert and customize dynamic variables within their content, enhancing the personalization and flexibility of their campaigns. With this update, users can create tailored experiences with greater ease and efficiency.

5. Fixed Link Formatting in Console

The issue with console links containing an unnecessary trailing "/" at the end has been resolved. All links have been updated to remove the trailing slash, ensuring they correctly follow the expected URL structure.