Branch using a hidden-field value
Use link context for a convenience branch, while keeping security decisions independent of editable URL parameters.
Select a screenshot to enlarge it.
Steps
- Create and save the hidden field under Logic → Customize using data → Hidden Fields.
Definitions identify the fields expected in the respondent URL. Supply harmless URL-encoded values when testing. - Open Branching & Calculations at the question where the branch should apply.
- Select the saved hidden field as the condition source if the editor offers it, choose the comparison, and enter the expected value.
- Choose a valid destination, complete every condition and action, and select Save logic.
Read the condition and destination together. This example was canceled; it does not demonstrate a saved or executed rule. - Test a matching value, a different value, and a link without the field. Ensure every path reaches a valid next step.
Check before you rely on it
A missing field needs a deliberate fallback. Avoid sending a respondent to a question already passed or back to the same question.
If you need help
Hidden fields are caller-controlled context. They must not grant access to private results or account data.
Contact support with the relevant screen, time, and a redacted description. Keep credentials and private respondent information out of screenshots.