StatusSupport
Changelog
Tweakwise.comTweakwise AppContact
Back to All

Overall | Fixes and improvements (Aug 2026)

August 27th, 2026

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

📘

Delivery API | We changed how smart rankings are applied to facets. We now first apply the smart ranking to the entire filter template, and then determine which facets are relevant. Previously, we first determined whether a facet was relevant (based on percentage), and then sorted all relevant facets based on their smart index/score. Facets that fell beyond the 25 mark (configurable number of facets to show) were not even considered for display, although they could have had a higher smart index score. Although this update sounds fairly impactful, in practice only a few facets are usually affected on a given page.

📘

Delivery API | We've changed which facets count towards the 'maximum number of visible filters' setting on a filter template. Facets which were hidden by the 'Hide filter when only 1 option is available' setting counted towards the total number of visible filters. You could have 25 relevant filters, while only 19 showed because the rest were hidden by that option. Now, those hidden filters do not count towards the total and are ignored, meaning we'll always display up to the maximum number of visible filters, unless there really are not enough relevant filters.

Tweakwise App

  • Tweakwise App | Main error pages now have working 'Back'-buttons, so users can get back to the instance select instead of hitting dead ends.
  • Tweakwise App | When customer success manager data is missing or incomplete, dashboard no longer shows broken content.
  • Tweakwise App | As we had validation on incompatible GA4 metrics with certain dimensions in Tweakwise App and our API already, we have added validation on itemViewEvents being incompatible with itemListId and itemListName.
  • Tweakwise App | We have improved the performance of the publish in relation to the amount of blacklisted suggestions in your instance. When you have a lot of blacklisted suggestions you should see a significant improvement in publish time, up to 8 times faster.
  • Tweakwise App | Deleting instance languages in Tweakwise App > Settings now checks usage first, so blocked references stop accidental removal.
  • Tweakwise App | We added an extra warning in the feed import. When you import a feed with an unknown element, we skip it. Now we also show a warning that we did so.
  • Tweakwise App | We now do return a clear error message when you do not have the correct rights on a Google Analytics 4 report.
  • Tweakwise App | Fixed an issue where you were not able to delete a Filter Template in some cases.
  • Tweakwise App | Fast navigation from Plugin Studio to Insights no longer leaves the App stuck on Plugin Studio. This bugfix removes a frustrating stall during page switching and should make movement between areas feel much smoother and more reliable.
  • Tweakwise App | To prepare Filter Templates on integrating with upcoming App Agents, we needed to change the UX of the detail pages. We decided to remove the modal and integrate it within the page. Small update, big impact.
  • Tweakwise App | We fixed an issue for 'Category match algorithms' when you had both synonyms and conjugations enabled as options. This sometimes led to errors during the publish. We also made some performance improvements in this step.
  • Tweakwise App | Unfortunately, it seemed possible to import items with articlenumbers containing a ' in it. That caused issues in both our Backend API and Publish scripts. We now sanitize this special character in the id during import, while extra validations were added to our API's and publish.

Demoshop

  • Demoshop | The 'Search algorithms per tile' view that was previously only available for search pages is now also available for lister pages. Allowing you more insights in the impact different Boost & Bury rules have on your lister pages.
  • Demoshop | We did a small bugfix for the facet relevancy log. It didn't respect filter template translations, and instead sometimes showed the attribute URL name.