Unique codes for each respondent

You can attach a respondent-specific code to every submission by passing it through hidden variables in the survey URL. That code is stored with the answer row, so exports and Analysis stay tied to your CRM row, ticket ID, employee number, or invitation batch—without asking people to retype an ID they already have on your side.

Responsly does not mint or email unique codes for you. You create and manage codes in an external tool (for example a CRM, HR system, spreadsheet mail merge, or script), then substitute each value into the link you send.

How it fits together

In Responsly, define a hidden variable for the code (for example respondent_id or token).
Build the URL template Responsly shows for that variable (see What is hidden variables? for setup and the usual X placeholder pattern).
In your external system, generate or look up one value per person.
Send each respondent their own link with that value in the query string.
When they submit, the code is saved alongside the rest of the answers.

You can combine codes with a personalized greeting using the same mechanism—see Greeting the respondent.

Identification and duplicate control

Per-respondent codes are a common pattern for identification of respondents when you already know who should answer. They also pair well with rules that limit duplicate submissions—see Prevent survey duplicate submissions for options that match how you distribute the survey.

FAQ

Does Responsly generate unique codes for each respondent?

No. Responsly stores whatever value you pass in the survey URL using hidden variables. You generate one-off or sequential codes in your own systems—CRM, HRIS, spreadsheet mail merge, or custom scripts—and substitute them into each personalized link.

How do I pass a unique code into a Responsly survey?

Define a hidden variable in the survey settings, build the share URL template that includes that parameter, then replace the placeholder with each person’s code before sending the link. Values are saved with their response.

Why use per-respondent codes instead of only an email question?

Codes let you pre-identify rows before open, reduce typos versus self-reported IDs, support offline lists, and give a stable key for exports even when you do not collect an email address.