GUIDES8 MIN READ
The survey tool checklist for panel studies.
Prolific will work with any survey tool that can catch a URL parameter and hand back a code. That is a low bar, and it hides how different the day-to-day actually is: with the right tool a study launches in an afternoon and approves itself; with the wrong one you are copy-pasting participant IDs out of a spreadsheet at midnight. Here is the capability checklist that matters, and an honest comparison of the common choices.
01The seven capabilities that decide your week
1. Automatic ID capture. The tool must read PROLIFIC_PID (and study / session IDs) off the link and store them with each response. The workaround — asking participants to paste their ID into a text question — produces typos in a few percent of rows, and every typo is a submission you cannot match to a person at approval time.
2. Completion redirect + visible code. Finish → bounce back to Prolific automatically, with the code printed on the thank-you screen as the manual fallback.
3. A separate screen-out exit. Different message, different code, different redirect for disqualified participants.
4. Duplicate blocking by participant ID. Retakes happen — back buttons, second devices, returned-then-retaken submissions. Server-side one-response-per-PID protects the dataset.
5. Data-quality instrumentation. Attention checks, speeder and straight-liner detection, and exports that carry the flags — because your exclusion rule needs evidence.
6. Quotas and screening. Cap segments (e.g. 50 per condition per gender) and disqualify early, enforced server-side so concurrent participants cannot oversubscribe a cell.
7. A test mode. You will rehearse the study several times. Those rehearsals should never sit in your data.
02How the common choices compare
Scored against the checklist above. This is opinionated but we have tried to keep it fair — every tool below can run a Prolific study; the question is how much of the workflow is built versus hand-rolled.
| CAPABILITY | QUALTRICS | TYPEFORM | GOOGLE FORMS | PLUMEFORM |
|---|---|---|---|---|
| ID capture | Yes, via embedded-data fields you configure per study | Yes, via hidden fields you configure per form | No — participants paste their ID manually | Automatic — any link parameter is captured |
| Completion redirect | Yes (end-of-survey element) | Yes (redirect on completion, paid plans) | No | Yes, plus the code shown on screen |
| Screen-out exit | Yes, via branch logic you assemble | Partial — logic jumps, single redirect | No | Built in: separate screen, code, redirect |
| Duplicate blocking by PID | Configurable with effort | No (cookie-based only) | No | One toggle, enforced server-side |
| Attention checks & quality flags | Checks yes; flags via your own analysis | No | No | Checks, speeders, straight-liners flagged automatically |
| Quotas | Yes | No | No | Yes, server-enforced |
| Test mode | Preview mode (separate from live data) | No | No | ?test=1 — flagged, excluded, one-click purge |
| Typical cost to a researcher | Institutional license (five to six figures) or you lose access when you leave | Paid tiers per feature; research features thin | Free | $15/mo; the research pack is the point |
The honest summary: Qualtrics is the incumbent for a reason— it can do nearly everything on the list if you invest in learning its flow editor and embedded-data plumbing, and if your institution pays for it, that knowledge transfers across labs. Typeform optimizes for marketing forms, not research; the gaps are structural. Google Forms is free and fine until the first time you lose an hour matching mistyped IDs. Plumeform's bet is that the whole checklist should be product defaults rather than configuration — judge that claim on the researcher tour.
03Questions to ask before you commit
Whatever you choose, run this gauntlet with a real pilot before the study that matters: Can you launch, complete, and approve a submission end to end without touching a spreadsheet? Does a screened-out participant exit cleanly? If you open the study link twice as the same participant, what happens? Where do your dry runs go? And — the one people forget — can you export every column you will need for your methods section: durations, quality flags, IDs, condition assignments?
An afternoon spent on that pilot is the cheapest insurance in online research. The expensive version is discovering the answer with 400 paid participants in flight.
Quick answers
Does Prolific require a specific survey tool?+
No. Prolific hands participants a link and expects a completion code back; anything that can capture URL parameters and show or redirect to a code works. The differences are in how much of the workflow the tool automates and how much you hand-roll.
Is Google Forms good enough for a Prolific study?+
For a one-off pilot, maybe. It cannot capture the PROLIFIC_PID automatically (participants must paste their ID into a question, which they mistype), has no redirect, no screen-out handling, no attention checks, and no duplicate blocking. Every one of those becomes manual work or lost data.
My university has Qualtrics. Why would I use anything else?+
If your license is paid for and you know the embedded-data workflow, Qualtrics is a fine, battle-tested choice. People leave it for two reasons: the workflow overhead (embedded data fields, flow editor, and query strings you must wire by hand for every study) and losing access when they leave the institution.
What about jsPsych, Gorilla, or other experiment builders?+
Different category. If your study is a reaction-time task or needs millisecond stimulus control, use an experiment builder. If it is questions and scales — most panel studies — a survey tool with proper panel support is faster to build in and easier for participants.
Keep reading: Completion codes, set up right · Plumeform vs Qualtrics, feature by feature · Stopping duplicate participants
Put it into practice.
250 responses a month free. Every control in these guides is built in.