Panel Provider Redirects (Rep Data, Cint, CloudResearch)

What This Covers

This article is about third-party panel providers — external sample sources like Prolific, CloudResearch, Cint, RepData, or YouGov that route their own respondents to your survey and expect a completion signal back. That is different from Domandata's own Panels (a reusable participant list you manage yourself) and from personal links (tokenized invitations you generate in Deploy). Use this article when a panel vendor is sending you respondents and you need redirect URL passthrough with respondent IDs such as RDUD.

Panel vendors work one of two ways. Some (Prolific, SONA) expect a fixed completion code or credit link at the end. Others (CloudResearch Prime Panels, Cint, and most panel aggregators) append their own respondent ID to the link and expect the survey to redirect back to a different address for each outcome — complete, screened out, over quota, or quality terminate. The Recruitment card in Deploy sets either kind up in one step. Everything it does is built from ordinary end screens and redirects, so you can still configure any panel by hand, as described further down.

Deploy: End Screen Redirect

One-Click Setup In Deploy

Step 1: Open Deploy → Recruitment and pick your provider. Supported: Prolific, CloudResearch Connect, CloudResearch Prime Panels, Cint (Cint Exchange, formerly Lucid Marketplace), SONA Systems, YouGov, Rep Data, and Other Panel for any other redirect-based panel.
Step 1: Pick a Provider
Step 2: Fill in what the provider asks for. Prolific needs your completion code (plus optional screen-out and failed-attention-check codes). CloudResearch Connect needs the redirect URL from the end of its Create a Study wizard. SONA needs your site address, experiment ID, and credit token. Prime Panels needs nothing, and Cint only asks whether your study uses Verify Callback. You can paste the whole completion URL Prolific or SONA shows you — Domandata pulls the code, experiment ID, and credit token out of it. YouGov, Rep Data, and Other Panel set links per project, so paste the respondent-ID parameter and redirect URLs your project team sent, using {{parameter}} where the respondent ID goes.
Step 3: Choose the safeguards and connect. One Response per Participant (on by default) blocks a second response from the same provider participant ID, even from another device. Require a Provider ID shows a notice instead of the survey to anyone who opens the link without a participant ID, such as someone who was forwarded the link. The dialog previews exactly which end screens it will reuse or add before you confirm.
Step 4: Paste the study link into the provider. The card shows the link with the provider's placeholders already added (for example PROLIFIC_PID={{%PROLIFIC_PID%}} for Prolific or RID=[%RID%] for Cint), followed by a short list of what to set in the provider's dashboard.
Step 5: Work through the checklist. Once connected, the card shows how many things are left before launch and four short steps, with the next one highlighted: Share the study link, Finish in the provider, Send non-qualifiers back, and Try it yourself. In Send non-qualifiers back, Domandata suggests your likely screener — an early eligibility question such as "Are you 18 or older?" — and the answers that should end the survey; choose Yes, Route It to accept, or Choose Answers to pick yourself. If your quality rules define attention checks, Use My Attention Checks sends every wrong answer to Quality Terminate. Suggestions are only offered, never applied on their own. This writes ordinary Skip Rules on that question, so you can also route with Flow or your own Skip Rules. Then use Open Test Link to walk each outcome with a sample participant ID.
Step 5: Route Outcomes

What connecting does:

End screens: your first end screen becomes Complete (its message is kept). Screened Out, Over Quota, and Quality Terminate screens are reused if you already have end screens with those names, and added otherwise. Each one redirects automatically to the provider. When a provider has no redirect for an outcome (for example Prolific without a screen-out code), that screen shows a short message asking the participant to return to the provider instead.
Quotas: a quota that ends the survey but has no destination, or points at the Complete screen, would otherwise report over-quota respondents to the provider as completes. Setup sends those quotas to the Over Quota screen (or Screened Out when the provider has no over-quota path). Quotas you already sent to another end screen are left alone.
Survey closed by a quota: when a survey-wide quota has closed the survey, arriving panel respondents are sent straight back to the provider's over-quota address instead of a closed page.
Quota counting: every quota is set to count completes only, so screened-out, over-quota, and quality-terminated respondents don't fill it and close fielding early.
Outcome on every response: each response records how it finished (Complete, Screened Out, Over Quota, or Quality Terminate). It shows in the response table's Completion column and as a Recruitment Outcome column in exports, next to one column per captured link parameter (such as PROLIFIC_PID or RID) for reconciling with the provider.
Setup Check: the card warns when an outcome's end screen was deleted, its redirect was edited by hand, a quota would still land on Complete or counts every response, or nothing routes to a screen yet. Re-Apply Setup fixes everything except routing. The same warnings appear in the Instrument Review card in Deploy, and the connected end screens are labeled (for example Prolific · Screened Out) in Block Builder and on the Flow canvas so a hand edit isn't made by accident. When you have unpublished changes, the card offers Push Changes right there.
Disconnect forgets the integration but leaves your end screens and redirects in place.

The Test Link

Open Test Link opens the published survey with a sample participant ID. Walk it once per outcome. Instead of sending you to the provider, each end screen shows the exact address a real participant would be sent to, so nothing is reported to the provider. Test runs are labeled Test in the response table and exports, never count toward quotas or the one-response-per-participant rule, and the card shows how many exist with a Delete Test Responses button. The Published card at the top of Deploy also reminds you while any remain, with Delete Before Launch.

Prolific Account (Optional)

With Prolific connected, the card can also talk to Prolific directly:

Connect a token: paste a Prolific API token (create one in Prolific under API Tokens). Domandata checks it with Prolific and stores it encrypted, for your account only.
Create the study: enter a title, description, places, minutes, and reward (or choose Fill In From My Survey for the title, the survey's estimated length, and — when your quotas make the total clear — the number of places), and Domandata creates the Prolific study with your study link and completion codes already filled in (the screen-out code gets the fixed screen-out payment you enter). The study is created unpublished — nothing is charged and no one is invited until you review and publish it on Prolific.
Review and approve: Review Submissions matches each Prolific submission to the response with the same participant ID. Submissions awaiting review whose response finished as a complete, with the completion code, and that aren't excluded or critically flagged in quality review can be approved together in one click. The rest are listed with the reason. Domandata never rejects a submission for you — rejections affect participants' standing, so decide those in Prolific.

The Domandata MCP exposes the same setup: read_deploy with include: ["recruitment"] returns the study link, dashboard steps, outcomes and their routing, test response count, and setup issues, and include: ["prolific_submissions"] returns the Prolific review. edit_deploy with a recruitment patch can connect, re-apply, disconnect, route answers, delete test responses, create the Prolific draft study, approve submissions, or unlink the study. Prolific tokens can only be saved in the app — the MCP refers to a saved token by its id and never accepts or returns the token itself.

Build The Panel Invitation Link

Step 1: Publish the survey. Panel integrations read from the published snapshot, the same as any other public link.
Step 1: Publish the Survey
Step 2: Copy the published URL. This is the base link you give the panel — do not add your own query parameters to it.
Step 2: Copy the Published URL
Step 3: Ask the panel for its macro names. Every panel has its own placeholder syntax it substitutes with real values before sending a respondent your link — a respondent ID macro, and usually a completion URL, quota-full URL, and termination URL macro. These names vary by panel and sometimes by project, so confirm them from the panel's own study setup rather than assuming.
Step 4: Append the panel's macros as query parameters. For example, a link built for a panel using completion_url/quota_url/termination_url macros might look like:

https://www.domandata.net/s/{surveyId}?RID=[respondent_id]&completion_url=[completion_url]&quota_url=[quota_url]&termination_url=[termination_url]
Give this constructed URL to the panel as the survey's start link — do not use the plain published URL from Step 2 once you've added these.

Domandata reserves only one query parameter, d, for its own personal links feature. Never reuse d as a panel macro name — pick any other name.

Route Outcomes To Separate End Screens

A panel needs to redirect completed, screened-out, and quota-full respondents to different destinations, so each outcome needs its own end screen.

Step 1: Add an end screen per outcome. In Block Builder, add a distinct end screen block for completion, for each screen-out reason that matters, and for quota-full.
Step 1: Add End Screens
Step 2: Route to them. Use Flow to send screen-out logic to its end screen, and set each quota's destination to the quota-full end screen.
Step 2: Route Outcomes
Step 3: Set each screen's redirect. On each end screen, fill in the Redirect field and turn on automatic redirect so respondents leave without an extra click.
Step 3: Set Redirect URLs

Deploy: Quota Destinations

The Redirect Token Syntax

Every query parameter on the incoming survey link, other than d, is captured automatically — no setup required. An end screen's redirect field can reference any captured parameter by name, wrapped in double curly braces, and Domandata fills it in right before the redirect fires:

Whole-link redirect: set the redirect field to {{completion_url}} (matching whatever parameter name you used in Step 4 above) when the panel supplies a complete, ready-to-use redirect URL of its own. This is the normal pattern for CloudResearch, Cint, and RepData.
ID-append redirect: embed a token inside an otherwise fixed URL, e.g. https://panel.example/thanks?pid={{RID}}, to carry a respondent ID through to a static destination for reconciliation.

A value inserted inside a URL (after ? or elsewhere past the start) is URL-encoded, so an ID containing &, #, or a space can't break the address; a token that makes up the whole redirect is inserted as-is. If a token has no matching parameter — a typo, or a respondent who reached the survey without going through the panel — no redirect fires, rather than sending the respondent to a broken URL. That makes a misconfigured parameter visible during testing instead of quietly sending respondents to the wrong place. For the same reason, a redirect only ever fires to a plain http:// or https:// address.

Panel-By-Panel Setup Notes

Each provider has its own step-by-step guide: Prolific, CloudResearch Connect, CloudResearch Prime Panels, Cint, SONA Systems, YouGov, and Rep Data. The notes below summarize the conventions the Recruitment card uses, so you can check them against your provider or reproduce them by hand.

Prolific: study link parameters PROLIFIC_PID={{%PROLIFIC_PID%}}, STUDY_ID={{%STUDY_ID%}}, and SESSION_ID={{%SESSION_ID%}} (choose "I'll use URL parameters" in Prolific). Each outcome redirects to https://app.prolific.com/submissions/complete?cc=CODE with its own code. Prolific has no separate over-quota path, so over-quota respondents get the screen-out code.
CloudResearch Connect: turn on passing the participant ID in Connect's study setup, and Connect adds participantId, assignmentId, and projectId itself. Completion redirects to the Redirect URL shown at the end of Connect's Create a Study wizard.
CloudResearch Prime Panels: Prime Panels adds aid itself. Outcomes redirect to https://app.cloudresearch.com/Router/End, /Router/ThankYouNotQualified, /Router/QuotaFull, and /Router/ThankYouTerm, each with ?aid={{aid}}. Route every termination to its screen, because unrouted terminations can get a Prime Panels study paused.
Cint (Cint Exchange): study link parameter RID=[%RID%]. Outcomes redirect to https://samplicio.us/s/ClientCallBack.aspx?RIS=10&RID={{RID}} for a complete, with RIS=20 for a terminate, 30 for a quality terminate, and 40 for over quota. If your Cint study has Verify callback checked, turn on Verify Callback in the setup dialog: the study link also carries RISN=[%RSFN%], and completes send that value back as &RISN={{RISN}}. (Cint reports error 137 when verify callback is on but the link lacks it.)
SONA Systems: set the study URL in SONA to the study link, which ends in id=%SURVEY_CODE%. Completion redirects to https://yourschool.sona-systems.com/webstudy_credit.aspx?experiment_id=…&credit_token=…&survey_code={{id}}, which grants credit automatically.
YouGov and Rep Data: neither publishes a self-serve redirect spec. Your project team sends the respondent-ID parameter and the complete, screen-out, over-quota, and quality URLs per project. Paste them into the Recruitment card with {{parameter}} where the ID goes. The card suggests pid (YouGov) and RDUD (Rep Data) as starting parameter names, but always confirm them with your project team.
Any other panel (Dynata, Pollfish, Lucid Theorem, and similar): use Other Panel with the macro and redirect URLs from the panel's project setup.

Security-Fail Redirects

Panels that distinguish a security-fail outcome (fraud checks, failed attention or eligibility rules treated as a security termination) pass a fourth redirect URL on the inbound link, just like completion, terminate, and quota-full URLs. Add a dedicated end screen for that outcome, set its redirect to the matching {{token}} (for example {{security_fail_url}} when the panel uses that macro name), and route respondents there from Flow when your screener, attention check, or quality rule fires. Confirm the exact macro name from the panel's study setup — it varies by vendor and project.

Test Before You Launch

Step 1: Build a test link. With a recruitment integration connected, use the card's Open Test Link (see above). Otherwise take the exact invitation URL format from the "Build The Panel Invitation Link" section, fill in fake values by hand for every macro parameter, and add dd_test=1 to mark the runs as tests.
Step 2: Walk each outcome. Complete the survey once for each path — a normal completion, a screen-out, and a quota-full response if quotas are in use — and confirm the browser lands on the correct destination each time.
Step 2: Test the Survey
Step 3: Check the captured data. Export a test response and confirm the panel's respondent ID and any other parameters appear in the data.
Step 3: Check Export

Run this full pilot with the exact link format the panel will use, not a hand-simplified version — a parameter name that's missing or misspelled in testing will be missing in production too.

Export and Reconciliation Notes

Every captured link parameter becomes its own export column named after the parameter (for example PROLIFIC_PID, STUDY_ID, or RID), so a panel's respondent ID can be joined back to that panel's own records after collection. With a recruitment integration connected, a Recruitment Outcome column shows how each respondent finished. Panel IDs identify people, so they are left out when you export with identifying information excluded. Keep a copy of the exact macro names and invitation link you used, since that's what determines which columns show up.

Export: Data Output

Related Help