[{"data":1,"prerenderedAt":132},["ShallowReactive",2],{"support-article-form-in-person-fields":3,"ls-connection":130},{"article":4,"related":33,"neighbors":102,"alternates":124},{"feature":5,"category":6,"locale":7,"slug":5,"title":8,"lede":9,"purpose":10,"steps":12,"notes":25,"generatedFrom":31,"updated":32},"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],{"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},"Click a row to open it. “Field label” is what visitors read above the field; leave it empty to restore the default.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-2.webp",{"text":20,"image":21},"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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-3.webp",{"text":23,"image":24},"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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-4.webp",[26,27,28,29,30],"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.","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) · useManualFields.ts · i18n wizard.form.manual.*","July 31, 2026",[34,54,77],{"feature":35,"category":6,"locale":7,"slug":36,"title":37,"lede":38,"purpose":39,"steps":41,"notes":49,"updated":53},"form-columns","two-columns","Show fields in two columns","Shorten the form by placing short fields side by side.",[40],"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.",[42,45],{"text":43,"image":44},"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":46,"image":47,"caption":48},"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.",[50,51,52],"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”.","August 3, 2026",{"feature":55,"category":6,"locale":7,"slug":56,"title":57,"lede":58,"purpose":59,"steps":61,"video":71,"poster":64,"notes":72,"updated":76},"form-multi-step","multiple-steps","Split the form into multiple steps","Turn a long form into a progressive flow, with a progress bar.",[60],"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.",[62,65,68],{"text":63,"image":64},"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":66,"image":67},"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":69,"image":70},"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",[73,74,75],"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.","July 15, 2026",{"feature":78,"category":6,"locale":7,"slug":79,"title":80,"lede":81,"purpose":82,"steps":84,"notes":98,"updated":32},"form-copy","wording","Customize the form's wording","Give the form title and catch line your own voice.",[83],"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.",[85,88,91,94],{"text":86,"image":87},"Open your page in the builder, on step 3 · Design.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-1.webp",{"text":89,"image":90},"Select the registration form: its properties carry a “Text inside the form” block.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-2.webp",{"text":92,"image":93},"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":95,"image":96,"caption":97},"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.",[99,100,101],"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":103,"next":123},{"feature":104,"category":6,"locale":7,"slug":105,"title":106,"lede":107,"purpose":108,"steps":110,"notes":118,"updated":32},"form-fields","fields-and-consents","Fields, consents and re-import","The form mirrors your Livestorm fields; manage them at the source and re-sync.",[109],"The Form step is a read-only mirror of your Livestorm registration form: same fields, same custom fields, same consents, with their required state. You control how it looks, not the list itself.",[111,114],{"text":112,"image":113},"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":115,"image":116,"caption":117},"Added, renamed or removed a field in Livestorm? Click “Re-pull from Livestorm” to re-sync the form.","\u002Fsupport\u002Fform-fields\u002Fen\u002Fstep-2.webp","Adding, renaming and removing fields always happens on the Livestorm side.",[119,120,121,122],"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 yourself: see “Fields on an in-person page”.","The layout (columns, steps, wording) is set separately — see the dedicated Form guides.","Re-import overwrites local labels with Livestorm's: redo your layout tweaks after a big change.","Fields you marked “Hide this field” stay hidden across a re-import, whether you trigger it from the Event step or the Form step.",null,[125,128],{"hreflang":126,"path":127},"fr","\u002Fsupport\u002Fformulaire\u002Fchamps-en-presentiel",{"hreflang":7,"path":129},"\u002Fsupport\u002Fform\u002Fin-person-fields",{"connected":131},false,1787923385347]