Field across suppliers and pay only for people who were real
Set up a project once, place four endlinks in your survey, and route respondents from every supplier you work with. Screening removes automated and duplicate traffic before it reaches you, and reversals handle what your cleaning finds.
From programmed survey to live fieldwork
Five steps in the console, or the same through the buyer API.
Create the project
Survey URL with
{RDID}, country, language, LOI, incidence and completes target.Capture the session ID
Store the
rdidURL parameter as a hidden or embedded data field.Add endlinks
Redirect to complete, terminate, over quota or quality with the stored
rdid.Choose screening
Monitor or enforce, and whether suspicious sessions are blocked.
Test and launch
Run sandbox sessions through every path, then set the project live.
Your endlinks
The same four URLs work for every supplier on the project. The session ID tells ResearchDart who the respondent is.
Replace [rdid] with your platform's piping, for example ${e://Field/rdid} in Qualtrics.
| Complete | /s/end/complete?rdid=[rdid] |
|---|---|
| Terminate | /s/end/terminate?rdid=[rdid] |
| Over quota | /s/end/overquota?rdid=[rdid] |
| Quality | /s/end/quality?rdid=[rdid] |
What you control per project
Every setting is per project, so a tracker and a B2B study can run with different rules on the same account.
- Completes target
- 1,000412 accepted
- Supplier allocations
- 3 open, 1 paused
- Pre-survey screening
- EnforceSuspicious sessions blocked
- Minimum LOI
- 4 min
- Duplicate devices
- Blocked
- Signed endlinks
- Required
- Completes target
- Entry closes automatically when accepted completes reach the target.
- Supplier allocations
- Per-supplier caps and prices, paused or closed independently.
- Pre-survey screening
- Off, monitor or enforce, with a choice for suspicious sessions.
- Minimum LOI
- Faster completes are recorded as quality terminates.
- Duplicate devices
- Stop one browser taking the survey under several IDs.
- Signed endlinks
- Refuse any endlink your survey did not generate.
Numbers you can reconcile against
The console and the buyer API calculate the same metrics from live sessions. Sandbox sessions never appear in totals.
| Metric | Calculation |
|---|---|
| Incidence rate | Completes ÷ (completes + terminates) |
| Conversion | Completes ÷ all entries |
| Accepted completes | Completes minus reversals |
| Screened out | Sessions flagged or blocked by screening |
| Length of interview | Average seconds from entry to complete |
Buyer questions
Which survey platforms work with ResearchDart?
What does a buyer pay for?
How do I reject completes after fieldwork?
How do I stop someone forging a complete?
Should I turn on pre-survey screening?
Further reading
Incidence rate, LOI and CPI: how online sample is priced, and why quotes go wrong
Three numbers set the price of almost every online sample quote. Industry benchmark data shows the first one is routinely sold higher than it turns ou...
Research OperationsSample exchange or single panel? A candid comparison from a routing company
We run a router, so you would expect us to say exchanges win. For some studies a single good panel is the better choice, and we say which ones.
Routing & IntegrationSetting up third-party sample redirects in Qualtrics
Capture the session ID with embedded data, send each exit to the right endlink, and test every path with a sandbox session. The part most setups get w...
Field your next study through ResearchDart
Share your audience, length of interview and timing. We will confirm supplier coverage, set up screening and send your endlinks.