Field types and conditional logic
The 8 field types, mapping fields to contacts, and single-condition visibility rules.
Field types
| Type | Notes |
|---|---|
text | Single-line text |
email | Single-line, expected to hold an email address |
textarea | Multi-line text |
number | Numeric input |
select | Dropdown — needs Options |
checkbox | Boolean |
radio | Single choice, shown as radio buttons — needs Options |
date | Date picker |
Each field also has:
- Label — shown to the visitor.
- Placeholder — optional hint text.
- Required — blocks submission if empty.
- Maps to contact field — see below.
Mapping fields to a contact
A field's Maps to contact field setting decides what happens to its value on submission. It's either:
- One of the standard contact columns:
email,firstName,lastName,phone,company, or - A custom field you've defined.
A field with no mapping is still recorded in the raw submission (see
Viewing submissions), but doesn't write anywhere on the
contact record. At least one field should map to email — that's what Threadliner uses
to match the submission to an existing contact or create a new one.
Conditional logic
A field can have a conditional rule: show this field only if another field's value matches. In the field editor this appears as an "Only show if another field matches a value" checkbox, which reveals a target field and value to compare against.
This is a single-condition rule (field equals/doesn't equal one value) — not a boolean expression engine. You can't chain multiple conditions on one field or reference more than one other field. For multi-step logic, use separate fields each with their own single condition.
Last updated on