Minor releases introduce new features and improvements. Check out what’s new!

API's

• Backend API | Small bugfix in two Backend API endpoints, which now are only available via authentication.
• Analytics API | We’ve made it possible to supply the instanceKey to the Analytics API via a query parameter instead of via a header. This was done to make it possible to use so called beacon requests. This will allow our Event Tag to track events more reliably in the background. With this change we’ve made using the instance key header obsolete. Using a query parameter is now the preferred way. This has also been reflected in the API specification.

Tweakwise App

• Tweakwise App | We've improved the Derived Attributes Preview and Value distribution tabs. When the values are being calculated, a message is displayed to reflect this. When the calculation is done, values will automatically be displayed. There will also be no longer a timeout error for larger complex attributes.
• Tweakwise App | Fixed a bug where established and manual suggestions would not load in the detail page if the selected category had ID 0 (zero).
• Tweakwise App | We renamed the use of the name Autocomplete to Suggestions throughout Tweakwise App.
• Tweakwise App | When searching for a specific category in Tweakwise App, it now is possible to search on both the ID as Key too in category selectboxes (for example in those in Search Algorithms, Suggestions and Demoshop). Previously only searching by Category Name was possible.
• Tweakwise App | Google Analytics (UA) has stopped working and is replaced by Google Analytics 4 (GA4) for quite some time now. There were however still some instances that had recurring tasks for importing old reports based on UA; now we have set these tasks to inactive as results were no longer beneficial to your Tweakwise setup.
• Tweakwise App | The Tweakwise App's menu now correctly expands on page reload if a visitor is currently in a module within any group.
• Tweakwise App | A small bug was fixed in the new Filter Template module, in which validation on the facet type IsMultipleChoice resulted in an error. We fixed that so that all existing templates from the old module should save correctly again in the new module as well.
• Tweakwise App | You can now quickly update settings for a filter with the context menu (three dots). It supports setting the visibility, the collapsibility and the relevancy percentage for AI Smart Filters. When you select an option, it will be immediately applied for that filter. Also the lister page is extended with two columns: Usage and the amount of facets attached.
• Tweakwise App | We have updated the interlinking of the Attribute Used tab page to navigate to the new Filter Template module if that one is enabled for your instance.
• Tweakwise App | We added a clearer error messaging for failed connections to Google Analytics servers in order to assist with troubleshooting.

Demoshop

• Demoshop | We added an optional login to the Demoshop (same credentials as your Tweakwise account), which enables us to show more relevant data and in the Demoshop (as this information is not present in the Delivery API). First usecase of this is showing the SKU on the product tile and details about running A/B Tests.

Tweakwise JS

• Tweakwise JS | We improved the way personalized requests are sent to the server. Sometimes due to a raise condition the profile key was not part of the request. This should now be fixed. We also added the requestId to the navigation-success event.
• Search & Merchandising JS | We added a new option called selection that allows to pre-select filters for search. This setting was already available for category pages but was missing for search.
• Search & Merchandising JS | Search & Merchandising JS now automatically trigger the Event Tag events where possible: search, page impression, item click, add to cart, add to wishlist. Events not mentioned here (for example the purchase or productView) still need to be implemented manually.
• Search & Merchandising JS | We've fixed a bug where the search term would not update properly in some cases.
• Recommendations JS | We fixed an issue in the recommendations where the carousel would 'jump' while scrolling through the results. This issue should be fixed now.
• Suggestions JS | Recommendations JS | Guided Selling JS | Automatically trigger the Event Tag events where possible: item click, add to cart, add to wishlist. Events not mentioned here need to be implemented manually. The JS does not automatically include the Event Tag on it own. It still needs to be added to the platform manually for this to work.

Plugin Studio

• Plugin Studio | Added a new configuration option to the Plugin Studio's JS Suggestions configuration page to show the number of results for the given search suggestion. This number is shown on the results button, which of course needs to be enabled in order to see the number of results as well.
• Plugin Studio | We have added Event Tag configuration to the Plugin Studio so that you can setup which events should be fired automatically. Currently it is possible to configure whether, and what, events are fired automatically from each JS module (search, page impression, click, add to cart, add to wishlist), essentially changing the package's configuration. Manual implementation of the tag itself is still required.

Every visitor on a platform leaves behind substantial data like search queries, views, clicks, and purchases. Tweakwise helps by connecting these separate data points, revealing patterns, and guiding users toward better choices through comprehensive Insights reports. These reports already allow you to discover what is truly happening on your platform and how visitors search, filter, and convert. We are excited to announce two major expansions: the Conversion Report has been updated with session-differentiation, and we're introducing Data Exports.

Measuring the true impact of search

The Conversion Report has been upgraded to provide a sharper view of how onsite search contributes to your platform’s performance. The biggest addition is the ability to now clearly distinguish between conversions with and without the use of search. This separation provides immediate insight, allowing you to see at a glance how substantial the impact of search is on your total conversion. It gives clear insight into how visitors behave differently when they interact with your search engine compared to browse-only visitors.

📘

Event Tag

Implementing the Tweakwise Event Tag is essential to analyze the performance of your configuration, power our insights reports and support personalization. To support this, Tweakwise needs key e-commerce events on your platform. These are events such as product views, item clicks, add-to-carts, and purchases.

Export Data from Insights Module

To further enhance data usability and support external analysis, we are introducing Export Data functionality across the Insights Module. From now on, it is possible to export the underlying data from any chart within the Insights module. This function is available for all reports, including the E-commerce Report, Conversion Report, Task Statistics Report, Search Word Analysis Report, Usage Report, and Filtering Usage Report.

Accessing this data is simple: navigate to any report in the Insights Module, hover over the chart you wish to export, click on the three dots that appear, and select Export Data. You have the flexibility to choose between .xlsx (Excel) and .csv formats for your exported data.

We are happy to announce our renewed Filter Templates module in the Tweakwise App, redesigned to make managing your product filters faster, easier, and completely intuitive. As an e-commerce manager or digital marketeer, you need to manage your filters quickly, clearly, and without friction. Dealing with filters hidden in code, inconsistent translations, too many clicks, or constantly waiting for a developer costs time and flexibility. This updated module solves those issues by offering a fresh, intuitive interface with a multilingualism setup as a key benefit.

The redesign ensures that you manage your filters completely independently, without relying on developers. It has been revamped from the ground up to give you more control with fewer clicks and greater clarity. Everything now feels faster, clearer, and more logical. With the new interface, you manage filters faster and easier. You define the structure, sequence, types, and even translations yourself, all within one intuitive interface.

• Faster configuration: The redesigned interface means fewer clicks, more efficiency and clarity. You can configure filters in seconds.
• Full Filter control: You gain full filter control, managing filter structure, order, and languages without relying on developers.
• Flexible setup: You can effortlessly add new filter options and adjust their order. Filters can be reordered simply by dragging and dropping them into the position that best fits your category pages.
• Integrated Language Management: The new language management is fully integrated, allowing you to easily manage translations directly within the module. This keeps all filter labels consistent and centralized across every language and region. And don't be bothered to do all your translations yourself; with the help of AI translating was never be that simple.

This renewed Filter Template module gives you more control and boosts your speed. You can keep tweaking until your filtering perfectly matches what your visitors need. The result is a smoother experience, higher relevance, and stronger conversion, all without hassle. And even better, it works smoothly with our A/B Testing module too. Not sure whether your changes are right? Test them first in a make decisions based on clear, factual data instead of assumptions.

Languages management

To ensure you can fully utilize multilingual capabilities of the renewed Filter Templates module, it is essential that your instance recognizes languages as such. Language Management is a new, central feature within Tweakwise App designed to manage your languages. It allows you to easily define which languages are active, set a default language, and ensure your entire platform remains consistent across all languages and regions.

This new structure is what enables the fully integrated translation workflow now visible in the Filter Templates module. By managing languages from one place, it allows you to translate directly where you work: editing texts instantly within the filter configuration screen. This interaction ensures that all your filter labels are kept consistent and centralized, avoiding duplicate entries and mistakes. Tweakwise is continuing to integrate this structure into other modules like categories and products, ensuring you maintain clean oversight and control over multilingual content throughout the entire app.

📘

Utilizing the tn_lang parameter

To ensure filter templates appear in the correct language, the tn_lang parameter should be present in Frontend API requests. The code provided must be configured within the language settings in Tweakwise App. This configured language is mapped to a Full Text Language, which is crucial to apply complex linguistic processing to search terms, including plurals, verb conjugations, and splits. Utilizing the tn_lang parameter guarantees the correct display of filter translations and enhances search relevance and accuracy.

We are delighted to announce the launch of A/B Testing, a powerful new feature in the Tweakwise App. With A/B Testing, you can now move beyond assumptions and make decisions based on facts. This new module gives you all the freedom and ability to optimize endlessly until everything aligns with your goals, your customers, and your vision. The new feature allows you to steer more effectively with data, accelerate optimizations, and avoid costly assumptions. By running tests, a bit of tweaking and learn from outcomes, you will achieve higher conversions and a more relevant shopping experience.

The A/B Testing feature enables comprehensive testing across crucial areas of your online platform:

• Test your lister pages: You can easily run tests comparing various elements on your lister pages, like grid layouts, visual components, and campaigns. Compare how different arrangements of components such as 'Popular', 'Visual', and 'Sale' blocks perform against each other You can also compare different product displays and visual promotions.
• Optimize filters: Experiment with filtering by adjusting the order and visibility of your filters. You can instantly define the best order and visibility for your filters.
• Smart sorting: Experiment with sorting by testing different sort options against each other, each utilizing its own logic. This functionality allows you to find the most effective sort option for your visitors. Test which order of sorting options, such as 'Relevant', 'Especially for you', 'Best reviews', and various price ranges, drives better results.

📘

To understand the impact of A/B testing, imagine trying to choose the best route to work. Instead of simply guessing which road is fastest (an assumption), A/B testing is like driving two different routes simultaneously (Variants A and B) with different drivers, accurately measuring the travel time, and then choosing the winning route based on clear, factual data.

The A/B Testing tool ensures your decisions are always well-founded and based on reliable insights. The itself tool shows you directly whether there is a clear winner or no measurable difference between the tested variants. We focus on higher conversion (in the terms of Conversion Rate), but will also measure Revenue, Average Order Value, Units per Transaction. All of our A/B tests will run in an even 50/50 percent split and will run as long as you want: you can change your end date as long as the test is running, although this is not a best practice to do.

👍

Integration agnostic set-up

No A/B-specific code is required on your side: Tweakwise A/B Testing runs entirely within our platform. Variant assignment, distribution, and evaluation are handled server-side. Your implementation only needs to supply the required identifiers and events to enable consistent variant exposure and accurate measurement.

This guide outlines the technical requirements for developers integrating A/B testing via API or Tweakwise JS. Be aware that proper A/B Test reporting depends on Event Tag data.

Minor releases introduce new features and improvements. Check out what’s new!

API's

• Delivery API | We've added a nrofitems field to the suggestion products and suggestion products grouped endpoints. This field contains the total number of products found for the given search term.
• Delivery API | We've significantly improved the performance of the Filter Wizard endpoint (Guided Selling funnel type) in the Delivery API. The average response time has been cut by nearly 40%, dropping from ~180ms to ~110ms. This optimization delivers the most dramatic improvement for the slowest requests.
• Delivery API | The origin name field now contains the value 'Product' if the instance has placed specific products on the builder and has not configured item types. If a customer already had item types configured, then it would've already said 'Product'.
• Backend API | On our docs website the Backend Api endpoint for Patch filter template attribute was in the wrong place and we resolved this.
• Backend API | From now on, we do not set some default values for filter template attributes when using POST or PUT. Previously we set some default values in our API, but we now want all the settings to be explicitly defined by the users input.
• Backend API | Some API validation logic was updated regarding Filter template attributes, which now makes it possible to set multiple choice options for the attribute type 'link'.
• Backend API | The maximum allowed length for categorykey has been increased from 64 to 128 characters.
• Analytics API | New events were added to the Analytics API, namely: add-to-cart, add-to-wishlist, page-impressions.

Tweakwise App

• Tweakwise App | We've implemented a retry-logic for Google Analytics tasks. Sometimes the Google servers are not reachable when running these tasks, which then resulted in failed reports and task. With this improvement we implemented retry logic when trying to reach Google Analytics, that way we should be able to reduce the failures.
• Tweakwise App | Fixed a minor bug where dragging a content item within a builder would not show its "ghost" properly. And you're now able to open the page of an item or attribute in a new tab from the builder tile.
• Tweakwise App | All (new) data tables now display clear error message when a request fails, e.g. request time-out so users are not presented with non-relevant data in case they miss the error toast notification.
• Tweakwise App | Since upgrading to a new UI library recently, we got the option to easily add some transition animations to the UI for a more seamless experience - disclosures and dropdown menus/select boxes are now animated.
• Tweakwise App | In case an instance has image characteristic set up (attribute Use as 'Image') we now show the correct, potentially derived, image value in Builder Tiles, the Items module and item lookups (select boxes) across the App. Item edit (/create) page now shows no image in this case with another explanation for the characteristic. This is to prevent confusion when creating a new item/visual/.. in what the final, published image, is going to be.
• Tweakwise App | When an attribute has been selected (Use as) SKU, item records with empty SKU-values would not show up in the preview tab of rules. This issue was fixed, all items do show up in the preview tab no matter if SKU is empty or not.
• Tweakwise App | We have implemented some performance improvements for our search functionality in Tweakwise App > Catalog > Items, especially resulting in faster response times for instances with lots of items.
• Tweakwise App | Fixed an issue where items with special characters in their id (e.g. #) were not able to be opened. Also, when pressing enter with opened attribute selection dropdown (in items edit page, attributes tab) rows would be deleted via an auto-focus on the delete button. This has been solved as well.
• Tweakwise App | We added a new validation rule for One-way synonyms where a keyword can not appear in the list of terms too. Also potential API error messages while importing synonyms are displayed to users in notifications, instead of 'something went wrong'.
• Tweakwise App | Fixed a bug where clicking on 'Create new attribute' in some forms (e.g. Items edit form) would break the select component. Also fixed a small bug where labels for Radio group form components would not show up properly.
• Tweakwise App | Fixed a bug where showing Builder statistics would result in an error.
• Tweakwise App | In the publish process, we've updated our retry logic in order to reduce any potential publish failures during a small availability interruption in our Deployment API.

Demoshop

• Demoshop | The sort-by option is now preserved and not automatically removed when filtering. It will only be reverted to default when the 'remove all filters' is clicked.
• Demoshop | Fixed a bug where smart filter badges in front of respective facet values would not show up. We also changed Pins label from 'Content merchandising' to 'Product Pin'.

Tweakwise JS

• Tweakwise JS | We've fixed a problem where a part of the 'no results' page wasn't translated properly. Also some French translations were updated.
• Suggestions JS | For category search suggestions (e.g. 'T-Shirts in Clothing') we have added missing translations for the word 'in'. As with other translations it's possible to overwrite this in the config.
• Suggestions JS | There is now a new configurable option resultsButton.showResultsCount (boolean) that shows the number of results for a given suggestion. This feature is opt-in because an instance may have redirects configured for some terms and the amount of products may not match with what is on that redirected page.

Plugin Studio

• Plugin Studio | Fixed a bug in the Plugin Studio where a product tile sometimes wouldn't load.
• Plugin Studio | Added an 'auto initialization' toggle to the Search & Merchandising settings page to make it easy to prepare an instance for a manual configuration. In case you opt-in for manual configuration, disabling this setting will prevent Search & Merchandising from automatically initializing on page load.
• Plugin Studio | In the Tile Editor it is now possible to use string values (e.g. SKU) beginning with zero without losing these leading 0s after automatic conversion to a number.

Minor releases introduce new features and improvements for our Shopware plugin. Check out what’s new!

• SW-Tweakwise 5.1.0 | An new setting is introduced for the feed to respect Shopware settings to hide products after clearance. When enabled, products and variants will then be excluded from the feed after clearance. To achieve this, it is neccessary to set the option in the Tweakwise feed-settings in Shopware as well as in the product settings of Shopware. With this additional toggle in the Tweakwise feed-settings, we prevented this change to be breaking. This change was already released for the 4.x version of the plugin.
• SW-Tweakwise 4.5.1 | A small bugfix was done to make sure the sold out products are also excluded in the feed when you use the non-grouped approach.

📘

Reminder

The 4.x version of the plugin is compatible with Shopware v6.5 and v6.6. The 5.x version of the plugin is compatible with Shopware 6.7. Click this link to visit corresponding repository and update on Github.

We’ve expanded the Plugin Studio with two new configuration pages that make it easier to customize the behavior and some look & feel of your JavaScript implementation. You can now directly configure settings for the Suggestions and Recommendations modules; similar to how configuration has already been available for Search & Merchandising. These new pages allow you to fine-tune how Tweakwise interacts with your platform without modifying code, ensuring faster implementation and consistent results.

Suggestions JS settings Page

The Suggestions module settings page enables you to define how product and category suggestions behave and appear in your frontend, when implemented via Javascript. This page contains default settings for the implementation of the Suggestions module.

Although the contents of your suggestions are setup in Tweakwise App > Search > Suggestions, the way how the overlay behave is configured in Plugin Studio. You can set latency to control when results appear after typing, and choose the keyboard layout for search optimization. It also allows you to include or exclude products based on specific parameters, enable grouped products, and customize the product tile and language for display. These default settings determine the behavior and appearance of the Tweakwise Suggestions module and can still be overridden programmatically if needed.

Recommendations JS settings page

The Recommendations module settings page lets you manage how product recommendations are displayed and filtered on your platform. You can choose how recommendations are presented visually, with options for product tile design, language, and layout type per device (carousel or grid), limit results to specific categories, and include or exclude products based on custom parameters. Additionally, you can pass extra data to external components and specify a source name for better tracking. All these defaults can be overridden programmatically for advanced customization.

📘

All settings defined in the Plugin Studio act as defaults. You can still override them programmatically for advanced use cases, providing the flexibility needed for tailored implementations.

Minor releases introduce new features and improvements for our Magento plugins. Check out what’s new!

Magento2Tweakwise

• Magento2Tweakwise 8.7.1 | Added 'Show More/Less' functionality to color and size swatches for a cleaner display on product listings.
• Magento2Tweakwise 8.7.1 | Moved the itemclick tracking logic to ensure it functions correctly across all module configuration settings.
• Magento2Tweakwise 8.7.1 | Fixed a issue where special characters were not correctly handled in the in-filter search.
• Magento2Tweakwise 8.7.1 | Resolved a bug with category redirects when the category URL was changed.
• Magento2Tweakwise 8.7.1 | Fixed an issue where removed filters would sometimes remain in the URL.
• Magento2Tweakwise 8.7.1 | Corrected a bug where a category could be hidden if it was the only category returned.
• Magento2Tweakwise 8.7.1 | Fixed an issue preventing the page parameter from being correctly saved in the browser history on the first request.
• Magento2Tweakwise 8.7.1 | Added an alias to a function to maintain compatibility with Magento Commerce (Adobe Commerce).

Magento2TweakwiseExport

• Magento2TweakwiseExport 7.7.0 | Added a new setting to control how created/updated dates are exported. You can now select to export all dates (default), only the earliest date, or only the latest date.
• Magento2TweakwiseExport 7.7.0 | The Attribute Set is now included in the export data.
• Magento2TweakwiseExport 7.7.0 | Fixed an issue with incorrect prices being exported for grouped and bundle products when using special prices.
• Magento2TweakwiseExport 7.7.0 | Resolved a bug that resulted in the wrong store view being used in the category URLs in the export.

Magento2AttributeLanding 6.0.1

• Magento2AttributeLanding 6.0.3 | Fixed an SQL error that occurred when changing the category URL suffix setting for landing pages.

Magento2TweakwiseHyva

• Magento2TweakwiseHyva 4.4.0 | Added 'Show More/Less' functionality to color swatches, aligning with the core module update.
• Magento2TweakwiseHyva 4.4.0 | Moved the itemclick tracking logic to ensure it functions correctly across all module configuration settings.
• Magento2TweakwiseHyva 4.4.0 | Fixed an error that occurred when activating Personal Merchandising.
• Magento2TweakwiseHyva 4.4.0 | Resolved an error that would prevent default functionality from working correctly if an error occurred while selecting a filter.

As part of our ongoing evolution of the attribute model in Tweakwise, and to support the fact that you can now create new attributes directly in the App (rather than only via feed/external import), we are introducing a streamlined model: the previous distinction between Feed and External attribute types is removed, and both are now treated as one type: Standard. This change simplifies the internal logic and the user experience, and removes legacy distinctions that no longer reflect how attributes are created or managed.

With the ability to create attributes directly in the App (in addition to import), the old notion of Feed vs External no longer mapped cleanly to how customers actually set up attributes. Rather than adding a new type (such as 'App' or 'API'), we simplified logic by merging Feed and External into a Standard attribute. Many parts of our backend logic and UI had special cases (added complexity) for External attributes, which now has been removed. No action is required for users. All existing attributes are migrated behind the scenes: filters, facets and characteristics continue to work as before.

When you see Standard attribute, you now know it covers all attributes created via feed, external feed, API or App. This way the terminology is aligned across UI, API, documentation and internal logic, and lays the groundwork for further advancements without being tied to legacy types.

Minor releases introduce new features and improvements for our Magento plugins. Check out what’s new!

• Magento2Tweakwise 8.7.0 | Moved the analytics setting to the General section, as it’s not dependent on personal merchandising.
• Magento2Tweakwise 8.7.0 | The Suggestions endpoints will now be used as the default endpoint for search suggestions, instead of the old Autocomplete endpoints.
• Magento2Tweakwise 8.7.0 | Fixed an issue where the wrong URL was used for ALP pages when filtering by swatch.
• Magento2Tweakwise 8.7.0 | Resolved an issue where product images were missing when the Tweakwise API was not configured for images, ensuring the correct image is shown when grouped products are disabled.
• Magento2TweakwiseExport 7.6.1 | We’ve reverted some poor performing changes to the export.
• Magento2TweakwiseExport 7.6.1 | PHP 8.4 is fully supported, so you can run the latest version with confidence.
• Magento2TweakwiseExport 7.6.1 | Resolved an issue in grouped export where the wrong group code was exported for certain products.
• Magento2TweakwiseExport 7.6.1 | Fixed a type error.