StudiesDocsSign inCreate account
docs/Power features/Qualtrics
connect your survey tool

Qualtrics.

Capture the Samply IDs as Embedded Data, then redirect from the End of Survey element.

Plan requirement
The end-of-survey redirect is not available on free Qualtrics accounts — it needs a licensed/institutional account.

1 · Pass the Samply IDs into the survey

Embedded Data in the Survey Flow, left unassigned so Qualtrics fills each field from the matching query-string key.

  1. Open the Survey Flow (Survey tab → Survey Flow), click "Add a New Element Here" and choose Embedded Data.
  2. Add one field per Samply placeholder, named EXACTLY like the query-string keys in the start link (e.g. msg, id, code). Leave each unassigned so it reads "Value will be set from Panel or URL". Capitalization must match.
  3. Drag the Embedded Data element to the TOP of the Survey Flow (above anything that uses it) and save the flow.
  4. Configure the Samply start link so its keys match these field names. The fields are then stored with every response and appear in the data export automatically.
Example start link
https://<your-org>.qualtrics.com/jfe/form/SV_xxxx?id=%SAMPLY_ID%&code=%PARTICIPANT_CODE%&msg=%MESSAGE_ID%

2 · Register completion

The End of Survey element's "Redirect to a URL" option, piping the captured field with Qualtrics syntax ${e://Field/msg}.

  1. In the Survey Flow (or Survey Options) open an End of Survey element, click "Customize…" and check "Override Survey Options".
  2. Select "Redirect to a URL".
  3. Enter the Samply completion URL with the captured message id piped in: https://samply.uni-konstanz.de/studies/<study-slug>/done/${e://Field/msg} (use whatever field name holds %MESSAGE_ID%).
  4. Optionally use ${e://Field/msg?format=urlencode} to be safe, then save and publish. Test with a real Samply link end-to-end.
Example completion redirect
https://samply.uni-konstanz.de/studies/<study-slug>/done/${e://Field/msg}

Reserved parameters & gotchas

Avoid Q_-prefixed names (Q_Language, Q_TotalDuration, …) and other built-ins (RID/rid, SID, EndDate, IPAddress). Field names are case-sensitive and must match the URL keys exactly.

Things to watch out for

  • The message id sits in the URL path; Samply's %MESSAGE_ID% is a plain 15-char ID, so it is URL-safe, but ${e://Field/msg?format=urlencode} is the cautious choice.

Sources

These steps were verified against the platform's official documentation.