Data quality at every point a session can go wrong

No single check catches everything. ResearchDart layers controls before, during and after the survey, and records a reason for every decision so buyers and suppliers can see where quality was lost.

Every control, and what it records

Each row is a decision the router can make about a session, and the reason it writes down when it does.

StageControlWhat it stopsRecorded as
EntrySigned entry linksRespondent IDs edited in the address barRefused, nothing recorded
EntryRespondent ID deduplicationThe same supplier ID entering a project twiceduplicate_respondent, GDQ 4
EntryDevice deduplicationOne browser entering under several IDsduplicate_device, GDQ 4
EntryAutomation checksHeadless and scripted browsersautomation, GDQ 1
ScreeningProvider session scoringAI agents, bots, VPN and datacenter traffic, multi-accountingautomation or anonymized_network or fraud_tool
ScreeningTrue locationConnections outside the project countrygeo_mismatch, GDQ 3
Survey endSigned endlinks or status APIForged or edited complete URLsRefused, nothing recorded
Survey endMinimum LOICompletes faster than a person can read the questionsspeeder, GDQ 6
Survey endFirst outcome winsReplayed endlinks changing a recorded outcomeOriginal outcome kept
After fieldGDQ-coded reversalsCompletes that fail cleaningAny of the 18 GDQ codes

Recommended starting settings

Adjust after soft launch, once you have real timings and screening results.

Screening mode
Monitor for the first project with a new supplier, then enforce.
Suspicious sessions
Allow and flag for consumer studies; block for B2B and other high-incentive studies, which show the highest removal rates in the 2025 industry benchmark.
Minimum LOI
About one third of the median LOI from your first 50 completes.
Duplicate devices
On, except for studies in shared locations.
Signed endlinks
On whenever your survey platform can sign server-side; otherwise use the status API.

Data quality questions

What is a quality terminate?
An outcome for respondents who reached the router or the survey but whose response cannot be accepted: automation, anonymised networks, duplicates, speeding, failed attention checks or other fraud signals. It is reported separately from terminates so suppliers can act on it.
Does ResearchDart replace in-survey quality checks?
No. ResearchDart covers what happens before and after the questionnaire. Attention checks, open-end review and consistency checks still belong in the survey; send failures to the quality endlink or reverse them after cleaning.
How is a duplicate device identified?
At entry, with a one-way hash of the network address, browser user agent and language settings. When a screening provider is connected, its device intelligence adds multi-accounting detection across sessions.
Why can some duplicates be legitimate?
Households and offices share networks and browsers. For studies in shared locations, switch off duplicate device blocking and rely on respondent-ID checks and provider scoring.

Put a quality layer in front of your next study

Tell us whether you buy sample or supply it. We set up your account, share sandbox links and walk through the first integration with your team.