Understand hidden fields

Hidden fields attach context supplied through a form link. They do not hide information securely or prove a respondent’s identity.

2 min read · Last reviewed

On this page

Select a screenshot to enlarge it.

Steps

  1. Choose the context you need, such as a campaign source or a non-sensitive product reference.
  2. In Design → Logic → Customize using data → Hidden Fields, add a distinct field name and save it.
    In Design, open Logic → Customize using data to find Hidden Fields and Variables.
    Definitions identify the fields expected in the respondent URL. Supply harmless URL-encoded values when testing.
  3. Add that field as a query parameter to a copy of the respondent link, preserving the link’s existing parameters.
    Use the current respondent URL rather than a builder URL.
  4. Open the link with a harmless test value and complete a synthetic response. Inspect the intended response detail or integration output.
  5. Test the link with the parameter missing and decide how the form should behave.

Check before you rely on it

For a campaign field named source, append &source=newsletter when the copied URL already contains a question mark. URL-encode the value.

If you need help

Anyone with the link can inspect or change its query parameters. Do not use a hidden field as authorization.

Contact support with the relevant screen, time, and a redacted description. Keep credentials and private respondent information out of screenshots.

Related tasks