[{"data":1,"prerenderedAt":151},["ShallowReactive",2],{"ls-connection":3,"support-article-form-fields-and-consents":5},{"connected":4},false,{"article":6,"related":40,"neighbors":108,"alternates":145},{"feature":7,"category":8,"locale":9,"slug":10,"title":11,"lede":12,"purpose":13,"steps":15,"notes":31,"updated":39},"form-fields","form","en","fields-and-consents","Fields, consents and re-import","The form mirrors your Livestorm fields; manage them at the source and re-sync.",[14],"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.",[16,19,21,23,27],{"text":17,"image":18},"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":20},"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":22},"Visitors then get the control that fits, and the page 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":24,"image":25,"caption":26},"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":28,"image":29,"caption":30},"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.",[32,33,34,35,36,37,38],"For a connected event you can't add or remove a field on the page. 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 and can write your own questions: 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 your page while it is enabled. What to do about it is in “Connect Microsoft Teams”.","October 5, 2026",[41,61,83],{"feature":42,"category":8,"locale":9,"slug":43,"title":44,"lede":45,"purpose":46,"steps":48,"notes":56,"updated":60},"form-columns","two-columns","Show fields in two columns","Shorten the form by placing short fields side by side.",[47],"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.",[49,52],{"text":50,"image":51},"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":53,"image":54,"caption":55},"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.",[57,58,59],"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":62,"category":8,"locale":9,"slug":63,"title":64,"lede":65,"purpose":66,"steps":68,"video":78,"poster":71,"notes":79,"updated":60},"form-multi-step","multiple-steps","Split the form into multiple steps","Turn a long form into a progressive flow, with a progress bar.",[67],"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.",[69,72,75],{"text":70,"image":71},"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":73,"image":74},"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":76,"image":77},"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",[80,81,82],"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":84,"category":8,"locale":9,"slug":85,"title":86,"lede":87,"purpose":88,"steps":90,"notes":104,"updated":60},"form-copy","wording","Customize the form's wording","Give the form title and catch line your own voice.",[89],"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.",[91,94,97,100],{"text":92,"image":93},"Open your page in the builder, on step 3 · Design.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-1.webp",{"text":95,"image":96},"Select the registration form: its properties carry a “Text inside the form” block.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-2.webp",{"text":98,"image":99},"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":101,"image":102,"caption":103},"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.",[105,106,107],"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":83,"next":109},{"feature":110,"category":8,"locale":9,"slug":110,"title":111,"lede":112,"purpose":113,"steps":115,"notes":136,"generatedFrom":144,"updated":39},"in-person-fields","Fields on an in-person page","Choose what you ask for, and how it reads, when the form is yours to build.",[114],"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.",[116,119,122,125,128,130,133],{"text":117,"image":118},"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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-1.webp",{"text":120,"image":121},"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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-2.webp",{"text":123,"image":124},"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":126,"image":127},"“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":129},"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.",{"text":131,"image":132},"“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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-5.webp",{"text":134,"image":135},"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.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-6.webp",[137,138,139,140,141,142,143],"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 \u002F 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”.","FormBuilder.vue (manual fields) · FormAddMenus.vue · QuestionEditor.vue · QuestionChoices.vue · FieldCopyBlock.vue · useManualFields.ts · useQuestions.ts · i18n wizard.form.manual.* \u002F wizard.form.questions.* \u002F wizard.form.fields.*",[146,149],{"hreflang":147,"path":148},"fr","\u002Fsupport\u002Fformulaire\u002Fchamps-et-consentements",{"hreflang":9,"path":150},"\u002Fsupport\u002Fform\u002Ffields-and-consents",1792141116906]