[{"data":1,"prerenderedAt":175},["ShallowReactive",2],{"support-article-form-in-person-fields":3,"ls-connection":173},{"article":4,"related":35,"neighbors":103,"alternates":167},{"feature":5,"category":6,"locale":7,"slug":5,"title":8,"lede":9,"purpose":10,"steps":12,"notes":27,"generatedFrom":33,"updated":34},"in-person-fields","form","en","Fields on an in-person page","Choose what you ask for, and how it reads, when Venue owns the form.",[11],"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.",[13,16,19,22,25],{"text":14,"image":15},"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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-1.webp",{"text":17,"image":18},"Add what you need from “Add a field”: phone, job title, company, address, postal code, country, or a consent checkbox. One click adds it to the form, and its chip leaves the list. “Remove field”, in the open row, takes one back out.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-2.webp",{"text":20,"image":21},"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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-3.webp",{"text":23,"image":24},"“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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-4.webp",{"text":26},"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.",[28,29,30,31,32],"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 \u002F optional switch.","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 Venue mirrors them, see “Fields, consents and re-import”.","FormBuilder.vue (manual fields) · FieldCopyBlock.vue · useManualFields.ts · i18n wizard.form.manual.* \u002F wizard.form.fields.*","September 23, 2026",[36,56,78],{"feature":37,"category":6,"locale":7,"slug":38,"title":39,"lede":40,"purpose":41,"steps":43,"notes":51,"updated":55},"form-columns","two-columns","Show fields in two columns","Shorten the form by placing short fields side by side.",[42],"By default, each form field takes its own row. On forms with more than 3 to 4 fields, a 2-column layout shortens the form on screen: the register button stays visible without scrolling, which helps conversion.",[44,47],{"text":45,"image":46},"Open your page in the builder, on step 2 · Form. The Columns setting is in the Layout card, below the field list.","\u002Fsupport\u002Fform-columns\u002Fen\u002Fstep-1.webp",{"text":48,"image":49,"caption":50},"Choose 2 columns. In the live preview, short fields (first name, last name) sit side by side.","\u002Fsupport\u002Fform-columns\u002Fen\u002Fstep-2.webp","First name and Last name now share the same row in the preview.",[52,53,54],"Long fields (email, dropdowns) automatically stay full-width, even in 2 columns.","Below 4 short fields, a single column is usually easier to read.","The setting only changes the layout. The fields themselves come from Livestorm, except on an in-person page, which owns them. See “Fields on an in-person page”.","September 9, 2026",{"feature":57,"category":6,"locale":7,"slug":58,"title":59,"lede":60,"purpose":61,"steps":63,"video":73,"poster":66,"notes":74,"updated":55},"form-multi-step","multiple-steps","Split the form into multiple steps","Turn a long form into a progressive flow, with a progress bar.",[62],"A 7-field form shown all at once can discourage sign-ups. By splitting it into 2 or 3 steps, visitors see only a few fields at a time and move forward with a Next button. A progress bar shows where they are.",[64,67,70],{"text":65,"image":66},"Open your page in the builder, on step 2 · Form. The Steps setting is in the Layout card, below the field list.","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fstep-1.webp",{"text":68,"image":69},"Choose 2 steps. The live preview immediately shows the progress bar, “Step 1 of 2” and the Next button.","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fstep-2.webp",{"text":71,"image":72},"Very long form? Switch to 3 steps, the maximum. Then drag fields from one step to another to spread them out.","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fstep-3.webp","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fwalkthrough.webm",[75,76,77],"Consents and the submit button always stay on the last step. They can't be moved.","Each step adds a click before sign-up: reserve multi-step for forms of at least 6 to 7 fields.","An empty step is flagged by the builder. Spread the fields before publishing.",{"feature":79,"category":6,"locale":7,"slug":80,"title":81,"lede":82,"purpose":83,"steps":85,"notes":99,"updated":55},"form-copy","wording","Customize the form's wording","Give the form title and catch line your own voice.",[84],"The form ships with default wording. Replacing it with your own title and catch line aligns the form with the event tone and gives a concrete reason to sign up.",[86,89,92,95],{"text":87,"image":88},"Open your page in the builder, on step 3 · Design.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-1.webp",{"text":90,"image":91},"Select the registration form: its properties carry a “Text inside the form” block.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-2.webp",{"text":93,"image":94},"Replace the form title with a message in your own voice. The preview updates as you type.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-3.webp",{"text":96,"image":97,"caption":98},"Add a catch line below the title (urgency, benefit or the event format) and, right under it, your own button label.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-4.webp","Custom title and catch line, visible right away in the live preview.",[100,101,102],"An action-oriented title (“Save your seat”) usually converts better than a descriptive label.","The same properties panel carries “Show logo on the form”, and the text that sits outside the form card.","Leave a field empty to fall back to the default text, translated into the event's language.",{"prev":104,"next":135},{"feature":105,"category":6,"locale":7,"slug":106,"title":107,"lede":108,"purpose":109,"steps":111,"notes":127,"updated":34},"form-fields","fields-and-consents","Fields, consents and re-import","The form mirrors your Livestorm fields; manage them at the source and re-sync.",[110],"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.",[112,115,117,119,123],{"text":113,"image":114},"On step 2 · Form, the field list shows exactly what's configured in Livestorm, including custom fields and consent checkboxes.","\u002Fsupport\u002Fform-fields\u002Fen\u002Fstep-1.webp",{"text":116},"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.",{"text":118},"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.",{"text":120,"image":121,"caption":122},"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.","\u002Fsupport\u002Fform-fields\u002Fen\u002Fstep-2.webp","A checkbox has no placeholder, so its button reads “Customize label”. A consent keeps its wording: it is the platform’s legal text.",{"text":124,"image":125,"caption":126},"Added, renamed or removed a field in Livestorm? Click “Re-pull from Livestorm” to re-sync the form. Your types and placeholders survive it.","\u002Fsupport\u002Fform-fields\u002Fen\u002Fstep-3.webp","Adding and removing fields always happens on the Livestorm side.",[128,129,130,131,132,133,134],"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”.",{"feature":136,"category":6,"locale":7,"slug":137,"title":138,"lede":139,"purpose":140,"steps":143,"notes":160,"updated":166},"form-conditional-fields","conditional-fields","Show a field only when an earlier answer matches","Ask a question only to the people it concerns: a field can depend on an earlier answer.",[141,142],"Every field on the Form step has a Visibility setting with three states. Always shows the field to every visitor. When… shows it only when an earlier answer matches a rule you write: a job title once a company is named, a dietary question for the people coming in person. Never hides it from the page while a link can still fill it in.","A field the rule skips is not shown, not required, not validated and not sent to your event platform. The same rule runs on the page and again when the registration is saved. It works on an in-person page as much as on a page built on a Livestorm, Zoom or Microsoft Teams event.",[144,147,151,154,157],{"text":145,"image":146},"On step 2 · Form, open the row of the field you want to show conditionally. A field that already carries a rule sums it up under its name.","\u002Fsupport\u002Fform-conditional-fields\u002Fen\u002Fstep-1.webp",{"text":148,"image":149,"caption":150},"Under Visibility, pick When…: the rule then reads as a sentence under Show when. A field asked before this one, an operator and, when the operator takes one, a value. Here Job title shows when Where do you work? is not empty.","\u002Fsupport\u002Fform-conditional-fields\u002Fen\u002Fstep-2.webp","The operators follow the type of the field being read: a dropdown offers “is” and “is any of”, a date “is before” and “is after”, a checkbox “is ticked”.",{"text":152,"image":153},"Look at the live preview: the field the rule hides shows as a dashed row in its place, with what would reveal it. Type a matching answer above it and the field appears. Visitors never see the dashed row: on the page, the field is simply skipped.","\u002Fsupport\u002Fform-conditional-fields\u002Fen\u002Fstep-3.webp",{"text":155,"image":156},"Add a condition to narrow the rule, up to five. Every condition joins with the same word, and or or, which you pick on the row. While a condition is still incomplete the rule is paused and the field shows to everyone, so nothing disappears from a live form while you are still picking.","\u002Fsupport\u002Fform-conditional-fields\u002Fen\u002Fstep-4.webp",{"text":158,"image":159},"A rule only reads what the visitor has already answered, so the field menu lists the fields asked before this one. A field asked after shows greyed out: drag the row below it to read it. Move a field above the one it reads and its rule pauses, with the row saying so.","\u002Fsupport\u002Fform-conditional-fields\u002Fen\u002Fstep-5.webp",[161,162,163,164,165],"The email can never depend on another answer: it identifies each registrant. A consent checkbox cannot either, and no rule can read one.","On a page built on a Livestorm, Zoom or Teams event, a field the platform requires always shows: skipping it would make the platform refuse the registration. Make it optional on the platform, then re-pull. On an in-person page you own the form, so a field can be both required and conditional: required only when shown.","Unanswered is no match: for a field the visitor left blank, only “is empty” and “is not ticked” are true. A field hidden by a rule counts as unanswered for the rules that read it, so hiding a question also retracts what it would have shown. A step whose every field is skipped is skipped too.","A field on Never, filled from the link, can be read by a rule: it counts as answered first, wherever it sits. That is how a page asks a question only to the visitors who arrived through a given link.","Texts compare without regard to case or spaces around them, numbers and dates by value. Rules survive a re-pull from your platform, like types and placeholders; only a field the platform has since made required loses its rule, since it must always show.","September 18, 2026",[168,171],{"hreflang":169,"path":170},"fr","\u002Fsupport\u002Fformulaire\u002Fchamps-en-presentiel",{"hreflang":7,"path":172},"\u002Fsupport\u002Fform\u002Fin-person-fields",{"connected":174},false,1790942614196]