Panel Provider Redirect Integration

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's a different feature from Domandata's own Panels, which is a reusable participant list you manage yourself. Use this article when a panel vendor is sending you respondents; use Panels when you're maintaining your own invitee list across waves.

Panel vendors work one of two ways. Some (Prolific) send respondents with no special parameters and expect a fixed completion code at the end. Others (CloudResearch, Cint, RepData, and most panel aggregators) append their own respondent ID and completion/quota/termination URLs as parameters on the link they send respondents to, and expect the survey to redirect back to whichever one matches how the respondent finished. Domandata supports both without any per-vendor configuration: every query parameter on the survey link is captured automatically, and the end screen's redirect field can reference any of them.

1. Step 1: Publish the survey. Panel integrations read from the published snapshot, the same as any other public link.

   Step 1: Publish the Survey

2. 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

3. 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.

4. 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.

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

1. 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

2. 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

3. 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

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.

If a token has no matching parameter — a typo, or a respondent who reached the survey without going through the panel — the redirect field is left with the literal {{token}} text still in it rather than a silently broken URL, and no redirect fires. 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.

• Prolific: Prolific does not send a redirect-URL parameter. Set a fixed redirect — https://app.prolific.com/submissions/complete?cc=YOURCODE — on the completion end screen with automatic redirect on; no token syntax is needed. It's still worth appending Prolific's own PROLIFIC_PID, STUDY_ID, and SESSION_ID macros to your invitation link so they're captured for reconciliation, even though they aren't used in the redirect itself.
• CloudResearch / Connect: use the whole-link pattern — invite with CloudResearch's own completion/quota/termination macros as query parameters, then set each end screen's redirect to the matching {{token}}.
• Cint: same whole-link pattern, using Cint's respondent and completion-link macros for that project.
• RepData: same pattern, using RepData's macro names for that project.
• YouGov: typically ID-append style — a fixed YouGov-provided redirect URL with a respondent ID token embedded in it, e.g. ?pid={{RID}}.

Macro names are set per panel and sometimes per project — always confirm the exact names from the panel's own study setup before building the invitation link.

1. Step 1: Build a test link. Take the exact invitation URL format from the "Build The Panel Invitation Link" section and fill in fake values by hand for every macro parameter.

2. 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

3. 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.

Captured link parameters appear on each response alongside answers and other submission metadata, so a panel's respondent ID can be joined back to that panel's own records after collection. Keep a copy of the exact macro names and invitation link you used, since that's what determines which fields show up.

• Panel Recruitment for Surveys
• Survey Incentives and Completion Codes
• End Screens and Debriefing for Surveys
• Set Survey Quotas
• Branching and Skip Logic for Research Surveys
• Survey Participant Links
• Manage Participant Panels and Attrition
• Export Research Survey Responses