Fields, consents and re-import
Updated September 23, 2026
The form mirrors your Livestorm fields; manage them at the source and re-sync.
What it’s for
The Form step mirrors your Livestorm registration form: same fields, same custom fields, same consents, with their required state. You control how each field behaves and reads on your page, not the list itself.
On step 2 · Form, the field list shows exactly what's configured in Livestorm, including custom fields and consent checkboxes.
Open a field’s row to say what it really asks for. Under “Field type”, a field your platform sends as plain text can become Long text, Phone, Website, Number, Date, Postal code, Address or Country.
Visitors then get the control that fits, and Venue checks the answer before accepting the registration: a phone is stored as an international number, a website with its https, a date the same way whatever calendar the visitor uses. Your platform still receives every answer as text.
Still in the row, “Customize label and placeholder” opens the field’s two texts. “Field label” renames the field on your page only; leave it empty to bring back the label Livestorm sends. “Placeholder” is the example shown inside the field until someone types; left alone, the field suggests what its type expects.
A checkbox has no placeholder, so its button reads “Customize label”. A consent keeps its wording: it is the platform’s legal text. Added, renamed or removed a field in Livestorm? Click “Re-pull from Livestorm” to re-sync the form. Your types and placeholders survive it.
Adding and removing fields always happens on the Livestorm side.
Good to know
- For a connected event you can't add or remove a field from Venue. That's what guarantees a sign-up stays valid in Livestorm. An in-person page has no platform behind it, so there you own the field list: see “Fields on an in-person page”.
- A re-pull keeps a label you changed on your page. A label you never touched follows Livestorm, so a field renamed there is renamed on your page too. A field’s Visibility survives it, Never as much as a When… rule: see “Show a field only when an earlier answer matches”.
- Both texts stay folded behind that button while they are the defaults. Once you have written one, the row opens straight on them.
- An Address field suggests real addresses as someone types, and a visitor can always ignore the suggestions and write their own: an address the lookup has never heard of never blocks a registration.
- A Livestorm question that accepts several answers shows as checkboxes and keeps every ticked one. A page created before that worked shows a single dropdown for such a question: re-pull the event and it comes back as a multiple choice.
- The layout (columns, steps, wording) is set separately. See the dedicated Form guides.
- Microsoft Teams webinar: a custom “Legal terms” item in the webinar’s Teams registration setup cannot appear on this form, and it blocks every registration coming from Venue while it is enabled. What to do about it is in “Connect Microsoft Teams”.
Related articles
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?