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"