UPDATE: MAY 5 2015
Please note that the content in this article focuses on a legacy version of the iPerceptions code, and as such may no longer be applicable. To learn more about our Universal Code, please check out this section of our support forum, as well as this section for more information about implementing the Universal Code.
Many users want to test their code placement before pushing the scripts to their live, or "production" environment. To do so successfully requires that the location you're testing have access to the internet. The location doesn't have to be publicly accessible, but it does need to be "exposed".
The invitation logic and all the survey information is contained on iPerceptions's servers, not hosted on the user's local machine. To be successfully invited, a query needs to go from the test page, to the iPerceptions' servers, and back again. If there is no connection between the test location (i.e. your stuff) and the internet (i.e. our stuff), then any testing you're attempting will fail.
Further, please note that the survey cannot be tested on localhost in IE or Chrome (Firefox and Safari do not have this issue). As well, please note that the file: protocol (the default used when a file is double-clicked in Windows Explorer) should be completely avoided.