The form builder offers a full set of field types, grouped by purpose. Drag any
of them onto the canvas from the field palette.
| Field |
Use for |
| Text |
Short single-line input, such as a name or company |
| Email |
Email address; maps to the contact email and validates format |
| Textarea |
Longer multi-line input, such as a message |
| Number |
Numeric input, such as a quantity or age |
| Phone |
Telephone number |
| URL |
A web address |
| Field |
Use for |
| Select |
A dropdown of choices, one selection |
| Radio |
Visible options, one selection |
| Checkbox |
One or more toggles, or a single yes/no |
| Field |
Use for |
| Date |
A date picker, such as a preferred contact date |
| Hidden |
A value the visitor does not see, such as a source or campaign tag passed in the page |
| Field |
Use for |
| Consent |
A required opt-in checkbox with your consent text, for GDPR-style capture |
| Field |
Use for |
| File |
A file upload, such as a document or image |
| Field |
Use for |
| HTML |
Custom static markup between fields, such as an intro paragraph |
| Divider |
A visual separator to group sections of a long form |
Any input can map to a contact field so the value is stored where you can use it:
- Map Email to the contact email (required for a usable contact).
- Map name inputs to first and last name.
- Map anything else to a custom field by key.
Mapped values become available for segmentation and for
personalization in later emails. For example, a mapped
company field can be greeted with {{contact.meta.company}}.
Mark a field as required to block submission until it is filled. Email fields
validate address format automatically. Keep required fields to a minimum, because
each one reduces completion.
See Forms for building and placing a form, and
Spam Protection for adding a CAPTCHA.