# Preventing bots

**URL:** <https://forum.surveyengine.com/t/preventing-bots/77>\
**Category:** Live Surveys\
**Tags:** bots, fraud\
**Created:** [13 February 2023 18:28 UTC](https://forum.surveyengine.com/t/preventing-bots/77 "2023-02-13T18:28:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Freddo](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.surveyengine.com/freddo/32/55_2.png) [@Freddo](https://forum.surveyengine.com/u/Freddo)\
**Post date:** [13 February 2023 18:28 UTC](https://forum.surveyengine.com/t/preventing-bots/77/1 "2023-02-13T18:28:46Z")

</div>

How can I prevent fraud/bots filling in my survey?

---

<div class="post-metadata">

**Author:** ![Nayara](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.surveyengine.com/nayara/32/15_2.png) [@Nayara](https://forum.surveyengine.com/u/Nayara)\
**Post date:** [13 February 2023 22:39 UTC](https://forum.surveyengine.com/t/preventing-bots/77/2 "2023-02-13T22:39:50Z")

</div>

We have several methods we use internally and hope to publish them for general use at a later date.

For now look for

- repeated IPs
- speeders
- patterned responses
- incident rates getting better over time
- nonsense text in open text fields
- known distributions not matching data e.g. 50% gender splits

These evaluations can be performed post collection and respondents removed from the dataset.

To prevent users from reentering the survey, a cookie script can be implemented

---

<div class="post-metadata">

**Author:** ![thanhmai](https://avatars.discourse-cdn.com/v4/letter/t/e8c25b/32.png) [@thanhmai](https://forum.surveyengine.com/u/thanhmai)\
**Post date:** [17 September 2024 08:49 UTC](https://forum.surveyengine.com/t/preventing-bots/77/3 "2024-09-17T08:49:03Z")

</div>

Dear Nayara, how is the cookie script implemented? Please elaborate.
