Customer Feature Requests

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

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.

QA panel needs to fix bug where it tells you the correct triggering criteria and why it matches or not. Most of the time when you are rejected it doesn't give enough information which is useless for diagnosing why a test's segment/targeting criteria may be wrong. See attached for example.

Generally I forgot the play QA mode after everything is done. And spent lots of times on links which I got from share links button with paused mode. So If have not started the QA env share link button should not be enabled.

The cookie option is effective but requires non technical users to know how to target a specific cookie and clear it when they're done with QA. The IP option works great a majority of the time for our team. When required to be in office and on VPN, this means sharing an IP with hundreds of other people and potentially displaying these experiences in QA with the rest of the company. A query string trigger can be applied in the trigger step of an experience but this means that to QA the experience, we actually have to set the tests as "Live" which can cause a frenzy for team members who know this experience shouldn't be live yet. Proposing that Query String is added to the QA parameters so that an experience can be gated to users who are given a url with a certain query string and this experience's status is "Live In QA", not "Live"

I would like to QA tests we run on pages deep within our conversion funnel. This is currently impossible since you have to pass through the prior funnel parts to get to that part (ie you cant just navigate to that step via url)

Good day Product team, I experienced a scenario recently, where I gave my QA tester "Creator" level access, ignorant of the nuance of how the play/pause restrictions were setup on your platform. I noticed that the QA user turned on the IP restriction in my test's QA module - and then the QA user enabled the QA assistant for desktop, which essentially published the test, as part of its native system function. However, when the user was done QAing, they ignorantly only turned off the IP restriction, not realizing the test should have been paused first. Which, because they could not un-publish the test, opened the experiment up to actual user traffic. I caught this relatively quickly and paused the test, but when I investigated what happened with the QA user. I obviously discovered she was not able to pause the test, given her user role (which I corrected). But again for her - the button, simply wasn't interactable. But given the fact that she is still able to publish the test by engaging with the QA assistant, there needs to be something that also un-publishes the test whe nthey are done. I wonder if maybe, if you add an alert or something that detects that a user is trying to disable the IP restriction, while the test is still live, so it warns or even automatically pauses the test as a failsafe, to ensure that no external traffic begins accessing the test. I would appreciate this feature. Thank you.