Editor Content - Form Field
The Form Field allows you to create and customize input fields for your popup forms. It helps you collect user information such as names, email addresses, or phone numbers.
Accessing the Form Builder
When you add a Form component to your popup and click the gear icon, the Form Builder Settings panel appears.
This panel lets you configure each field type and customize how users interact with your form.
Form Builder Settings
Field Type
This section defines the type of input field you want to include in your form.
Available Field Types
Type: First Name
The First Name field type is used to collect the user's given name. It’s typically placed as one of the first input fields in signup or lead capture forms.
Field Settings
Label: The name displayed above or beside the input box.
Example: First name
Placeholder: The example text shown inside the input box before the user types.
Example: First name
Required: When enabled, this field must be filled out before the form can be submitted.
(Recommended for better data accuracy.)
Purpose
Use this field to personalize future communication with users, such as in email greetings or popup messages. It’s often paired with the Last Name and Email fields.
Best Practice
Keep the label short and clear. Avoid making too many fields required—shorter forms convert better.
Type: Last Name
The Last Name field type collects the user’s family or surname. It’s commonly added after the First Name field to capture a full name.
Field Settings
Label: The text displayed next to or above the input box.
Example: Last name
Placeholder: The hint text shown inside the input box.
Example: Last name
Required: When enabled, users must enter their last name before submitting.
(Optional if only the first name is needed.)
Purpose
Useful for collecting complete identification for CRM synchronization, billing, or account creation.
Best Practice
Use only when necessary to minimize form friction.
Type: Email
The Email field type collects a user’s email address. It automatically validates input to ensure proper email format (e.g., example@domain.com).
Field Settings
Label: The name displayed above or beside the input box.
Example: Email
Placeholder: The text displayed inside the box.
Example: you@example.com
- Required: When checked, users must enter a valid email before submission.
Purpose
Essential for collecting contact information, sending follow-ups, or newsletter subscriptions.
Best Practice
Always validate this field and consider including a consent checkbox if collecting emails for marketing.
Type: Text
The Text field type provides a single-line input box for short responses like usernames or company names.
Field Settings
Label: Text shown beside or above the input box.
Example: Company name
Placeholder: Example text shown before typing.
Example: Enter your company name
- Required: When checked, the field must be completed before submission.
Purpose
Use this for general text input where no special format is required.
Best Practice
Use clear, descriptive labels so users understand what to enter.
Type: Multiline Text
The Multiline Text field allows users to enter longer text, such as messages, comments, or feedback.
Field Settings
Label: The name shown next to or above the text area.
Example: Message
Placeholder: Hint text shown inside the box.
Example: Enter your text
- Required: When enabled, users must write something before submission.
Purpose
Ideal for open-ended responses such as feedback or questions.
Best Practice
Use a helpful placeholder and only require it if necessary.
Type: Phone
The Phone field type collects a user’s phone number. It includes formatting and country code options for standardized input.
Field Settings
Label: The name shown next to or above the field.
Example: Phone number
Placeholder: Sample text inside the field.
Example: +1 555 123 4567
Default Country: Sets the initial country code.
Example: United States (+1)
- Required: Ensures the user enters a valid phone number before submission.
Purpose
Used for SMS marketing, follow-ups, or verification.
Best Practice
Set the default country to your main target region. Only make it required when necessary.
Type: Hidden Field
The Hidden Field type stores invisible data not shown to users. It allows you to pass tracking information or campaign details with each submission.
Field Settings
Value: The predefined data stored in the field.
Example: campaign_2025 or signup_popup_v1
Purpose
Useful for:
- Tracking campaign sources
- Tagging users automatically
- Passing metadata to integrations
Best Practice
Keep values short, consistent, and descriptive.
Type: Radio Buttons
The Radio Buttons field allows users to select one option from a list.
Field Settings
Label: Title or question above the list.
Example: Choose an option
Items: Click Add item to create selectable choices.
Example: Email, Phone, SMS
- Required: Users must select one option before submitting.
Purpose
Use for single-choice questions like “Preferred contact method.”
Best Practice
Limit options (3–5 ideal). Keep labels short and clear.
Type: Checkboxes
The Checkboxes field allows users to select multiple options from a list.
Field Settings
Label: Title or question above the list.
Example: Select your interests
Items: Add one checkbox per option.
Example: News updates, Product launches
- Required: When checked, at least one option must be selected.
Purpose
Use when users can select multiple answers or preferences.
Best Practice
Use short, clear labels. For single-choice questions, use Radio Buttons instead.
Type: Dropdown List
The Dropdown List allows users to select one option from a collapsible list.
Field Settings
Label: Text or question above the dropdown.
Example: Select your country
Items: Add selectable options.
Example: United States, Canada, United Kingdom
- Required: When enabled, users must select one option.
Purpose
Ideal for long lists where space is limited.
Best Practice
Use dropdowns for large lists and radio buttons for shorter ones.
Type: Button
The Button field adds an actionable button, typically used to submit the form or trigger another action.
Field Settings
Button Text: The text shown on the button.
Example: Submit, Sign Up, Get Offer
Purpose
Completes user interaction by submitting the form or triggering an event.
Best Practice
Keep button text action-oriented and visually distinct. Use one primary button per form.
Type: Validation Message
The Validation Message field displays a warning or note when input doesn’t meet required conditions (e.g., missing data or invalid format).
Field Settings
Message Text: The message shown when validation fails.
Example: This field is required.
Purpose
Guides users to fix errors before submission and ensures accurate data collection.
Best Practice
Keep text polite, clear, and consistent in style and placement.
Field Settings Summary
Once a field type is selected, you can configure its details:
- Label – The field name shown to users.
- Placeholder – Example text inside the input box.
- Required – Makes the field mandatory before submission.
Additional Actions
- Add field – Insert a new input field below the current one.
- Delete field – Remove the selected field.
- Apply Changes – Save all modifications.
- Cancel – Discard unsaved edits.
The Form Builder enables you to create structured and user-friendly forms tailored to your campaign goals. By selecting appropriate field types, using concise labels, and applying clear validation, you can enhance user experience, improve data accuracy, and increase overall form conversions.
Learn how to configure and style your popup’s email input field to optimize signups and lead collection: Editor Content – Email Input