Customer Feature Requests

Current behaviour It is not possible to track nested keys using isDeclared statement when using the dataLayer custom tracking option and complete path to key Expected behaviour Ability to track nested keys with isDeclared statement using the path to the key, example: DL object { nested:{ key:'value' } } Expected AB Tasty configuration to trigger the tracking nested.key isDeclared

Its extremely challenging to verify action trackings are firing correctly in the QA assistant when new widget events (dwell time, scroll time) are constantly populating and pushing down all other events. I would like dwell time and scroll time tracking to be moved to a new tab. We actively use A/A tests (or dwell time as a key metric) and having multiple instances of these populate makes using the QA Assistant cumbersome and difficult to quickly verify the appropriate events are firing.

Suggestion: it would be amazing to set up a recurrence on countdown widgets. Currently, the best you can do is: setting-up a fixed deadline (e.g. December 6th) and hour. Let's imagine you'd like to put a countdown on PDPs to promote the Express Delivery option. Such as Only xx h xx min xx sec left to order and get delivered tomorrow. With a fixed cut-off hour. Currently if I want to manage this kind of things, I have to manually change every single day the due date attached to my countdown in the Editor. It would be awesome to chose "today" or "week day" etc. instead. So you can keep your campaign running without any break.

A client has reported that ARIA labels in our widgets, such as "your call to action" and "close dialogue," are being read by text-to-speech editors, which can lead to confusion for users relying on assistive technologies. Currently, these labels cannot be edited without modifying the HTML, which is not recommended.

It would be helpful to receive notifications when a scheduled test concludes, so we can promptly review and report on the results.

Hi team, is it possible for us to add the URL parameter QA option to all types of tests? Currently it's only available for AB and Patch tests but it's an easier and alternative option of QA'ing and clients like it.

Following the revamp of the editor, I've noticed some usability issues regarding the switch between navigation and edit modes: Lack of Clear Shortcut Indication: Previously, the "CTRL+M" shortcut was clearly displayed, making it intuitive for users to switch between edit and navigation modes. This functionality was especially valuable for those familiar with the editor. Its absence in the new design makes the transition less intuitive. Confusing Messaging: The current labels "Start Editing" and "Stop Editing" are not very clear for users. They don't effectively convey the functionality or the context of these modes, which could cause confusion. Suggestions for Improvement: Reintroduce the "CTRL+M" shortcut display in the UI to enhance usability and inform users of this convenient feature. Consider revising the labels "Start Editing" and "Stop Editing" to something more descriptive, such as "Enter Edit Mode" and "Exit Edit Mode." Let me know if you need further clarification or examples to elaborate on this feedback. Thank you.

I would like to have a more integrated solution that allows for a single pane of glass view by automatically feeding client-side data into the server-side. This would help in achieving a holistic view of experiments and data.

Mobile confirmation in QA mode cannot be debugged properly. When opening QA mode on mobile using a QR code, a login error is displayed repeatedly, and there are many cases where the QA mode does not start, possibly due to a cache issue. I would like this to be improved.

The long loading times when launching the editor and switching between steps are frustrating, so I would like this to be improved.