Release Summary 26.01 | Jan 08, 2026
The following key features and improvements, along with bug fixes, have been released in Algonomy CXP products in the release version 26.01.
Enterprise Dashboard
Enabled Experience Reporting APIs in Placement Profile
The Placement Profile page has been enhanced to integrate Experience reporting APIs, allowing rrPortal to directly access advanced performance data. This update enables deeper visibility into placement-level analytics, including strategy performance, merchandising rule impact, and key engagement metrics. By securely sourcing data from the Experience service, users can now analyze placement performance more comprehensively within a single interface, improving decision-making and optimization workflows.
Jira: ENG-31195, ENG-31521
Added a User Segments Tab in Test Drives
Added a new User Segments tab to the Recs and Content Test Drives to improve transparency into how user context influences recommendations and content. When a user ID is provided, the Test Drive now displays the user’s active segments, aligned with the logic used in the User Profile page.
Jira: ENG-31516
Introduced Product Impact Visibility for Rules in Recs Test Drive
Enhanced the Recs Test Drive UI to show how many products are affected by each applied rule. A new “No. of Products” column has been added to the Rules table, giving merchandisers immediate insight into the impact of restriction, boosting, manual recommendation, and advanced merchandising rules (strategy rules are shown as N/A).
The product count is clickable, opening a side panel that lists the impacted products with images, product names, and IDs, along with direct links to the Product Catalog. This improvement makes it easier to evaluate rule effectiveness and fine-tune merchandising strategies directly from the Test Drive experience.
Jira:ENG-31425
Enhanced Content Test Drive to Preview Content Using Current URL
Content Test Drive has been enhanced to support previewing personalized content based on the current URL. A new Preview URL field has been added to the Advanced section, which sends the specified URL as a custom header (x-algonomy-referrer) in the personalize API request. The field validates the input, automatically applies https when a protocol is missing, and clearly indicates when the custom header is included. This enhancement allows marketers to validate URL-triggered personalization logic before campaigns go live, improving testing accuracy and efficiency.
Jira: ENG-31424
Added Multi-Currency to the Strategy Performance Graph on Placement Profile
The Placement Profile page now supports multi-currency analysis for Strategy Performance. A new currency selector lets users view performance metrics in different currencies, with the chart updating based on the selected option. The default currency is automatically selected to match existing report behavior, enabling clearer insights for multi-currency sites.
Jira: ENG-31400
Added Strategy Performance Button on Placement Profile Page
Enhanced the Placement Profile experience by adding a Strategy Performance button alongside existing actions. This enables users to view real-time performance data for strategies and Advanced Merchandising rules in an overlay, streamlining analysis without disrupting configuration workflows.
Jira:ENG-31028
Added New Dynamic Experience for Recipes
A new Dynamic Experience has been added to display recipes using the Recipe API. Shoppers can launch the experience from a recs placement or a product page link, view a list of recipes relevant to the product context, and click to see individual recipe details including title, images, ingredients, and instructions. Each ingredient links to the corresponding product, and shoppers can navigate between recipes without leaving the overlay.
This enhancement provides an interactive, personalized recipe experience and demonstrates the capability for future template-based dynamic experiences.
Jira:ENG-30917
Social Proof – Data Engineering
Introduced Social Proof Coverage Analysis (Site-Level Rollup)
Introduced Social Proof Coverage Analysis to help teams evaluate metric coverage across an entire site and identify optimal thresholds for social proof display. This enhancement provides a snapshot view of how many products meet defined user and event count thresholds across key metrics (Views, Clicks, Add to Cart, Purchases), intervals, and categories.
The feature supports configurable metric, category, interval, and threshold selection, and delivers both graphical and tabular visualizations showing product coverage trends. This enables data-driven decisions when tuning social proof thresholds and intervals to maximize impact and consistency across placements.
Jira:ENG-26556
MVT
Improved User Experience
Improved the usability and clarity of the MVT Tests UI to make test management more intuitive. Tests are now sorted by start date in descending order by default (including expired views), making it easier to find recent experiments. Additionally, placement swap tests now include clearer guidance, explicitly indicating which placements should be selected for swapping to reduce user confusion and configuration errors.
Jira: ENG-31321
Other Feature and Technical Enhancements
The following feature enhancements and upgrades have been made in the release version 26.01.
Bug and Support Fixes
The following issues have been fixed in the release version 26.01.
| Jira # | Module/Title | Summary | General Availability |
|---|---|---|---|
|
Engineering: |
Fixed an issue where synonym rules were not applied correctly when search terms contained dashes or hyphens. In some cases, terms indexed without hyphens (for example, using spaces instead) caused searches with hyphenated queries to return no results instead of falling back to relevant synonyms or higher-level matches. The fix ensures consistent handling of hyphenated and non-hyphenated terms so that applicable synonyms are correctly matched and search results are returned as expected. |
08-Jan-26 |
|
|
Enterprise Dashbaord: |
Fixed a security bug in p13n.js where unencoded values from the rcs cookie (including the rid parameter) could lead to unintended script execution. Inputs such as cfrad, visibility, context properties, and rr_rcs are now properly encoded using encodeURIComponent, preventing code injection across supported p13n versions (v1.2, v2.0, and v2.1). |
08-Jan-26 |
|
|
Recommend: |
Resolved a 500 error on the Manual Recommendations (Strategy Rules) page caused by SQL syntax issues after upgrading to PostgreSQL 14+. The issue stemmed from missing spaces in dynamically constructed SQL queries, which are no longer tolerated by the stricter PostgreSQL parser. Queries were updated to include proper spacing, restoring correct page load and rule display. The fix was deployed to staging and verified, and additional unit test coverage is being added to prevent similar issues. |
08-Jan-26 |
|
|
Discover/Find: Fixed Zero Results in New Browse API Due to Missing Global Rank Fields
|
Fixed a bug where the new Browse API returned zero results when the expected global rank Solr field was missing for an active Discover configuration. The Browse logic was updated to safely handle cases where the global rank field is missing or not yet published by the global rank job, preventing runtime failures and ensuring results are returned even when configurations become active before ranking data is available. |
08-Jan-26 |
|
|
|
Recommend: Applied Brand, Category, and Price Filters to ecentItemStrategy |
Fixed an issue where RecentItemStrategy ignored dynamic filters such as brand, category, and price (filcat, filbrand, filprmin, filprmax) passed in the request. These filters are now correctly applied alongside existing recommendation rules, ensuring only eligible products are returned. The fix was verified, and recommendations now respect category, brand, and price constraints as expected. |
08-Jan-26 |
|
|
Find: Fixed Category Drops in Streaming Find Indexer Due to Missing Language Overrides |
Fixed an issue where streaming-find-indexer dropped category documents when category override names were missing for certain languages during indexing. The indexer now handles missing or incomplete language overrides more robustly, preventing unintended category drops across multiple languages and ensuring category data remains consistent between the streaming engine and the Find index. |
08-Jan-26 |
|
|
Enterprise Dashboard: i18n JSON Conversion Failed for Property Keys with Inconsistent Hierarchy Across Locales |
Fixed an issue in the i18n JSP custom tag where properties files with inconsistent key hierarchy depths across locales (for example, a simple text key in one language and nested singular/plural keys in another) caused a server error during JSON generation. The conversion logic has been updated to gracefully handle these cases by correctly reconciling text and object nodes, preventing JSP failures and ensuring valid JSON is generated for all supported languages. |
08-Jan-26 |
|
|
Find: Fixed Intermittent Empty Related Searches in Suggestion Component |
Resolved an issue where the related searches section in the Find recommendations API would intermittently return empty results. The root cause was the use of non–thread-safe class-level variables (stats and suggestionSections) within the suggestion component, which were being modified concurrently in multi-threaded execution. The fix replaces these shared class variables with method-local variables passed explicitly to dependent functions, ensuring thread safety and consistent related search results in API responses. |
08-Jan-26 |
|
Find: Removed Double Boosting of Lexical Results in Hybrid Search |
Fixed an issue in hybrid search where lexical results were being boosted twice due to the interaction between vector reranking and existing boost rules applied via the Solr rerank parser. A new custom rrRerank parser was introduced, based on the standard Solr rerank parser, with overridden logic to ensure boost rules are applied only once. This prevents unintended score inflation for lexical results while preserving correct reranking behavior for vector-based matches. |
08-Jan-26 |
|
|
Recommend: |
Fixed an issue where “Only Recommend” (whitelist) restriction rules were not being applied in Recs Test Drive, even when strategy and placement context conditions were correctly configured. As a result, attribute-based filters (such as enforcing specific product attributes) were not reflected in Test Drive results. The fix ensures restriction rules are now evaluated and triggered correctly in Recs Test Drive, aligning its behavior with live recommendation responses. |
08-Jan-26 |
|
|
Engineering: Provided Placement Optimization for Multi-Content Layouts |
Enhanced the optimization framework to support placements configured with multi-content layouts. Such placements are now exposed on the Campaign Optimization page, allowing configuration of optimization metrics and personalization levels. The system enforces configuration constraints by disabling fallback content for multi-content placements to prevent conflicting optimization behavior. |
08-Jan-26 |
|
|
Engineering: Scoped Action Replace/Update Events Not Published in Certain Catalog Scenarios |
Fixed an issue where legacy catalog scoped actions intermittently failed to publish replace or update events when the final item in a snapshot did not pass the existsInCatalog validation. This could result in expected catalog updates not being propagated. The fix ensures replace and update events are correctly sent in these scenarios, while preserving existing behavior—items containing only enrichment properties still do not trigger events. All existing scoped action, ingest, and streaming workflows continue to function as expected. |
08-Jan-26 |
|
|
User Profile Service: Ups Writer was Exiting Abruptly Without Pushing Data in Ups During Restart |
Fixed an issue where the UPS Writer could exit abruptly during restart without writing UserEvents to UPS. The throttler now retries failed writes. Regression tests completed for end-to-end event upload and retrieval through the Profile API. |
08-Jan-26 |
|
|
Placement Profile UI: |
Fixed several issues on the Placement Profile page, including long rule names not wrapping, inconsistent handling of multi-element Where/What conditions, missing product names due to backend issues, incorrect search placeholder text on the list page, and missing descriptions in the edit flow. |
08-Jan-26 |
|
|
Guided Selling: |
Fixed Guided Selling translation template issues that caused quiz launch failures with multi-row files and prevented variable names from appearing when translations are missing. |
08-Jan-26 |
|
|
Advanced Merchandising: Advanced Merchandising Rules Page Failed to Load for JA Users |
Fixed an issue where the Advanced Merchandising Rules page failed to load for JA users due to incorrect API routing. Rule requests were incorrectly redirected to a tooltip endpoint returning null, causing an infinite loading state. Requests are now correctly routed to the rules API, restoring normal page load behavior. |
08-Jan-26 |
|
|
Recommend: CategoryProductCP recommendations were not visible |
We have resolved an issue where the CategoryProductCP strategy (recommend items purchased by shoppers who viewed this category) was not generating or displaying recommendations for a client. The issue was caused by underlying model build and data processing problems, including stale input paths and configuration inconsistencies that prevented new data from being processed. These issues have been fixed, model builds now run successfully with the latest data, and category-based recommendations are correctly visible in the dashboard. |
08-Jan-26 |
|
|
Engage: |
We have resolved an issue where Engage API responses incorrectly identified the fallback rule (Rule ID 109) as the active rule for recommendations that were actually generated by an affinity rule (Rule ID 108). While recommendations and scoring were correct, the rule information returned in the response was inaccurate. The fix ensures that the response now correctly reflects the rule that generated each recommendation, improving validation and troubleshooting accuracy. |
08-Jan-26 |
|
|
Sales Assistant Chatbot: Fixed Chat Session Restart and Suggested Question Click Issues |
We have fixed an issue where users were frequently prompted to restart the chatbot session and experienced unresponsive clicks on suggested questions. The issue occurred due to a timing conflict that caused suggested prompts to be hidden before click actions could complete, particularly on slower devices. The chatbot now correctly handles focus state during prompt selection, ensuring clicks register reliably and the chat session flows smoothly. |
08-Jan-26 |
|
|
Sales Assistant Chatbot: Removed Suggested Questions Display After Initial Chat Query |
We have resolved an issue where suggested questions continued to appear after the initial chatbot query and were reused as follow-up prompts. Because these prompts were based on the same queries used to fetch and display products, subsequent interactions became overly restrictive and reduced recommendation relevance. Suggested questions are now removed after the initial query for both the chat template and LSI, ensuring broader and more accurate product discovery. |
08-Jan-26 |
|
|
Recommend: Fixed Missing Text in Vector Database for Rec Chatbot Issue |
Fixed an issue where some text was missing from the vector database used by the recommendations chatbot, resulting in incomplete responses. The missing content has now been added to ensure accurate and complete chatbot answers. |
08-Jan-26 |
|
|
Enterprise Dashboard: |
Fixed an issue where page titles in the portal displayed HTML-encoded characters (such as " instead of quotation marks) in the browser tab, including on the Boosting Rules page. The title rendering has been corrected to properly decode and display special characters, ensuring page titles appear correctly and consistently across the dashboard. |
08-Jan-26 |
|
|
Enterprise Dashboard: |
Fixed an issue where cloning a Multiple Contents layout incorrectly created it as a Recs layout in the portal. This occurred because the forMultiPromo flag was not included in the clone payload and the Multiple Contents option was being added multiple times during layout creation. The cloning logic has been updated to copy and send the correct forMultiPromo flag from the source layout, and the Multiple Contents option is now added only during initialization, ensuring cloned layouts retain the correct type. |
08-Jan-26 |
|
|
Engage: Fixed Content Test Drive Placement Cache Issue |
Fixed an issue in Content Test Drive where changing the selected placement continued to display results from a previously cached placement, even though the backend API returned the correct placement. The UI cache handling has been corrected so that the selected placement is refreshed properly, ensuring the displayed content and campaigns always match the current placement selection. |
08-Jan-26 |
|
|
Platform: |
Products with ambiguous names (for example, “15 Black 12/256 GB”) were sometimes incorrectly matched to the wrong model, such as being identified as iPhone 15 instead of the correct Xiaomi 15. This issue has been fixed by enhancing seed product extraction to include brand context. A new use_brand_for_seeds flag was introduced, and seed products now pass brand information using a [BRAND: X] prefix during extraction. |
08-Jan-26 |