Hidden Field
Purpose
The Hidden field type renders a hidden input that submits a value with the form. The value can come from a preset (e.g. page name, post ID) or from Custom or ACF.
When to use
- Pass page title, URL, user ID, or other server-side value without showing a field.
- Prefill from ACF or custom logic.
Key settings
- Field — Field Type: hidden.
- Hidden — Hidden Value (source: e.g. page_name, custom, ACF), Hidden Value Custom, Hidden Value ACF.
Top features to configure
- Hidden value source — Choose whether the value comes from system data, custom text, or ACF.
- Hidden value custom — Pass fixed context such as campaign/source tags.
- Hidden value ACF — Pull dynamic values directly from ACF fields on the current item.
- Context tracking — Use hidden fields to pass metadata without adding visible inputs.
Validation behavior
- Hidden fields are submitted with the form even though users do not interact with them directly.
- The submitted value depends on the selected source (preset, custom, or ACF).
- A missing or invalid source can produce empty values in entries and integrations.
Common mistakes
- Choosing an ACF source that is unavailable on the current page/post context.
- Assuming hidden values are visible for user confirmation when they are not.
- Passing hidden values without testing where the form is embedded.
Verify it works
- Submit a test entry and inspect the hidden value in Entries.
- If using ACF, test on the exact content type where the field should resolve.
- Confirm mapped notifications or integrations receive the hidden value.
What's Next
- Use Field mapping to send hidden values into mapped destinations.
- Pair with Step field and HTML content for guided multistep workflows.
- Check FAQ when hidden values are missing.