Glossary
What is Hidden fields?
How it works
You declare the fields on the form (source, customer, plan) and add values to the link you share: forms.example.com/feedback?source=email&customer=4821. When someone opens that link and submits, the values are stored alongside their answers.
Because you set the values, hidden fields are ideal for things the respondent shouldn’t have to type or can’t know, such as a campaign name, an order number or an account ID.
Example
A subscription company emails an NPS survey to every customer. Each email’s link carries the customer’s plan and signup month. When results come in, the team filters by plan and sees that annual customers score much higher than monthly ones, without asking anyone which plan they’re on.
Tips
- Never put sensitive data (passwords, health details) in a link; links get forwarded and logged.
- Use short, consistent field names, and document them for anyone who builds links.
- Combine hidden fields with logic to skip questions you already know the answer to.
- Use UTM parameters as hidden fields to see which campaigns bring responses.
Hidden fields in FormsAI
In FormsAI, add hidden fields in the Logic tab and put values in the link. They’re saved with each response, on every plan. Branch on them, recall them in text (“Hi {{hidden:name}}”), pre-fill answers, and filter and export by them. Embeds pass the page’s own query string through, and the values appear in webhooks and the API.
FAQ
Hidden fields, answered
Can respondents see hidden fields?
Not on the form itself, but the values are visible in the link they opened. Don’t put anything private in a hidden field.
Can hidden fields pre-fill a question?
Yes, in FormsAI a hidden field can pre-fill an answer, such as an email address you already know, so the respondent only checks it.