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.

We’ve enhanced our search capabilities by embedding autocorrection directly into two key algorithms: Word Search and Fuzzy Search. This allows for smarter, more precise typo handling exactly where it's needed, without applying corrections globally for the majority of your Search funnel.

Like already possible in Exact Match and Exact Start it now is possible to configure the removal of punctuation marks in the configuration of a Search Word algorithm: ( ) Space, (/) Slash, (-) Hyphen, (,) Comma, (.) Period. These characters will be stripped from the search phrase before the word search algorithm executes, as can be observed in the search log of Tweakwise Demoshop.

📘

Autocorrect algorithm

Importantly, our original autocorrection algorithm remains available. You now have the flexibility to choose between global correction or targeted correction within specific algorithms, offering greater control and improved performance for complex search configurations.

Suggestions upgrades

• For category suggestions, we’ve made it possible to prioritize results exactly match the given search term. Whenever the search term exactly matches the name of a category, that category will be pushed to the top of the suggestions.
• Search phrase and Facet suggestions are now made insensitive to diacritics. So searching on 'cafe' will now also result in a suggestions like 'café au lait'.
• The same behavior has been applied to Category suggestions as well, more specifically: we ignore diacritics (special characters like éë). 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.

With the introduction of the new E-commerce Report in Tweakwise App > Insights, designed to provide comprehensive insights into your e-commerce performance, you gain a deeper understanding of user behavior and preferences through detailed search and click data. This report offers a detailed view of various metrics that are crucial for understanding customer behavior, optimizing marketing strategies, and enhancing overall business performance.

Here’s a breakdown of the key features and metrics included in the E-commerce Report, which uses both data from your Google Analytics 4 integration, as collected data by Tweakwise:

• Total Sessions: Displays the total number of sessions on your e-commerce site. This metric helps you understand the volume of traffic your site is receiving.
• Total Searches: Shows the total number of searches conducted on your site, providing insight into user engagement and interest in your products.
• Conversion Rate: Indicates the percentage of sessions that resulted in a purchase. This metric is crucial for assessing the effectiveness of your marketing and sales strategies.
• Click-Through Rate: Represents the ratio of item clicks to item views, often used for search or product listings.
• Total Active Users: Displays the number of unique users who actively engaged with your site. This helps in understanding the reach and engagement level of your site.
• No-Result Rate: Shows the percentage of searches that did not return any results. This metric can help identify gaps in your product offerings or search functionality.
• Total Revenue: Displays the total revenue generated from your e-commerce site. This metric is essential for tracking the financial performance of your online store.
• Most Clicked Position: Provides insights into the positions of search results that receive the most clicks from within a Builder. This can help optimize your search and product placement strategies.
• Top Searches: Lists the most frequent search queries on your site. Understanding what users are searching for can help in inventory management and marketing efforts.
• Searches Without Results: Identifies search queries that did not yield any results. This can highlight potential areas for product expansion or improvements in search functionality.
• Most Clicked Products: Displays the products that received the most clicks. This helps in identifying popular products and planning inventory accordingly.

This new E-commerce Report will give you a deeper understanding of user behavior and preferences through detailed search and click data. Optimize your marketing campaigns by analyzing click-through and conversion rates and identify gaps in product offerings and search functionality to improve user experience and satisfaction. We strongly believe that this will be a valuable tool in driving your e-commerce success.

In order simulate a full Google Analytics 4 eCommerce and Tweakwise event tracking flow, the Tweakwise Demoshop has been expanded with some nice options. On the topbar some extra icons were added to fake a real shopping experience, while product modals were extended with some button which interacts with these icons. Once you add a product to your (fake) wishlist, the heart-icon will get a notification and the wishlist will become accessible. Same applies for adding a product to your shopping cart. From within the shopping cart, it is even possible to simulate a purchase.

Simulating products to your wishlist, adding them to a shopping cart or even purchase them (not for real of course), will fire events to Google Analytics 4. A detailed and highly technical representation on what events are fired is visible under if you click the third icon on the topbar (see screenshot below). Events will also be fired if you for example scroll the list with products, if you view an item or simulate an action as mentioned above.

📘

Google Analytics 4

All events fired to Google Analytics 4 will be done to an isolated environment. This data will not be present nor harm your GA setup. The tracking log just shows which events need to be fired for a full GA 4 eCommerce and Tweakwise event tracking flow.

AI-profile information

As Tweakwise is collecting data from users, we are able to create so called profiles and offer every visitor a unique and personalized shopping experience. Personalization now can be configured in easy to understand Builder components like 'last viewed', 'previous bought' or 'personal products', but in order to take it a step further we need to understand what information is stored in a profile. Next to the old fashioned personalization profile matrix, we now do show a generated textual representation of the current profile you're browsing with. This will give you more context on why we recommend certain products for now, and could lead to better product recommendations in the future.

Redirects

Searchterms that result in a redirect now show a visual representation in the autocomplete as well as a banner indicating this on the result page itself. The goto-url of the redirect was already present in the corresponding suggestion endpoints.

• Backend API | New endpoints were created in order to manage the hidden filter/parameter settings.
• Backend API | We added a new endpoint to the Backend API to update an instance configuration. This way you can assign attributes as reserved characteristics.
• Frontend API | We've fixed the ordering of advanced attributes in navigation responses. In the app, you can order attribute values for use in facets. You can also extend your API response by including certain attributes with their values. The ordering of item attribute values in the navigation response did not match the ordering of attribute values in facets. That is now fixed.

Tweakwise App

• Tweakwise App | You can now create empty Feed attributes in the App! This makes it a lot easier for the customer to start importing non-product items when the item type attribute does not exist yet.
• Tweakwise App | Minor performance enhancements were made to Feed Import and Publish tasks, improving overall system responsiveness.
• Tweakwise App | We fixed validation on the derived replace attribute when configured as a personalization dimension in advanced settings. The check on maximum number of unique values was not working correctly which could result in a configuration which caused problems. This has been fixed and validation should work properly now.
• Tweakwise App | A bug in the attribute module is fixed. Creating a new item from the button didn't work anymore.
• Tweakwise App | We updated the existing error message that occurs when trying to import a feed where some attributenames contain html tags or html-encoded symbols. Like similar messages, it now also previews the first 10 issues and provides the option to download the full list of errors. These errors now also contain the itemid where the incorrect attribute name was found.
• Tweakwise App | Fixed a bug regarding the Builder. When a visual component (or another type of component) cannot be filled, we have a fallback to show a regular product instead on that spot. However, that product would get the row and col span of the visual that was supposed to be. It now has the default row and col span of 1.
• Tweakwise App | We've added the option to delete unused attributes in Tweakwise App > Catalog > Attributes, even if they do have values. This is for example useful for deleting external attributes that are no longer used but still have values due to something like Google Analytics 4.
• Tweakwise App | A new Google Analytics 4 report has been released. It's called 'Item Page Views' and it is only getting the events registered as an view_item event. In GA4 items are mainly implemented as products. So every proper GA4 implementation uses the view_item event for their product detail page views. The report preview is showing the first 20 results and shows in the title the amount of records. It is sorted by the amount of events.

Demoshop

• Demoshop | Visuals are now fully visible instead of cutting of parts of the images.
• Demoshop | The presentation of item_types that are not familiar are changed so it is better recognizable that it's a different type. We will now differentiate products, visuals and 'other'. The respective type will be shown as a label.
• Demoshop | Support for multiple fonts is added, and some minor styling issues are fixed.
• Demoshop | Inspecting your configured search algorithm has become more powerful in Demoshop. Instead of viewing the search algorithm results per item, you can now view the items and their scores per algorithm. To enable this view. Open a search page by choice and click on the select box on the top right corner where you can select how you wish to view the search results. The first option is a default lister page. The second option shows the search algorithm scores per item. And the third and new option shows the results per search algorithm!

JavaScript

• Tweakwise JS | You're now able to enable a sorting button for the mobile overlay. Once enabled in Tweakwise App > Plugin Studio > Search and Merchandising > Advanced, sorting will be visible in filter overlay on mobile.
• Tweakwise JS | For infinite loading and loading with button, the lifecycle events started, success, failed and completed are fired correctly.
• Tweakwise JS | Filters on top were expandable but not collapsible, this is now added with an extra state.
• Tweakwise JS | The behavior when returning to the lister page from the previous page has been improved. The result is that you are now scrolling to the top instead of the scroll restoration point. This only applies when visitor is not on the first page.
• Tweakwise JS | Fixed a bug that was ruining presentation of products with a col span bigger than 1 in JS Search & Merchandising on different screen sizes. If the width was higher than the number of columns in the products grid, the grid itself was broken. Now all scales correctly and is capped at maximum size.
• Tweakwise JS | Applied a fix to restore the scroll position to the top when pagination is configured as infinite or button and the page is not the first page.

Plugin Studio

• Plugin Studio | It is now possible to open the Demoshop with multiple fonts applied; very useful for showcasing examples that for example have different fonts for headers and texts.

Some advanced functionality which was previously only accessible via your Customer Success Manager has now become public, giving you more flexibility to setup your Tweakwise configuration and speed up time to market. Three options are added to the attributes module in Tweakwise App. You can find them at attribute level by clicking on the three dots and open the 'use as' modal from the contextual menu.

1. In order for Tweakwise to work correct, we need to have certain characteristics assigned. A characteristic has some specific meaning or context within Tweakwise, like for example an image or url. We do need that information in order to populate our API responses in a standardized manner. But as it is not always possible to have this already present in your import feed, it is hard to standardize this. Therefore, you now can 'tell' the system which property should act as a characteristic. At the moment you can assign SKU, Url, Image, Brand and Item Type.
2. The second option you can configure in this modal, is the option to enable an attribute as include or exclude parameter. These parameters can act as so called hidden filters, but in order to have them fully working it is necessary that all those values are calculated and present in the publication of your instance. Usually, filters are present on a filtertemplate and will be present in your publish for that reason. However, there might be situations where you do want to use that parameter (for example to show in stock products only), but do not want to have it available as a filter. You then need to make sure that the attribute is marked as an include or exclude parameter.
3. The final option is whether you want to have the attribute available in the API response of the item node. The item node is containing data used for building op your product tiles on your webshop. For example, you definitely want to show a review-rating on your product-card, but do not want to show your gross margins (while that information might be useful for other purposes in Tweakwise). Simply do not publish gross margin to your API response then, by not enabling it. The display name will be name on how the attribute shows up in the API. Be aware that adding too many attributes to your API response, might have impact on performance. We advice to stay under 15 attributes in total.

With our newest additions improvements to our Demoshop, we are (almost) fully compatible with all features Tweakwise has to offer. And that is important as we consider the Demoshop as point of truth. If you're experiencing an issue in your shop or environment, you should always check the Demoshop to determine whether the cause lies within Tweakwise or if there is something with the rest of your shop. Our latest improvement does allow you to configure a catalog language and use include and/or exclude parameters.

• First of all, our Demoshop has moved in Tweakwise App. You can no longer find it in the navigation bar on the left, but need to access it via a modal which can be opened from everywhere in the app. That modal can be triggered via the new button on the top of Tweakwise App.
• In the Demoshop modal, you now might get the option to choose between versions. The standard one is available to everyone, but if you have enabled Plugin Studio (useful for JS implementations), you can switch to the Javascript version of the Demoshop as well. This will showcase the exact version of your JS implementation, including look and feel and configured behavior you have done in Plugin Studio. However, for debugging purposes you need to access the standard version of the Demoshop. Do there is no option to switch, you'll open the standard version by default.

• More advanced options (which will be remembered by your browser for your specific Tweakwise instance) can be found under additional configuration. First notable setting is whether you want to make use of grouped products. This is a straightforward setting. By simply enabling a checkbox, the Demoshop will make use of the so called grouped endpoints of the Frontend API. The catalog language setting has everything to do with the behavior of search. If Tweakwise knows which language is requested, we can apply word transformations like plurals, verb conjugations and splits. All languages which are enabled for your Tweakwise instance, will be available here.
• The final two settings are related: include parameters and exclude parameters (previously also known as hidden filters). These parameters can be used for example if you want to readily filter certain pages on a property 'under water'. For example, if Tweakwise contains all products, regardless of stock status, you may want to filter out products without stock from your category pages. You can do this by using include and exclude parameters. This parameter needs to be added to the request. Without the technical knowledge on how to implement this on your webshop, it has been made way easier to reproduce the same settings and behavior in Tweakwise Demoshop.

To analyze the performance of your configuration, power our insights reports and support personalization, we capture key e-commerce events on your platform via our Tweakwise Event Tag. These are events such as search terms, product views, item clicks, add-to-carts, and purchases. As our Shopware integration is making use of our JavaScript solutions the item clicks event was already covered (by default), but now it is possible to enable sending in search actions, product views and purchases as well. The only thing you have to do, is enabling this feature in the frontend settings of the Shopware plugin. This works out of the box, no extra code is necessary.

Furthermore the Shopware plugin now does check settings in your instance-configuration, preventing you to enable certain options and features which are not in your plan.

📘

SW-Tweakwise 4.1.0

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