Run your Prolific study with Plumeform, from first link to last bonus.

Build and publish as usual. Keep the participant's time in mind: the welcome screen shows an estimated completion time, and the pilot in Part 3 gives you the real median to put in Prolific.

Leave the link as it is. The slug is the address Prolific will use, and renaming it later is possible (old links forward), but there is no reason to change a link that is already in a live study.

In the After submission card, fill in both fields. You will get the code from Prolific in Part 2; if you are doing this in one sitting, create the study there first and come back.

(opens the screenshot at full size in a new tab)

• COMPLETION CODE: the code Prolific gives your completed path. It appears on the thank-you screen, so a participant whose redirect never ran can still type it in.
• REDIRECT ON FINISH: Prolific's completion URL with the same code, https://app.prolific.com/submissions/complete?cc=YOURCODE. Participants land back on Prolific already marked complete.
• Redirect immediately: skips the thank-you screen. Off, the thank-you screen (with the code) shows for 2.5 seconds and then continues on its own. Either works with Prolific; leave it off if you want the code seen.

In the Limits card, turn on One response per panel participant. The PROLIFIC_PID on the link is then allowed one submission, enforced on the server: a participant who already completed or was screened out is turned away before the first question, and two submissions racing with the same ID cannot both be saved.

(opens the screenshot at full size in a new tab)

Prolific already stops a participant from taking the same study twice. The check matters when you run several studies on one survey, reopen a study, or recruit the same people again later.

If some people should not take the full survey, add a logic rule with the screen out action (Logic tab), or cap segments with quotas. Then, in the Screening & quotas card, give screen-outs their own code and redirect, taken from the screened-out path you create in Prolific (Part 2, step 9).

(opens the screenshot at full size in a new tab)

• Screen people out in the first minute. Prolific pays screened-out participants a small fixed amount and expects screening to come before they have done real work.
• When a quota fills, the next matching participants are screened out at the next page, and they leave through the same screen-out exit.
• Screened-out participants never count as responses or against your monthly limit.

These are Pro, and each one changes what you can do at review time:

• Attention checks (a multiple-choice question with a correct answer marked) flag failures in results and exports, and feed the reject list. Check Prolific's current attention-check rules before you rely on one for a rejection.
• Informed consent puts an agree/decline screen before the first question. Under “If someone declines” on that screen, paste the URL of Prolific’s “No consent” path (step 9) into DECLINE REDIRECT, so anyone who declines goes back to Prolific and frees their place.
• Desktop only shows phone visitors a polite screen before anything starts. Match it with Prolific's device settings so phone users are not recruited at all.
• Bot protection blocks certain scripted submissions and flags others, without a CAPTCHA.

Open the survey's Share panel and find Launch on a panel. With Prolific selected, it gives the study URL with Prolific's placeholders already in place, and a checklist read from your settings.

(opens the screenshot at full size in a new tab)

https://plumeform.com/s/YOUR-SLUG?PROLIFIC_PID={{%PROLIFIC_PID%}}&STUDY_ID={{%STUDY_ID%}}&SESSION_ID={{%SESSION_ID%}}

The {{%…%}} placeholders are Prolific's: it replaces them with each participant's values. Plumeform saves every parameter on the link with the response, up to ten of them.

A completion path is one way of finishing, with its own code and its own handling. Create one for completers, one for screen-outs if the survey screens anyone out, and one for people who decline if it asks for consent. Set them before publishing: Prolific warns that changing paths can disrupt submissions already in progress.

Before you publish, use Prolific's Preview to check the link opens your survey. Read Part 3 first: a preview you submit is saved as a real response.

Open your study URL with test=1 added and sample IDs in place of Prolific's placeholders:

https://plumeform.com/s/YOUR-SLUG?PROLIFIC_PID=TEST001&STUDY_ID=TEST&SESSION_ID=TEST001&test=1

A test response is:

• ✓stored and flagged, so you can check what was captured;
• ✓left out of results, exports, quotas and the one-per-participant check;
• ✓removable in one click (Delete them in the results header).

Change PROLIFIC_PID for each run so you can tell them apart.

• ✓Complete the survey. You should land on Prolific's completion page (or, without a Prolific login, on its sign-in page with cc= in the address).
• ✓Answer so you are screened out. You should see the screen-out screen and land on the screen-out URL with its own code.
• ✓Fill a quota (set its limit to 1 while testing, or test on a copy). The next matching run should be screened out.
• ✓After the pilot, reopen the link with a pilot participant's ID and without test=1: the one-response check should turn you away before the first question. Test runs never trigger it.
• ✓Decline consent, if you ask for it: nothing is recorded, and you are sent to the “No consent” path’s URL, its code in the address.

(opens the screenshot at full size in a new tab)

Publish with a handful of places, often five to ten. When they are in, check the export has the three ID columns, the timing matches what you are paying for, attention checks behave, and the screen-out rate is what you expected. Then add places.

• Fieldwork shows completes, people still in progress, screen-outs, drop-off by question and median time. A drop-off spike on one question usually means a problem with that question.
• Quality shows speeders, straight-liners, failed attention checks, duplicate and pasted text, and the bot-protection signals, each as a flag for review.
• On Prolific, watch Awaiting review for submissions with a missing or wrong code, and the returned and timed-out counts.

On the Quality tab, Copy N clean IDs copies the participant IDs of every response with no quality flag, separated by commas, the way Prolific's bulk approve box takes them. In Prolific, open the study's submissions, choose Bulk actions → Bulk approve, paste and approve. Prolific's approval article (opens in a new tab) has the details.

Copy N flagged IDs gives you the rest, to look at one by one before deciding.

On the Analysis tab, Panel payouts → Download reject list lists every participant who failed an attention check, with the question they failed. It is a list for review, not a verdict: open each response, check it against Prolific's rules for rejections (opens in a new tab), and reject in Prolific with a clear reason. Never reject someone only because their answers disagree with their prescreening answers.

The Panel payouts card builds the list Prolific's Bulk bonus payment box takes: one submission ID,amount line per participant. Pay every completion, only completions that passed every attention check, or an amount per quiz point.

(opens the screenshot at full size in a new tab)

State the bonus rule in the study description and the consent text before anyone starts, and pay once: Prolific asks you not to retry a bulk bonus unless it tells you the payment failed.

CSV (every plan) and XLSX (Pro) exports have one column per question plus PROLIFIC_PID, SESSION_ID and STUDY_ID, the survey version, duration, quality flags and per-question timings where recorded. Large exports are prepared in the background and download when ready. The Pro research pack adds a codebook, an R loader and a methods appendix.