Darkstar2 wrote:valerie wrote: Folks, it is all what I have already stated. Truly it is. These surveys are really cracking
down these days on amounts they will pay and blocking people that fail questions, speed
through their surveys, etc. You MUST keep these things in mind when completing surveys.
Thanks for the email Valerie.
Investigating this with the compliance and dev team at the moment. The main cause looks to be that members are incorrectly answering red herring questions, e.g.
From the list below, only click "I am definitely not a robot"...and members are clicking other options.
Although we're checking this thoroughly to be sure we don't have any UI or logic issues that are incorrectly flagging members.
Can you please pass along the following to Mark as well, what if people ARE actually answering those trap questions correctly, could there be other reasons why people are being banned unfairly ?
Try asking him about this. I am aware that LUCID (the provider of Samplicio surveys) has different callback statuses. If you screen out of a survey normally your status would be screenout, but LUCID clients also use other callbacks, such as QualityTerm. QualityTerm internally has several sub statuses and is not always for fraud or lack of attention but some clients use QualityTerm in the place of ScreenOut or for other reasons like you do not fit the requirements, already took survey, etc. So could ySense be logging all those QualityTerm returns as suspicious ? Many times on CS when taking Samp surveys, the final redirect was a QualityTerm when screening out and not qualifying, even though 100% of trap questions were answered correctly, some advertisers often misuse QualityTerm, could this have an impact on ySense receiving many false positives from their partners ? I don't know about other routers and what flags they return, but the principle would be the same, if a client misuses and returns back a wrong flag, those could be used against us, right ? Wrong ?
Thanks for your considered reply Darkstar.
We're compiling more cases of blocks or bans, to identify if there's a common cause that requires attention. Client callback statuses will be included as part of that - thankyou.
In the meantime, we'll continue to review member feedback on account blocks