Skip to content

What participants experience

This page describes the survey-taking side, useful when writing instructions, troubleshooting participant reports, or describing the platform to an ethics board.

Access

Participants open the survey link, no account, no app, phones and desktops both work. If the survey is paused, stopped, or unpublished they see a clear closed message instead.

Answering

One block per screen with a continue button (whose label you control). Required questions enforce on submit, with plain inline messages and a scroll to the first problem. Questions with validation check answers as they are typed and again on submit with identical rules. Questions governed by display logic appear and disappear live as earlier answers change, a hidden question never blocks submission and any stale answer it held is discarded.

File-upload questions accept the configured types and sizes, show what has been attached, and keep already-uploaded files when the participant fixes other answers on the page.

Rating tasks deal the participant their batch of items and repeat the rating questions per item.

Timing and ordering

Each response records when it was opened and submitted, per-page timings, and the participant's actual ordering wherever randomization applied (question order, choice order, item order). All of it lands in exports.

Bot protection

Surveys with CAPTCHA enabled verify invisibly via Google reCAPTCHA v3, there are no puzzles. Failing verification blocks the submission before any data is recorded.

Completion

After the last block the participant sees the completion page, your configured message (which can include a completion code for panel platforms and any custom variables) or an automatic redirect to your configured URL with placeholders filled in.

Privacy notices participants see

A small cookie notice appears once per browser explaining that only essential cookies are used (session, security, and reCAPTCHA where enabled), with a link to the Privacy Policy. The session cookie is what keeps a response attached to the participant's browser while they work through the blocks.