Customer Feature Requests

Today the QA process is still time consuming for the client team and the clients. Would it be possible to automatize the QA process - for delegated experimentations to start with - considering that: We shall have a comprehensive brief with the Trello form (campaign description + trackers + audience + mockups) Hypothesis field shall be filled in by clients

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.

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.

Since the “Save” CTA was raised to the level of the first stage, the tag is reloaded upon click. Is it necessary to reload the tag again when choosing the QA mode?

Problem: IP based QA testing is very troublesome for our team. I wish to have more easier and faster access to QA of a test. Perhaps you can rethink the QA process. A preview link would be sufficient to review a test, regardless the IPs or cookie setting of a team member.

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.

I would like the ability to create a sharable QA link that can be used by multiple people, not just one time use.

I would like to have an option to hide the console logs that AB Tasty is logging in the browser. Currently, all users can see what variation and what experiments are going on, which is not ideal. It would be great if there was a way to hide this information from the console.

Client Cosentino complained about the fact that the "Paused QA" status was available anymore and they really did not know how to put their campaign in QA (they thought they could do it only through the QA assistant now) and said they were confused when launching their campaign, if it was going to go live for real on or in QA. Especially in the dashboard: if you want to launch a campaign from the dashboard, you have no idea if you are launching it in QA or for real. They would like to have the QA Paused back.

If a client is activating the 1 visitor 1 test feature, the QA become very difficult. We would like the QA of the campaigns easier