Skip to content

Changelog: May 2024

API

Added

  • Added PopularityMultiplier property to the PopularProductsRequest recommendation, which can be used to influence the weighing of views or purchases on the product level. This enables the use case where you want the purchase or view of certain products to weigh more or less in recommendation ordering.
  • Added new DataValueHasKeyFilter for all entities, to allow querying for entities with or without a specific data key.
  • Added new HasValueCondition, which can be used to identify if a given Data Key has a Value. Empty collections will be considered as not having a value.
  • Added new filter EntityDisabledFilter, which allows you to filter on whether a given entity is Disabled. This will, for example, make it easier to identify and delete all disabled products on your Relewise dataset.
  • Added the Descendants selection strategy to the CategoryHierachyFacet. This allows you to return entities from a certain category path, and any potential child category of that path.
  • Added the ability to use tracked, anonymous purchases when recommending popular products by purchases, and when sorting search results by popularity.
  • B2B Feature: Added new Popularity type LineRevenue for the PopularProductsRequest. This enables the scenario where you want a recommendation of the products that have generated the largest revenue in some specific currency within a certain range of time.

Changed

  • ProductQuery received new properties, PageSize and NextPageToken, to allow cursor-alike behavior. Should page results span across multiple pages, ProductDetailsCollectionResponse will contain a NextPageToken to supply should further results are to be consumed by client. Properties NumberOfResults and SkipNumberOfResults are marked as obsolete.

My Relewise

Added

  • Merchandising: Added a field that shows how many products are being targeted by the merchandising rule when applying a filter.

Changed

  • Changed the label shown for key inclusion/exclusion in filter merchandising rules to "Include If Key Is Not Found".
  • Search Index: Changed the name of the ISO-639 field to ISO-Alias, and added a tooltip with an example value.

Fixed

  • Fixed a bug where modals would close unexpectedly when a vertical scrollbar was selected.
  • Fixed a bug where some filter options would sometimes not be visible in Search Analytics.

Integration

Added

  • JS SDK: Added support for allowing null to be parsed to selected property functions. This ensures that you only get the id back when requesting entities, and allows you to reset the properties to request.
  • Web Components: Added support for setting the variant property settings, to define what variant attributes you want to be returned.

Fixed

  • Demo Shop: Fixed a bug where a price filter would wrongfully be added to the next search when encountering a zero hit search.

Documentation

Added

  • .NET Examples: Added @relewise/client package as a requirement due to DataValueFactory being used in examples.
  • Added a glossary entry for Product Listing Page (PLP). Available here.
  • Added documentation detailing the use of Promoted Variants (also known as Default Variants), which allows you to specify a particular variant of a product to be shown in Relewise searches and on the PLP. Available here.
  • Added documentation for Email Recommendations, which is a way of adding personalized Relewise recommendations to your marketing emails. Available here.
  • Added documentation for the Shopify App, which allows you to integrate your Shopify Shop directly with Relewise. Manage product integration, personalized search, and powerful recommendations directly from the Shopify interface with the Relewise App for Shopify. Available here.

Don't know us? Don't worry - you can find more information about us, by visiting our main page www.relewise.com