1 · Pass the Samply IDs into the survey
A Hidden Value Action on the first page populated with the URL-variable merge code [url("msg")] (lowercase) names and stores the parameter for export.
- On the FIRST page, Add New → Action → Hidden Value; give it a title like "Samply Message ID".
- In the value, click "Select a Merge Code", search "URL variable", insert it and set the name to your parameter, e.g. [url("msg")]. The merge-code name MUST be lowercase.
- Repeat for the Samply ID and participant code as needed.
- When exporting, enable "Include URL Variables" so the values appear.
Example start link
https://<survey>.alchemer.com/s3/<id>/survey?id=%SAMPLY_ID%&code=%PARTICIPANT_CODE%&msg=%MESSAGE_ID%
2 · Register completion
A URL Redirect Action on the final page; the URL field is merge-code compatible, so the path carries [url("msg")].
- Capture the message id first (Hidden Value with [url("msg")]).
- On the LAST page, Add New → Action → URL Redirect.
- In the protocol dropdown choose https://, and in the URL field put host+path WITHOUT the protocol: samply.uni-konstanz.de/studies/<study-slug>/done/[url("msg")].
- Do NOT use "Fields To Pass" (that appends ?name=value query strings rather than building the /done/<id> path). Save and test.
Example completion redirect
samply.uni-konstanz.de/studies/<study-slug>/done/[url("msg")] (choose https:// in the protocol dropdown)
Reserved parameters & gotchas
Do not name a variable source (breaks quotas/logic) or sguid (reserved). The merge-code name inside [url("…")] must be lowercase, though the incoming key is matched case-insensitively.
Things to watch out for
- Alchemer's redirect docs mostly show appending query strings via "Fields To Pass"; the path-style approach relies on the URL field being merge-code compatible — verify the rendered redirect in a test response.
- The merged value must not contain http://; the protocol is set by the dropdown, so put only host+path in the field.
Sources
These steps were verified against the platform's official documentation.