Workarounds for QA automation machines
We have QA automation machines on our internal networks and I was wondering if there's a scalable way to exclude those machines from being served with experiments? Our team is concerned that the scripts will break when experiments are launched. Does anyone have a good way of handling this?
Alternatively, if no user agent is present but they share a common set of static of IP addresses, you could use IP targeting(if available to you)to prevent them from being added to the experiment that way as well.
The main idea is to find something unique about the automated QA machines that you can use to target off of. Once you identify what is unique you can use that in our Audience conditions to prevent them from being added to your experiments.