Thanks for your response, Daniel. Thanks for the qa=true tip, my team had something like that set up so I will definitely make more use of that in the future. I resolved the issue by setting up a mock experiment with 100% of traffic going to the challenger where a console log message would appear for users bucketed into the experiment. Using the same audience list, I was able to determine with the appended mbox override parameter that the geotargeting conditions functioned as expected. Eventuall...

Thanks for your response, Parit. I had gone over the article you referenced prior to you mentioning it, and was able to build a quick experiment that tested whether the appropriate states were seeing the test. I think one extremely important piece of information I did not find in the article was that in order to see what a visitor from a certain IP is seeing with the additional parameter, that additional parameter (mboxOverride.browserIp=60.234.0.39), it needs to be appended to the end of the UR...