Use Hidden to carry a browser-supplied reference such as a campaign name without displaying a question. It is a real submitted string, unlike Content or Section. Its label identifies it in the builder and entry tools.
Availability: Core (Free).
Add and configure the field
- Open the form in Build and add Hidden from Add fields.
- Select its canvas card to open Field options, then configure the controls below.
- Save the form and check its saved Preview and embedded page.
Field-specific settings
| Setting | What it does |
|---|---|
| Default value | Seed the initial hidden input with a string. A deliberately submitted blank stays blank and the string 0 remains a real value. |
Applicable shared options
This field also provides Label. See common field options for their behavior.
Dynamic population offers Disabled, Parameter, Current user. Parameter name binds an external URL or embed value. User property selects the supported WordPress profile value. Submitted or cleared answers are not refilled.
No duplicates and Duplicate value message require Pro. They compare accepted entries for this form and field, separately from Required.
Answers and behavior
The public form has a hidden input with no visible grid footprint. Its builder preview is disabled and marked Hidden. Saved values are available to entries, selected columns, searches, notifications and merge tags.
Its conditional control uses Include / Exclude this value. An excluded value is cleared and omitted; inclusion never makes it a visible input. Hidden can also be a condition source. There is no separate visibility selector.
Hidden values can be inspected and changed in the browser. Use them for context, rather than trusted authorization, ownership, permissions or a price that must be protected. Internal visibility is a separate server-owned workflow; visually hiding an ordinary field does not turn it into Internal.
Example and checks
For a campaign reference, label the field Campaign and choose Parameter dynamic population with parameter name campaign. Open the form using a URL containing ?campaign=spring, then inspect a test entry. Test the page with no parameter and with an explicit empty candidate as well.
Keep shared cached pages from leaking personalized populated values. If the value needs to be authoritative, have a developer derive or validate it on the server. See dynamic population for precedence and initial-value behavior.
Use the testing checklist to check validation and the saved entry. Explore all fields provides live examples.
