• FORM FIELDS AND CONDITIONAL LOGIC • SETUP GUIDE

How to Use the Hidden Field

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Use Hidden for configured context that should travel with the application without a visible question. This guide explains setup, a practical example, and how to check the result on your Shopify storefront.

When to use it

Choose this type when you need configured context that should travel with the application without a visible question. Choose the type before configuring mappings, visibility conditions, or approval rules that depend on the answer.

Before you begin

Open the intended form in Rivio B2B Registration Forms and confirm its name and storefront slug. Inspect template fields and smart-block sub-fields so you do not ask for the same information twice. Use dummy details for your first test.

Set up Hidden

  1. In the form builder, select Add field and choose Hidden.

  2. Expand its settings and enter a clear label or heading, such as Application source.

  3. Give the hidden data a meaningful key or label and enter its intended value using the controls provided. Keep this value descriptive, such as a campaign source, rather than sensitive or permission-related.

  4. Drag the element into the intended position. If the form uses steps, review its assigned step.

  5. Select Save, preview the form, and confirm the actual storefront page loads this saved form’s slug.

Example

Question or content: Application source

Example: partner-directory

Adapt this example to the information your team needs. Use help text to explain the expected answer, and require it only when your review process needs it.

Test and expected result

Save, open the actual storefront form, submit dummy answers, and inspect the recorded hidden value. Check each placement if you use separate forms or copies for different sources.

Expected result: the saved application contains the intended answer. Any configured visibility, rule, or mapping is checked separately; collecting an answer does not itself approve an applicant.

Limitations and important behavior

Hidden fields are not secret storage or trusted authorization. Do not store passwords, API keys, approval decisions, or price entitlements in them. Do not assume automatic URL or product-value capture unless the app explicitly configures it.

Troubleshooting

If context is absent or wrong, inspect the saved value and the slug used by the actual page. A hidden field does not establish a secure server-side source or prove that a buyer qualifies.

Screenshots to add

  • Screenshot placeholder: Builder with Hidden expanded, showing Application source and the applicable saved settings.
  • Screenshot placeholder: Dummy submission showing the example answer; include the storefront input if it helps explain selection or validation.

Related guides