Fields on an in-person page
Updated October 5, 2026
Choose what you ask for, and how it reads, when the form is yours to build.
What it’s for
A page built on a connected event mirrors that platform’s form. An in-person page has no platform behind it, so the form is yours: you pick the fields, write your own questions, set the labels and placeholders, and decide what is required.
On step 2 · Form of an in-person page, the list is your form. The email is always there, it identifies each registrant, and two menus at the bottom add the rest: “Ready-made field” for the fields the builder already knows, “Add a question” for a question of your own.
Add what you need from “Ready-made field”: phone, job title, company, address, postal code, country, or a consent checkbox. One click adds it to the form, and it leaves the menu. “Remove field”, in the open row, takes one back out.
Click a row to open it, then “Customize label and placeholder” to unfold its two texts. A row whose label or placeholder you already wrote opens on them directly.
“Field label” is what visitors read above the field; leave it empty to restore the default. “Placeholder” is the example shown inside the field until someone types: optional, and empty by default. The live preview shows both as you type.
Several of those check what they collect, so the data arrives usable: a phone is stored in international format (+33 6 12 34 56 78), ready for an SMS tool or a CRM; an address suggests real addresses as someone types, so what you collect is spelled properly rather than four different ways; a postal code is checked for shape only, so a code from anywhere is accepted; country offers the full list.
“Add a question” asks for the kind of answer first: short text, long text, dropdown, multiple choice, checkbox, number or date. The question lands above the consents, already open, with the cursor in its Question box.
Write the question visitors will read. A dropdown or a multiple choice also needs its choices, from 2 to 50, each one once. A checkbox takes the sentence shown beside its box, and the other types take an optional placeholder. Until the question is written, and a list has two different choices, its row says Incomplete and visitors don’t see it.
Good to know
- The email can never be removed: it is the identity behind the registration, the check-in and the QR ticket.
- Each field and each question carries its own required / optional switch.
- A question works like the other fields: it can be required, shown only when an earlier answer matches, read by another field’s rule, moved to another step, filled in from the link and translated with the page.
- You can change a question’s type, or rename one of its choices, whenever you like: the answers already received stay as they were given. “Delete question” takes it off the form, and the answers it collected stay in the Registrants tab and the export, under its last label, tagged Deleted.
- Collect job title and company if you print badges. Those two lines come from these fields. Add address and postal code if you post anything to your registrants.
- Layout works exactly as elsewhere: columns, steps and wording have their own Form guides.
- A page built on a Livestorm or Zoom event works the other way round. The fields live on the platform and the page mirrors them, see “Fields, consents and re-import”.
Related articles
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?