One routing layer between every supplier and your survey
Projects, supplier allocations, signed links and outcome records in one place. Suppliers keep their respondent IDs, buyers keep their survey platform, and both see the same session history.
How a session moves
The same sequence runs for every respondent, whether a supplier integrates by link or by API.
Invite
The supplier sends a respondent to its entry link with the respondent's ID in
rid.Check
Signature, project status, quotas, duplicates and, where enabled, pre-survey screening.
Survey
The respondent opens the buyer survey with a session ID the survey carries to the end.
Return
The survey redirects to the endlink for complete, terminate, over quota or quality.
Reconcile
The outcome is recorded once, the supplier gets a postback, and reversals follow after cleaning.
Projects and allocations
A project describes one survey. Each supplier works it through an allocation with its own payout, quota, status and entry link, so sources can be paused, capped and compared independently.
- Project
- Survey URL with the
{RDID}placeholder, country, language, expected LOI and incidence, CPI and completes target. - Allocation
- Supplier payout, optional completes cap and a unique entry link.
- Quotas
- Entry closes when live completes reach the project target or the allocation cap. Reversed completes reopen quota.
- Sandbox
- Test sessions run through the real survey and redirects without counting toward totals.
Outcomes that cannot be forged
A complete is worth money, so ResearchDart treats the endlink as a security boundary rather than a convenience URL.
- Signed links
- HMAC-SHA256 signatures on entry links and endlinks. Edited or copied URLs are refused.
- Server-to-server outcomes
- Buyers who cannot sign in their survey platform report outcomes with the status API instead.
- First outcome wins
- A session records one outcome. Replayed endlinks only show the outcome already recorded.
- Minimum LOI
- Completes faster than the project threshold become quality terminates with reason
speeder.
Returning respondents to their panel
Respondents see a plain-language outcome page, then return to the supplier's URL for that outcome. The supplier's server hears about it at the same moment.
- Redirect placeholders
{RID},{STATUS},{CODE},{PAYOUT},{RDID},{LOI}and more, in any URL format.- Postbacks
- HTTP GET on every outcome, retried after 1, 5, 30, 120 and 720 minutes.
- Reconciliation feed
- Every session a supplier sent, with screening status, GDQ code and reversal details.
Further reading
What is a survey endlink? Complete, terminate, over quota and quality redirects
Endlinks decide what gets paid for. Most reconciliation disputes we would expect to see trace back to four of them being set up carelessly, usually in...
Routing & IntegrationHow to secure survey redirects with HMAC signatures
A quarter of supplier traffic still arrives on links that can be edited in the address bar. Signing redirects takes an afternoon. The one rule people...
Routing & IntegrationServer-to-server postbacks vs browser redirects: which one should you trust?
Survey outcomes travel through the respondent's browser or directly between servers. Each channel breaks in its own way. Use redirects to move people...
Put a quality layer in front of your next study
Tell us whether you buy sample or supply it. We set up your account, share sandbox links and walk through the first integration with your team.