![]() (Although a user can add a survey flow branch to kick the respondent out of the survey based on the likelihood of them being a bot.) This requires no interaction from the respondent, but will not block them from proceeding if they are indeed a bot. On the other hand, bot detection uses reCAPTCHA V3 to flag the response with the likelihood of it being taken by a bot. The Captcha question requires the respondent to successfully interact with it and complete the proposed challenge in order to proceed. Qtip: Although the Captcha question and bot detection both use Google reCAPTCHA technology, how they use it is very different. Every response is rated on the probability that the respondent was a bot, which you can then use to filter out data or build reports. Bot Detectionīot detection allows you to track which responses are likely bots by adding a field to each response called Q_RecaptchaScore. However, in order to set up logic based on this field (such as screening out possible bots), you must add this embedded data field to your survey flow. You can report on or analyze Q_BallotBoxStuffing without adding it to the survey flow. If true (1), it means the response is likely a duplicate. Here’s how you interpret this field: Embedded Data Field Name When you select Continue survey and set embedded data field, respondents will not be sent out of the survey, but their response will be recorded and be assigned a value under the field Q_BallotBoxStuffing. Qtip: Save this step for when you are done setting up your survey! You can enable Prevent multiple submissions, Bot detection, Security scan monitor, and RelevantID all in the same survey. You can also prevent email scanning software from inadvertently submitting a survey response to begin with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |