Bot detection

Keep your survey data relevant by filtering out spam responses

Bot submissions can sabotage your surveys. Bot fraud happens when automated programs fill surveys with random data, distorting your results and turning your valuable research inaccurate. That’s where bot detection becomes crucial. 

Bot detection helps you capture genuine insights from real people, not robots. This ensures your data reflects true customer sentiment, empowering you to make informed choices that drive success. 

Let’s see how to enable bot detection and keep your survey data relevant.

1. Click the settings icon in your survey.

2. Turn on the Bot detection toggle.

Once your survey starts receiving responses, the bot responses will be filtered and shown in a separate section.

Filtering bot responses

1. Navigate to the Results section of your survey.

2. Go to the Responses section.

3. Under the Flagged section, select the Spam filter. All the spam responses will be shown along with the reason why they were marked as spam.

If you find a spam response marked incorrectly, you can choose to whitelist the same.

Select a response to be whitelisted.

Click White list responses.

The white listed responses will be considered valid and included in the survey data analysis. In this way you can effectively manage survey data and steer clear of bot responses. 

Note

• Spam responses will not be considered in reports, overviews, and dashboards.
• Note: If you see email “opens” within minutes but no submissions, those opens may be generated by your organization’s email security scanner (safe-link/anti-phishing tools) that automatically loads email content. This does not indicate a real respondent opened the survey.
• If ‘Allow partial submission’ configuration is enabled, when a bot is detected while answering the first question embedded in an email share, the submission will not be recorded
• If opens are tracked but responses are not coming in, check whether your recipients’ email security is quarantining, filtering, or blocking the survey email after scanning. Ask your IT/admin team to review quarantine logs and allowlist the sender/domain used for survey emails.
• No integration, trigger, workflow or webhook would work for spam responses

Feel free to reach out to our community if you have any questions.