Mitigating Bots in REDCap Surveys

For the next version of the study, you can also spot certain bots in your reports and data quality rules (left-menu) by creating a hidden question field on your first instrument/survey like so:

Learn about @ Action Tags and add hidden survey tag to hide the question from participants. Humans will not be able to see the hidden question, however, certain bots will answer the hidden question using some automated script.

For your version 3 project question, it is common that more bot entries have been inputted after the 383 records once they have found the public survey link. We cannot make a 100% determination for records that came in after that period that are bot responses and our teams do not have the bandwidth to make the determination, unfortunately. Mike was able to spot the 383 records due to rapid responses in a row within 5 minutes.  

We would say 2171-2188 has high potential for bot activity due to survey completion time all being completed at the same time by participants for 3 forms and consents in a row. The project manager most well-versed with the data will be able to determine if responses completed in x time with y data are bot responses. It's suggested to export reports in "Data Exports, Reports, and Stats" and check timestamps to completion etc.,

We would also suggest exporting out the logging survey timestamp (logging left menu) to check time to completion and page views: Virginia Living Well Registry V3 | REDCap (vcu.edu)