Documentation

Setting up a Dynata respondent source

Use a Dynata respondent source to connect a manually configured Dynata project with signed survey entry and outcome links. Obtain the project's key ID and secret key from the project owner before creating the source.

Create the respondent source

  1. On the survey's Summary tab, select Add respondent source and choose Dynata.
  2. Enter the source's name, target responses, market, default language and domain. Set days in field and the other source controls as needed.
  3. Choose Link signing mode. Use Signed for signed respondent entry and return links. Use Signed+ when Dynata also validates a fixed study identifier.
  4. For Signed+, enter Survey identifier and agree its value with Dynata. Dynata must validate it as _d on both entry and return links.
  5. Enter Dynata keyId, containing digits only, and Dynata secret key. Both credentials are required when creating the source. Preserve the secret key's exact spelling and case.
  6. Save the source.

Credentials are encrypted and write-only. Saved source details and generated launch links omit the secret key.

The screenshots use example domains and links. Copy your source's generated links when configuring Dynata.

Dynata respondent source in Signed mode with Sample Integration links and masked credentials

With Signed+ selected, the form also shows the required Survey identifier.

Dynata respondent source in Signed+ mode with a sample survey identifier and masked credentials

Send the launch templates to Dynata

Use Sample Integration to copy the generated Survey URL and Test URL. Dynata sources provide separate live and test links, and both require valid signatures.

The generated templates preserve the literal {psid} and {_k} placeholders. Send the complete generated links to Dynata so they can configure respondent substitutions and signing in the declared parameter order.

ModeEntry parameter order before Dynata adds the signature
Signedpsid={psid}&_k={_k}
Signed+_d=<survey-identifier>&psid={psid}&_k={_k}

The fixed Signed+ identifier is URL-encoded in the generated link. Dynata substitutes the respondent PSID and key ID, signs the populated path and query, and appends _s. Keep the generated template's ordering and encoding when configuring Dynata.

MX8 Labs validates the signature, configured key ID and Signed+ study identifier on entry. Missing, duplicate or undeclared parameters and unresolved placeholders fail validation.

Outcome redirects

The platform generates a fresh signed return URL for each outcome using the respondent's original PSID and key ID. Signed+ returns also carry the configured study identifier. These outcome links are generated automatically for the Dynata return endpoint.

Survey outcomeDynata outcome code
Completerst=1
Terminated, consent refused, poor quality or duplicate respondentrst=2
Quota screenout or quota overquotarst=3

An invalid signature with a recognizable respondent and configured key returns a signed rejection with rst=2 and svFlag=1. Missing or ambiguous identity opens the local invalid-link page.

Test before fielding

Use a Dynata test project and its signed test link to check the complete handoff. Confirm the substitutions, parameter ordering and encoding with Dynata. Exercise Complete, Screenout and Quotafull, an invalid entry signature, and the Signed+ identifier check. Resume a survey and confirm the final redirect retains the original respondent identity.

Agree the return endpoint and the consent, quality, duplicate and quota outcome mappings with Dynata before fielding.

Update or rotate credentials

When editing a saved source, leave both credential fields blank to keep the saved pair. Enter both values together to replace them, when the source's fielding status permits the edit.

Coordinate rotation with Dynata. Respondents already admitted retain their original key ID and signed return URLs, so Dynata must continue accepting that pair until those respondents finish. Test the new launch credentials and an existing respondent's return before resuming fielding.

Deleting the source also removes its stored credential pair.