Design a registration form

The form designer builds the data collection screens used during registration. A form can contain several pages, sections, and field types.

Before you start

Open a session and make sure “Registration & Sales” and “Registration Forms” are available in the navigation.

Create a form

1. Open “Registration & Sales” > “Registration Forms”.
2. Select “Create Form”.
3. Enter the “Form Name”. The “Slug” is generated from the name and can be edited at this stage.
4. Select “Next”.
5. Choose “Blank Form” to start without content or “Use a Template” to start from one of the available templates:
   • “Event registration”: personal information, organization, and consents;
   • “Survey”: satisfaction survey with ratings and multiple-choice questions.
6. When using a template, select its card to open the designer with the initial structure.

The “Form Templates” list shows the name, display name, mode, entity type, and status. The row actions let you edit, duplicate, or delete a form.

Understand the designer

Area	Use
Pages	Select, add, and reorder form pages.
Elements	Add input fields and content blocks.
Properties	Configure the selected page, section, or element.
Design / Preview	Switch between building the form and viewing the participant experience.
Save	Keep the changes made to the form.

Pages contain sections, and sections contain fields and blocks. Use “Add Page”, “Add Section”, and “Add element” at the corresponding level. Use the drag handles to reorder the structure.

Add elements

The “Elements” panel includes:

• input fields: text, text area, number, email, phone, URL, date, date and time, time, password, and hidden field;
• choice fields: select, multi-select, tree select, autocomplete, checkbox, checkbox group, radio buttons, and toggle;
• file upload, slider, and color picker fields;
• content blocks: headings, static text, HTML content, images, dividers, spacers, buttons, and alerts.

1. Select the destination section.
2. Add the item from “Elements”.
3. Select the new item on the page.
4. Configure it under “Properties”.

Configure a field

Input field properties are grouped by purpose.

General

• “Label” defines the text shown to the user.
• “Field Binding” links the answer to a data field, such as person.firstName or a custom field.
• “Placeholder”, “Help Text”, and “Default Value” provide supporting content.
• “Required”, “Read-only”, “Visible”, and “Disabled” control the field behavior.
• “Required Message” customizes the message shown when a required field is empty.

Validation

Text fields can use a minimum length, maximum length, regular expression, and a specific pattern error message. Set these rules to match the data you expect to collect.

Presentation and visibility

Use “Style” and “Layout” to adjust the field presentation. “Visibility Rules” can make its display depend on other form data.

Add a custom field

When the data you need to collect doesn’t match any standard field, create a custom field directly from the form field, without leaving the designer.

1. Open “Field Binding” in the field properties.
2. Scroll down to “Create custom field” (“+” icon), at the bottom of the list, and select it.
3. Enter the “Label” — the technical “Code” is generated automatically from the label and can no longer be changed after creation.
4. The “Type” is preselected and limited to the types compatible with the form field being configured.
5. Add a description, placeholder, and, for choice types, the options (manual entry or an existing reference list) as needed.
6. Select “Create”.

The custom field is created for the form’s entity type (participant, company, or exhibitor), automatically bound to the field being edited, and then available under the “Custom Fields” group of any other compatible binding. It can later be managed from “Settings” > “Custom Fields”.

Configure a section or page

A section has a title, description, and icon. It can be collapsible or hidden and has its own style, layout, and visibility settings.

For a page, select it in “Pages”, then edit its properties. Add another page when the form should be presented as a sequence of steps.

Consent checkboxes

The labels of checkboxes, checkbox groups, and toggles accept HTML tags. You can therefore link to your terms and conditions or privacy policy directly inside the consent text:

I agree that my personal data will be processed as part of my registration,
in accordance with the
<a href="https://example.com/privacy">privacy policy</a>.

Links automatically open in a new tab, and the HTML is sanitized for security: only links and formatting tags are kept.

Suggested wording to adapt:

Consent	Suggested wording
Terms	“I have read and accept the terms and conditions of sale.”
Personal data	“I agree that my personal data will be processed as part of my registration, in accordance with the privacy policy.”
Marketing	“I agree to receive communications about the organizer’s news and offers.”
Tracking	“I agree that my browsing may be measured for audience analytics (cookies / pixel).”

Link without a URL

A validation warning flags any link whose href attribute is missing or empty in a label, help text, or choice option.

Configure the complete form

Open the “…” menu in the top bar.

Form Settings

Configure the “URL Slug”, “Display Name”, title display, description, default language, and “Enabled” state.

The “Submission Settings” define the “Default category”: it is assigned to the participant on creation if the form does not provide a category. Without a category, the participant is created as a prospect.

Changing the default language

If the selected language has no translation yet for this form, its content (labels, text, messages) is automatically translated with AI and becomes the new default content. If the language already has translations, those become the new default content instead. Either way, the previous default language is kept and remains available from the “Translations” tab.

Form Style

Choose a preset — Eveos, Modern, Corporate, Dark, or Minimal — then adjust colors, typography, width, spacing, logo, background image, and custom CSS. The preview panel reflects these settings while you work.

Other tools

The same menu provides “Export Form”, “Import Form”, “Translations”, and “Help”.

Before importing

Check the file you are about to import and keep an export of the current form if you may need to restore its configuration.

Translate the form

Every form has a default language (set in the form settings) and can offer as many additional languages as needed. Open the “…” menu in the top bar, then “Translations” to manage multilingual content.

Add a language

1. The “Translations” window shows the form’s “Default Language” at the top.
2. Under “Additional Languages”, pick a language from the “Add Language” dropdown (searchable). The available languages come from the organizer’s languages reference list.
3. The language appears in the list with a progress bar showing the percentage of translated items.

To remove a language and all of its translations, click the trash icon next to the language.

Translatable content

Select a language to open the translation table, with the “Key”, “Original”, “Translation”, and “Type” columns. Every text in the form is listed:

Type	Content
page	Page titles and descriptions
element	Field labels, placeholders, and help texts; section titles and descriptions; component headings, static texts, alerts, and button labels
button	Submit button text
message	Form display name and confirmation message

Type or fix each text directly in the “Translation” column. A field left empty falls back to the default-language text.

Translate with AI

The “AI Translate” button offers two actions:

• “Translate empty fields”: only items without a translation are translated automatically — existing translations, including manual ones, are kept.
• “Retranslate all”: after confirmation, replaces every translation of the language with new AI-generated translations. This action cannot be undone and manual translations are lost.

Review and save

Translations are part of the form: select “Save” in the designer to keep them, and use “Preview” to check the rendering in each language.

On the participant side, the public form’s display language is driven by the registration flow: its default language and available languages are configured in the flow settings (see Configure a registration flow).

Review validation

The designer top bar shows a validation indicator: a green check when everything is correct, or a warning badge otherwise. Click it to open the “Form Validation” panel, which lists errors, warnings, and suggestions. Clicking an entry selects the related field or opens the relevant panel.

Notable warnings:

Warning	Meaning
No category assigned	No “Category” field guarantees a value (field missing, or hidden without a default value) and no “Default category” is set in the settings: submissions will create prospects.
Conditional category	The “Category” field — or a parent section or page — depends on visibility rules: assignment is not guaranteed. Set a “Default category” to secure it.
Link without a URL	An HTML link in a label, help text, or option has no href attribute.

Check the form

1. Select “Preview”.
2. Choose an available language in the preview.
3. Move through every page with the form controls.
4. Check labels, help text, required fields, choices, and visibility rules.
5. Return to “Design” to correct the structure.
6. Select “Save”.

Map the form

After designing the form, open the mapping tab on the “Registration Forms” page to choose a default template and, when needed, a template for an individual participant category. Categories without a mapping use the default template. A registration flow can also map a form to a product under its “Registration” step.

Continue with

• Configure a registration flow
• Manage participants