Fields on an in-person page
Updated July 31, 2026
Choose what you ask for, and how it reads, when Venue owns the form.
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 their 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 “Add a field” at the bottom offers the rest.
Click a row to open it. “Field label” is what visitors read above the field; leave it empty to restore the default.
Add a placeholder — the example shown inside the field until someone types. Optional, and empty by default. The live preview shows both as you type.
Add what you need from “Add a field”: phone, job title, company, or a consent checkbox. “Remove field”, in the open card, takes one back out.
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 carries its own required / optional switch.
- Collect job title and company if you print badges — those two lines come from these fields.
- 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 Venue 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?