<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id><journal-id journal-id-type="publisher-id">jmir</journal-id><journal-id journal-id-type="index">1</journal-id><journal-title>Journal of Medical Internet Research</journal-title><abbrev-journal-title>J Med Internet Res</abbrev-journal-title><issn pub-type="epub">1438-8871</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v28i1e88838</article-id><article-id pub-id-type="doi">10.2196/88838</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Battling the Bots and Defending Against Fraudulent Responses in an International Community-Engaged Web-Based Survey With People Living With Long COVID: Methodological Study</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>McDuff</surname><given-names>Kiera</given-names></name><degrees>BSc (Hons) Kin, MScPT</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Su</surname><given-names>Tai-Te</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Brown</surname><given-names>Darren A</given-names></name><degrees>OBE, BSc, MSc, MRes, FCSP</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Martin</surname><given-names>Jessica M</given-names></name><degrees>BSc, MSc</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Chan Carusone</surname><given-names>Soo</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>O'Connell</surname><given-names>Sarah</given-names></name><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>O'Donovan</surname><given-names>Imelda</given-names></name><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>St. Clair-Sullivan</surname><given-names>Natalie</given-names></name><degrees>PhD, PT</degrees><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Townsend</surname><given-names>Liam</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff8">8</xref><xref ref-type="aff" rid="aff9">9</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Goulding</surname><given-names>Susie</given-names></name><xref ref-type="aff" rid="aff10">10</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kelly</surname><given-names>Mary</given-names></name><degrees>PT</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>McCorkell</surname><given-names>Lisa</given-names></name><degrees>MPP</degrees><xref ref-type="aff" rid="aff11">11</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Wei</surname><given-names>Hannah</given-names></name><degrees>BComp</degrees><xref ref-type="aff" rid="aff12">12</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>O'Hara</surname><given-names>Margaret</given-names></name><xref ref-type="aff" rid="aff13">13</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Soares</surname><given-names>Leticia</given-names></name><xref ref-type="aff" rid="aff11">11</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Avery</surname><given-names>Lisa</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff14">14</xref><xref ref-type="aff" rid="aff15">15</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bannan</surname><given-names>Ciaran</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff8">8</xref><xref ref-type="aff" rid="aff9">9</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bergin</surname><given-names>Colm</given-names></name><degrees>MB, MD</degrees><xref ref-type="aff" rid="aff8">8</xref><xref ref-type="aff" rid="aff9">9</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Harding</surname><given-names>Richard</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Nathanson</surname><given-names>Julia</given-names></name><degrees>BA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Solomon</surname><given-names>Patricia</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff16">16</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Cheung</surname><given-names>Angela M</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff17">17</xref><xref ref-type="aff" rid="aff18">18</xref><xref ref-type="aff" rid="aff19">19</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Vera</surname><given-names>Jaimie</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff20">20</xref><xref ref-type="aff" rid="aff21">21</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>O'Brien</surname><given-names>Kelly K</given-names></name><degrees>BSc, BScPT, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff17">17</xref><xref ref-type="aff" rid="aff22">22</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Physical Therapy, Temerty Faculty of Medicine, University of Toronto</institution><addr-line>160-500 University Avenue</addr-line><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff2"><institution>School and Graduate Institute of Physical Therapy, College of Medicine, National Taiwan University</institution><addr-line>Taipei</addr-line><country>Taiwan</country></aff><aff id="aff3"><institution>Chelsea and Westminster Hospital NHS Foundation Trust</institution><addr-line>London</addr-line><country>United Kingdom</country></aff><aff id="aff4"><institution>Long COVID Physio</institution><addr-line>London</addr-line><country>United Kingdom</country></aff><aff id="aff5"><institution>McMaster Collaborative for Health and Aging, McMaster University</institution><addr-line>Hamilton</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff6"><institution>Long COVID Advocacy Ireland</institution><addr-line>Dublin</addr-line><country>Ireland</country></aff><aff id="aff7"><institution>Cicely Saunders Institute, Florence Nightingale Faculty of Nursing Midwifery and Palliative Care, King's College London</institution><addr-line>London</addr-line><country>United Kingdom</country></aff><aff id="aff8"><institution>Department of Infectious Diseases, St. James's Hospital</institution><addr-line>Dublin</addr-line><country>Ireland</country></aff><aff id="aff9"><institution>Department of Clinical Medicine, Trinity College Dublin, St. James's Hospital</institution><addr-line>Dublin</addr-line><country>Ireland</country></aff><aff id="aff10"><institution>COVID Long Haulers Support Group</institution><addr-line>Cambridge</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff11"><institution>Patient-Led Research Collaborative</institution><addr-line>Oakland</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff12"><institution>Patient-Led Research Collaborative</institution><addr-line>Ottawa</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff13"><institution>Long Covid Support UK</institution><addr-line>Birmingham</addr-line><country>United Kingdom</country></aff><aff id="aff14"><institution>Department of Biostatistics, Princess Margaret Cancer Centre, University Health Network</institution><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff15"><institution>Dalla Lana School of Public Health, University of Toronto</institution><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff16"><institution>School of Rehabilitation Science, Faculty of Health Sciences, McMaster University</institution><addr-line>Hamilton</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff17"><institution>Institute of Health Policy, Management and Evaluation (IHPME), Dalla Lana School of Public Health, University of Toronto</institution><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff18"><institution>Department of Medicine, Temerty Faculty of Medicine, University of Toronto</institution><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff19"><institution>Department of Medicine, University Health Network</institution><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><aff id="aff20"><institution>Department of Global Health and Infection, Brighton and Sussex Medical School, University of Sussex</institution><addr-line>Brighton</addr-line><country>United Kingdom</country></aff><aff id="aff21"><institution>Brighton and Sussex University Hospitals NHS Trust, Royal Sussex Hospital</institution><addr-line>Brighton</addr-line><country>United Kingdom</country></aff><aff id="aff22"><institution>Rehabilitation Sciences Institute, University of Toronto</institution><addr-line>Toronto</addr-line><addr-line>ON</addr-line><country>Canada</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Mavragani</surname><given-names>Amaryllis</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Sinamo</surname><given-names>Joshua K</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Johnson</surname><given-names>Timothy</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Kelly K O'Brien, BSc, BScPT, PhD, Department of Physical Therapy, Temerty Faculty of Medicine, University of Toronto, 160-500 University Avenue, Toronto, M5G 1V7, ON, Canada, 1 (416) 978-0565; <email>kelly.obrien@utoronto.ca</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>23</day><month>7</month><year>2026</year></pub-date><volume>28</volume><elocation-id>e88838</elocation-id><history><date date-type="received"><day>09</day><month>12</month><year>2025</year></date><date date-type="rev-recd"><day>04</day><month>05</month><year>2026</year></date><date date-type="accepted"><day>03</day><month>06</month><year>2026</year></date></history><copyright-statement>&#x00A9; Kiera McDuff, Tai-Te Su, Darren A Brown, Jessica M Martin, Soo Chan Carusone, Sarah O'Connell, Imelda O'Donovan, Natalie St. Clair-Sullivan, Liam Townsend, Susie Goulding, Mary Kelly, Lisa McCorkell, Hannah Wei, Margaret O'Hara, Leticia Soares, Lisa Avery, Ciaran Bannan, Colm Bergin, Richard Harding, Julia Nathanson, Patricia Solomon, Angela M Cheung, Jaimie Vera, Kelly K O'Brien. Originally published in the Journal of Medical Internet Research (<ext-link ext-link-type="uri" xlink:href="https://www.jmir.org">https://www.jmir.org</ext-link>), 23.7.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.jmir.org/">https://www.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://www.jmir.org/2026/1/e88838"/><abstract><sec><title>Background</title><p>Web-based surveys involving self-reported questionnaires are vulnerable to fraudulent responses. Advancements in artificial intelligence and bots have introduced additional challenges to preventing and identifying fraudulent responses to online questionnaires.</p></sec><sec><title>Objective</title><p>This study aimed to describe our experiences with fraudulent responses, strategies for preventing and identifying fraudulent responses, lessons learned when conducting a web-based survey with adults living with Long COVID, and recommendations for web-based survey research.</p></sec><sec sec-type="methods"><title>Methods</title><p>The Long COVID and Episodic Disability Study is an international community-engaged study among adults living with Long COVID in Canada, Ireland, the United Kingdom, and the United States. We conducted a longitudinal web-based survey, with online administration of a self-reported questionnaire at 2 timepoints (Time 1 and Time 2), 1 week apart. We recruited through Long COVID community groups using social media, emails, and word of mouth. The survey was disrupted by fraudulent responses, including bots. To defend data integrity, we implemented the following strategies: (1) pausing our initial launch (Wave 1), (2) developing and implementing screening criteria to identify fraudulent responses, and (3) relaunching the web-based survey (Wave 2) with revised recruitment strategies and questionnaire design to prevent and identify fraudulent responses.</p></sec><sec sec-type="results"><title>Results</title><p>We received 4663 responses for Time 1 and 1281 responses for Time 2, of which we retained 798 of 4663 (17%) responses and 629 of 1281 (49%) responses. Strategies for preventing fraudulent responses included enabling survey protection features in survey software, shutting down compromised survey links, avoiding recruitment via public social media groups, and removing mention of a financial incentive from recruitment materials. Strategies for identifying fraudulent responses included monitoring response completion times, start and end time stamps, geolocation, and screening for suspicious email address characteristics and duplicates.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Our lessons learned fell into the following three areas: (1) survey-design and implementation to prevent and identify fraudulent and bot-generated responses, (2) recruitment strategies to mitigate the risk of disruption by bots, and (3) responding to disruptions caused by fraudulent and bot responses. We recommend the following tactics to prevent and mitigate the risks of fraudulent and bot responses when administering online web-based questionnaires: (1) review current literature and connect with researchers and Research Ethics Boards about strategies before launching, (2) invest in survey software with rigorous information security technology, (3) use bot-detection features available in survey software before launching, (4) design questionnaire items to identify bots and fraudulent actors, (5) tailor criteria for identifying fraudulent and bot responses to the characteristics of the target population, (6) avoid recruitment in public social media groups, (7) engage community leaders in tailored and targeted recruitment, (8) avoid advertising incentives, (9) shut down compromised links rapidly, (10) communicate with the Research Ethics Board about disruptions, and (11) combine automated and manual methods to identify potentially fraudulent responses on time.</p></sec><sec sec-type="registered-report"><title>International Registered Report Identifier (IRRID)</title><p>RR2-10.1136/bmjopen-2022-060826</p></sec></abstract><kwd-group><kwd>survey</kwd><kwd>questionnaire</kwd><kwd>online research</kwd><kwd>survey fraud</kwd><kwd>social media</kwd><kwd>artificial intelligence</kwd><kwd>bots</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Web-based surveys, defined as surveys administered via online platforms (such as Qualtrics [Qualtrics, LLC], SurveyMonkey [SurveyMonkey Inc], or REDCap [Vanderbilt University Medical Center]) [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref4">4</xref>], have become an increasingly popular and important study design [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. They may involve cross-sectional, observational cohort, or longitudinal study designs. Web-based surveys often involve recruitment through online platforms, including email or social media, and administration of online self-reported questionnaires for data collection [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. With online recruitment methods, participants may not directly communicate with researchers and may remain anonymous [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>].</p><p>Although the rising popularity of web-based surveys is attributable to the perceived benefits, there are also disadvantages to web-based surveys. Perceived benefits include that online recruitment and data collection may be more efficient than in-person, telephone, or postal mail-based methods and have the ability to reach diverse populations, including people living with disabilities [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. Online questionnaires are also relatively low-cost to administer [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. However, a disadvantage of web-based surveys is their vulnerability to fraudulent responses, especially if recruitment is conducted on social media [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Recruitment on social media is vulnerable to fraud as it involves a limitless pool of (mostly anonymous) potential participants and may involve limited interaction with researchers [<xref ref-type="bibr" rid="ref16">16</xref>]. Fraud may significantly impair data integrity and necessitate extensive and time-consuming data cleaning to protect the integrity of the collected data [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. Researchers must consider the limitations of web-based surveys alongside the strengths.</p><p>Different types of fraud can impact web-based survey studies. For example, (1) unique participant fraud, defined as individuals who access a survey multiple times intentionally (eg, to obtain compensation) or unintentionally [<xref ref-type="bibr" rid="ref20">20</xref>]; and (2) alias fraud, defined as a single individual using sophisticated techniques to conceal their identity and submit multiple responses to take advantage of participant incentives [<xref ref-type="bibr" rid="ref20">20</xref>]. Bots are an example of technology that can be applied to commit alias fraud. Bots are a form of automation scripts designed to execute tasks that require limited human intervention [<xref ref-type="bibr" rid="ref21">21</xref>]. Programmers customize automation scripts to perform automated tasks, such as completing surveys that offer incentives to participants or infecting computers with malware [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref22">22</xref>].</p><p>Bots pose unique threats to web-based survey research [<xref ref-type="bibr" rid="ref23">23</xref>]. They can rapidly and automatically complete surveys, creating a large volume of invalid data. Bots have disrupted web-based surveys in health services research across a variety of topics, including e-cigarette usage [<xref ref-type="bibr" rid="ref8">8</xref>] and psychology [<xref ref-type="bibr" rid="ref22">22</xref>], as well as in a range of populations, including Two-Spirit, lesbian, gay, bisexual, transgender, and queer and questioning communities and people living with HIV [<xref ref-type="bibr" rid="ref24">24</xref>]. These disruptions to health services research can impair data integrity, generate research that misrepresents the intended research population, and lead to interventions and treatments that are guided by skewed results [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. Furthermore, these disruptions impose time and financial costs on researchers in the form of additional hours cleaning data, rewriting surveys, and rerecruitment and may foster mistrust in research among research populations [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>].</p><p>Generative artificial intelligence (AI) has made it more challenging to identify bot-generated responses to online questionnaires [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref28">28</xref>-<xref ref-type="bibr" rid="ref30">30</xref>]. Research is emerging on the potential benefits of AI for health services research, such as enhanced accuracy of data analysis and optimization of resources through efficiency [<xref ref-type="bibr" rid="ref31">31</xref>]. However, generative AI has disrupted previously effective means of identifying bot-generated responses to online questionnaires. Before recent advancements in generative AI, bots tended to follow a consistent and identifiable pattern when responding to web-based surveys (such as gibberish or irrelevant answers to open-ended questions, similarly formatted email addresses, and relatively short survey completion times), which could be used to differentiate their responses to web-based surveys from those of humans [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. AI-guided bots now can generate human-like responses to surveys, increasing the challenge of differentiating valid from invalid responses [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref28">28</xref>-<xref ref-type="bibr" rid="ref30">30</xref>]. As researchers have begun to experience disruptions to web-based surveys by AI-generated bots, methods are evolving to address and prevent this threat to data integrity [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. However, as bot technology and programming continue to evolve, there is a need for researchers to continue implementing adjustments to prevention and mitigation strategies [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>].</p><p>Bot and AI technology is rapidly evolving, posing complex challenges to maintaining data integrity for web-based surveys [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. Authors of a 2025 scoping review [<xref ref-type="bibr" rid="ref34">34</xref>] on identifying and counteracting fraudulent responses generated through online recruitment for health research concluded that existing research on strategies to mitigate fraud in online health research is insufficient to provide evidence-based guidance on the effectiveness of those strategies. While in-person, telephone, and postal mail-based survey methods may pose less risk of fraudulent responses, web-based surveys are important for reaching diverse and vulnerable populations, including people living with disabilities [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. As identified by Pozzar et al [<xref ref-type="bibr" rid="ref17">17</xref>], &#x201C;Development and testing of novel strategies to prevent and detect fraud is a research priority.&#x201D;</p><p>Our aim is to describe our experiences conducting an international community-engaged web-based survey with adults living with Long COVID in Canada, Ireland, the United Kingdom, and the United States. Specifically, we describe (1) our experiences with fraudulent and bot responses, (2) our iterative strategies to prevent and to detect fraudulent and bot responses, and (3) our lessons learned and recommendations to prevent and mitigate fraudulent and bot responses in web-based survey research.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design</title><p>We conducted a community-engaged longitudinal measurement study using a web-based survey study design involving electronic administration of 2 questionnaires, approximately 1 week apart, with adults living with Long COVID in Canada, Ireland, the United Kingdom, and the United States [<xref ref-type="bibr" rid="ref35">35</xref>].</p></sec><sec id="s2-2"><title>Context</title><p>The aim of the Long COVID and Episodic Disability Study is to advance the conceptualization and measurement of episodic disability among adults living with Long COVID to inform clinical practice, research, and policy [<xref ref-type="bibr" rid="ref35">35</xref>-<xref ref-type="bibr" rid="ref37">37</xref>]. This paper will focus on the second phase of this study, for which the aim was to describe health challenges experienced among adults living with Long COVID and assess the measurement properties of a self-reported disability questionnaire, the Episodic Disability Questionnaire (EDQ) [<xref ref-type="bibr" rid="ref35">35</xref>]. This phase of the study involved online recruitment of adults living with Long COVID in Canada, Ireland, the United Kingdom, and the United States and electronic administration (via Qualtrics) of 2 online questionnaires (Time 1 and Time 2) [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Respondents were asked to indicate their email address in the Time 1 questionnaire. We sent a Qualtrics link to a second online questionnaire (Time 2) to the email addresses provided at Time 1, 1 week after completing Time 1 [<xref ref-type="bibr" rid="ref1">1</xref>]. The questionnaires were estimated to require 30&#x2010;40 minutes and 10&#x2010;15 minutes to complete for Times 1 and 2, respectively.</p></sec><sec id="s2-3"><title>Participants</title><p>We included adults (aged &#x2265;18 years) living in Canada, Ireland, the United Kingdom, and the United States, who self-identified as living with Long COVID, with access to a computer, tablet, or smartphone and internet [<xref ref-type="bibr" rid="ref38">38</xref>]. We included individuals with suspected or confirmed acute COVID-19 irrespective of whether they were hospitalized or had a positive or negative SARS-CoV-2 test (polymerase chain reaction, antigen, or antibody) [<xref ref-type="bibr" rid="ref38">38</xref>].</p></sec><sec id="s2-4"><title>Initial Recruitment Strategy</title><p>On January 11, 2024, we launched recruitment of participants through online Long COVID community groups (COVID Long Haulers Support Group Canada [<xref ref-type="bibr" rid="ref39">39</xref>], Long COVID Advocacy Ireland [<xref ref-type="bibr" rid="ref40">40</xref>], Long COVID Physio [<xref ref-type="bibr" rid="ref41">41</xref>], Long Covid Support UK [<xref ref-type="bibr" rid="ref42">42</xref>], and Patient-Led Research Collaborative [<xref ref-type="bibr" rid="ref43">43</xref>]). Recruitment materials included a poster with a link or QR code to the Time 1 questionnaire, with contact information for the relevant research coordinator, social media posts, and an email to participants from an earlier phase of the study who agreed to be contacted about future research (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Information provided in the recruitment materials included a brief description of the study, the inclusion criteria, and indicated that a token of appreciation (a CAD $40 [CAD $1=US $0.72 as of June 15, 2026]) or equivalent currency, an Amazon electronic gift card) would be offered to participants upon completion of the Time 2 questionnaire (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Leaders of community groups circulated the study recruitment materials electronically within their networks on social media (including Facebook [Meta Platforms, Inc], Instagram [Meta Platforms, Inc], and X [X Corp]), via email, and word of mouth [<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. The social media pages of these groups, some of which were public (ie, no group membership required to view posts), have up to 25,000 followers. Research coordinators emailed the recruitment poster to participants from an earlier phase of the study who provided their contact information and indicated they were interested in participating in future phases of the study [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>].</p></sec><sec id="s2-5"><title>Initial Data Collection Procedures</title><sec id="s2-5-1"><title>Time 1</title><p>We administered an online questionnaire that included (1) the EDQ [<xref ref-type="bibr" rid="ref46">46</xref>]; (2) Long COVID Episodic Disability Questionnaire Supplement; (3) four criterion measures, including the World Health Organization Disability Assessment Schedule 2.0 [<xref ref-type="bibr" rid="ref47">47</xref>], Work and Social Adjustment Scale [<xref ref-type="bibr" rid="ref48">48</xref>], EuroQol 5-Dimensions 5-Levels [<xref ref-type="bibr" rid="ref49">49</xref>], and modified COVID-19 Yorkshire Rehabilitation Scale [<xref ref-type="bibr" rid="ref50">50</xref>]; (4) a sensibility questionnaire; and (5) a demographic questionnaire. If an individual participated in Time 1 (and completed &#x2265;50% of the questionnaire), the research coordinator (JMM) emailed a link for the Time 2 questionnaire, 1 week later (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). We downloaded responses from Qualtrics weekly [<xref ref-type="bibr" rid="ref1">1</xref>].</p></sec><sec id="s2-5-2"><title>Time 2</title><p>We administered an online questionnaire comprised of the EDQ and Long COVID Episodic Disability Questionnaire Supplement only. At the end of the questionnaire, participants were asked if they wanted to receive a token of appreciation. If they responded &#x201C;yes,&#x201D; they were asked to provide their name and email address to receive the token of appreciation (by email).</p></sec><sec id="s2-5-3"><title>Prelaunch Strategies for Prevention and Detection of Fraudulent Responses</title><p>We recognized the potential risk of receiving fraudulent (including bot-generated) responses to our online questionnaire and implemented the following prevention and detection strategies before launching the survey.</p></sec><sec id="s2-5-4"><title>Fraudulent Response and Bot Prevention</title><p>We enabled and used Qualtrics survey protection settings [<xref ref-type="bibr" rid="ref1">1</xref>], such as preventing multiple responses (a setting that prevents multiple submissions by placing a cookie in the browser of the participant), and reCAPTCHA scores (a question placed before the questionnaire asking the respondent to confirm they are a human).</p></sec><sec id="s2-5-5"><title>Fraudulent Response and Bot Detection</title><p>We monitored the rate and quality of incoming responses. Research coordinators (KM and JMM) manually assessed the quality of responses, one by one, for indicators of potential fraudulent responses (herein referred to as Human Review).</p></sec><sec id="s2-5-6"><title>Initial Launch of Recruitment: Wave 1</title><p>Refer to <xref ref-type="fig" rid="figure1">Figure 1</xref> for an overview of the timeline of events for survey implementation. We launched recruitment on January 11, 2024 (Wave 1). Despite our initial bot prevention and detection strategies, we received a rapid influx of fraudulent responses within the first 24 hours of launch. We closed the link to the Wave 1 (Time 1) questionnaire on January 12, 2024, while allowing responses that were in progress to be completed after we closed the link.</p><p>We contacted the Research Ethics Board (REB) at the University of Toronto and sought strategies to protect the integrity of the data and study. We contacted Qualtrics to explore options within the software to detect bot-generated (or other fraudulent) responses [<xref ref-type="bibr" rid="ref1">1</xref>]. We also conducted a revised literature review on recent strategies for the prevention and detection of fraudulent responses in web-based surveys.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Overview of the timeline of events for survey implementation.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e88838_fig01.png"/></fig></sec><sec id="s2-5-7"><title>Review of Responses</title><p>We refined our Human Review of the data to identify suspicious patterns and characteristics that were most likely indicative of fraudulent responses and/or bots, based on available literature and guidance [<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. This was time-sensitive, given that the Wave 1, Time 2 questionnaire was to be administered and completed 1 week later. The Human Review involved time-intensive and careful examination of participants&#x2019; reported names, email addresses, dates of survey completion, and survey completion duration, with particular attention to identifying repeating patterns and assessing the sensibility of free-text responses. The research coordinator (KM) removed Wave 1, Time 1 responses received before January 12, 2024, identified as likely fraudulent if (1) multiple consecutive responses were submitted with identical start and end dates (to the min), (2) responses did not correspond to a unique IP address, (3) less than half (&#x003C;50%) the questionnaire was completed, (4) responses did not correspond to a unique email address, (5) consecutive responses were submitted with a pattern of email addresses (eg, a repeating pattern of similar email addresses, such as &#x201C;firstname.lastname123@samedomain.com&#x201D;; non-English characters; random strings of letters and numbers), (6) responses were completed within an unrealistically short completion time (Time 1: &#x003C;20 min and Time 2: &#x003C;4 min), or (7) responses did not have a unique geolocation stamp (exported from Qualtrics) [<xref ref-type="bibr" rid="ref1">1</xref>]. We recognized that these criteria could potentially screen out some valid participants; however, the large volume of likely fraudulent responses necessitated an approach that maximized the detection of fraudulent responses.</p><p>We emailed the Wave 1, Time 2 link to email addresses for participants who passed the Human Review for Wave 1, Time 1 (original Time 2 link). In the meantime, we developed new bot prevention and detection procedures, new survey links, and a new recruitment strategy, submitted as an amendment to the REB at the University of Toronto for a wave of recruitment on January 30, 2024 (Wave 2). Our amendment was approved on February 15, 2024 (<xref ref-type="fig" rid="figure1">Figure 1</xref>).</p><p>We continued to examine the integrity of the data collected during Wave 1, Time 1. We iteratively revised our screening criteria, balancing our need to maximize detection of fraudulent responses with our aim to minimize the risk of removing valid participant data. For example, we found that our original cutoff of &#x2264;50% survey completion was overly sensitive (as determined by true participants reaching out when they did not receive the Time 2 link); we relaxed the threshold to &#x2264;80% completion for Time 1 and &#x2264;60% completion for Time 2. As we revised the criteria, we converted our Human Review into rules that were coded using R (Code Review; <xref ref-type="table" rid="table1">Table 1</xref>) [<xref ref-type="bibr" rid="ref52">52</xref>]. We applied our Code Review to the responses from Wave 1 (Time 1) and compared it with our Human Review. This comparison identified 35 participants who were originally screened out by the Human Review but were later identified as likely legitimate respondents by Code Review. We sent a new Wave 1 (Time 2) link to those 35 participants from Wave 1 (Time 1) on March 29, 2024 (<xref ref-type="fig" rid="figure1">Figure 1</xref>).</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Rules for identifying fraudulent responses across 2 time points in the web-based survey (Code Review).</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top">Wave and type of rule</td><td align="left" valign="top">Rules for identifying fraudulent responses in the Time 1 questionnaire</td><td align="left" valign="top">Rules for identifying fraudulent responses in the Time 2 questionnaire (administered 1 week later)</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="3">Wave 1</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Survey completeness</td><td align="left" valign="top">We removed responses: Rule 1.1: &#x2264;80% complete.</td><td align="left" valign="top">We removed responses: Rule 2.1: &#x2264;60% complete.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Inclusion criteria<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td><td align="left" valign="top">We removed responses: Rule 1.2: for which the respondent&#x2019;s self-reported age was &#x003C;18 years.<break/>Rule 1.3: submitted from outside of Canada, Ireland, the United Kingdom, or the United States.<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup></td><td align="left" valign="top">Not applicable.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Indicator of potential fraud</td><td align="left" valign="top">We removed responses: Rule 1.4: with a survey completion time (in s) identical to that of &#x2265;3 other responses as recorded by Qualtrics (Qualtrics, LLC).<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup><break/>Rule 1.5: that did not have a unique combination of survey start and end time stamps (to the min).<break/>Rule 1.6: for which the respondent&#x2019;s self-reported date did not align with the survey start date recorded by Qualtrics (allowing for a 1-d grace period for time zone differences and human error).<break/>Rule 1.7: &#x003C;20 minutes in duration.<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup><break/>Rule 1.8: with duplicate email addresses across responses.<break/>Email address rules&#x2014;unique to Wave 1 (Time 1).<break/>We removed responses: Rule 1.9: with strings of consecutive responses that shared the same email address format (eg, a pattern of letters plus digits) and identical email domains.<break/>Rule 1.10: if the participant&#x2019;s email address contained a string of &#x2265;5 digits.<break/>Rule 1.11: if the respondent&#x2019;s email address contained a mix of upper- and lower-case letters (excluding if only the first letter is capitalized).<break/>Rule 1.12: if the respondent&#x2018;s email address contained abnormal or special characters (eg, #, &#x2019;, %, $, &#x0026;, *, ?).<break/>Rule 1.13: if the respondent&#x2019;s name contained abnormal or special characters (eg, #, &#xFFFD;, %, $, &#x0026;, *, ?).</td><td align="left" valign="top">We removed responses: Rule 2.2: with a survey completion time (in s) identical to that of &#x2265;3 other responses as recorded by Qualtrics.<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup><break/>Rule 2.3: that did not have a unique combination of survey start and end time stamps.<break/>Rule 2.4: for which the respondent&#x2019;s self-reported date did not align with the survey start date recorded by Qualtrics (allowing for a 1-day grace period for time zone differences and human error).<break/>Rule 2.5: &#x003C;4 minutes in duration.<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup><break/>Rule 2.6: With duplicate email addresses across responses.<break/>Rule 2.7: if the email address did not correspond to an email address that had passed our checkpoints at Time 1 and been sent a link to Time 2 by the research coordinator.</td></tr><tr><td align="left" valign="top" colspan="3">Wave 2</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Survey completeness</td><td align="left" valign="top">We removed responses: Rule 1.1: &#x003C;80% complete.</td><td align="left" valign="top">We removed responses: Rule 2.1: &#x003C;60% complete.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Inclusion criteria<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td><td align="left" valign="top">We removed responses: Rule 1.2: for which the respondent&#x2019;s self-reported age was &#x003C;18 years old, per our inclusion criteria.<break/>Rule 1.3: submitted from outside of Canada, Ireland, the United Kingdom, or the United States, per our inclusion criteria.<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup></td><td align="left" valign="top">Not applicable.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Indicator of potential fraud</td><td align="left" valign="top">We removed responses: Rule 1.4: with a survey completion time (in s) identical to that of &#x2265;3 other responses as recorded by Qualtrics.<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup><break/>Rule 1.5: that did not have a unique combination of survey start and end time stamps (to the min).<break/>Rule 1.6: for which the respondent&#x2019;s self-reported date did not align with the survey start date recorded by Qualtrics (allowing for a 1-d grace period for time zone differences and human error).<break/>Rule 1.7: &#x003C;20 minutes in duration.<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup><break/>Rule 1.8: with duplicate email addresses across responses.<break/>Unique to Wave 2.<break/>We removed responses: Rule 1.14: that contained answers to any of the honeypot questions.<break/>Rule 1.15: for which the email address corresponded to an email address that completed the Wave 1 questionnaires.</td><td align="left" valign="top">We removed responses: Rule 2.2: with a survey completion time (in s) identical to that of &#x2265;3 other responses as recorded by Qualtrics.<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup><break/>Rule 2.3: that did not have a unique combination of survey start and end time stamps.<break/>Rule 2.4: for which the respondent&#x2019;s self-reported date did not align with the survey start date recorded by Qualtrics (allowing for a 1-d grace period for time zone differences and human error).<break/>Rule 2.5: &#x003C;4 min in duration.<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup><break/>Rule 2.6: with duplicate email addresses across responses.<break/>Rule 2.7: if the email address did not correspond to an email address that had passed our checkpoints at Time 1 and been sent a link to Time 2 by the research coordinator.<break/>Unique to Wave 2.<break/>We removed responses: Rule 2.8: that contained answers to any of the honeypot questions.<break/>Rule 2.9: for which the email address corresponded to an email address that completed the Wave 1 questionnaires.</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Screening for inclusion criteria (not necessarily for fraud).</p></fn><fn id="table1fn2"><p><sup>b</sup>We were only able to apply this rule to responses that were 100% complete. Complete responses were tagged with latitude and longitude coordinates by Qualtrics, enabling us to identify the respondent&#x2019;s geolocation. </p></fn><fn id="table1fn3"><p><sup>c</sup>This rule is based on the assumption that participants had an unlimited amount of time to complete the survey questionnaire (given the questionnaire&#x2019;s length and the flexibility to pause or take breaks). Because of this, the probability that 2 people would complete the survey in the same number of seconds is extremely low (nearly 0). Despite the low probability, 2 people can take the same amount of time due to coincidence. Therefore, we applied this rule with some flexibility (eg, it is acceptable for 2 people to have the same completion time). </p></fn><fn id="table1fn4"><p><sup>d</sup>Time cutoffs were established based on feedback from members of the research team who piloted the questionnaires. During piloting, it took between 30 and 40 minutes to complete the Time 1 questionnaire and between 10 and 15 minutes to complete the Time 2 questionnaire.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-5-8"><title>Relaunch of Recruitment With Additional Bot Prevention and Mitigation Strategies: Wave 2</title><p>We launched Wave 2 with new links to Times 1 and 2 questionnaires on February 19, 2024. We applied revised and new recruitment, data collection, and bot prevention and detection strategies as approved by the REB at the University of Toronto (<xref ref-type="fig" rid="figure1">Figure 1</xref>). Refer to <xref ref-type="table" rid="table1">Table 1</xref> for an overview of strategies to prevent and identify fraudulent responses in Waves 1 and 2.</p></sec></sec><sec id="s2-6"><title>Strategies for Preventing Fraudulent Responses</title><sec id="s2-6-1"><title>Modifications to Recruitment Procedures</title><p>We made the following changes to our recruitment strategy: (1) we created new, uncompromised Qualtrics links [<xref ref-type="bibr" rid="ref1">1</xref>]; (2) we stopped posting the links on public social media groups (community leads posted the links only in private social media groups for which new membership requests were monitored and validated by the community leads); (3) we removed mention of the token of appreciation from the recruitment poster and study materials; and (4) we administered gift cards at the end of the study, providing additional time for us to ensure responses met our final validity and quality checks for Time 1 and Time 2.</p></sec><sec id="s2-6-2"><title>Modifications to Data Collection Tools</title><p>We added 4 honeypot questions to both the Time 1 and Time 2 questionnaires for Wave 2. Honeypot questions are HTML-coded questions that are not visible to humans, but are detectable by bots (and, depending on implementation, potentially by screen readers) [<xref ref-type="bibr" rid="ref22">22</xref>]. Responses to honeypot questions are indicative of bots [<xref ref-type="bibr" rid="ref22">22</xref>]. In addition, we added a question to the Wave 2 (Time 2) questionnaire asking about the participants&#x2019; country of residence. This question was added so that it could be cross-referenced with the response to the same question at Time 1 (inconsistent responses between Time 1 and Time 2 may indicate a fraudulent response). We applied the same Qualtrics survey protection settings as we did for Wave 1 [<xref ref-type="bibr" rid="ref1">1</xref>].</p></sec><sec id="s2-6-3"><title>Modifications to Bot Detection Strategies</title><p>We modified our Code Review for Wave 1 to use the new bot prevention features added to the Wave 2 questionnaires (honeypots, repeat question between Time 1 and Time 2) (<xref ref-type="table" rid="table1">Table 1</xref>). For Wave 2, we modified the code to be less strict than for Wave 1 because we were more confident in the integrity of our data after having improved our recruitment strategy for Wave 2. The new fraud-detection code for Wave 2 was applied across both time points.</p></sec><sec id="s2-6-4"><title>Strategies for Identifying Fraudulent Responses</title><p>Our strategies for identifying fraudulent responses involved applying the final version of our Code Review to screen out responses that did not meet inclusion criteria (aged &#x003C;18 years, lived in a country other than Canada, Ireland, the United Kingdom, or the United States), responses that were &#x2264;80% complete for Time 1 and &#x2264;60% complete for Time 2, and likely fraudulent responses as identified by survey completion time stamps, alignment of self-reported and survey-recorded dates, and characteristics of email addresses (<xref ref-type="table" rid="table1">Table 1</xref>). We tested and refined the code to remove all potentially fraudulent responses. Details of the iterations of the Code Review are described in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. The final version of the Code Review is described in <xref ref-type="table" rid="table1">Table 1</xref>.</p><p>Some of the criteria in the Code Review were primarily aimed at removing incomplete responses or responses that did not meet our inclusion criteria (age and country of residence) and may or may not indicate fraudulent responses (<xref ref-type="table" rid="table1">Table 1</xref>). However, we applied all of our screening criteria together, and the criteria are not mutually exclusive.</p><p>For Wave 1, we applied 13 rules for Time 1 and 7 rules for Time 2 (<xref ref-type="table" rid="table1">Table 1</xref>). Five of the rules were unique for Wave 1 (Time 1) and were designed to identify suspicious email addresses and names because screening email addresses has been recommended as one of the most effective strategies for identifying bots [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. For Wave 2, we applied 10 rules for Time 1 and 7 rules for Time 2 (<xref ref-type="table" rid="table1">Table 1</xref>). We removed the rules for screening email addresses because we were more confident in the integrity of our data after having improved our recruitment strategy for Wave 2 and wanted to decrease our risk of excluding valid participants. Two of the rules in Wave 2, Times 1 and 2, were unique and were designed to detect responses to honeypot questions and to prevent repeat responses (intentional or accidental) from participants in Wave 1 (<xref ref-type="table" rid="table1">Table 1</xref>).</p><p>We recognized that it was possible for true participants to fail the Code Review. For example, due to memory issues commonly associated with Long COVID or human error, some participants may have unintentionally taken part in the study more than once. Since our aim was to remove all potentially fraudulent responses, we chose to accept this possibility. If participants contacted us via email to indicate they were awaiting the Time 2 link or expecting further results from the research, we cross-referenced their email addresses with the list of responses that we had screened out using the Code Review. If the participant seemed to be legitimate through correspondence and only failed minor aspects of the Code Review (eg, submitted 2 responses under the same email address), we would manually add that participant&#x2019;s response back into the dataset.</p></sec></sec><sec id="s2-7"><title>Ethical Considerations</title><p>The Long COVID and Episodic Disability Study was approved by the Health Sciences REB at the University of Toronto (protocol 41749) and the Saint James Hospital/Tallaght University Hospital Joint Research Ethics Committee (2024-Mar-34453445). The cover page of the Time 1 questionnaire included information about the purpose and rationale of the study, inclusion criteria, potential medical and social risks of participation, the voluntary nature of participation, the types of questions asked (questionnaires), and participants&#x2019; right to withdraw at any time. Both Time 1 and Time 2 questionnaires included an electronic eligibility and consent form. Eligible participants provided informed consent by clicking &#x201C;I agree to participate in this research study.&#x201D; Data were deidentified. Participants whose responses met the final validity and quality checks received a CAD $40 (CAD $1=US $0.72 as of June 15, 2026) or equivalent electronic gift card at the end of the study.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Overview</title><p>We describe the resulting number of responses (defined as having viewed the survey, consented to participate, and completed at least 1 item on the questionnaire) across Waves 1 and 2 and Times 1 and Time 2 questionnaire administrations (<xref ref-type="fig" rid="figure2">Figure 2</xref>).</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Flowchart of Waves 1 and 2 web-based survey responses.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e88838_fig02.png"/></fig></sec><sec id="s3-2"><title>Final Responses Retained</title><p>Across both waves, we retained 798 of 4663 (17%) responses for Time 1 and 629 of 1281 (49%) responses for Time 2 using our Code Review (<xref ref-type="fig" rid="figure2">Figure 2</xref>). Refer to <xref ref-type="table" rid="table2">Table 2</xref> for a detailed breakdown of the number of responses removed based on each rule of the Code Review for Waves 1 and 2. These rules were applied together and were not mutually exclusive, and they may not always indicate fraudulent or bot-generated responses. For instance, many responses in Time 1 were removed because of questionnaire incompleteness, represented by &#x2264;80% completion for Time 1 or &#x2264;60% completion for Time 2.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Results of responses removed by Code Review during Waves 1 and 2.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Rule no</td><td align="left" valign="top">Rule for identifying fraudulent responses</td><td align="left" valign="middle">Wave 1 (failed rule and removed), n (%)</td><td align="left" valign="top">Wave 2 (failed rule and removed), n (%)</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="4">Time 1<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup></td></tr><tr><td align="left" valign="top">1.1</td><td align="left" valign="top">&#x2264;80% complete.</td><td align="left" valign="top">769 (21)</td><td align="left" valign="top">441 (43)</td></tr><tr><td align="left" valign="top">1.2</td><td align="left" valign="top">For which the respondent&#x2019;s self-reported age was &#x003C;18 years, per our inclusion criteria.</td><td align="left" valign="top">646 (18)</td><td align="left" valign="top">44 (4)</td></tr><tr><td align="left" valign="top">1.3</td><td align="left" valign="top">Submitted from outside of Canada, Ireland, the United Kingdom, or the United States, per our inclusion criteria.<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup></td><td align="left" valign="top">309 (8)</td><td align="left" valign="top">33 (3)</td></tr><tr><td align="left" valign="top">1.4</td><td align="left" valign="top">With a survey completion time (min) identical to that of &#x2265;3 other responses as recorded by Qualtrics (Qualtrics, LLC).</td><td align="left" valign="top">858 (24)</td><td align="left" valign="top">Not applicable</td></tr><tr><td align="left" valign="top">1.5</td><td align="left" valign="top">That did not have a unique combination of survey start and end time stamps.</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">1.6</td><td align="left" valign="top">For which the participant&#x2019;s self-reported date did not align with the survey start date recorded by Qualtrics (allowing for a 1-d grace period for time zone differences and human error).</td><td align="left" valign="top">714 (20)</td><td align="left" valign="top">172 (17)</td></tr><tr><td align="left" valign="top">1.7</td><td align="left" valign="top">&#x003C;20 minutes in duration.</td><td align="left" valign="top">1160 (32)</td><td align="left" valign="top">365 (36)</td></tr><tr><td align="left" valign="top">1.8</td><td align="left" valign="top">With duplicate email addresses.</td><td align="left" valign="top">62 (2)</td><td align="left" valign="top">23 (2)</td></tr><tr><td align="left" valign="top">1.9</td><td align="left" valign="top">Strings of consecutive responses that shared the same email address format (a pattern of letters plus digits) and identical email domains.</td><td align="left" valign="top">794 (22)</td><td align="left" valign="top">Not applicable</td></tr><tr><td align="left" valign="top">1.10</td><td align="left" valign="top">If the participant&#x2019;s email address contained a string of &#x2265;5 digits.</td><td align="left" valign="top">155 (4)</td><td align="left" valign="top">Not applicable</td></tr><tr><td align="left" valign="top">1.11</td><td align="left" valign="top">If the participant&#x2019;s email address contained a mix of upper- and lower-case letters (excluding if only the first letter is capitalized).</td><td align="left" valign="top">317 (9)</td><td align="left" valign="top">Not applicable</td></tr><tr><td align="left" valign="top">1.12</td><td align="left" valign="top">If the participant&#x2019;s email address contained abnormal or special characters (eg, #, &#x2019;, %, $, &#x0026;, *, ?).</td><td align="left" valign="top">0 (0)</td><td align="left" valign="top">Not applicable</td></tr><tr><td align="left" valign="top">1.13</td><td align="left" valign="top">If the participant&#x2019;s name contained abnormal or special characters (eg, #, &#xFFFD;, %, $, &#x0026;, *, ?).</td><td align="left" valign="top">338 (9)</td><td align="left" valign="top">Not applicable</td></tr><tr><td align="left" valign="top">1.14</td><td align="left" valign="top">Where the respondent had answered honeypot questions.</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">1.15</td><td align="left" valign="top">With email addresses that corresponded to respondents who had completed Wave 1.</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">202 (20)</td></tr><tr><td align="left" valign="top" colspan="4">Time 2<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup></td></tr><tr><td align="left" valign="top">2.1</td><td align="left" valign="top">&#x2264;60% complete.</td><td align="left" valign="top">57 (8)</td><td align="left" valign="top">35 (6)</td></tr><tr><td align="left" valign="top">2.2</td><td align="left" valign="top">With a survey completion time (min) identical to that of &#x2265;3 other responses as recorded by Qualtrics.</td><td align="left" valign="top">104 (14)</td><td align="left" valign="top">50 (9)</td></tr><tr><td align="left" valign="top">2.3</td><td align="left" valign="top">That did not have a unique combination of survey start and end time stamps.</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top">2.4</td><td align="left" valign="top">For which the participant&#x2019;s self-reported date did not align with the survey start date recorded by Qualtrics (allowing for a 1-d grace period for time zone differences and human error).</td><td align="left" valign="top">55 (8)</td><td align="left" valign="top">24 (4)</td></tr><tr><td align="left" valign="top">2.5</td><td align="left" valign="top">&#x003C;4 minutes in duration.</td><td align="left" valign="top">54 (7)</td><td align="left" valign="top">28 (5)</td></tr><tr><td align="left" valign="top">2.6</td><td align="left" valign="top">With duplicate email addresses.</td><td align="left" valign="top">2 (&#x003C;1)</td><td align="left" valign="top">30 (5)</td></tr><tr><td align="left" valign="top">2.7</td><td align="left" valign="top">If the email address did not correspond to an email address that had passed our checkpoints at Time 1 and had been sent a link to Time 2 by the research coordinator.</td><td align="left" valign="top">451 (61)</td><td align="left" valign="top">Not applicable</td></tr><tr><td align="left" valign="top">2.8</td><td align="left" valign="top">If the self-reported country did not match the self-reported country from Time 1.</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">97 (18)</td></tr><tr><td align="left" valign="top">2.9</td><td align="left" valign="top">That contained answers to any of the honeypot questions.</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">0 (0)</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>Wave 1 (n=3638 responses) and Wave 2 (n=1025 responses).</p></fn><fn id="table2fn2"><p><sup>b</sup>This rule could only be applied to responses that were 100% complete. Complete responses were tagged with latitude and longitude coordinates by Qualtrics, enabling identification of respondent geolocation.</p></fn><fn id="table2fn3"><p><sup>c</sup>Wave 1 (n=734 responses) and Wave 2 (n=547 responses).</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>Our experiences conducting an international community-engaged web-based survey with adults living with Long COVID included substantial disruption caused by fraudulent responses and bots. Strategies implemented to prevent and mitigate the threat of fraudulent responses and bots included immediately closing our survey link and making swift amendments to our study protocol (including limiting our recruitment strategy and incorporating additional validity-check questions in our survey questionnaires). Concurrently, we established a set of rules to identify potentially fraudulent responses. Strategies for identifying fraudulent responses included monitoring response completion times, start and end time stamps, geolocation, and screening for suspicious email address characteristics and duplicates. We retained 17% of responses for Time 1 and 49% of responses for Time 2. While not all responses were removed because of fraudulent activity (many were removed because of incompleteness), we identified and removed a substantive number of responses attributed to suspected fraudulent activity. Furthermore, the 2 time points, 1 week apart, in our study design posed challenges as well as opportunities for preventing and detecting fraudulent responses.</p><p>Other research teams are experiencing similar challenges with fraudulent responses and bots when administering web-based surveys [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref54">54</xref>]. Although information about bots and web-based surveys is emerging for researchers to draw upon when designing web-based surveys, it is challenging for researchers to remain current given the rapidly evolving technology available to fraudulent actors, particularly in the context of generative AI [<xref ref-type="bibr" rid="ref28">28</xref>-<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref57">57</xref>]. This poses a risk to web-based survey research, as the rapid evolution and sophistication of the technology mean that research may continue to be vulnerable.</p><p>We outline lessons learned and recommendations for mitigating fraudulent- and bot-related disruptions and enhancing the integrity of web-based surveys. Our lessons learned can be categorized into (1) survey-design and implementation to reduce and identify fraudulent and bot-generated responses, (2) recruitment strategies to decrease the risk of web-based surveys being disrupted by fraudulent actors and bots, and (3) responding to disruptions caused by fraudulent actors and bots. We provide 11 recommendations (<xref ref-type="table" rid="table3">Table 3</xref>). We suggest the recommended strategies be used in combination to optimize the ability of research teams to prevent and identify bot-generated responses to web-based questionnaires.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Lessons learned and recommendations for researchers to prevent and identify fraudulent, including bot-generated responses to online web-based questionnaires.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="middle">Lessons learned and recommendations for researchers</td><td align="left" valign="top">Type of strategy (prevention or mitigation)</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Survey design and implementation to reduce and identify bot-generated responses</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Perform a review of the current literature, connect with other researchers performing web-based surveys, and liaise with the relevant Research Ethics Board about the newest threats and effective strategies before you design and launch an online survey.</td><td align="left" valign="top">Prevention</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Inquire about and evaluate the information security technology used by survey software when selecting the platform to administer your online survey (eg, REDCap [Vanderbilt University Medical Center], Qualtrics [Qualtrics, LLC], and SurveyMonkey [SurveyMonkey Inc]). Invest in survey software with rigorous information security technology.</td><td align="left" valign="top">Prevention</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Use bot-detection features embedded in survey software prior to launching web-based questionnaires. For example: (1) CAPTCHA<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup>, (2) prevention of multiple responses from the same IP address, and (3) software-specific bot-detection (information security) features.</td><td align="left" valign="top">Prevention</td></tr><tr><td align="left" valign="top">Design questionnaire items to identify bots and fraudulent actors. For example: (1) honeypots, (2) repeated questions, and (3) open-ended questions.</td><td align="left" valign="top">Mitigation</td></tr><tr><td align="left" valign="top">Tailor screening criteria to the characteristics of the target population (eg, cognitive differences, intellectual disabilities, age-related factors, and language barriers).</td><td align="left" valign="top">Mitigation</td></tr><tr><td align="left" valign="top" colspan="2">Recruitment strategies to decrease the risk of web-based surveys being disrupted by bots</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Avoid recruitment in public social media groups.</td><td align="left" valign="top">Prevention</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Engage community leads in tailored and targeted recruitment.</td><td align="left" valign="top">Prevention</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Avoid advertising incentives for completing web-based questionnaires.</td><td align="left" valign="top">Prevention</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Shut down corrupted links as quickly as possible.</td><td align="left" valign="top">Mitigation</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Communicate with the Research Ethics Board about the disruption and strategies to mitigate the impacts of the disruption.</td><td align="left" valign="top">Mitigation</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Use a combination of both manual (Human Review) and automated methods to screen for potentially fraudulent responses.</td><td align="left" valign="top">Mitigation</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>CAPTCHA: Completely Automated Public Turing test to tell Computers and Humans Apart.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s4-2"><title>Survey Design and Implementation to Reduce and Identify Bot-Generated Responses</title><p>Researchers should consider and explore information security features embedded in survey software that can assist in identifying bots and fraudulent actors before launching web-based questionnaires. For example, a CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) may be added to a web-based questionnaire to assess whether a computer user is a human and rule out less sophisticated bots [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref58">58</xref>]. Unfortunately, this is not a foolproof method, as there is ever-evolving technology to decrypt reCAPTCHA [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref58">58</xref>]. Our questionnaire was corrupted by bots despite the use of a CAPTCHA at initial launch. While survey software also may include settings to prevent multiple responses from the same IP address, IP addresses may be obscured intentionally or unintentionally through the use of virtual private networks [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref58">58</xref>]. We were able to use IP addresses and associated data on geolocation to identify potentially fraudulent responses in conjunction with other strategies. Survey software companies, such as Qualtrics [<xref ref-type="bibr" rid="ref1">1</xref>], also may have a bot-detection feature that analyzes responses and provides a score indicating how likely a response is to have been generated by a human. However, these bot-detection features are often moderately effective, can be costly, and should be used in combination with other strategies to protect the integrity of web-based questionnaires [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. We applied these available features during our Wave 2 relaunch, which may have contributed to the improved integrity of our data.</p><p>Researchers may design questionnaire items to identify potential bots and fraudulent actors. For example, honeypots are questions that are programmed to engage bot respondents while being invisible to human respondents [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. We added honeypots to our questionnaires in Wave 2; however, we did not receive any responses to these questions despite having other indicators of bots. Other research teams have had similar experiences, suggesting that most bots are now able to evade honeypots [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref59">59</xref>]. Including open-ended questions in web-based questionnaires provides opportunities to assess for potentially fraudulent responses, as researchers can check for identical or illogical responses to questions [<xref ref-type="bibr" rid="ref23">23</xref>]. In our study, a research coordinator used this method in our early Human Review efforts for screening. It was time-consuming to apply to such a large volume of responses, and at times, difficult to systematically define what constituted an illogical response. As generative AI improves, it may become even more difficult to discern between human- and bot-generated text responses [<xref ref-type="bibr" rid="ref15">15</xref>]. Given the vulnerabilities of each individual mitigation strategy, we recommend that these strategies be applied in combination. It is critical for researchers conducting web-based surveys to invest in survey platforms with rigorous and current cybersecurity measures to prevent breaches in survey integrity in the first place, as bot-detection strategies are ever-evolving in response to the evolving technology used to implement cyberattacks.</p></sec><sec id="s4-3"><title>Recruitment Strategies to Decrease the Risk of Web-Based Surveys Being Disrupted by Bots</title><p>Our experiences with this study taught us the importance of avoiding broad recruitment on social media, avoiding advertising incentives for completing web-based surveys, and engaging community leads in recruitment to reduce the risk of survey corruption by bots. Social media&#x2013;based recruitment has advantages, notably the potential to reach demographically and geographically diverse groups at a relatively low cost [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. However, fraudulent scams have become common on social media platforms [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. The large volume of fraudulent responses we received during Wave 1 likely was influenced by our use of broad social media recruitment and mention of compensation in recruitment materials [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. The number of fraudulent responses we received substantially decreased in Wave 2 when we only used private groups on social media (monitored by community leads) for recruitment and removed any mention of compensation from recruitment materials. Although avoiding advertising financial incentives may be a critical step to prevent bot-related disruptions to web-based surveys, it can also lead to less diversity among recruited participants [<xref ref-type="bibr" rid="ref60">60</xref>]. Future research could explore whether other strategies regarding incentives, such as (but not limited to) lottery-based incentives, are effective at minimizing fraudulent responses while maintaining diversity among recruited participants. However, this may introduce issues related to compensating participants unequally. Engaging community leads in our recruitment efforts also helped us target our recruitment to real adults living with Long COVID, as community leads had established relationships within this population and were able to vet potential respondents.</p></sec><sec id="s4-4"><title>Responding to Disruptions Caused by Bots</title><p>Despite our preventative efforts to reduce fraudulent responses, we experienced an unprecedented influx of responses to our Time 1 questionnaire. Bots will respond to surveys quickly and repeatedly once they have access to a link [<xref ref-type="bibr" rid="ref22">22</xref>]. When compromised, it is important to close links to web-based questionnaires as quickly as possible once they have been disrupted by bots [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. Despite our relatively quick response (&#x003C;24 h), we were left with thousands of responses to sort through, muddying the picture of which responses were valid.</p><p>We learned several strategies (both manual and automated) for screening data to identify bots and other potentially fraudulent responses. We adopted manual (Human Review) strategies, such as reviewing responses for suspicious names and email addresses, dates of survey completion, and duration of survey completion, that were similar to the approaches implemented by other research teams (<xref ref-type="table" rid="table3">Table 3</xref>) [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]. Manually screening for suspicious patterns in email addresses has been reported by other teams as one of the most effective [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref22">22</xref>], though time- and resource-intensive [<xref ref-type="bibr" rid="ref24">24</xref>], strategies for identifying bots. A unique aspect of our approach was that we developed code in R (Code Review) to replicate our Human Review [<xref ref-type="bibr" rid="ref52">52</xref>], while adding new automatic screening criteria. This allowed us to apply our screening criteria efficiently and in a standardized way across all responses we received. A combination of both manual and automatic screening is essential for identifying and removing bot-generated data [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref34">34</xref>].</p><p>When responding to disruptions caused by fraudulent and bot-generated responses, it is important to consider both the sensitivity (correctly detecting fraudulent responses) and specificity (correctly identifying true human respondents) of the methodology. It is difficult to achieve high levels of both sensitivity and specificity at the same time, as methods that improve one may reduce the performance of the other. Researchers should navigate the balance between the two, using strategies such as question design, checking survey completion times, and analyzing patterns in responses to classify fraudulent and true responses. In this study, we prioritized sensitivity. This increased our risk of removing true participant responses from the dataset. However, this was necessary to maximize the integrity of our dataset. Regular meetings with the community leads were invaluable for guiding our approach.</p></sec><sec id="s4-5"><title>Strengths and Limitations</title><p>Given that fraudulent- and bot-related disruptions to web-based surveys are common among research teams, it is important to document and communicate strategies to prevent and mitigate fraudulent responses [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. Strengths of our study included our documented methodical approach to identifying and handling bots and other potentially fraudulent responses. We systematically identified fraudulent responses using a rigorously developed set of automated rules (Code Review). Future research teams using web-based surveys may apply similar strategies. Another strength was our community-engaged approach to participant recruitment. The 5 community groups involved in this study were instrumental in troubleshooting our recruitment strategy, helping us shift to more targeted recruitment methods such as word of mouth, listservs, and private social media groups while still being able to reach our target population of adults living with Long COVID [<xref ref-type="bibr" rid="ref61">61</xref>].</p><p>This web-based survey involved 2 time points of questionnaire administration, 1 week apart. Therefore, when the Wave 1 (Time 1) questionnaire was disrupted by bots, we had to act fast to determine who to invite to complete the Wave 1 (Time 2) questionnaire with the original link (and screen out potentially fraudulent responses). Since the Human Review was manual and time-consuming, we iteratively revised our screening process several times before we developed our Code Review. By that time, we had already sent invitations to some likely fraudulent actors, as indicated by a greater number of Time 2 responses than invitations sent in Wave 1, and screened out some likely legitimate participants (<xref ref-type="fig" rid="figure2">Figure 2</xref>). As a result, we created a new link to access the Wave 1 (Time 2) questionnaire to capture as many of our legitimate participants as possible. In other ways, having the second time point to our web-based survey was valuable, allowing us to cross-reference responses between Time 1 and Time 2 to check the quality and effectiveness of our screening approaches (eg, consistency of country of residence between Time 1 and Time 2).</p><p>Although our findings are specific to our experiences with a 2-time point survey among people living with Long COVID, the lessons learned and recommendations from this work may be applicable to researchers conducting international community-engaged web-based surveys across other conditions. Strategies to prevent and mitigate fraudulent and bot-generated responses should be tailored to the intended research population using community-engaged approaches throughout. For example, we decided to avoid the use of logic-check strategies given the high prevalence of cognitive challenges among people living with Long COVID [<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]. For other populations, logic-check strategies may be useful and effective for identifying bots. The recommendations from this work build upon the recommendations of other teams and existing guidelines [<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref51">51</xref>].</p></sec><sec id="s4-6"><title>Implications for Future Research</title><p>It is likely impossible to prevent all risk of disruption by fraudulent actors and bots when using a web-based survey research design. However, best efforts should be made to reduce this risk and protect the integrity of data collected through web-based questionnaires. It is essential for computer science researchers and coders to develop effective and affordable anti-bot or anti-AI technology that can help protect web-based questionnaires from these threats. Researchers should regularly evaluate their bot-prevention and screening strategies throughout the study design, data collection, and screening. Researchers should also transparently report their process for ensuring data integrity when publishing results from web-based surveys and remain in close correspondence with the relevant REB throughout. Peer reviewers and journal editors should also consider whether and how researchers using web-based surveys have reported their methods for mitigating fraudulent responses during the peer-review process. In addition to threatening data integrity, bot-related disruption may influence the experiences of legitimate research participants. For example, in our study, we were at times delayed in sending invitations to the Time 2 questionnaires, as outlined in our study protocol, and in administering the token of appreciation to participants. It is possible that these disruptions could cause stress among participants or decrease their trust in researchers or community leads involved in recruitment. Therefore, researchers should address risks associated with bot infiltration and bot-screening processes with participants as part of informed consent processes.</p></sec><sec id="s4-7"><title>Conclusions</title><p>Despite the benefits of web-based survey study designs, the risk of fraudulent responses threatens the integrity of online research. Prevention and detection of fraudulent responses may become increasingly difficult because of bot- and AI-assisted fraud. Researchers should proactively plan for the prevention and detection of fraudulent responses, including bots. Their strategies should be well-documented and reported so that researchers can learn from one another and adapt their strategies to keep pace with technological advances in bots and AI. The strategies we have documented and recommended here may be useful to other research communities, but are also specific to our study and experiences. We recommend that research teams implement multiple bot-prevention and detection strategies that are systematic and suited to each study design and study population.</p></sec></sec></body><back><ack><p>We acknowledge the community organizations involved in this research, including the Patient-Led Research Collaborative, Long Covid Support, Long COVID Physio, COVID Long Haulers Support Group Canada, and Long COVID Advocacy Ireland. Artificial intelligence was not used in any portion of the paper generation.</p></ack><notes><sec><title>Funding</title><p>This study was supported by the Canadian Institutes of Health Research, Emerging COVID-19 Research Gaps and Priorities Funding Opportunity (funding research GA4-177753). KKO is supported by a Tier 2 Canada Research Chair in Episodic Disability and Rehabilitation (CRC-2022-00510).</p></sec><sec><title>Data Availability</title><p>The datasets generated or analyzed during this study are not publicly available because participants of this study did not give consent for their data to be shared publicly.</p></sec></notes><fn-group><fn fn-type="con"><p>KM drafted and revised this paper for publication. KM, JMM, KKO, and TTS contributed to data collection and study coordination. KM, JMM, and TTS contributed to data analysis. KKO and DAB were coprincipal investigators for this study. C Bannan, C Bergin, DAB, SG, MK, MO, LM, SO, IO, NSCS, LT, and HW comprised the core community team that guided the process of developing the mitigation and prevention strategies. TTS implemented the coding rules. KKO is the senior responsible author and takes responsibility for the content of this paper.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AI</term><def><p>artificial intelligence</p></def></def-item><def-item><term id="abb2">CAPTCHA</term><def><p>Completely Automated Public Turing test to tell Computers and Humans Apart</p></def></def-item><def-item><term id="abb3">EDQ</term><def><p>Episodic Disability Questionnaire</p></def></def-item><def-item><term id="abb4">REB</term><def><p>Research Ethics Board</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="web"><article-title>Homepage</article-title><source>Qualtrics</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="http://www.qualtrics.com">http://www.qualtrics.com</ext-link></comment></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="web"><article-title>Homepage</article-title><source>SurveyMonkey</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://tinyurl.com/yb8cu7ps">https://tinyurl.com/yb8cu7ps</ext-link></comment></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Harris</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>R</given-names> </name><name name-style="western"><surname>Thielke</surname><given-names>R</given-names> </name><name name-style="western"><surname>Payne</surname><given-names>J</given-names> </name><name name-style="western"><surname>Gonzalez</surname><given-names>N</given-names> </name><name name-style="western"><surname>Conde</surname><given-names>JG</given-names> </name></person-group><article-title>Research electronic data capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support</article-title><source>J Biomed Inform</source><year>2009</year><month>04</month><volume>42</volume><issue>2</issue><fpage>377</fpage><lpage>381</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2008.08.010</pub-id><pub-id pub-id-type="medline">18929686</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Harris</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>R</given-names> </name><name name-style="western"><surname>Minor</surname><given-names>BL</given-names> </name><etal/></person-group><article-title>The REDCap consortium: building an international community of software platform partners</article-title><source>J Biomed Inform</source><year>2019</year><month>07</month><volume>95</volume><issue>103208</issue><fpage>103208</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2019.103208</pub-id><pub-id pub-id-type="medline">31078660</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Griffin</surname><given-names>M</given-names> </name><name name-style="western"><surname>Martino</surname><given-names>RJ</given-names> </name><name name-style="western"><surname>LoSchiavo</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Ensuring survey research data integrity in the era of internet bots</article-title><source>Qual Quant</source><year>2022</year><volume>56</volume><issue>4</issue><fpage>2841</fpage><lpage>2852</lpage><pub-id pub-id-type="doi">10.1007/s11135-021-01252-1</pub-id><pub-id pub-id-type="medline">34629553</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Teitcher</surname><given-names>JEF</given-names> </name><name name-style="western"><surname>Bockting</surname><given-names>WO</given-names> </name><name name-style="western"><surname>Bauermeister</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Hoefer</surname><given-names>CJ</given-names> </name><name name-style="western"><surname>Miner</surname><given-names>MH</given-names> </name><name name-style="western"><surname>Klitzman</surname><given-names>RL</given-names> </name></person-group><article-title>Detecting, preventing, and responding to &#x201C;fraudsters&#x201D; in internet research: ethics and tradeoffs</article-title><source>J Law Med Ethics</source><year>2015</year><volume>43</volume><issue>1</issue><fpage>116</fpage><lpage>133</lpage><pub-id pub-id-type="doi">10.1111/jlme.12200</pub-id><pub-id pub-id-type="medline">25846043</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>R</given-names> </name><name name-style="western"><surname>Fielding</surname><given-names>N</given-names> </name><name name-style="western"><surname>Blank</surname><given-names>G</given-names> </name></person-group><article-title>Online research methods in the social sciences: an editorial introduction</article-title><source>The SAGE Handbook of Online Research Methods</source><year>2017</year><publisher-name>SAGE</publisher-name><fpage>1</fpage><lpage>16</lpage><pub-id pub-id-type="doi">10.4135/9781473957992.n1</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Guillory</surname><given-names>J</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>A</given-names> </name><name name-style="western"><surname>Murphy</surname><given-names>J</given-names> </name><name name-style="western"><surname>Bradfield</surname><given-names>B</given-names> </name><name name-style="western"><surname>Nonnemaker</surname><given-names>J</given-names> </name><name name-style="western"><surname>Hsieh</surname><given-names>Y</given-names> </name></person-group><article-title>Comparing Twitter and online panels for survey recruitment of e-cigarette users and smokers</article-title><source>J Med Internet Res</source><year>2016</year><month>11</month><day>15</day><volume>18</volume><issue>11</issue><fpage>e288</fpage><pub-id pub-id-type="doi">10.2196/jmir.6326</pub-id><pub-id pub-id-type="medline">27847353</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bybee</surname><given-names>S</given-names> </name><name name-style="western"><surname>Cloyes</surname><given-names>K</given-names> </name><name name-style="western"><surname>Ellington</surname><given-names>L</given-names> </name><name name-style="western"><surname>Baucom</surname><given-names>B</given-names> </name><name name-style="western"><surname>Supiano</surname><given-names>K</given-names> </name><name name-style="western"><surname>Mooney</surname><given-names>K</given-names> </name></person-group><article-title>Bots and nots: safeguarding online survey research with underrepresented and diverse populations</article-title><source>Psychol Sex</source><year>2022</year><volume>13</volume><issue>4</issue><fpage>901</fpage><lpage>911</lpage><pub-id pub-id-type="doi">10.1080/19419899.2021.1936617</pub-id><pub-id pub-id-type="medline">36439051</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Allsworth</surname><given-names>JE</given-names> </name></person-group><article-title>Invited commentary: recruiting for epidemiologic studies using social media</article-title><source>Am J Epidemiol</source><year>2015</year><month>05</month><day>15</day><volume>181</volume><issue>10</issue><fpage>747</fpage><lpage>749</lpage><pub-id pub-id-type="doi">10.1093/aje/kwv007</pub-id><pub-id pub-id-type="medline">25883156</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lei</surname><given-names>F</given-names> </name></person-group><article-title>Online recruitment for an online survey study: our experience of dealing with fraudsters</article-title><source>Appl Nurs Res</source><year>2024</year><month>12</month><volume>80</volume><fpage>151854</fpage><pub-id pub-id-type="doi">10.1016/j.apnr.2024.151854</pub-id><pub-id pub-id-type="medline">39617618</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sterzing</surname><given-names>PR</given-names> </name><name name-style="western"><surname>Gartner</surname><given-names>RE</given-names> </name><name name-style="western"><surname>McGeough</surname><given-names>BL</given-names> </name></person-group><article-title>Conducting anonymous, incentivized, online surveys with sexual and gender minority adolescents: lessons learned from a national polyvictimization study</article-title><source>J Interpers Violence</source><year>2018</year><month>03</month><volume>33</volume><issue>5</issue><fpage>740</fpage><lpage>761</lpage><pub-id pub-id-type="doi">10.1177/0886260517744845</pub-id><pub-id pub-id-type="medline">29295005</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Agans</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Schade</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Hanna</surname><given-names>SR</given-names> </name><name name-style="western"><surname>Chiang</surname><given-names>SC</given-names> </name><name name-style="western"><surname>Shirzad</surname><given-names>K</given-names> </name><name name-style="western"><surname>Bai</surname><given-names>S</given-names> </name></person-group><article-title>The inaccuracy of data from online surveys: a cautionary analysis</article-title><source>Qual Quant</source><year>2024</year><month>06</month><volume>58</volume><issue>3</issue><fpage>2065</fpage><lpage>2086</lpage><pub-id pub-id-type="doi">10.1007/s11135-023-01733-5</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Rasmussen</surname><given-names>KB</given-names> </name></person-group><article-title>Data quality in online environments</article-title><source>The SAGE Handbook of Online Research Methods</source><year>2017</year><access-date>2026-06-24</access-date><publisher-name>SAGE</publisher-name><fpage>38</fpage><lpage>54</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://tinyurl.com/2p4ju7x4">https://tinyurl.com/2p4ju7x4</ext-link></comment></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Caven</surname><given-names>I</given-names> </name><name name-style="western"><surname>Yang</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Okrainec</surname><given-names>K</given-names> </name></person-group><article-title>It&#x2019;s raining bots: how easier access to internet surveys has created the perfect storm</article-title><source>BMJ Open Qual</source><year>2025</year><month>06</month><day>1</day><volume>14</volume><issue>2</issue><fpage>e003208</fpage><pub-id pub-id-type="doi">10.1136/bmjoq-2024-003208</pub-id><pub-id pub-id-type="medline">40451296</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Harris</surname><given-names>ML</given-names> </name><name name-style="western"><surname>Loxton</surname><given-names>D</given-names> </name><name name-style="western"><surname>Wigginton</surname><given-names>B</given-names> </name><name name-style="western"><surname>Lucke</surname><given-names>JC</given-names> </name></person-group><article-title>Recruiting online: lessons from a longitudinal survey of contraception and pregnancy intentions of young Australian women</article-title><source>Am J Epidemiol</source><year>2015</year><month>05</month><day>15</day><volume>181</volume><issue>10</issue><fpage>737</fpage><lpage>746</lpage><pub-id pub-id-type="doi">10.1093/aje/kwv006</pub-id><pub-id pub-id-type="medline">25883155</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pozzar</surname><given-names>R</given-names> </name><name name-style="western"><surname>Hammer</surname><given-names>MJ</given-names> </name><name name-style="western"><surname>Underhill-Blazey</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Threats of bots and other bad actors to data quality following research participant recruitment through social media: cross-sectional questionnaire</article-title><source>J Med Internet Res</source><year>2020</year><month>10</month><day>7</day><volume>22</volume><issue>10</issue><fpage>e23021</fpage><pub-id pub-id-type="doi">10.2196/23021</pub-id><pub-id pub-id-type="medline">33026360</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Goodrich</surname><given-names>B</given-names> </name><name name-style="western"><surname>Fenton</surname><given-names>M</given-names> </name><name name-style="western"><surname>Penn</surname><given-names>J</given-names> </name><name name-style="western"><surname>Bovay</surname><given-names>J</given-names> </name><name name-style="western"><surname>Mountain</surname><given-names>T</given-names> </name></person-group><article-title>Battling bots: experiences and strategies to mitigate fraudulent responses in online surveys</article-title><source>Applied Eco Perspectives Pol</source><year>2023</year><month>06</month><volume>45</volume><issue>2</issue><fpage>762</fpage><lpage>784</lpage><pub-id pub-id-type="doi">10.1002/aepp.13353</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Buchanan</surname><given-names>EM</given-names> </name><name name-style="western"><surname>Scofield</surname><given-names>JE</given-names> </name></person-group><article-title>Methods to detect low quality data and its implication for psychological research</article-title><source>Behav Res Methods</source><year>2018</year><month>12</month><volume>50</volume><issue>6</issue><fpage>2586</fpage><lpage>2596</lpage><pub-id pub-id-type="doi">10.3758/s13428-018-1035-6</pub-id><pub-id pub-id-type="medline">29542063</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lawlor</surname><given-names>J</given-names> </name><name name-style="western"><surname>Thomas</surname><given-names>C</given-names> </name><name name-style="western"><surname>Guhin</surname><given-names>AT</given-names> </name><etal/></person-group><article-title>Suspicious and fraudulent online survey participation: Introducing the REAL framework</article-title><source>Methodological Innovations</source><year>2021</year><month>09</month><volume>14</volume><issue>3</issue><fpage>205979912110504</fpage><pub-id pub-id-type="doi">10.1177/20597991211050467</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><article-title>What is a bot? How do bots work?</article-title><source>FORTINET</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.fortinet.com/resources/cyberglossary/bot">https://www.fortinet.com/resources/cyberglossary/bot</ext-link></comment></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Storozuk</surname><given-names>A</given-names> </name><name name-style="western"><surname>Ashley</surname><given-names>M</given-names> </name><name name-style="western"><surname>Delage</surname><given-names>V</given-names> </name><name name-style="western"><surname>Maloney</surname><given-names>EA</given-names> </name></person-group><article-title>Got bots? Practical recommendations to protect online survey data from bot attacks</article-title><source>TQMP</source><year>2020</year><volume>16</volume><issue>5</issue><fpage>472</fpage><lpage>481</lpage><pub-id pub-id-type="doi">10.20982/tqmp.16.5.p472</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Xu</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Pace</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Threats to online surveys: recognizing, detecting, and preventing survey bots</article-title><source>Soc Work Res</source><year>2022</year><month>11</month><day>14</day><volume>46</volume><issue>4</issue><fpage>343</fpage><lpage>350</lpage><pub-id pub-id-type="doi">10.1093/swr/svac023</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bauermeister</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Pingel</surname><given-names>E</given-names> </name><name name-style="western"><surname>Zimmerman</surname><given-names>M</given-names> </name><name name-style="western"><surname>Couper</surname><given-names>M</given-names> </name><name name-style="western"><surname>Carballo-Di&#x00E9;guez</surname><given-names>A</given-names> </name><name name-style="western"><surname>Strecher</surname><given-names>VJ</given-names> </name></person-group><article-title>Data quality in web-based HIV/AIDS research: handling invalid and suspicious data</article-title><source>Field methods</source><year>2012</year><month>08</month><day>1</day><volume>24</volume><issue>3</issue><fpage>272</fpage><lpage>291</lpage><pub-id pub-id-type="doi">10.1177/1525822X12443097</pub-id><pub-id pub-id-type="medline">23180978</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chandler</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sisso</surname><given-names>I</given-names> </name><name name-style="western"><surname>Shapiro</surname><given-names>D</given-names> </name></person-group><article-title>Participant carelessness and fraud: consequences for clinical research and potential solutions</article-title><source>J Abnorm Psychol</source><year>2020</year><month>01</month><volume>129</volume><issue>1</issue><fpage>49</fpage><lpage>55</lpage><pub-id pub-id-type="doi">10.1037/abn0000479</pub-id><pub-id pub-id-type="medline">31868387</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Hallberg</surname><given-names>L</given-names> </name></person-group><article-title>Understanding survey bots and tools for data validation: strategies for identifying possibly fraudulent responses</article-title><source>The University of Kansas</source><year>2022</year><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://lifespan.ku.edu/news/article/2022/07/27/online-surveys-and-data-collection-tools">https://lifespan.ku.edu/news/article/2022/07/27/online-surveys-and-data-collection-tools</ext-link></comment></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hardesty</surname><given-names>JJ</given-names> </name><name name-style="western"><surname>Crespi</surname><given-names>E</given-names> </name><name name-style="western"><surname>Sinamo</surname><given-names>JK</given-names> </name><etal/></person-group><article-title>From doubt to confidence-overcoming fraudulent submissions by bots and other takers of a web-based survey</article-title><source>J Med Internet Res</source><year>2024</year><month>12</month><day>16</day><volume>26</volume><fpage>e60184</fpage><pub-id pub-id-type="doi">10.2196/60184</pub-id><pub-id pub-id-type="medline">39680887</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="web"><article-title>Guidance for mitigating fraud and safeguarding data integrity in online research</article-title><source>Centre for Research &#x0026; Innovation Support</source><year>2025</year><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://cris.utoronto.ca/guides/mitigating-fraud-online-research">https://cris.utoronto.ca/guides/mitigating-fraud-online-research</ext-link></comment></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>King-Nyberg</surname><given-names>B</given-names> </name><name name-style="western"><surname>Thomson</surname><given-names>EF</given-names> </name><name name-style="western"><surname>Morris-Reade</surname><given-names>J</given-names> </name><name name-style="western"><surname>Borgen</surname><given-names>R</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>C</given-names> </name></person-group><article-title>The bot toolbox: an accidental case study on how to eliminate bots from your online survey</article-title><source>J Soc Thought</source><year>2023</year><access-date>2026-06-24</access-date><volume>7</volume><issue>1</issue><comment><ext-link ext-link-type="uri" xlink:href="https://ojs.lib.uwo.ca/index.php/jst/article/view/14331">https://ojs.lib.uwo.ca/index.php/jst/article/view/14331</ext-link></comment></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lebrun</surname><given-names>B</given-names> </name><name name-style="western"><surname>Temtsin</surname><given-names>S</given-names> </name><name name-style="western"><surname>Vonasch</surname><given-names>A</given-names> </name><name name-style="western"><surname>Bartneck</surname><given-names>C</given-names> </name></person-group><article-title>Detecting the corruption of online questionnaires by artificial intelligence</article-title><source>Front Robot AI</source><year>2023</year><volume>10</volume><fpage>1277635</fpage><pub-id pub-id-type="doi">10.3389/frobt.2023.1277635</pub-id><pub-id pub-id-type="medline">38371744</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Muley</surname><given-names>A</given-names> </name><name name-style="western"><surname>Cheemalapati</surname><given-names>S</given-names> </name><name name-style="western"><surname>Muzumdar</surname><given-names>P</given-names> </name></person-group><article-title>The role of AI in epidemiological research: applications, benefits, and risks in modern public health</article-title><source>Asian J Med Health</source><year>2025</year><volume>23</volume><issue>6</issue><fpage>89</fpage><lpage>107</lpage><pub-id pub-id-type="doi">10.9734/ajmah/2025/v23i61246</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hohn</surname><given-names>KL</given-names> </name><name name-style="western"><surname>Braswell</surname><given-names>AA</given-names> </name><name name-style="western"><surname>DeVita</surname><given-names>JM</given-names> </name></person-group><article-title>Preventing and protecting against internet research fraud in anonymous web-based research: protocol for the development and implementation of an anonymous web-based data integrity plan</article-title><source>JMIR Res Protoc</source><year>2022</year><month>09</month><day>12</day><volume>11</volume><issue>9</issue><fpage>e38550</fpage><pub-id pub-id-type="doi">10.2196/38550</pub-id><pub-id pub-id-type="medline">36094806</pub-id></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ng</surname><given-names>WZ</given-names> </name><name name-style="western"><surname>Erdembileg</surname><given-names>S</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>JCJ</given-names> </name><name name-style="western"><surname>Tucker</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Tan</surname><given-names>RKJ</given-names> </name></person-group><article-title>Increasing rigor in online health surveys through the reduction of fraudulent data</article-title><source>J Med Internet Res</source><year>2025</year><month>08</month><day>21</day><volume>27</volume><fpage>e68092</fpage><pub-id pub-id-type="doi">10.2196/68092</pub-id><pub-id pub-id-type="medline">40840500</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Comachio</surname><given-names>J</given-names> </name><name name-style="western"><surname>Poulsen</surname><given-names>A</given-names> </name><name name-style="western"><surname>Bamgboje-Ayodele</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Identifying and counteracting fraudulent responses in online recruitment for health research: a scoping review</article-title><source>BMJ Evid Based Med</source><year>2025</year><month>05</month><day>20</day><volume>30</volume><issue>3</issue><fpage>173</fpage><lpage>182</lpage><pub-id pub-id-type="doi">10.1136/bmjebm-2024-113170</pub-id><pub-id pub-id-type="medline">39715631</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Brien</surname><given-names>KK</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>DA</given-names> </name><name name-style="western"><surname>Bergin</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Long COVID and episodic disability: advancing the conceptualisation, measurement and knowledge of episodic disability among people living with Long COVID - protocol for a mixed-methods study</article-title><source>BMJ Open</source><year>2022</year><month>03</month><day>7</day><volume>12</volume><issue>3</issue><fpage>e060826</fpage><pub-id pub-id-type="doi">10.1136/bmjopen-2022-060826</pub-id><pub-id pub-id-type="medline">35256450</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Brien</surname><given-names>KK</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>DA</given-names> </name><name name-style="western"><surname>McDuff</surname><given-names>K</given-names> </name><etal/></person-group><article-title>Conceptualising the episodic nature of disability among adults living with Long COVID: a qualitative study</article-title><source>BMJ Glob Health</source><year>2023</year><month>03</month><volume>8</volume><issue>3</issue><fpage>e011276</fpage><pub-id pub-id-type="doi">10.1136/bmjgh-2022-011276</pub-id><pub-id pub-id-type="medline">36863719</pub-id></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Brien</surname><given-names>KK</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>DA</given-names> </name><name name-style="western"><surname>McDuff</surname><given-names>K</given-names> </name><etal/></person-group><article-title>Episodic disability framework in the context of Long COVID: findings from a community-engaged international qualitative study</article-title><source>PLoS ONE</source><year>2025</year><volume>20</volume><issue>2</issue><fpage>e0305187</fpage><pub-id pub-id-type="doi">10.1371/journal.pone.0305187</pub-id><pub-id pub-id-type="medline">40014600</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Soriano</surname><given-names>JB</given-names> </name><name name-style="western"><surname>Murthy</surname><given-names>S</given-names> </name><name name-style="western"><surname>Marshall</surname><given-names>JC</given-names> </name><name name-style="western"><surname>Relan</surname><given-names>P</given-names> </name><name name-style="western"><surname>Diaz</surname><given-names>JV</given-names> </name><collab>WHO Clinical Case Definition Working Group on Post-COVID-19 Condition</collab></person-group><article-title>A clinical case definition of post-COVID-19 condition by a Delphi consensus</article-title><source>Lancet Infect Dis</source><year>2022</year><month>04</month><volume>22</volume><issue>4</issue><fpage>e102</fpage><lpage>e107</lpage><pub-id pub-id-type="doi">10.1016/S1473-3099(21)00703-9</pub-id><pub-id pub-id-type="medline">34951953</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="web"><person-group person-group-type="author"><collab>COVID Long Haulers Support Group Canada (Goulding)</collab></person-group><source>COVID Long Haulers Support Group Canada</source><year>2021</year><access-date>2026-07-06</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.facebook.com/groups/920314451799658/">https://www.facebook.com/groups/920314451799658/</ext-link></comment></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="web"><article-title>Homepage</article-title><source>Long Covid Advocacy Ireland</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://longcovidadvocacyireland.com">https://longcovidadvocacyireland.com</ext-link></comment></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="web"><article-title>Homepage</article-title><source>Long COVID Physio</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://longcovid.physio/">https://longcovid.physio/</ext-link></comment></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="web"><source>Long COVID Support</source><year>2021</year><access-date>2026-06-26</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.longcovid.org">https://www.longcovid.org</ext-link></comment></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="web"><article-title>Homepage</article-title><source>Patient-Led Research Collaborative</source><access-date>2026-06-12</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://patientresearchcovid19.com/">https://patientresearchcovid19.com/</ext-link></comment></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="web"><article-title>Homepage</article-title><source>Meta</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.meta.com/about/company-info/">https://www.meta.com/about/company-info/</ext-link></comment></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="web"><article-title>Homepage</article-title><source>X</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://about.x.com/">https://about.x.com/</ext-link></comment></nlm-citation></ref><ref id="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Brien</surname><given-names>KK</given-names> </name><name name-style="western"><surname>Erlandson</surname><given-names>KM</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>DA</given-names> </name><etal/></person-group><article-title>Episodic disability questionnaire (EDQ) measurement properties among adults living with HIV in Canada, Ireland, United Kingdom, and United States</article-title><source>BMC Infect Dis</source><year>2024</year><month>01</month><day>10</day><volume>24</volume><issue>1</issue><fpage>71</fpage><pub-id pub-id-type="doi">10.1186/s12879-023-08958-7</pub-id><pub-id pub-id-type="medline">38200425</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="web"><article-title>Measuring health and disability: manual for WHO disability assessment schedule (&#x200E;WHODAS 2.0)&#x200E;</article-title><source>World Health Organization</source><year>2012</year><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.who.int/publications/i/item/measuring-health-and-disability-manual-for-who-disability-assessment-schedule-(-whodas-2.0)">https://www.who.int/publications/i/item/measuring-health-and-disability-manual-for-who-disability-assessment-schedule-(-whodas-2.0)</ext-link></comment></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mundt</surname><given-names>JC</given-names> </name><name name-style="western"><surname>Marks</surname><given-names>IM</given-names> </name><name name-style="western"><surname>Shear</surname><given-names>MK</given-names> </name><name name-style="western"><surname>Greist</surname><given-names>JH</given-names> </name></person-group><article-title>The Work and Social Adjustment Scale: a simple measure of impairment in functioning</article-title><source>Br J Psychiatry</source><year>2002</year><month>05</month><volume>180</volume><fpage>461</fpage><lpage>464</lpage><pub-id pub-id-type="doi">10.1192/bjp.180.5.461</pub-id><pub-id pub-id-type="medline">11983645</pub-id></nlm-citation></ref><ref id="ref49"><label>49</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Herdman</surname><given-names>M</given-names> </name><name name-style="western"><surname>Gudex</surname><given-names>C</given-names> </name><name name-style="western"><surname>Lloyd</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Development and preliminary testing of the new five-level version of EQ-5D (EQ-5D-5L)</article-title><source>Qual Life Res</source><year>2011</year><month>12</month><volume>20</volume><issue>10</issue><fpage>1727</fpage><lpage>1736</lpage><pub-id pub-id-type="doi">10.1007/s11136-011-9903-x</pub-id><pub-id pub-id-type="medline">21479777</pub-id></nlm-citation></ref><ref id="ref50"><label>50</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sivan</surname><given-names>M</given-names> </name><name name-style="western"><surname>Preston</surname><given-names>N</given-names> </name><name name-style="western"><surname>Parkin</surname><given-names>A</given-names> </name><etal/></person-group><article-title>The modified COVID-19 Yorkshire Rehabilitation Scale (C19-YRSm) patient-reported outcome measure for Long COVID or Post-COVID-19 syndrome</article-title><source>J Med Virol</source><year>2022</year><month>09</month><volume>94</volume><issue>9</issue><fpage>4253</fpage><lpage>4264</lpage><pub-id pub-id-type="doi">10.1002/jmv.27878</pub-id><pub-id pub-id-type="medline">35603810</pub-id></nlm-citation></ref><ref id="ref51"><label>51</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yarrish</surname><given-names>C</given-names> </name><name name-style="western"><surname>Groshon</surname><given-names>L</given-names> </name><name name-style="western"><surname>Mitchell</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Appelbaum</surname><given-names>A</given-names> </name><name name-style="western"><surname>Klock</surname><given-names>S</given-names> </name><name name-style="western"><surname>Winternitz</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Finding the signal in the noise: minimizing responses from bots and inattentive humans in online research</article-title><source>Behav Ther (N Y N Y)</source><year>2019</year><access-date>2026-07-22</access-date><volume>42</volume><issue>7</issue><fpage>235</fpage><lpage>242</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://tinyurl.com/expdbfs4">https://tinyurl.com/expdbfs4</ext-link></comment></nlm-citation></ref><ref id="ref52"><label>52</label><nlm-citation citation-type="web"><article-title>The R Project for Statistical Computing</article-title><source>The R Project for Statistical Computing</source><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.R-project.org">https://www.R-project.org</ext-link></comment></nlm-citation></ref><ref id="ref53"><label>53</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Donkin</surname><given-names>L</given-names> </name><name name-style="western"><surname>Henry</surname><given-names>N</given-names> </name><name name-style="western"><surname>Kercher</surname><given-names>A</given-names> </name><name name-style="western"><surname>Pedersen</surname><given-names>M</given-names> </name><name name-style="western"><surname>Wilson</surname><given-names>H</given-names> </name><name name-style="western"><surname>Chan</surname><given-names>AHY</given-names> </name></person-group><article-title>Effective recruitment or bot attack? The challenge of internet-based research surveys and recommendations to reduce risk and improve robustness</article-title><source>Interact J Med Res</source><year>2025</year><month>03</month><day>14</day><volume>14</volume><issue>1</issue><fpage>e60548</fpage><pub-id pub-id-type="doi">10.2196/60548</pub-id><pub-id pub-id-type="medline">40086470</pub-id></nlm-citation></ref><ref id="ref54"><label>54</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bonett</surname><given-names>S</given-names> </name><name name-style="western"><surname>Lin</surname><given-names>W</given-names> </name><name name-style="western"><surname>Sexton Topper</surname><given-names>P</given-names> </name><etal/></person-group><article-title>Assessing and improving data integrity in web-based surveys: comparison of fraud detection systems in a COVID-19 study</article-title><source>JMIR Form Res</source><year>2024</year><month>01</month><day>12</day><volume>8</volume><fpage>e47091</fpage><pub-id pub-id-type="doi">10.2196/47091</pub-id><pub-id pub-id-type="medline">38214962</pub-id></nlm-citation></ref><ref id="ref55"><label>55</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Zhang</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Zhu</surname><given-names>S</given-names> </name><name name-style="western"><surname>Mink</surname><given-names>J</given-names> </name><name name-style="western"><surname>Xiong</surname><given-names>A</given-names> </name><name name-style="western"><surname>Song</surname><given-names>L</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>G</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Wang</surname><given-names>G</given-names> </name></person-group><article-title>Beyond bot detection: combating fraudulent online survey takers&#x2731;</article-title><conf-name>WWW &#x2019;22: Proceedings of the ACM Web Conference 2022</conf-name><conf-date>Apr 25-29, 2022</conf-date><pub-id pub-id-type="doi">10.1145/3485447.3512230</pub-id></nlm-citation></ref><ref id="ref56"><label>56</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>M&#x00E9;nard</surname><given-names>AD</given-names> </name><name name-style="western"><surname>McMurphy</surname><given-names>S</given-names> </name><name name-style="western"><surname>Sterling</surname><given-names>M</given-names> </name><name name-style="western"><surname>Armstrong</surname><given-names>N</given-names> </name><name name-style="western"><surname>Cheek</surname><given-names>O</given-names> </name><name name-style="western"><surname>Balint</surname><given-names>S</given-names> </name></person-group><article-title>Bots, scammers, and fraudulent responders: a year of disrupted data collection</article-title><source>Ethics Behav</source><year>2025</year><volume>36</volume><issue>3</issue><fpage>1</fpage><lpage>15</lpage><pub-id pub-id-type="doi">10.1080/10508422.2025.2518270</pub-id></nlm-citation></ref><ref id="ref57"><label>57</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Irish</surname><given-names>K</given-names> </name><name name-style="western"><surname>Saba</surname><given-names>J</given-names> </name></person-group><article-title>Bots are the new fraud: a post-hoc exploration of statistical methods to identify bot-generated responses in a corrupt data set</article-title><source>Pers Individ Dif</source><year>2023</year><month>10</month><volume>213</volume><fpage>112289</fpage><pub-id pub-id-type="doi">10.1016/j.paid.2023.112289</pub-id></nlm-citation></ref><ref id="ref58"><label>58</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Dupuis</surname><given-names>M</given-names> </name><name name-style="western"><surname>Meier</surname><given-names>E</given-names> </name><name name-style="western"><surname>Cuneo</surname><given-names>F</given-names> </name></person-group><article-title>Detecting computer-generated random responding in questionnaire-based data: a comparison of seven indices</article-title><source>Behav Res Methods</source><year>2019</year><month>10</month><volume>51</volume><issue>5</issue><fpage>2228</fpage><lpage>2237</lpage><pub-id pub-id-type="doi">10.3758/s13428-018-1103-y</pub-id><pub-id pub-id-type="medline">30091086</pub-id></nlm-citation></ref><ref id="ref59"><label>59</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Moss</surname><given-names>A</given-names> </name><name name-style="western"><surname>Litman</surname><given-names>L</given-names> </name></person-group><article-title>After the bot scare: understanding what&#x2019;s been happening with data collection on MTurk and how to stop it</article-title><source>CloudResearch</source><year>2018</year><access-date>2026-06-24</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.cloudresearch.com/resources/blog/after-the-bot-scare-understanding-whats-been-happening-with-data-collection-on-mturk-and-how-to-stop-it/">https://www.cloudresearch.com/resources/blog/after-the-bot-scare-understanding-whats-been-happening-with-data-collection-on-mturk-and-how-to-stop-it/</ext-link></comment></nlm-citation></ref><ref id="ref60"><label>60</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jacobson</surname><given-names>M</given-names> </name><name name-style="western"><surname>Molina-Henry</surname><given-names>D</given-names> </name><name name-style="western"><surname>Chang</surname><given-names>TY</given-names> </name><etal/></person-group><article-title>Financial incentives to increase diversity of older participants in a memory concerns registry: a randomized clinical trial</article-title><source>JAMA Health Forum</source><year>2025</year><month>08</month><day>1</day><volume>6</volume><issue>8</issue><fpage>e252273</fpage><pub-id pub-id-type="doi">10.1001/jamahealthforum.2025.2273</pub-id><pub-id pub-id-type="medline">40844772</pub-id></nlm-citation></ref><ref id="ref61"><label>61</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Hara</surname><given-names>ME</given-names> </name><name name-style="western"><surname>McDuff</surname><given-names>K</given-names> </name><name name-style="western"><surname>Wei</surname><given-names>H</given-names> </name><etal/></person-group><article-title>Community engagement in Long COVID research: process, evaluation and recommendations from the Long COVID and episodic disability study</article-title><source>Health Expect</source><year>2025</year><month>08</month><volume>28</volume><issue>4</issue><fpage>e70365</fpage><pub-id pub-id-type="doi">10.1111/hex.70365</pub-id><pub-id pub-id-type="medline">40783949</pub-id></nlm-citation></ref><ref id="ref62"><label>62</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Panagea</surname><given-names>E</given-names> </name><name name-style="western"><surname>Messinis</surname><given-names>L</given-names> </name><name name-style="western"><surname>Petri</surname><given-names>MC</given-names> </name><etal/></person-group><article-title>Neurocognitive impairment in Long COVID: a systematic review</article-title><source>Arch Clin Neuropsychol</source><year>2025</year><month>01</month><day>21</day><volume>40</volume><issue>1</issue><fpage>125</fpage><lpage>149</lpage><pub-id pub-id-type="doi">10.1093/arclin/acae042</pub-id><pub-id pub-id-type="medline">38850628</pub-id></nlm-citation></ref><ref id="ref63"><label>63</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Fanshawe</surname><given-names>JB</given-names> </name><name name-style="western"><surname>Sargent</surname><given-names>BF</given-names> </name><name name-style="western"><surname>Badenoch</surname><given-names>JB</given-names> </name><etal/></person-group><article-title>Cognitive domains affected post-COVID-19; a systematic review and meta-analysis</article-title><source>Eur J Neurol</source><year>2025</year><month>01</month><volume>32</volume><issue>1</issue><fpage>e16181</fpage><pub-id pub-id-type="doi">10.1111/ene.16181</pub-id><pub-id pub-id-type="medline">38375608</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Initial recruitment materials.</p><media xlink:href="jmir_v28i1e88838_app1.pdf" xlink:title="PDF File, 887 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Invitation to Time 2 questionnaire.</p><media xlink:href="jmir_v28i1e88838_app2.pdf" xlink:title="PDF File, 282 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Iterative Code Review strategies for identifying fraudulent responses.</p><media xlink:href="jmir_v28i1e88838_app3.pdf" xlink:title="PDF File, 234 KB"/></supplementary-material></app-group></back></article>