Form field types¶
Forms in 3Common support a range of field types for collecting information from attendees and buyers. You can mix and match these fields to build registration forms, waitlist sign-ups, vendor applications, and more.
Field types¶
Input fields¶
These fields collect a response from the person filling out the form.
| Field | Description |
|---|---|
| Single-line text | A short text answer, up to 300 characters. |
| Multi-line text | A longer freeform answer, up to 1,000 characters. |
| An email address. Can be linked to a contact's email field. | |
| Phone number | A phone number. Can be linked to a contact's phone field. |
| Date | A date picker. Supports optional min/max date constraints. |
| File upload | A file upload. Supports filtering by file type (images, documents, audio, data). |
Selection fields¶
| Field | Description |
|---|---|
| Dropdown | Pick one option from a dropdown list. |
| Radio buttons | Pick one option from a visible list. Supports an optional "Other" freeform option. |
| Checkboxes | Pick one or more options. Supports optional minimum/maximum selection counts and an "Other" freeform option. |
| Yes/no | A simple yes/no toggle. Can be shown as a checkbox or a dropdown. |
Content blocks¶
| Field | Description |
|---|---|
| Text block | A block of static text, with no input. Use it to display disclaimers, instructions, consent notices, or any other information you want attendees to read while filling out the form. |
Text blocks¶
Text blocks let you add plain text to any position in your form without asking for a response. Common uses include:
- Consent and liability disclaimers
- Instructions for a specific section of the form
- Privacy policy notices
- Any contextual information the attendee should read before answering the questions below
Adding a text block¶
- Open the form builder for your form or event.
- In the element picker, select Text block from the field list.
- Drag it into the position you want in the form.
- Click the text block to select it, then type directly in the canvas. You can also use the Content field in the settings panel on the right.
The content you enter is exactly what attendees will see. There is no title or label shown above the text block in the form. If you leave the content empty, the text block will not display anything to attendees.
Text blocks in form responses¶
Because text blocks don't collect any input, they are not included in form responses. They won't appear as columns in the form response table, and they won't show up in the order side panel when you review an attendee's answers. If a section of the form (buyer or ticket-holders) contains only text blocks and no input fields, that section will not appear in the order side panel at all.
Conditional logic on text blocks¶
Text blocks support conditional logic. You can configure other fields in your form to show or hide a text block based on what an attendee selects. For example, you could show a liability waiver only when a guest selects a ticket type that requires one.
To set this up, use the conditional logic controls on the question that should trigger the text block's visibility.
Buyer only vs. ticket-holders¶
Every input field in a form is scoped to either the buyer or ticket-holders. This determines how many times the question appears at checkout and how many answers are collected per order.
Buyer only — The question is asked once, answered by the person placing the order. Use this for information you need one copy of per transaction: a contact email, a billing address, or a single consent acknowledgment.
Ticket-holders — The question is asked once per ticket in the order. If someone purchases three tickets, the question appears three times, once for each ticket holder. Use this when you need individual details from every person attending.
Which scope should I use?
Use buyer only for order-level information: contact details, a billing address, or a liability waiver they're signing for themselves.
Use ticket-holders when each person at the event may have a different answer: name, T-shirt size, accessibility needs, emergency contact, or dietary restrictions.
Setting a question's scope¶
The form builder organizes questions into two sections:
- Buyer — questions in this section are answered once by the person placing the order.
- Ticket-holders — questions in this section are answered once per ticket purchased.
To move a question from one section to the other, select it in the canvas and use the Apply to buyer or Apply to ticket-holders button in the settings panel on the right.
Text blocks follow the same placement rules. A text block in the ticket-holders section will repeat once per ticket, so a liability waiver in that section will appear once for each person.
What buyers see at checkout¶
When a buyer reaches the form during checkout, they see:
- The Buyer section first. Every question there is presented once regardless of how many tickets are in the cart.
- If there are ticket-holder questions, a separate group follows for each ticket. Each group is labeled with the ticket type and number (for example, General Admission — Ticket 1, General Admission — Ticket 2) and repeats the same set of questions.
A buyer purchasing two tickets will fill out buyer-scoped questions once and ticket-holder-scoped questions twice.
Viewing responses¶
In the form response table and the order side panel, buyer answers appear once per order. Ticket-holder answers appear in a separate entry for each ticket, grouped by ticket holder. If a section contains only text blocks and no input fields, it will not appear in the response view.