NEW: Pagination options for Javascript

We have expanded the options regarding pagination in our Javascript implementation. Apart from paginating via page-numbers, which remains our default behavior, we have introduced two new options: infinite scroll and a load more button. If a customer lands on a paginated link (for example via a bookmark), we show a ‘load previous products’ on top in order to be able to paginate back. Both new ways are available for all existing and new implementations and can be triggered via a local javascript configuration or in Tweakwise App. See more: https://docs.tweakwise.com/docs/js-js-implementation-local-configuration#paginationtype

NEW: Dimensions Google Analytics 4 reports

With Universal Analytics (UA) being phased out last year (2023, July 1st) we implemented a Google Analytics 4 (GA4) module as its successor in Tweakwise App. As all of are customers are migrated in the meantime, we encountered some behavior we did not expect. Apparently, as GA4 is way more flexible in configuration than UA, customer reports can be set-up with some dimensions you can use to group and filter your data. And a lot of our customers do use it in this way. We updated our module so we are completely compatible with these configuration. So, if you have configured your GA4 property and dimension reports for example based on hostname or language, we can split your reports in Tweakwise App too. This means that there is no longer a requirement to have a one on one relation between storeview and Google-property. You can use one property for multiple storeviews and purposes.

Tweakwise App & Api

• It now is possible to enable a searchbox within a specific filter, which is configurable at filter-attribute-level. Through these settings you can turn on/off our so called in-filter-search and even set a 'placeholder' or 'no results' text. This feature is available through our Frontend API and works out of the box for Javascript implementations. Magento will follow soon. To test the feature, you can use our in App demoshop (after a successful publish).
• The tn_q parameter is now limited to the same 100 characters on every occasion. This parameter is used in Navigation Search, Facets, Products, Autocomplete and Suggestions.
• When trying to delete a featured product recommendation that is being used in a builder, it now will show the specific builders name upon preventing the deletion.
• In Merchandising>Templates and Merchandising>Builder, the connected tab will show full clickable pathnames to make it easier for finding (and browsing) corresponding categories and landing pages. The links will lead to the Catalog>Categories page, the selected item will be shown there and the category tree will also be opened to the corresponding path.
• The previously released improvements to other 'connected to' tabs are also now available in Catalogue > Products > Connected Categories and in in Filtering > Filtertemplates > Detailpage > Connected. It shows the full path and is clickable.
• We’ve added the API reference for the Analytics API to our documentation website, just like we have for the backend and frontend API. This should make it easier to do a server-side implementation of the Analytics API and track page views, purchases and searches that way. Feel free to take a look around: https://docs.tweakwise.com/reference/analytics-api-introduction
• The Analytics API contained a bug where it would return a 500 Internal Server error when a request with an empty request body was made. We now return a 400 Bad Request with a clear error message, as expected.
• You can now open the demo shop from the category module!!
• Our Backend API the /product call now includes optional search and paging parameters. This release also significantly enhances request performance, even if the optional parameters are not used.
• The filtertemplates detail pages in Tweakwise App have now paging & search functionality in order to make this module way faster than before. Some side effects are in place since: The quick filterbuttons on the right will no longer save on click, but only after clicking the button which saves the whole form. A few important notes:
• If you add filters to a template, it will always be added at last position(s). This mean in case of paging that after adding a new filter, you will automatically go to the last page where the newly added filter is. Paging is currently set at 50 items per page.
• If you change pages or search, it will not save the previous 'state'. So if you want to make changes in the filters and then search or use pagination, you have to save before doing that otherwise the changes will be lost.
• If you make any change and then accidentally (or on purpose) click away from the page - you will be warned of unsaved changes and asked to save before leaving.
• In this release we’ve made a minor tweak to the category selector in the app. Basically, it now prioritizes categories which start with the entered search term. This should make it easier to find the categories you are looking for compared to before where the categories were sorted only alphabetically. There was also a small bug that made is impossible to scroll through all the results. That’s now also fixed.
• In the filter statistics module it is possible to filter the results by usage in a specific category. If the ID of the category being filtered on was very large, then the results on the page would be as if no category filter got applied. This was confusing and has now been fixed.
• We have added direct links to entities on the property usage page. All property pages (feed, external, derived) now have clickable links on their ‘used’ tab. We also have added internal clickable linking to products and properties from multiple places in the app on occasions where this was still missing.

Javascript

• In our Suggestions JS we have added an identifying data-property to each suggestion group so that customers can target each if they wish. The values are ‘SearchPhrase’, ‘Category’, ‘FacetFilter’ and ‘Product’ and these are under the property ‘data-suggestion-type’. These data-properties can be used for styling customizations for example, as you now can target each property by itself.
• Suggestions JS now also listens to customer provided event listeners, and that is in two instances: when the suggestion container opens and when it closes. More information can be found here: https://docs.tweakwise.com/docs/js-suggestions-js-api-reference#on
• We've expanded the JS Implementation's settings in the App with ‘tn_parameters_except’ options. You can now configure these hidden exclusion filters for the search and lister page results.
• Fixed a bug where filters using the slider-settings could not be updated if the minimum value was 0.
• From now on some JS events will be fired with requests to our servers within the Javascript Recommendations plugin. In this way it is possible to hook into the plugin's life-cycle and, for example, inject more information to the product tiles. The following events will be fired: 'twn.request.started', 'twn.request.success' (with data payload), 'twn.request.failed', 'twn.request.completed'.
• We implemented a maximum number of showed categories in a category tree (facet tree; number already customizable in app), and after reaching this threshold (i.e. "Number of values"), showing a "Show more/less" button (as is the case with most other filters).
• We fixed a small bug when overriding translations.
• In this release we've fixed a bug in the Suggestions JS where incidentally nothing was shown for a search term even though our API did return some results.