Guided Selling, designed to help customers find the most suitable products in just a few logical steps instead of filtering, is now supported in the Tweakwise Demoshop. You can now explore the Guided Selling funnel experience directly in the Demoshop, which makes it easier than ever to demonstrate how Guided Selling can simplify product discovery, showcase its personalization and filtering logic in real time and inspire everybody with a hands-on example of its potential.

Guided Selling bridges the gap between online product discovery and the in-store sales experience. By guiding users through a series of dynamic questions and filters, Guided Selling simplifies complex assortments, boosts conversion, and enhances the shopping experience.

• SW-Tweakwise 4.4.0 | Besides the property 'Selected option', which contains the chosen options for a specific variant in one attribute, we have introduced the multi-value property 'Selected options' in the feed. This property will store the selected options of a variant as separate attributes.
• SW-Tweakwise 4.3.0 | Added an option to show sibling categories in the category filter on the merchandising pages (by adding the parent category in navigation.cid).
• SW-Tweakwise 4.2.3 | Added missing getters and setters in feed generation events.
• SW-Tweakwise 4.2.3 | The last generation date is now instantly updated when you click the refresh button in the feed admin, like it already worked for 'status' and 'renewal date'.
• SW-Tweakwise 4.2.2 | Added some missing Dutch translations in the admin of the plugin.
• SW-Tweakwise 4.2.2 | Adding products to your wishlist/favorites is now working (again) when using grouped products.
• SW-Tweakwise 4.2.2 | When you have non-string custom fields in your products (like prices), this will now not result in an error when generating the feed.
• SW-Tweakwise 4.2.2 | No error will show up in the browser console when you do not have activated the wishlist in Shopware.

📘

SW-Tweakwise 4.4.0

Click this link to visit corresponding repository and update on Github.

As part of our ongoing commitment to inclusive digital experiences, the Tweakwise Search & Merchandising JavaScript module has been updated to align with the latest web accessibility (a11y) practices. Accessibility in web development means designing interfaces that are usable by everyone including people relying on screen readers, keyboard navigation, or visual support tools. These enhancements are designed with WCAG 2.2 AA compliance in mind, supporting the European Accessibility Act, which took full effect on June 28, 2025.

This update ensures that Search & Merchandising JS functions optimally with assistive technologies. One of the biggest changes is that the entire module is now fully operable with a keyboard: users can navigate, select filters, interact with carousels, and more, without ever using a mouse. We’ve also added descriptive alt texts for icons and images, and proper ARIA roles and labels to make the experience compatible with assistive technologies. Smaller but meaningful improvements include better visual contrast (e.g., making filter count text easier to read) and eliminating tab traps that previously hindered smooth navigation.

While the core experience remains unchanged for most users, it’s now significantly more accessible for those using screen readers or keyboard navigation. Do note that accessibility can also be influenced by customizations in styling and structure of the Tweakwise JS implementation, which may vary per customer setup. We’re still working on a few follow-ups, so please let us know if you encounter anything unusual - your feedback is invaluable as we continue to improve.

📘

European Accessibility Act/WCAG 2.2 AA

In January 2013, a European Accessibility Report was created that prompted a legislative change (law), which was adopted by the EU member states in 2019. By June 2022, member states had to implement the changes in their own legislation. June 28, 2025, marks the official start date of the European Accessibility Act.

In the Netherlands, (semi-)government websites must already meet certain accessibility requirements. The main change in 2025 is that the legislation will apply to many more organizations, including e-commerce businesses.

Note: As we mainly focused on the Search & Merchandising JS in this release, we will follow up on this topic regarding other solutions, like Suggestions JS, Recommendations JS, Guided Selling JS and our Magento storefront plugins. Web accessibility for our Shopware plugin will be fully covered via our JavaScript solutions.

We’re excited to announce that our OpenAPI specification for the Frontend API has been significantly improved and is now fully valid and compliant with industry standards. This means developers can confidently use the specification to automatically generate API clients in a wide range of programming languages, streamlining the process of connecting to our API and reducing the risk of errors. For example, developers can take advantage of tools like OpenAPI Generator to quickly create ready-to-use API clients, saving time and ensuring consistency across different projects.

These improvements make it much easier and faster for teams to integrate with our services, whether they are building new features or maintaining existing applications. By providing a clear and accurate API specification, we’re making our platform more accessible and developer-friendly.

• Magento2Tweakwise 8.4.4 | A new setting for visual item types was added for enabling or disabling visuals. This new behavior prevents the default product tile layout from being overwritten, as we encountered some issues with this. When enabling Personal Merchandising or Visuals, the product tile layout may be replaced. To maintain a custom layout (built by yourself), you can override the default layout file with your own version.
• Magento2Tweakwise 8.4.5 | Fixed an issue where the category URL ended with a trailing slash, even though this was not configured.
• Magento2Tweakwise 8.4.5 | Fixed an issue where the 'clear filters' URL was incorrect in situations that the filter URL segment included the category URL.
• Magento2Tweakwise 8.4.5 | Fixed an issue where HTML was displayed as plain text on a button.
• Magento2Tweakwise 8.4.5 | Fixed a tiny bug where an analytics request from the Hyvä-theme was not processed correctly.
• Magento2Tweakwise 8.4.5 | Fixed an issue where a dot (.) in the personalisation profileKey caused analytics requests to be ignored by Tweakwise.
• Magento2Tweakwise 8.5.0 | Regarding our Event Tag integration, the purchase event now includes a revenue value, allowing for more accurate reporting. We also added the item_click event to track which products users click on.
• Magento2Tweakwise 8.5.0 | Introduced a compatibility adjustment for Magento 2.4.8. As full support is still being tested, more updates will follow.
• Magento2Tweakwise 8.5.0 | A wrong type declaration has been fixed to prevent potential runtime errors.
• Magento2Tweakwise 8.5.0 | Fixed an error that occurred when Tweakwise was configured for swatches, but no swatch attributes existed in Magento.
• Magento2TweakwiseHyva 4.4.0 | Just like in the main module, the item_click event is now supported.
• Magento2TweakwiseHyva 4.4.0 | The swatch mismatch error mentioned above has also been resolved for the Hyvä storefront.
• Magento2TweakwiseExport 7.4.0 | The SEO-Url of categories is included in the export data, required for a smooth interaction with the new/upcoming Magento Tweakwise JS plugin. By having category-urls available within Tweakwise, it is possible to refer category-suggestions and category-filters to their corresponding SEO-friendly urls instead of making use of query-parameters.
• Magento JS 1.1.0 | Added support for analytics events to track purchases, product views, and search events. Item click events were already supported. Meanwhile, fixed a small issue where the add to cart functionality could fail under certain conditions.

• Backend API | We have added the possibility to overwrite the order of category suggestions via the Backend API. From now, GET/POST/PUT /suggestions/autocomplete endpoints have a new PrioritizedCategories property.
• Backend API | Fixed a minor Google Analytics 4 metrics incompatibility validation bug.
• Analytics API | The session start event was added to the Analytics API. Having this event will, for example, allow us to say something about bounce rates on our customers’ websites when implemented.

Tweakwise App

• Tweakwise App | In the Google Analytics 4 reports, it is now possible to use custom created dimension instead of a standardized list. This does mean that all dimensions as available in GA4 are also available to use as Tweakwise data. Meanwhile some validation-logic to the Google Analytics 4 module has been changed. We do show relevant validation error messages in case dimensions and metrics are not compatible.
• Tweakwise App | In addition to setup exclusions for Category suggestions, it is also possible to prioritize certain categories in your category suggestion group by hand, so these categories will pop up in your category suggestions result set with more priority. Also changes were done in the regular algorithm. Category suggestions that exactly match the search term, will be pushed to the top of the suggestions.
• Tweakwise App | We have re-arranged the elements in the Suggestion groups headers and color-coded different groups' labels, so it's easy to recognize at first look.
• Tweakwise App | The attribute filter is now a required field for setting up facet suggestion groups, solving the problem of having a saved breaking configuration.
• Tweakwise App | We fixed the way how to edit already placed tiles in your Builder templates. In case there is a second step in the tile's edit modal (e.g. Basic and Advanced tiles), you go directly there and all fields are properly filled with current values, making it easy to make tiny modifications.
• Tweakwise App | When sorting facets in a Filter template detail page, you are no longer randomly redirected to the Facet detail page after dropping the dragged item as this side-effect is now prevented.
• Tweakwise App | We fixed a small issue where you could not save the concatenate derived attribute when the attributeName has [] in its name.
• Tweakwise App | Added validation to the feed import for when there are 'HTML tags' present in the values of attributes. The import will now continue to work, but a warning will be shown.
• Tweakwise App | Applied a more consistent UX/UI to the disclosures in the App. For example, the arrow indicating that something is collapsed is now always on the left side.
• Tweakwise App | We've changed the way we search for suggestions (search phrases, facets, categories), more specifically: we ignore 'diacritics', special characters like éë etcetera. Previously, when searching for pokemon, you would not find category suggestions for categories containing 'Pokémon' in the name. This is now fixed and aligns with the rest of our search behaviors.
• Tweakwise App | We've enhanced how AI Embedding attributes are processed to ensure more reliable search results. Previously, products with multiple values for an AI embedding attribute could cause inconsistent search behavior. Now, the platform will consistently select a value from such attributes when creating AI embeddings, guaranteeing that search queries always return predictable and stable results.
• Tweakwise App | Added API attribute names in the list view of the Attributes module. Now you can see the name next to the URL name.
• Tweakwise App | Fixed a bug where some category paths (e.g. in Suggestions module - Category Suggestions - Exclude/Prioritize categories list) would show the last category name twice.
• Tweakwise App | Fixed the layout of the GA preview so that no columns can overflow the table anymore.

Demoshop

• Demoshop | Pagination has been improved. It's now possible to directly go to the page you want by typing in the page number. Also you can quickly navigate to the first and last page of the response, instead of only browsing to next and previous pages.
• Demoshop | We've added a summary of the total amount of results on top of the lister page, like we already did with the amount of results on a search results page. The search results display options (for debugging purposes) are no longer visible in case the 'Weighted Search Algorithms' feature is not enabled.
• Demoshop | Fixed the layout of the JavaScript Demoshop so the header doesn't overflow on mobile and the documentation button does not overlap with filter button.

JavaScript

• Tweakwise JS | Loading attribute for images has been improved. Eager loading is enabled for the first row of items to increase page-load speed/LCP.
• Tweakwise JS | Fixed a bug in Suggestions that prevented the form to be submitted without any result.
• Tweakwise JS | Fixed a bug with JS integrations that was caused by a specific version of an external library we use, causing certain parts to not work in older Safari browsers.

Plugin Studio

• Plugin Studio | The UX for the deployment has been slightly improved. We have fixed some usability issues with the deployment process and are now showing a list of last (max 20) versions that have been previously deployed for a quick overview. Each version is tagged with a timestamp of when the change has been made and you can now see which version is currently active. Yet it is not possible to go back to an older version.
• Plugin Studio | An information message was added to the 'Browser History Mode' in Tweakwise App > Plugin Studio > Search & Merchandising > Advanced to prevent users from just changing the configuration and breaking their implementations.
• Plugin Studio | It is now possible to set a value for a hover image on your Product Tile. This makes setting up a tile easier and does not require extra development for a hover image. Simply select an attribute with image URL. By default the switch between base and hover image is only triggered by moving your cursor over the image itself, but can be customized so that the whole tile triggers the effect. Adding a transition can also easily be done with setting a custom CSS property via the CSS editor on the Image Element.

We’ve packed this release with four improvements that make feed generation faster, leaner and more accurate, while also giving you brand-new flexibility in how your product variants are exported and tracked as grouped products.

1. Configurable Batch Size for Feed Generation: You can now specify the number of products processed per batch during feed generation for better performance, and to only include custom fields if you need them in your feed. A larger batch usually shortens total generation time. If your server runs out of memory, simply lower the batch size or raise the server’s PHP/container memory limits. But first check your server logs.
2. Grouped Products Export: A new toggle has been introduced in the Shopware admin which lets you choose to export product as groups. In Tweakwise, the concept of main products with variants does not exist; instead, group keys are used for product grouping. Group keys provide the necessary flexibility for grouping products based on specific attributes, ensuring a tailored product display without relying on a main product/variant structure. Enabling this feature overrides Shopware’s default 'Main Variant in Listing' behavior - the system will no longer auto-pick a showcase variant for storefront listings.
3. Browser History Mode: The Shopware plugin now supports improved URL handling out of the box. You can choose how filters and pagination are reflected in the URL - either with cleaner query strings or the traditional hash format. This update enhances SEO and allows visitors to use their browser’s back and forward buttons more naturally when navigating filters or pages.
4. Revenue in Purchase Event: Shopware now supports the revenue property out of the box in the Event Tag for purchases. This means order totals are automatically included in the data sent to Tweakwise, enabling more accurate tracking of purchase value for personalization, performance insights, and eventually AB-testing.

📘

SW-Tweakwise 4.2.0

Click this link to visit corresponding repository and update on Github.

As part of SW-Tweakwise 4.1.1 (May 02, 2025), some minor changes were already implemented. Some small UX enhancements were done in the admin module to manage Tweakwise feeds; we fixed some unclear labels on collecting data and removed preloads and added defer tag to Plugin Studio JS in order to increase frontend performance.

Since the introduction of our refreshed Builder we've made several improvements and enhancements to it. We changed some minor things in look and feel and added new functionality, mainly focusing on ease of use and giving a visible representation of your setup/layout. Two additions are pretty impactful, namely: Flexible Height and Builder Click Distribution as Actionable Insights. As engagement with your customers is crucial and becoming a key indicator on how well you perform, both features could be very useful in order to keep improving your e-commerce setup. And by now the new version of the Builder is rolled out to all customers as a default.

1. It is now possible to create a copy of your builder configuration via one simple click. This could be incredibly useful if you want to do minor tweaks for a specific category for example, or if you want to make a copy into a separate language.
2. Components which are placed on the builder, from now on can be copied too.
3. All components now have an indicative label assigned to it, according to your plan. While adding a new component to your builder, everything is neatly sorted and it should be easy to find via newly introduced quick filters. Visuals and product pins also do show the specific items (banners, products) on the component itself. A quick 'shortcut' button to go to the next step of a component was added so that you don't have to scroll all the way down when you have a lot of components.
4. Building upon our earlier update that allowed components to span multiple columns (flexible width), you can now also adjust the height of components within the grid. This means you can create more dynamic and engaging layouts that better capture your customers' attention and enhance their shopping experience.

Actionable Insights | Builder Click Distribution

We’re excited to introduce click distribution insights directly in the our Builder! Now, each grid position in your layout shows a click rate label, giving you instant visibility into how your visitors interact with each item. These real-time metrics take the guesswork out of optimization. You’ll see exactly which positions are getting attention and which are being overlooked. For example, in the image shown: Position 6 and 8 both have a strong 10% click rate, while Position 5, with a flashy visual, only pulls in 1%. With these insights, you can make quick, data-driven layout adjustments like swapping components to boost performance. It’s micro-optimization made simple and effective.

📘

Event Tag: Item Click

To enable click distribution insights in the Builder, make sure you’ve implemented the Tweakwise event tag with the click_product event. This is essential for tracking user interactions and collecting accurate click data.

Customers expect to find what they’re looking for quickly, even before they’ve even finished typing. Autocompletion and intelligent suggestions have become essential tools for modern online retailers. Effective autocompletion helps reduce friction and improves product discoverability, while well-placed search suggestions offer strategic opportunities to show relevant products, brands or categories. To help you take full control of this aspect of the user experience, we introduce a new Suggestions module with a lot of configuration options.

Previously, in Tweakwise App we had four different modules to configure all autocomplete behavior. Now Autocomplete, Established Suggestions, Manual Suggestions and Blacklist Suggestions are merged into one single Suggestions module in which you can do all your configurations. You will find it in Tweakwise App > Search > Suggestions in which a couple of major improvements were implemented alongside:

1. Manage the order of suggestions groups: As the Suggestion groups are all combined in a single Frontend API endpoint, managing the order of suggestions is very useful to do without the need of writing code. Now you can simply change the order of the suggestions by dragging them to the right place in your configuration. Product suggestions however should still be implemented via a separate API endpoint, and therefore should be positions on top or bottom in your frontend application. In Tweakwise App we decided to put them at the bottom, as this is the most common use case.
2. Option to have multiple Facet suggestions: As Search phrase suggestions and Category suggestions speak for themselves, Facet suggestions can be implemented for every attribute available in your product catalog. With the introduction of this new module you now have the option to implement multiple Facet suggestions in one group, instead of having a limitation of one. With Facet suggestions, you direct users to a specific result based on a product attribute such as brand or type. This helps speed up the search experience.
3. Setup exclusions for Category suggestions: There might be some situations in which you don't want a category to pop up as a suggestion. This can now be managed to mark some categories as 'excluded'. Once configured, this specific category will not be in the API response, while it's children could still be present as Category suggestions.

• Backend API | In the Backend API, Filtertemplatelink could break when a category had more than one parent categories assigned. This has been fixed.
• Backend API | The attributes endpoint now has a optional filter for tags (type of usage: api, hiddenfilters or characteristic).
• Backend API | The GA4 report create\preview endpoint now validates incoming metrics and dimensions and return error message if some of them is incompatible. Example: 'The dimension itemId is incompatible with the metrics: itemViewEvents.'
• Backend API | The Get item endpoint has been expanded with LastModified and UpdatedBy properties, which displays the source that updated the item. Possible values: feed, api, app. If you update items using the Backend API, it checks the authentication method: if there is an ApiKey using, the source is gonna be api, otherwise app.
• Frontend API | The instance-endpoint now returns all features enabled for an instance. Before, it only returned a specific subset of features like: navigation, suggestions, personalization and recommendations.
• Analytics API | The option to add revenue was added to the purchase event in the Analytics API. Revenue (the total revenue from the purchase, calculated as the sum of product prices after discounts) can be empty, or must contain a value greater than or equal to 0. It will be necessary for setting up AB tests later on.
• Analytics API | All event-endpoints of the Analytics API were extended with a sessionKey. This key is used to group events that belong to the same session. And although this is optional, we do require this information for an upcoming feature in relation with A/B-testing.

Tweakwise App

• Tweakwise App | A bug was fixed where the Demoshop modal would not work for categories with ID 0.
• Tweakwise App | A more helpful warning message was added when assigning Item characteristics in the App.
• Tweakwise App | We fixed a validation error that occurred in feeds for external attributes that have multi values. Also, we now accept empty values (same as normal feed import) and there was a bug in exceptional long values that is now fixed and those will also not causes failures anymore.
• Tweakwise App | When a warning occurred during external attribute import, for example on max attribute value length, the import failed. Now the external attribute import succeed with warning, just like the feed import.
• Tweakwise App | The maximum length for published category-paths has been increased.
• Tweakwise App | The placement of the checkbox for 'hide filter when there is only one option available' was moved from the advanced options tab to the basic options > smart filters on the detail page of a filter template.
• Tweakwise App | While creating or editing an attribute, we made it visibly clear what type of attribute is related.
• Tweakwise App | The Czech language was added for full-text search support.
• Tweakwise App | When changing instance via in Tweakwise App, you will now get automatically focused on the search field and able to move through the list with the Tab key.
• Tweakwise App | Filtering on tags in the attribute module will now apply to the list view results, instead of just showing the labels.
• Tweakwise App | The list of returned dimensions for Google Analytics 4 reports has been expanded by including those available for the looking GA4 property. The five default dimensions we have standardized before are displayed on top, with the remaining ones sorted in ascending order.
• Tweakwise App | For specifically the search algorithm Category Match, all AI created synonyms were used in the publication of your instance, including pending and declined synonyms; leading to unexpected results. We fixed this and now, just like with the other search algorithms, in case of AI synonyms only accepted ones will be used.
• Tweakwise App | Added extra validation for two-ways synonyms upload so that the minimum amount of terms is two, in accordance with how validation works in the module itself.
• Tweakwise App | Fixed a bug with filter templates where a change to the quick actions in the list would not be saved if the changed item was moved to a different position before clicking save.
• Tweakwise App | We now do show the SKU-numbers in the list overviews in preview tabs of the following modules: Attributes, Merchandising Rules, Product Recommendations. The SKU column is not visible when the attribute is not configured as such (at attribute level). At the moment SKU's are not searchable.
• Tweakwise App | A small bug in relation to the behavior of default values of feed-attributes has been fixed. Now the default values are shown in the value distribution tabs, and the default values are covered in the publish.
• Tweakwise App | We updated the feedimport to trim \n and \r characters in categoryId's. This was previously also done on other fields, and is now also implemented for this one.

Insights

• Tweakwise App | The Insight module has changed; the title on top has been removed because in some scenarios we showed up to three titles.
• Insights | We have added a new tab to the E-commerce Report with insightful information about revenue and costs. In this new tab, sourced by Google Analytics 4, you will find total revenue, total tax cost, total shipping cost, total refunds and a revenue breakdown chart.
• Insights | For the Task Usage Report we have changed the default page to provide a list off all the tasks with their runtime. This should prevent unnecessary switching between detail page and the overall task dashboard. In addition we have added a tooltip for this table to give details about the selected task.

Demoshop

• Demoshop | The item click event is now part of the tracking console in Tweakwise Demoshop. It is not fired for real to the Analytics API to avoid messing up the builder CTR statistics.
• Demoshop | AI profiles (personalization) have been updated. We added more explanation on the profiles when no data is showing. Now it can have a message telling something about a lack of data (as it is being generated still) or that you have to authenticate (login) in the App.
• Demoshop | Suggestions view is optimized by showing something when the group name was missing.
• Demoshop | A small bug was fixed where searching failed in cases where custom category-urls were invalid.

JavaScript

• Tweakwise JS | Recommendations for JavaScript now accept a new configuration option view with values either carousel (default) or grid that allows you to display the recommendation as either standard carousel (as you are used to it) or a simple items grid. You can customize these views per viewport in the products configuration object with (mobile|tablet|desktop)View.
• Tweakwise JS | We have added a new configuration property (experimental) for Search & Merchandising JS package: history. It can take up the values hash (default), query or none and its purpose is to configure in what way data is saved in the URL. The value query omits the hash and saves the state as a standard query in the URL, e.g. /page?tn_p=2. With this setting, pagination controls will also become anchor links which may have some advantages for SEO. As a consequence both hash and query now allow for navigating in your browser history back and forth for each navigation/facet change you make (previously only navigating back was possible).
• Tweakwise JS | A title attribute has been added to the images which makes the image more accessible, as part of web accessibility standards.
• Tweakwise JS | As the order of suggestion groups will be handled by a new module (June 3rd), the layout configuration for Suggestions JS has been retired. The suggestions groups will now respect the order as set up in the new Suggestions module, i.e. how they come in the Frontend API.

Plugin Studio

• Plugin Studio | The Product Tile Editor has been expanded with a new Rating Element. You can customize height and colors, link to a property that has a numeric value from 0 to 5 and this will then display on your product tile.
• Plugin Studio | Added the history setting (experimental) to Search & Merchandising in the Plugin Studio.