ResearchDart
Talk to us

Send respondents to live surveys and learn from every outcome

Panels, rewards apps and communities connect with one entry link per project. Respondents return to your URLs with a clear outcome, your server receives a postback, and quality removals arrive with standard reasons you can trace to a source.

Become a supplier Supplier API

Your entry link

Each project allocated to you has its own entry link. Replace {RID} with your respondent ID; it comes back unchanged in every redirect and postback.

https://researchdart.com/s/entry/k3m9q2xa7hpd?rid={RID}

Turn on signed entry links to append an HMAC-SHA256 signature. How signing works

Placeholders

{RID}Your respondent ID, exactly as sent on the entry link
{RDID}ResearchDart transaction ID
{STATUS}Outcome slug: complete, terminate, overquota or quality
{CODE}Outcome code: 10, 20, 30 or 40
{PAYOUT}Payout in USD for completes, otherwise 0.00
{PROJECT}ResearchDart project code
{LOI}Length of interview in seconds
{TEST}1 for sandbox sessions, otherwise 0

What you get back

Everything you need to reward members fairly and clean up sources that cause removals.

Outcome on every session
Complete, terminate, over quota or quality, with a router reason when ResearchDart closed the session.
Postbacks with retries
Up to six delivery attempts over about fifteen hours.
Screening status
Passed, flagged, blocked or unavailable for each respondent you sent.
GDQ-coded reversals
The removal code, label and buyer note for every reversed complete.
Sandbox sessions
Test redirects and postbacks end to end, flagged with {TEST} = 1.

Example redirect setup

Most panels use one base URL and change a status parameter. Any full URL works.

# Complete
https://panel.example.com/return?uid={RID}&s=complete&pay={PAYOUT}
# Terminate
https://panel.example.com/return?uid={RID}&s=terminate
# Postback (server to server)
https://api.panel.example.com/rd?uid={RID}&code={CODE}&tx={RDID}

Supplier questions

What do I need to integrate as a supplier?
The ability to append your respondent ID to a URL, and redirect URLs on your side for complete, terminate, over quota and quality outcomes. A postback endpoint and the supplier API are optional.
Can I keep my existing redirect URL format?
Yes. Enter your URLs with placeholders such as {RID}, {STATUS}, {CODE} and {PAYOUT} and ResearchDart fills them in for every respondent.
Why was my respondent stopped before the survey?
The session record includes the reason: a closed project or full quota, a repeat respondent ID, a duplicate device, or a pre-survey screening decision such as automation or an anonymised network. Each quality reason maps to a GDQ code.
What happens if my postback endpoint is down?
ResearchDart retries after 1, 5, 30, 120 and 720 minutes. You can reconcile at any time from the supplier transactions API.
How do I learn about reversals?
Reversed completes appear in the transactions API with the GDQ code, label, the buyer's note and the reversal date, and their payout drops to zero.

Further reading

Routing & Integration

Survey redirect status codes: mapping outcomes across sample platforms

Every sample platform encodes survey outcomes its own way, and a surprising amount of reconciliation pain is just translation errors between them. Map...

 Routing & Integration

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

 Data Quality

The GDQ removal codes, and why free-text reversal reasons have to go

Reconciliation has run on spreadsheets of IDs and reasons like "bad data" for as long as online sample has existed. The Global Data Quality code frame...

Connect your panel to ResearchDart

Tell us about your audience, countries and integration method. We will set up a supplier account and test links with you.

Talk to us Read the docs