• Frontend API | We've added additional info in the response of the Guided Selling endpoints in our Frontend API. This info can be used to customize the UX for specific questions and answers. Specifically for questions attributeid, name and urlkey is now available, while we added the actual attribute values for answers.
• Backend API | We added DataType property to 'Get Attributes' and 'Get Attribute' endpoints of our Backend API. Also it's possible to filter out result by DataType in 'Get Attributes' endpoint. Possible values: text or number.
• Demoshop | We fixed a bug that caused no weighted sorting debug information to be shown on pages other than the first page of the Demoshop.
• Tweakwise App | The use of the Full Text Rank in Word Search algorithms has been re-introduced as an optional. setting. Previously, when weighted sorting was enabled, the relevancy score provided by full text search was always used, as if this checkbox was always checked. Now it’s possible to disable this feature again. Once disabled, all products found by the word search algorithm will get a raw score of 1, instead of it being determined by the relevancy score provided by full text search.
• Tweakwise App | The category match Search Algorithm now considers in which language the user is searching. This is applicable when the 'Use conjugations' and 'Use synonyms' feature is turned on. Before, there was a bug in the category match algorithm where the same category could be found multiple times, and therefore wouldn’t be applied. This happened because the category had the same conjugations or synonyms in multiple languages. Now, by filtering on the language for which the conjugations and synonyms were created, we only find a single category.
• Tweakwise App | When weighted sorting is enabled, the 'Use configured Builder, Sorting and Filter settings of the matching category' feature wouldn’t work. When a category was found, those templates did not get applied. From now on, we always apply the templates of the first category match algorithm with a result. That means if you’re using two category match algorithms, for example one before and one after auto correct. We’ll use the templates from the algorithm before auto correct if it has results. If it doesn’t, we’ll use the second category match if that one has results. If both has results, we’ll use the first. And if none have results… well, no templates to apply.
• Tweakwise App | An option to filter on item types in the items module was added. Next to that, we've added a notice when an item is not linked to a category and/or an item doesn't have any attributes.
• Tweakwise App | A bug was fixed in Tweakwise App > Search > Search Algorithms, where category names that contain comma's were not displayed correctly in category match algorithm.
• Tweakwise App | We have enhanced the 'attribute values are too long' warning message and the 'attribute names are too long' error message, which were introduced lately. Each now includes a list of the first 10 violations with details such as the attribute name, attribute value, and item ID. Additionally, a download is available containing a full-text error message file for warnings.

Plugin Studio

• Plugin Studio | Some ease-of-use additions to the editor in Plugin Studio were introduced (in Tweakwise App): elements are now deselected when clicked on empty working areas making the controls more intuitive; if an element has a value assigned you will see that clearly stated in the working area so you have better control over what is included in the tile already; the live preview toggle now has a more prominent location, and; all elements can be duplicated (next to the delete button that also found it's new location at the top of the right panel when an element is selected).
• Plugin Studio | A new element is available to use on your product cards and it will make life a bit easier: an Input-element that controls the quantity of products that will be passed into the add-to-cart event. The element itself works as an add-on with the add to cart buttons and comes with some basic configuration options, like the option to choose between an input element or select element for example. Basic look and feel options are applicable and in case it isn't, custom CSS can always be applied. This new element is also now supported by all JS packages that can use the created product tiles.
• Plugin Studio | In the editor, we have also added a new way to add styling. It is a little bit technical as some CSS knowledge is needed, but there is now a direct CSS-editor where users may add styles not (yet) supported in the UI. You can switch to this via the button on the bottom of the right panel when an element is selected.

JS Implementation

• Search & Merchandising JS | Added prefix/suffix to filter facet values if set in App > Filter template > Facet > Advanced options.
• Search & Merchandising JS | Added an option to disable auto initialization if manual method is preferred.
• Suggestions JS | Added support for manually supplying the profileKey.
• Suggestions JS | Automatically close suggestions overlay after clicking on a suggestion. This is especially helpful for customers who have implemented both the suggestions as search results on the same HTML-page.
• Suggestions JS | We've fixed a problem where Text and Button elements from the Product Tile Editor did not show anymore in the Suggestions JS.
• Recommendations JS | Added support for manually supplying the profileKey, like was done for Suggestions JS.
• Recommendations JS | We made a fix where clicking on the previous and next buttons in the carousel won't cause unwanted side-effects when placing the Recommendations JS in a HTML form.
• Guided Selling JS | Added twn.question.open event hook for manipulating the look & feel of the questions.

We have updated the Tweakwise App dashboard to provide a more personalized experience. The renewed dashboard includes your key metrics, quick links to essential documentation, your personal information, and the latest news and changelog. In addition, we have refreshed the main navigation of Tweakwise App for easier use and made some smaller styling adjustments across the App.

Demoshop

Support was added for Custom CSS classes for navigation filters as configured in Tweakwise App > Filtertemplates > Filter > Advanced options. The classes will be applied to the filter facet, and that's it. This marks no visible change, just shows that we pass it on from the API. In the same vein, we also now support Prefix and Suffix values for (all types of) filter facet values.

We fixed a bug when fetching product recommendations of an item with a name containing special characters (e.g. a space) would not work. Finally, we've added the full calculation of the Algorithm Weighting scores to the Demoshop. Simply hover over an algorithm to see how the value is calculated!

Other improvements

• Backend API | We extended the Backend API with A new 'types' parameter for Get all items endpoint. This parameter accepts item types such as 'product', 'visual', etc to filter out end results.
• Frontend API | It is now possible to determine whether an instance has recommendations enabled in the admin panel. This information should be used by a client application to determine if it should make recommendation requests or not, to avoid unnecessary costs.
• Frontend API | The Frontend API now returns sorting debug information for items placed by Builder components. This can be used by customers to determine if a Builder component makes sense on a certain spot or not. Note that the Demoshop still needs to show this information, it doesn't do that yet.
• Tweakwise App | We have added a validation warning to the feed import task in case of an attribute outreaches the maximum field length of 400 characters. This warning is not blocking and the feed import will continue. A file is available for download which shows you a full list of warnings.
• Tweakwise App | Upon creating a new AI Synonym task a (random) trigger will be automatically added between 07:00 AM and 09:00 AM to prevent all instances from running the task at the same time.
• Tweakwise App | We fixed a bug in the new AI Synonyms task. Previously, if there was a validation error with the generated synonyms, the task itself would fail before displaying the error message. This problem was discovered as some synonyms were identical to the search term, something which is also fixed now.
• Tweakwise App | We have added the option to fill in test values for variables used in the URL of External Data Components, making it easier to test your configuration.

After a long wait, we have implemented native functionality for our Bucket Sliders for Magento. This is a special slider with extra features like clickpoints and buckets. Buckets let your customers see how many products are in a certain step along the slider, while clickpoints are often-used steps in a slider (for example on fixed sizes) so a customer quickly can skip to certain positions on the slider.

Apart from that, we implemented the API Request Headers for Magento as well. This Request Source says something about what application is generating traffic, like your website, mobile app or Tweakwise Demoshop. On Magento-installations, we provide this header source now with default information.

Other improvements

• Magento2Tweakwise v8.2.0 | The cron process has been adjusted so it doesn’t interfere with other Magento tasks while running.
• Magento2Tweakwise v8.2.0 | Templates now escape Tweakwise filter values automatically to avoid issues with special characters. Although this should not affect custom templates, we do recommend to double check custom templates to make sure that everything is properly escaped.
• Magento2TweakwiseHyva v4.2.0 |Templates now escape Tweakwise filter values automatically to avoid issues with special characters. Although this should not affect custom templates, we do recommend to double check custom templates to make sure that everything is properly escaped.
• Magento2TweakwiseExport v7.1.2 | The export process has been adjusted to avoid blocking other Magento tasks.

As Tweakwise is gathering more and more data, there is an increased need of transforming this data into insights. The difference between the two? Data is pure data, while information consists of data that is placed in a certain context. For that reason we introduce a new module: Insights. It is a powerful tool for improving your e-commerce experience. It provides customizable reports for areas such as conversion rates, sorting behavior, personal profiles, and search term drop-off rates.

By utilizing these Power BI-reports in Tweakwise App > Insights, you can make data-driven decisions to enhance your Tweakwise setup, improve user experience, and increase conversion rates. This feature, built on PowerBI, gives you in-depth insights to help you stay ahead in the competitive e-commerce world. Insights is now enabled (for free) for all of our customers and consists at the time being of three interactive reports, related to:

• API Requests usage
• Filtering usage
• Search Algorithm behavior and usage

📘

Are you missing a specific look at your data?

We just getting started. As we continuously updating Insights and want to roll out many reports later, please let us know what key insights you are looking for. We might be able to create a new report for you!

Creating product tiles is easy via Plugin Studio, but is just was made even easier by introducing some templates. When creating new tiles in the Product Tile Editor (In Tweakwise App > Plugin Studio) we have made it also a bit easier to get started with templates for both a vertical Product Tile as well as Product Suggestion. When you open the editor for a new tile you will be prompted to choose a starting template. Of course you can start with a blank canvas still, as you might want to design your new product cards from scratch.

Yes, you read that right! We have made it easier to create horizontal product tiles too by allowing to set alignment in the root frame of your product tile. In the alignment settings you you can change the flow of components from vertical to horizontal, commonly used in product suggestions. We have also made it possible to set specific dimensions (width and height) for all elements in the editor; this is useful for example when creating a product suggestion tile to set a limit to how large the product image can be.

Other improvements

• Tweakwise App | In case you have multiple shops or instances available in your account, it has been made easier to copy instance keys from any instance within the instance switcher. It easier to see the whole instance name if it is too long, and for customers with more than 10 instances a search bar also appears to help you find a specific instance more quickly.
• Tweakwise App | Fixed a performance issue where product images wouldn't load if the page size was set to 48 on Tweakwise App > Items.
• Tweakwise App | We've moved some logic and tiny improvements on our Apps menu. Most of it being a technical change, this should not have any functional effects.
• Tweakwise App | Finally, we moved the Bucket Slider feature out of beta, as it is now considered complete and fully adopted by all our solutions, including Javascript and Demoshop. (Magento will follow soon).
• Tweakwise Demoshop | Our brand new Demoshop now also has filters on mobile view, which is something that's has been missing until now. As the old version of the Demoshop is not longer accessible, we promise to not put the label new on our Demoshop from now on.
• Tweakwise App | The automatic generation of synonyms via Tweakwise AI unfortunately resulted in generating synonyms which were present at the stop word lists as well (filler mutation + system stop words). This problem has now been fixed.
• Tweakwise App | The introduction of the new Search Algoritm Weighting feature caused some minor esthetic problems, making that module complex to use. Weighting slicers disappeared while adding new algorithms to your funnel, wrong support-articles were linked, tooltips were not functioning correctly and adding multiple algorithms of the same type could break functionality. This all was now solved!

From a more technical perspective of our product, some of our JavaScript plugins were extended with event hooks you can use in order to smoothen your integration with Tweakwise. The Suggestions JS now supports the twn.add-to-cart and twn.add-to-favorites event hooks. These events allow customers to make use of add-to-cart and add-to-favorites buttons in the product suggestions.

The Guided Selling JS now supports the following event hooks: twn.request.started, twn.request.success, twn.request.failed, twn.request.completed and twn.results.open. When using the product tile editor in Tweakwise App > Plugin Studio, all elements now have a new data-attribute containing the shown value

The concept of showing other items than products on your builder-pages (like search results page and/or listings) now has been natively supported in our Magento plugins. In order to show inspirational content, sponsored blocks, banners or visuals on your listings, Tweakwise has introduced the possibility to import non-product items to your catalog and interact with these items as you are used to do like it being products. Our Magento plugins could still only handle product-information, but from now on we support non-product items out of the box as well.

📘

PHP 8.1

The minimum required PHP version is now 8.1. It used to be 8.0, but Magento doesn’t support version 8.0, so this doesn’t affect you. This is related to the following plugins:

• Magento2Tweakwise v8.1.0
• Magento2TweakwiseHyva v4.1.0
• Magento2AttributeLandingTweakwise 4.3.5
• Magento2AttributeLanding 5.0.3

Other improvements

• Magento2Tweakwise v8.1.0 | Native support for non product tiles was added in order to show banners or visuals between products on your search results page or listings.
• Magento2Tweakwise v8.1.0 | Sorting preferences and page limits are now remembered when you use certain search settings.
• Magento2Tweakwise v8.1.0 | A bug was fixed where product tiles were displaying the wrong store or language. Fixed a similar issue with recommendation tiles showing incorrect store or language.
• Magento2TweakwiseHyva v4.1.0 |Native support for non product tiles was added in order to show banners or visuals between products on your search results page or listings.
• Magento2TweakwiseHyva v4.1.0 |A bug was fixed where product tiles were displaying the wrong store or language.
• Magento2AttributeLandingTweakwise 4.3.5 | Fixed an issue where the URL of the return landing page was incorrect. Resolved a problem where changes made to attributes in the backend weren’t being saved properly.
• Magento2AttributeLanding 5.0.3 | A 404 error page will now show correctly if a landing page is inactive for a specific store.
• Magento2TweakwiseExport v7.1.1 | Fixed a stock issue related to grouped products, and we fixed a problem with the return type for certain values (technical fix).

Plugin Studio has been expanded so that you can design and assign product tiles for your Product Suggestions as well, as you already could do for your listings. Without getting too technical, the whole idea behind Tweakwise JS is to offer an easy way of integrating Tweakwise via a collection of modular and configurable plugins. Configuration settings are done in Tweakwise App, now including the exact look and feel of product cards in suggestions. This does mean that you ideally should set-up multiple Product Tiles, and assigned them to the different JS modules.

Javascrips improvements

• Search & Merchandising JS | When ui.closeSearchButton is set to 'false', the search overlay will not show the close button on a search overlay. Useful when customers have migrated to autocomplete from instant search and wish to not have the overlay closeable.
• Search & Merchandising JS | Extra parameters were added as configurable options (in local configuration), which could be needed to pass on through the APIs we're using. We've added support for keyboard, pageSize, filterTemplateId and sortingTemplateId. You can use these parameters to force/override values for specific usecases.
• Suggestions JS | The keyboard parameter for Search Algorithm optimization can be used here too. Also the lang parameter is now handled well.
• Search & Merchandising JS | The lang-option in the Search & Merchandising JS configuration is now used to pass it through to the Search Algorithms.
• JS Implementations | All packages now utilize the TWN-Source header in their requests to our servers, e.g. the value of this header for Search & Merchandising package is 'Tweakwise Javascript Search & Merchandising'. This is useful for categorization of customer traffic for a better overview of their API usage and this information will be present in some new reports we will introduce pretty soon. All packages can override the default value in their configuration using the sourceName key, so customer may pick their own name depending where the script is used.

Other improvements

• Plugin Studio | The Search & Merchandising settings page in Plugin Studio has been extended with missing configuration options, for example for grouped products and page size.
• Plugin Studio | When an instance uses the grouped product calls (Search & Merchandising) we can now access these product variants when building customers' custom product tiles. This is useful for use cases such as size or color variants, in case the instance's feed is correctly set-up with group codes. We expect to have this supported in the Product Tile Editor soon
• Demoshop | The Demoshop now finally supports Bucket sliders (with or without clickpoints) next to the basic range sliders!
• Demoshop | The Demoshop is now localized, meaning users can now change the language of the UI in the same way they can do it in the Tweakwise App (via your user preferences settings menu).

With every request made to the Tweakwise Frontend API, it now is possible to define a Request Source. This Request Source says something about what application is generating traffic, like your website, mobile app or Tweakwise Demoshop. By sending in this information, you'll later get the possibility to get a detailed report on API statistics by request source in Tweakwise App > Insights. For example, to get insight into what application (or ip-address) is making all those requests you’re billed for.

We've pushed a SEO improvement we tested thoroughly over the past couple of months. In our JS implementations, previously only the filter options that were shown on screen were also present in the HTML. This meant that all filter options hidden behind the 'Show more' button were not visible by for example Google when indexing the page. We changed this so that all filter options now are present in the HTML regardless of whether the 'Show more' button is activated. Recent results found out that this update could result a major impact on your SEO rankings.

This also counts for when you 'collapse' a filter. Before, when a filter was collapsed, none of the filter options were there in the HTML. Now, even if a filter is collapsed, all filter options are there in the HTML.

Other improvements

• Suggestions JS | We've fixed a bug where the prices of product suggestions would not update after changing your search term.