Has this been enabled? We're interested in having a Survey123 form as part of a public-facing website, and the previous website's crowdsourcing efforts resulted in a lot of bot junk.
We are still examining this. In your previous experiences, were you able to tell if the bot junk was coming via the form page or from direct submissions to the form's submission endpoint (in ArcGIS terms, the feature layer's Service URL)?
I wasn't involved in the previous website, but received this info from a colleague:
"I think that most of the spam was coming from the 'contact us' form (which does not require sign-in). We were also getting spam submissions for PADDD events, which does require log in."
The Survey123 form would be for reporting these events.
Thanks for providing the information. It seems strange that the from that required a login was also getting spam. It seems possible that while the web page a person used to fill in the form was password protected, the submission endpoint (web page/resource that received the form's data) was not. CAPTCHA would not necessarily helped if this was the case - it's concerned with checking for the page that people use to fill out the form.
Ya for my case we are publishing a document to the public and my supervisors in the government want to have a captcha so as to prevent any bot use. The survey will be posted on a government website so they are concerned about bot usage
The new EU Regulation regarding the gathering of personal data (https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679) means we now have to add captcha to every public survey which collects nominative information.
Addin a captcha, regardless of how effective it is, will be mandatory for such surveys.