• Backend API | We have implemented the new category lookup endpoint, enabling you to implement a category select form component.
• Backend API | We've introduced the ability to manage blacklisted suggestions via the Backend API. Additionally, we've implemented a new endpoint for retrieving a category path by ID.
• Backend API | Support was added for the new itemViewEvents Google Analytics 4 metric, making it available in the GA4 metrics response. The validation of the fullPageUrl dimension on screenPageViews was removed.

JavaScript

• Tweakwise JS | Fixed a minor bug where the Recommendations JS would show an error in the developer console if the configured recommendation didn't return any products. Functionally nothing has changed.
• Tweakwise JS | We've fixed some German translations where some words needed to be capitalized.
• Tweakwise JS | Improved the UX of our Search & Merchandising solution by showing the loading state only if the request takes longer than 400ms. Which makes for a much smoother experience when filtering, sorting and/or paginating!
• Tweakwise JS | Fixed a bug where the pre-selected filters would disappear when using the browser's back button.
• Tweakwise JS | Added HTML title with a color value to Search & Merchandising color swatches for having useful tooltips on hover.
• Tweakwise JS | A new configuration option was added to Search & Merchandising JS that allows you to configure a minimum amount of characters before instant-search is triggered. This option is configurable by setting inputThreshold: 3. If omitted, instant-search is triggered after 1 character.
• Tweakwise JS | No result page now also has a function for adding customHtml, the function call is provided with some data of the result so you can use the searchTerm in the custom HTML.

Tweakwise App

• Tweakwise App | Fixed breadcrumb links that previously used an invalid double language prefix; fixed external links in navigation menu.
• Tweakwise App | Added missing translations from Tweakwise App > Dashboard.
• Tweakwise App | Added some validation for adding and editing synonyms. For the algorithm to be effective, a maximum of three words per synonym term is enforced.
• Tweakwise App | Added some additional hints and validation to the synonyms module to avoid breaking when adding a single synonym when two are required.
• Tweakwise App | Differentiated on two levels of severity for poor performance of external data components in the new Builder (so you can see either orange or red warning; based on avg. response time threshold).
• Tweakwise App | We fixed some issues with error pages and persisting the selected language. Before, in some scenario's you selected for example Dutch and the app switched back to English somehow.
• Tweakwise App | Slightly little changes are made to the UX of the menu, it's mainly the behavior of linking between pages and the current selected page.
• Tweakwise App | Builder tiles are now resizeable! On the right-hand side of the tile an indicator will pop up to drag the tile to the preferred width.
• Tweakwise App | There were cases where you could have duplicate categories for an item in the import feed. In some of these cases this caused a database error in the import task. We have improved the feed import task to spot these duplicate categories and give a warning, the feed import itself will succeed.
• Tweakwise App | The items detail page now contains links and tooltip on the Image and Url characteristics when it is assigned to an attribute.
• Tweakwise App | The UX of the Builder is updated a bit. The page size is more regulated, like: the minimum page size is 12 by default, but it also is depending on the configuration. So if the size is configured to be 24 and a component is configured on position 20, the size can't be smaller than 20. By changing this it is not possible to lose configured components. Also, the resize behavior is changed a bit, where the width now remains stable when changing the grid width. Before it was a bit unpredictable.

Demoshop

• Demoshop | Unified the look of all slider facets & added prefix/suffix to selected filter labels.
• Demoshop | Added product variants to Item detail context (even variants themselves will refer to all other items from the same group).
• Demoshop | Added category link after the actual link (same as we did in suggestions before).
• Demoshop | In the JavaScript specific Demoshop we no longer show implementation code but will redirect users to the documentation instead by clicking on the floating button at the end of the page.
• Demoshop | Price slider has changed so it can manage floating points instead of rounded values.
• Demoshop | Grouped products is added to the suggestions component.
• Demoshop | The presentation of item types that are not familiar (eg. products, visuals) are visually changed so it is better recognizable as a different type.

Plugin Studio

• Plugin Studio | The No Result page is now configurable in the Plugin Studio.
• Plugin Studio | Made sure all elements (even without a value) are easily selectable in the Product Tile Editor in Plugin Studio. Previously a no value TextElement would not render anything, making it hard to see.
• Plugin Studio | Fixed a bug where the Plugin Studio module retained stale data on its index page while navigating through the module.
• Plugin Studio | We made it simpler to redirect to the Javascript Demoshop from within the Plugin Studio with suggestions enabled (as long as the module itself is toggled on in the Plugin Studio module overview).
• Plugin Studio | We added an option to configure category links for Search & Merchandising in the Plugin Studio settings page (Merchandising > General > Allow redirects on category facet).
• Plugin Studio | Fixed a bug for the Product Tile Editor tiles that contain a link in the root frame in combination with fixed input elements controls to be affected by a parent frame with a link.
• Plugin Studio | The inputThreshold configuration has been added to the Plugin Studio configuration.

SW-Tweakwise 4.0.0 | Before, the Product ID for Tweakwise contained several pieces of information to identify the product. We changed the ID and removed unnecessary information. It is now usable for add-to-cart and add-to-favorite without the need to specify a specific attribute. You have to generate a new feed as soon as you have updated the plugin. The out-of-the-box add-to-cart and add-to-favorite will only work after an updated feed. If you have implemented your own handlers for add-to-cart and add-to-favorite, you definitely need to check if everything works as expected.

SW-Tweakwise 4.0.0 | In Shopware you have the option to set the visibility of a product show up in category listings and/or search within a sales channel. With this update, we will add a visibility attribute to the Tweakwise feed and filter on this attribute (behind the scenes) in category listings and search. On cross-sells and featured products, the products will be shown just like this is done in Shopware.

SW-Tweakwise 4.0.0 | If for some reason, no SEO Url is available for a product or a category, we will now add a fallback URL to the feed. This is a feed containing the ID of the product or category but will at least show the right information. Having proper SEO Url's is still the responsibility of Shopware and can be a matter of just updating the indexes of Shopware.

🚧

This update is a combination of multiple releases contains several breaking changes. Please test this update in a non-production environment before using on production.

• [4.0.0] - 13-03-2025
• [3.5.5] - 10-03-2025
• [3.5.4] - 06-03-2025
• [3.5.3] - 18-02-2025
• [3.5.2] - 14-02-2025
• [3.5.1] - 13-02-2025
• [3.5.0] - 12-02-2025
• [3.4.0] - 11-02-2025
• [3.3.1] - 06-02-2025
• [3.3.0] - 05-02-2025
• [3.2.0] - 28-01-2025

Click this link to visit corresponding repository and update on Github

• SW-Tweakwise 3.5.5 | The event [twn.add-to-favorites](https://docs.tweakwise.com/reference/add-to-favorites-wishlist) is now handled out of the box and working with the default Shopware wishlist feature.
• SW-Tweakwise 3.5.4 | It is now possible to add a Shopping Experience CMS element on the product detail page, enabling you to easily add cross-sell recommendations to all products. You simply set the group key of the cross-sell you want to show.
• SW-Tweakwise 3.5.4 | The URL’s of categories are now added to the feed by default. Besides that, the categories handler in suggestions is removed so it will be using the default features of Tweakwise.
• SW-Tweakwise 3.5.4 | For all products the attribute [item_type](https://docs.tweakwise.com/docs/item-types) with value product is added to prepare for other item types.
• SW-Tweakwise 3.5.4 | Some bugfixes are added to support older releases of Shopware 6.5.
• SW-Tweakwise 3.5.3 | Added right locale to the twig rendering context so translations will be handled correctly.
• SW-Tweakwise 3.5.2 | If you have expanded config in your variant listing config and it is not active, it will now not have a look at those settings anymore.
• SW-Tweakwise 3.5.1 | Fixed resetting the instant search when choosing suggestions in Tweakwise App > Plugin Studio; also made a fix regarding wrong languages once using Plugin Studio.
• SW-Tweakwise 3.5.1 | Fixed search page showing instant search and merchandise
• SW-Tweakwise 3.5.0 | An option Plugin studio integration is now available in the Frontend configuration of the plugin. Please check with your customer success manager if this setting is needed for your installation.
• SW-Tweakwise 3.5.0 | Refactored hashing of products to make them unique in Tweakwise. This refactoring made it sure that the same code is used in feed as well as cross-selling. Also renamed some field to match the naming within Tweakwise.
• SW-Tweakwise 3.4.0 | We now made sure the 3.x version of the Tweakwise for Shopware plugin, is now working with Shopware 6.5 as well. Please be aware updating from version 2.x to 3.x is a major update with breaking changes.
• SW-Tweakwise 3.4.0 | In Shopware 6.6 instances it is now possible to add the Featured Product CMS element again.
• SW-Tweakwise 3.4.0 | Use proper Product Id for recommendations and cross-selling when no variants are used.
• SW-Tweakwise 3.3.1 | Some twig block definitions are added to the feed template.
• SW-Tweakwise 3.3.0 | Added the option to be able to add logic to the data of variants which is added to the feed.
• SW-Tweakwise 3.2.0 | If no specific variant is selected for inclusion in the feed, all variants' options, attributes, and stock levels are now included by default.

As category-linking is one of the hardest things to overcome while setting up your JavaScript-implementation, it would be very useful to have predefined category URL's available to link to category pages without writing extra code. Instead of translating category IDs to URL's on the application side of your store, this functionality now works out of the box. By simply adding category-URL's to your import feed, we do serve these URL's in the response of our Frontend API too, so you can pick them up there.

If you make use of our JS-solutions, we have done it for you already. You just have to enable the functionality in Plugin Studio. If a category has it's own URL it will show up in Category suggestions even if the category suggestion handler function has not been defined and click on this suggestion will redirect to said URL. Once a handler has been set up it takes precedence over custom URLs.

No results page for JavaScript

We added a component and some styling to the 'No Result page' of our JavaScript Search & Merchandising solution. Previously it looked like a failure page, but with this feature enabled it looks a bit more helpful. It is fully configurable and customizable in the sense that you're able to add some custom HTML. This gives opportunities for showing Recommendations on the 'No Result page'. The feature is turned off by default and can be activated by adding some code or preferably by switching the toggle in Plugin Studio.

Other improvements

• Backend API | We updated the category lookup endpoint to include category key in the response.
• Backend API | Multiple endpoints for retrieving usages now have a uniform input and response schema.
• Tweakwise App | Fixed an issue where attribute names were not being trimmed during item creation.
• Tweakwise App | The instance environment widget is extended with a friendly warning for non-production instances. This is to emphasize the usage of non-production instances on a production shop.
• Tweakwise App | The UX of the navigation bar is improved a bit. Some slight changes are done on the UX like the active/current menu item that stays active or the behavior of the collapses. The Support menu is moved to the bottom of the page. We removed phased-out module links from the menu (Dynamic search and Menu & Bannering).
• Tweakwise App | As the identifier of recommendations sometimes is needed for implementing our software, we have made the id property visible in the Featured products and Upselling & cross-selling modules in Tweakwise App. It is now displayed in the list and the detail view. This makes it easier 'to use' in API requests and JS.
• Plugin Studio | Added the possibility to duplicate product tiles which were create via the editor (via context menu in the list or in the modal while creating a new component).
• Plugin Studio | The configuration options for the starter in the plugin studio are aligned with the latest options. We removed some fields that are only available for users that are using the JS. We added the parameter field for External Data Components.
• JS Implementations | We've added a reference to the HTML element to the following events in all JS integrations: twn.add-to-cart, twn.add-to-favorites, twn.product.visible and twn.product.click.
• JS Implementations | Some small parts of the JS implementation are refactored regarding the Product Tiles
• JS Implementations | Issue with the Top Filter Dropdown position has been resolved. It now makes sure it is always within the viewport! It is now also possible to show selected filters in combination with filters in top position via a new configuration option filters.selectedFilters (only works if position: 'top').
• JS Implementations | When doing your own initialization of the JS plugin via tweakwiseListerPage() the page is now fetched based on the filters set in the URL.
• Suggestions JS | Suggestions had an issue with the Gateway-failover. Although suggestions were fetched, products were not. This has been resolved.
• Suggestions JS | A new experimental feature was made available for suggestions.js, allowing shops to enable typing animation in the input element that's been set up with Tweakwise Suggestions. It comes with a bunch configuration settings.

It's finally here: flexible sized grid items! As engagement with your customers is crucial and becoming a key indicator on how well you perform, a default grid layout where all of your item-tiles are same in size does not help you. So our Builder now has been completely rebuilt and expanded with new functionality. Most important one? The option to determine width-spans (height-spans will follow later) of all of your components, making full-width promotion banners or USP-bars finally possible!

For experienced users, some important things have changed. Your list of components is completely removed from the left side of the builder. However, you will see all available components and simply select one, once you click on an empty or free spot in your builder. You can also change the grid with of the builder, giving you an instant visual representation of how your configuration will look like in a different (viewport) setup. Unfortunately, at the moment it is not possible to make a different setup for desktop and mobile viewports in one builder template.

📘

New Builder: Experimental

The Builder has been completely rebuilt and is available for everyone. If you want to use and experiment with it, click on your avatar in Tweakwise App and make sure the feature 'New builder' is toggled on. If you don't see the toggle in your instance, please reach out to your Customer Success Manager or Tweakwise Support.

Width-span settings

In order to have a component span multiple columns of the grid, you now have the possibility to configure the width of the entire component, no matter if it's a product or non-product component. You can simply set the amount of tiles your component should use and will instantly see how this will reflect your layout. If you configure a component to be larger than the total width of the row, it will take up the full row as it maximum size.

If there is no space for your component (for example if a spot is already claimed by another component), we will position your component on the first available spot. All empty spots will be filled up by, so there is always a full row with items available. This could lead to some reshuffling of the order of your components, but keeping your layout setup in place. In the example below, you see the full-width configured component marked with position 2 does not fit on that particular spot (because of its width settings) and therefore moves to the first available spot. The available space (initial spots 2, 3 and 4) are now filled in by the configured components 3 and 4.

Implementation

If you make use of our JavaScript implementation, all functionality is covered out of the box. For API-implementations, you do have to make changes to your frontend code yourself as our Frontend API now just support hints to allow the display of different width and height spans of your Builder components. A full implementation guide on this can be found in this article.

A solution has been implemented to link Attribute Landing Pages (ALPs) across different storefronts in Magento. With this multistore setup you should be able to ensure accurate SEO handling by linking ALPs across storefronts, allowing hreflang tags to be added.

Previously, each unique combination of category and filters generated a separate ALP ID per storefront, preventing the use of hreflang tags for SEO optimization. The fix in Magento2AttributeLanding 6.0 (breaking) establishes a connection between ALPs with the same parent category and filter combination across multiple storefronts. This could lead to the correct identification of duplicate ALPs on different domains (e.g., NL, DE, FR) and enables the proper implementation of hreflang tags (something you have to fix in the frontend yourself). This is essential for businesses with multiple regional storefronts, improving search engine indexing and avoiding duplicate content issues.

📘

Breaking change

Important: This update to Magento2AttributeLanding 6.0 changes the way how Attribute Landing Pages (ALPs) are saved in your Magento configuration. If you have custom code for ALPs, this update might require adjustments. If not, you can install it without issues.

• Magento2AttributeLanding 6.0 | This update changes how Attribute Landing Pages (ALPs) are saved. This ensures ALPs for the same page in different store views are properly linked.
• Magento2Tweakwise 8.4.2 | Fixed an issue where no products would appear if Tweakwise returned an empty result.
• Magento2Tweakwise 8.4.2 | Fixed a bug where category views in search results didn't match the demo shop.
• Magento2Tweakwise 8.4.2 | Resolved a compilation error for certain Magento/PHP versions.
• Magento2Tweakwise 8.4.2 | Now displaying visuals even when the merchandising builder, Varnish, and AJAX filtering are turned off.
• Magento2Tweakwise 8.4.2 | Fixed an issue where filtered URLs didn’t correctly redirect to the new category URL.
• Magento2TweakwiseExport 7.3.1 | Added product as an item type in the export process.
• Magento2TweakwiseExport 7.3.1 | Fixed an issue where child products were not correctly linked to the exported store.
• Magento2TweakwiseHyva 4.3.2 | Now displaying visuals even when the merchandising builder, Varnish, and AJAX filtering are turned off.
• Magento2TweakwiseHyva 4.3.2 | Fixed a JavaScript error.

Importing and exporting lists of synonyms has been made publicly available. Within Tweakwise App you can generate a csv-file with a full overview of all your synonyms, giving you the opportunity to expand your phrases in for example Excel (or another tool). Importing will update and insert modified and newly created synonyms. For deletion of synonyms you need to use Tweakwise App, but that also has been made simpler than ever before. With a bulk option, deletion of many synonyms at once is as simple as some quick mouse clicks.

Grouped products in Demoshop

In your Tweakwise Demoshop we've added a new option in the settings/preferences menu to enable grouped products! If enabled, a grouped navigation call will refresh the lister page and potential grouped products will be displayed on the product tile. The shown variants will open a modal onclick with representative data, while clicking on the main product (or first variant) will show the group in total. The screenshot below shows the grouped products highlighted, compared to the default way of showing products in the greyed out part.

Other improvements

• Frontend API | In Tweakwise App a merchandising rule can be configured to be sorted in either ascending or descending order and as we already respected this setting in terms of order in the response, we now also do passthrough this setting via the order-field in the corresponding API-endpoints.
• Frontend API | As part of a larger feature that will make it possible to configure items to have a different width/height using the builder, we've added colspan and rowspan information to all endpoints to which the builder can be applied.
• Backend API | Added validation in Backend API for detecting duplicate synonym terms with 'superscript characters' example: mm² and mm2 are now seen as duplicate and will return a validation error.
• Backend API | Created a new endpoint in the Backend API for category lookups.
• Backend API | Categories now can be provided with an url-attribute, both via the XML-feed as via our Backend API endpoints. Implementations could choose to use these category URL's to link to pages on an easy way, instead of translating the category ID's to an URL on the application side.
• Frontend API | Related to the new url-attributes, we've expanded some endpoints in the Frontend API with a new property called link. This will contain the category-url information as provided as on the import side and can be used to optimize your SEO. This information is added to the following endpoints: navigation, navigation-search, suggestions, facets, facets/[urlkey]/attributes.
• Tweakwise App | Fixed a bug in the App where the AI generated tag of a synonym would disappear upon changing the approved/rejected state. Now the AI generated tag remains no matter what.
• Tweakwise App | As it sometimes becomes a bit hard to configure a Google Analytics 4 report within Tweakwise, we've now made it possible to preview your report while editing.
• Tweakwise App | We've updated some of our list overviews throughout the App. At least the Insights, Attributes, Items, the new Builder (coming soon) and Google Analytics 4 modules now have a fresh and consistent look. Part of it is the possibility to bulk delete records in all of these modules; making your life much easier than before.
• Tweakwise App | When switching between different instances in Tweakwise App, the selected language is now retained and no longer resets to English as default.

Integrating Tweakwise into your platform via JavaScript solutions is the fastest way to get started. By using our JavaScript solutions you can quickly render standardized components for site navigation and search, which will always be up to date with our latest set of features. Our newest plugin for Magento stores - compatible for both Hyvä and default themes - simplifies the way of implementing Tweakwise by enabling our JavaScript solutions making use of Plugin Studio by default.

For the time being, our JavaScript plugin for Magento includes key functionalities like:

• Search Results
• Instant Search
• Suggestions (search phrases and products)
• Lister-pages (categories)
• Personalization
• Plugin Studio

Later:

• Suggestions (categories and facets)
• Grouped features
• Recommendations
• Guided Selling

With this release we re-introduce a tabular overview of all of your handled search phrase requests, upgrading our Insight module to the same scope of our previous modules in Tasks & Statistics. We have implemented the same filters in this new report, which can be found as a separate tab (Search Log) in Tweakwise App > Insights > Search Algorithm Usage. Additionally, if you hover your mouse over any value in the table, it will display a tooltip with pie charts that show the distributions of chosen search word among the categories.

• Search Algorithm Usage | We enhanced the histogram readability for the Algorithm Efficiency and No-Results tabs and added a new report/tab with Algorithm Distribution, showing a distribution of all used algorithms over the selected timespan.
• Search Algorithm Usage | Date slicers were added to the report so you can select the datetime-range for which the data should be printed. According to this same setting, the KPI-cards will show the right data.
• Search Algorithm Usage | Searchbars were added to the histograms of the Algorithm Efficiency report and the No-Results report. Also the description of some tooltips were changed to have a more relevant meaning.
• Filtering Usage | We enhanced the histogram readability and date slicers were added to the report. We also changed the percentages in the histogram to be relative to the selection of the category, filter and filter value.
• Usage | We fixed a small bug on the chart-selector in the daily API statistics.
• Task Usage | Fixed a date selection bug causing to not automatically selecting the latest day with data.

Overall improvements

• Backend API | In order to be prepared for flexible width and height configuration on Builder-components, we have extended the Backend API Builder endpoints to support ColSpan and RowSpan settings. These settings can now be configured via the API (only positive numbers are allowed).
• Frontend API | The feed-endpoint seemed to be broken in the Delivery API, which now has been fixed.
• Tweakwise App | The category match did not always took excluded categories into account, in resulting in not expected behavior of the search results.
• Tweakwise App | In the new Synonyms module there is now the option to change the type. For example changing from a regular synonym to an one way synonym. This functionality was not yet supported in our Backend API, resulting in broken functionality in the App. We also added validation for synonyms so that two duplicate synonyms can't be added.
• Tweakwise App | Fixed a bug where AI synonym suggestions didn't show up on Synonyms create/detail page.
• Tweakwise App | Support for multivalue attributes in the Product Tile Editor (Plugin Studio) was added.
• Tweakwise App | Fixed a bug where clicking external attributes card on the dashboard would lead to 404 page.
• Demoshop | While browsing on your Demoshop homepage, the settings/preferences overlay has been disabled.

JS Implementations

• Search & Merchandising | Product tiles that were build by the Plugin Studio now handle product attributes with multiple values (e.g. if a property returns array of strings instead of just a single value there will be an element for each of those values). This only applies for the TextElement.
• Search & Merchandising | A new configurable option edcParameters was added, allowing you to set values to variables as setup in External Data Components in the builder.
• Search & Merchandising | Non-product-tiles (like: visuals) are not clickable anymore when no link is provided, but will be shown as just static images.
• Search & Merchandising | On each Product Tile click a clickItem event is triggered via the Personalization Pixel if personalization is enabled for the instance.
• JS Suggestions | When searching and getting no results for your query, we no longer show an empty container, instead it is completely hidden. It can be however shown when combined with one of two new configuration values.
  • noResults - Indicator to show a message when no suggestion results are found.
  • resultsButton - Indicator to show a link to all search results for the current searchterm.

Just like a configuration setting for overriding Tweakwise filter templates and sorting (merchandising) templates, now it is also possible to connect your desired Tweakwise builder template for Attribute Landing Pages. This function might become useful in case you want to AB-test multiple templates against each other, or if you want to run a specific template based on (a combination of) specific filter-values (for example brand=[brandname]). For every landing page configured via Content > Attribute landing pages > Manage pages, the builder template setting will become available in case you have setup (and published) builders within Tweakwise App.

🚧

Dependencies

In order to run this feature, you need to upgrade the following modules to their latest versions:

• Magento2Tweakwise
• Magento2AttributeLanding
• Magento2AttributeLandingTweakwise

• Magento2Tweakwise 8.4.0 | Added support for selecting builder templates on Attribute Landing Pages.
• Magento2Tweakwise 8.4.0 | Resolved an issue where using $ as a filter name caused errors.
• Magento2AttributeLanding 5.1.1 | Added support for selecting builder templates on Attribute Landing Pages.
• Magento2AttributeLandingTweakwise 4.4.0 | Added support for selecting builder templates on Attribute Landing Pages.
• Magento2TweakwiseHyva 4.3.1 | An issue where the navigation/filterbar was not appearing in search results has been fixed.

We proudly present our refreshed synonyms module in Tweakwise App, offering both new functionality as a complete fresh look. Fully operated via our Backend API, our synonyms module now offers all features you need while managing your one-way and two-way synonyms. Biggest change in this fresh update is the smooth integration of Autopilot for synonyms, where you configure how Tweakwise AI to behave. Do you want to approve automatic created synonyms by default, or do you want to check them manually first? Also, on what threshold (how many search results in the past 7 days) should the AI trigger?

Some key functionalities:

• Bulk actions (like deletions)
• Importing and exporting (coming soon)
• Extended auto-synonyms configuration
• Approval and decline options for AI synonyms
• Easy navigation (search, filters)

This refreshed module can be seen as Tweakwise's new way of presenting information and will set the standard for other modules too. As we focus on implementing new features and functionality, we continuously try to improve UI and UX over time, making life more easy and your workload more efficient.

📘

Experimental feature

In order to start using our new Synonyms module, you can enabling it at your user preferences in Tweakwise App by clicking on your avatar and switching on the 'New synonyms' toggle.

Other improvements

• Tweakwise App | Returning from an attribute detail or creation page in any way (go back button, save and go back, etc.) will now work correctly.
• Tweakwise App | We improved the performance of opening a weighted merchandising rule. However, the saving performance is unchanged at the moment, as we need some time for validation. We did update the wait message to include this information.
• Tweakwise App | The Insights module got a small revisit, now featuring the classic data table you can see in other new modules (items, attributes,..) with pagination instead of showing a block with featured reports.
• Tweakwise App | The Task Report in Tweakwise App > Insights has been updated to show data with less delay and should show all the tasks with a maximum delay of around 10 minutes. Before this update, the data was refreshed every two hours during the day and thus resulting in long waits before tasks were showing up. We have added an explainer that tasks executed less than 10 minutes are possibly not shown yet.
• Tweakwise App | Fixed a problem where some links to the items module didn't work, for example when clicking on an item in the categories module you'd end up on a 'Not found' page.
• Tweakwise App | We have updated the instance information in the header of the Tweakwise App. In order to accommodate a label denoting the current instance's environment, we replaced the big button with a fresh looking link. You can see the environments of all your instances in the instance switcher (side-panel), by clicking on your instance name.
• Demoshop | We included the instance’s environment label also to the Demoshop; it's visible next to the instance name.
• Event Tag | The event itemClick has now been added in the Event Tag (previously known as tracking pixel), meaning you can log these events when itemId, requestId and a profileKey is provided.
• Backend API | We implemented a new endpoint /attribute/{id}/distinct that returns distinct attribute values. This is for example needed when selecting a brand in a dropdown, so those don't all show up multiple times because there are multiple products with the same value.
• Backend API | We extended the Backend API endpoints for categories with MerchandisingTemplateId. To better differentiate between the different templates, we also renamed existing parameter TemplateId to FilterTemplateId. This rename is a breaking change, however this was added just a couple of weeks ago and not yet in use by any. Along with MerchandisingTemplateId, we introduced MerchandisingBuilderId.

Javascript

• Search & Merchandising JS | It is now possible to configure used builder templates via the package configuration by setting builderTemplateId effectively overriding assigned builder.
• Recommendations JS | It was possible that related recommendation carousels showed duplicate products (as there are multiple queries) - this has now been fixed and potential duplicates are removed.
• Plugin Studio | If a JS deployment fails you will now get an error notification that it didn’t go through (previously it would just say all went good). Unfortunately as of now we cannot state the exact reason in the notification. Sometimes you’d also got two notifications instead of one after a deployment; this has now been fixed.