• FORM FIELDS AND CONDITIONAL LOGIC • SETUP GUIDE

How to Use the HTML Block in a Form

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 HTML block for formatted explanatory content placed between application questions. 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 formatted explanatory content placed between application questions. It organizes the form and does not collect an 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 HTML block

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

  2. Expand its settings and enter a clear label or heading, such as How we review applications.

  3. Add concise explanatory HTML using the supported content control. Explain the review process or document requirements, and use ordinary links where appropriate. Keep the content readable alongside the actual field labels.

  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: How we review applications

Example: We review your details before enabling wholesale access.

Adapt this example to the information your team needs. Keep it as supporting content beside the real questions.

Test and expected result

Preview the block on desktop and mobile and open any links. Complete the form to confirm the content does not obscure controls, required-field errors, or popup actions.

Expected result: the content appears in the right position and applicants can complete the surrounding questions without confusion.

Limitations and important behavior

HTML block is display content, not an applicant answer. Custom JavaScript is not supported. Use the app’s Appearance settings or Custom CSS for design changes rather than embedding scripts.

Troubleshooting

If formatting breaks the layout, simplify the markup and check its nesting. If you need a response or acknowledgement, add an appropriate input field rather than expecting the explanatory block to collect an answer.

Screenshots to add

  • Screenshot placeholder: Builder with HTML block expanded, showing How we review applications and the applicable saved settings.
  • Screenshot placeholder: Storefront showing the content in position beside its related questions.

Related guides