How it works in Surveti
Bot defense at entry
Cloudflare Turnstile screens out automated traffic before it becomes a response, keeping obvious bots out of your sample from the first click.
Quality scoring
Every response is checked for speeding, straightlining across grids and scales, and duplicate IPs within a configurable window — the classic signals of an inattentive or fraudulent respondent.
Open-end quality checks
Open-ended answers are evaluated for length and substance so gibberish and copy-paste get flagged instead of quietly polluting your verbatims.
Review workflow
Flagged respondents surface in a review view where you accept or reject them with notes, and configure auto-flag thresholds per project.
What teams use it for
- Keep panel buys clean before you pay for completes
- Defend a dataset’s quality to a research buyer
- Catch straightliners and speeders automatically
Frequently asked questions
How are bots blocked?
Cloudflare Turnstile screens traffic at survey entry, filtering automated visitors before they can submit a response.
What quality signals are scored?
Speeding below a configurable threshold, straightlining across grids and scales, duplicate IPs within a time window, and open-end quality such as length and substance.
Do flagged responses get removed automatically?
Flagging is surfaced for review — you accept or reject flagged respondents with notes, and set per-project auto-flag thresholds. You stay in control of what stays in the dataset.