Skip to main content

Release Summary - Apr 06, 2023

The following key features and improvements, along with bug fixes, have been released in the Algonomy products in the release version 23.09 during March 24-April 06, 2023.


Enabled Segment Creation Based on Visits not Tied to Session Id

Merchandisers can now create segments for the first-time shoppers to their eCommerce site. A visitor is considered first time shopper if they visit the site for ‘n’ number of times within ‘x’ number of days. These visits will not be correlated to external Session Id. 

Jira: ENG-25552


Experience Browser can now be Accessed Seamlessly

Experience Browser can now be accessed seamlessly through SSO Algonomy login. After the integration of SSO, some navigation issues were noticed in Omni Channel Personalization Platform, it was noticed that the Experience Browser was getting disappeared when navigated to other capabilities of the platform. The SSO pop-up was also noticed to be appearing more than once when navigated within the Platform, the issue has been fixed now.

Jira: ENG-25264

Other Feature Enhancements

The following feature enhancements and upgrades have been made during March 24-April 06, 2023.

Jira #



General Availability



Renamed the common status job UUID attribute to ‘jobId’

In UPS Attributes API response, the common status job UUID attribute ‘requestId’ has been renamed as ‘jobId’.




Implemented an alternate solution to replace the cookie-based authentication mechanism for Experience Browser

Accessing Experience Browser menu options like 'Placement Content' or 'Placement Segment' in Incognito Window causes an endless loop of SSO Login. Since the Experience Browser loads on a customer site, the cookies set by the experience server are treated as the third-party cookies by the browser. The user needs to disable or allow the third-party cookies on the browser, to be able to access the Experience Browser menu options in Incognito mode.



Enterprise Dashboard:

Enabled diversify by brand & category options in User purchase history model

With the UI enhancement, 'Diversify results by category' and 'Diversify results by brand' options are enabled for 'User purchase history' model within Configurable strategies. As a digital merchandiser, you can now create a Configurable strategy using user's purchase history and diversify the results by brand or category, so that you can recommend a diverse set of products based on the user's purchase history.



Enterprise Dashboard:

Modified maximum days under ‘Do not Recommend’ rule to restrict categories already purchased

The maxim number of purchased days under ‘Filter products already purchased’, has been modified from 90 days to 365 days. As an optimization manager, you can now restrict the categories already purchased in the past 365 days, for your Recommendation restriction rule.



Enterprise Dashboard:

Updated UI to enable ‘User Attribute’ in Merchandising Rules

Merchandising Rules UI has been updated to enable ‘User Attribute’ to boost the products if the attributes match.



Data Engineering:

Enabled Search Performance Metrics in Find Report

Search Performance Metrics have been enabled for Find report to understand the search performance through key metrics and optimize the search.




Enabled geo search language service support

A new Default Config set is added for the new indexingType as place and tested find-py-scripts to ensure compatibility with the new snapshot type.




Boost products with attributes that match User attributes

Attributes of users show their preferences which boost the products if the attributes match.


Bug and Support Fixes

The following issues have been fixed during March 24-April 06, 2023.




General Availability




Browser cache needed to be cleared before launching Experience Browser

After logging in, the page blocks the pop-up of Experience Browser when pop-up was allowed an error was shown.

The browser cache needs to be cleared before launching the Experience Browser.

The issue has been fixed now




Error while processing compressed payload in UPS Attributes API

A client was getting an error while processing compressed payloads in UPS Attributes API. The HTTP Content-Length header check has been removed in the Attributes API so that the compressed payloads can be processed without any errors and return the response in the following format:


    "version": 1660737487665,

    "jobId": "dbadea10-1e23-11ed-8080-808080808080",

    "message": "Accepted"





Site command access issue in BuildFTP server

While executing Site upload commands in BuildFTP server, the user is receiving the following error message "Request is in queue. File processing will begin shortly." This issue has been fixed now.





Getting 500 error in Find search term request

A client was getting 500 error in Find search term request. It looks like the Solr query was being timed out as there was no result found for the entered query, so the spellcheck came into action. Spellcheck is using all spell fields to get spell corrections and the data in the spell field was too large that's why the spellcheck component took more than solr socket timeout and hence, the search service gave timeout exception error. This issue has been fixed now. In the response, the search term will be truncated if it exceeds the max token length and spellcheck param will be passed as false to solr.



Data Engineering:

Scheduled MVT Job is not triggering

An MVT job in DBeaver was not being triggered on the scheduled time. However, the user was able to run the job manually. This issue has been fixed now by changing the schedule time.



Low Code Integration:

User ID not being set properly

The client was facing issue when using the low code integration. The userId parameter was being sent the same as the sessionId. Apparently, the function that initializes the R3_COMMON variable was sending the same value for both the parameters. This issue has been fixed now.



Enterprise Dashboard:

Unable to access second page in Campaign List

A client was unable to access the second page in ‘Campaign List’. This issue has been fixed.



Enterprise Dashboard:

Omnichannel Personalization portal’s default page navigating to ‘Service Unavailable 503’

During the ThoughtSpot maintenance activity, Omnichannel Personalization portal’s default page was navigating to ‘Service Unavailable 503’. This issue has been fixed.




Brand strategies are not using the new Top Seller model

Brand strategies are not using the new Top Seller model. Hence current Brand strategies (including new arrivals and oversandshakers) are converted to use the new Top Seller model.



Engage and Enterprise Dashboard:

Expired content is showing in the dashboard even after unchecking the ‘Show Expired’ checkbox.

A client was facing an issue with the Omnichannel Personalization dashboard where the expired content is showing even after unchecking the ‘Show Expired’ checkbox. This issue has been fixed.



  • Was this article helpful?