Skip to main content

External ID

Capture unique IDs like customer or employee numbers with the External ID question in Zonka Feedback.

Abhishek avatar
Written by Abhishek
Updated this week

The External ID question type allows you to capture a unique identifier for respondents, such as a customer ID, employee ID, booking ID, or membership number. This helps you link survey responses to your existing systems like CRM, HRM, POS, or support tools.

Use External ID when:

  • You want to map survey responses to a unique record in another system

  • You need to track feedback at an individual or transaction level

  • You’re integrating with CRMs, HR software, or ticketing systems

📌 External ID is available on all Zonka Feedback plans.


In this article

  • What is an External ID question?

  • Where to use it

  • How to add an External ID question

  • Customization options

  • Things to keep in mind


What is an External ID question?

  • A unique identifier field that captures numeric or alphanumeric values

  • Commonly used to link responses with external databases

  • Does not display personally identifiable information (PII) but ensures accurate tracking


Where to use External ID

  • Customer feedback surveys linked with order or booking IDs

  • Employee feedback surveys using staff IDs

  • Healthcare or finance surveys where identifiers are mandatory

  • Ticketing or service desk feedback using ticket/case numbers


How to Add an External ID Question

To add an External ID field to your survey:

  • Go to the Survey Hub and open the survey you want to edit.

  • Navigate to the Build section.

  • From the Question Types Panel, locate and select External ID under the Contact Information category.

  • Drag and drop the External ID field from the question list into your survey.

  • Click on the field to edit the label text, for example: “Enter your Customer ID”.


Customization options

  • Question Label: Modify as per your requirement (e.g., “Booking ID”, “Employee ID”)

  • Placeholder Text: Provide input hints (e.g., “ABC12345”)

  • Make Required: Ensure no response is submitted without an ID

  • Validation: Restrict to numeric or alphanumeric formats for accuracy


Things to keep in mind

  • External IDs are stored as part of the response and contact record

  • Useful for integrations and reporting, ensuring each response is tied back to the right entity

  • Not meant for anonymous surveys


Frequently Asked Questions

Can External ID be alphanumeric?
Yes, it supports both numeric and alphanumeric inputs.

Does External ID sync to Contacts?
Yes, it is stored with respondent data and can be used for segmentation.

Can I use External ID for API-based surveys?
Yes, it’s commonly used to map external system IDs via APIs and integrations.

Did this answer your question?