• FORM FIELDS AND CONDITIONAL LOGIC • SETUP GUIDE

How to Use the Email 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 Email for a reachable applicant address used for follow-up and customer matching. 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 a reachable applicant address used for follow-up and customer matching. 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 Email

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

  2. Expand its settings and enter a clear label or heading, such as Business email.

  3. Use a clear label, explain which contact should receive updates, and make the field required when your workflow needs applicant emails or customer creation. Review the supported customer-email mapping.

  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: Business email

Example: buyer@example.com

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

Try an invalid email format and then an email you control. Submit the valid application, inspect the recorded address, and check its application-received message if enabled.

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

Email format validation does not prove mailbox ownership or business identity. Email marketing integrations need an Email field or Customer block. Only the first email is used for the customer as indicated by the builder.

Troubleshooting

If the customer or notification uses an unexpected address, inspect duplicate Email fields and the Customer block. Compare the address actually recorded on that application before changing mappings.

Screenshots to add

  • Screenshot placeholder: Builder with Email expanded, showing Business email 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