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.
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=22.214.171.124), it needs to be appended
to the end of the UR...
Have a straightforward test that involves using Target's geo-targeting.
"Audiences" has been set so that only visitors in 5 states should be
seeing the experiment, however, I received a complaint that visitors
from a state outside of the 5 is seeing the experiment. Because this
report is coming from a person who is in one of the 5 states (so would
be seeing the challenger) but has an IP outside of the 5 states - is it
valid to say that this person is seeing the experiment because the
person is p...