[{"data":1,"prerenderedAt":157},["ShallowReactive",2],{"support-article-pages-embed-on-your-site":3,"ls-connection":155},{"article":4,"related":29,"neighbors":95,"alternates":149},{"feature":5,"category":6,"locale":7,"slug":8,"title":9,"lede":10,"purpose":11,"steps":13,"notes":22,"generatedFrom":27,"updated":28},"page-embed","pages","en","embed-on-your-site","Embed your page on your own site","Drop the registration form, or the whole page, into your own website with one snippet.",[12],"A published page can be embedded in your own site instead of being linked to. Venue hands you a ready-made snippet: an iframe plus a few lines that resize it, so the embed grows to fit its content with no inner scrollbar. Nothing to install, and the registrations land in exactly the same place.",[14,17,20],{"text":15,"image":16},"Open a published page and select the “Overview” tab, then find the “Embed on your site” block.","\u002Fsupport\u002Fpage-embed\u002Fen\u002Fstep-1.webp",{"text":18,"image":19},"Choose what the embed shows: “Form only” for the registration form on its own, or “Whole page” for the published page without the browser chrome.","\u002Fsupport\u002Fpage-embed\u002Fen\u002Fstep-2.webp",{"text":21},"Click “Copy embed code” and paste the snippet into your own site, where you want it to appear.",[23,24,25,26],"The embed is never indexed by search engines: only your standalone Venue page is, so the two never compete for the same visitors.","A paid page and a password-protected page cannot be embedded. The snippet still works, but it shows a short notice with a link that opens the full page in a new tab.","The form embed inherits your brand: it is the same form as on the page, with the same fields and the same confirmation.","Editing and re-publishing the page updates every embed of it, since the embed renders the live page.","pages\u002F[id]\u002Foverview.vue (embed block) · utils\u002Fembed.ts · i18n overview.embed.*","July 30, 2026",[30,50,71],{"feature":31,"category":6,"locale":7,"slug":32,"title":33,"lede":34,"purpose":35,"steps":37,"notes":45,"updated":28},"page-create","create-from-an-event","Create a page from an event","Start from a Livestorm or Zoom event: Venue pulls its details to pre-fill the page.",[36],"A Venue page is always backed by an event. By starting from the event, the title, date, session and form fields are imported automatically — you copy nothing by hand, and the page stays in sync with the source.",[38,41],{"text":39,"image":40},"From the Pages tab, click “New page” to get started.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-1.webp",{"text":42,"image":43,"caption":44},"On step 1 · Event, choose the source (Livestorm or Zoom when connected) then the event to promote. Search for it or filter by “Hosted by me”.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-2.webp","Teams as a source shows “Not configured” until it is set up on your Venue deployment.",[46,47,48,49],"Venue pre-fills the page with the event's data: you move straight on to the form, then the design.","You need a connected Livestorm or Zoom account to see your events — see “Connect your Livestorm account” and “Connect Zoom”.","A single event can back several pages (per language, per campaign).","No connector, because the event happens in a room? Pick the “In-person event” card instead — see “Create a page for an in-person event”.",{"feature":51,"category":6,"locale":7,"slug":52,"title":53,"lede":54,"purpose":55,"steps":57,"notes":66,"updated":70},"publish-page","publish","Publish your page","Take the page live at its public, crawlable and indexable address.",[56],"Publishing makes the page reachable at its public URL and opens it to registrations. It is also what makes it indexable by search engines — the whole point of a Venue page.",[58,60,62,64],{"text":59},"On step 5 · Launch, check the preview of what visitors will get, and the search-engine visibility set on the Settings step.",{"text":61},"The preview is a short window on the top of the page. “Expand preview” (or clicking the window itself) reopens it full size and scrollable, so you can read the whole page before committing to it.",{"text":63},"Click “Publish page”, in the bar at the bottom of the step alongside the link that opens the page for real. Anything still blocking the publish is spelled out right there.",{"text":65},"The page always carries three tabs — “Overview” (its public address, the embed code and the numbers), “Registrants” (who signed up) and “Setup” (the builder you just used). Publishing is what unlocks the first two; before that they read “Available once the page is published”.",[67,68,69],"You can “Unpublish” at any time to take the page back offline: its public link then answers “page not found”, and you can publish it again whenever you like.","The link to share, and the code to embed the page on your own site, are both on the Overview tab.","Re-publishing after a change updates the public page in place.","August 3, 2026",{"feature":72,"category":6,"locale":7,"slug":72,"title":73,"lede":74,"purpose":75,"steps":77,"notes":90,"updated":70},"track-registrations","Track registrations live","See who signed up on the page, with the answers they gave.",[76],"A published page has a Registrants tab that lists everyone who signed up through it, with the answers they gave. It is the drill-down behind the registration counter on the Overview tab.",[78,80,82,84,86,88],{"text":79},"Open a published page and select the “Registrants” tab.",{"text":81},"Read the table: one row per person, with the email, the date they registered and their answers. The counter says how many are loaded; “Load more” fetches the next batch.",{"text":83},"Search by email or by any answer to find someone. The search runs over the registrants already loaded, so load more if you cannot find them.",{"text":85},"On an event with several dates, the “Sessions” column names every date each person signed up for — one line per person, whatever they booked.",{"text":87},"For a Livestorm or Zoom event, “Open in Livestorm” opens the event’s own full registrant list.",{"text":89},"The menu at the end of a row corrects or removes that person: “Edit info” reopens the answers they gave (their email identifies them, so it stays fixed), and “Delete registrant” removes them from every date they booked.",[91,92,93,94],"The tab unlocks at publication: nobody can have registered to a page that was never published.","Only the sign-ups made through this page appear here; the event keeps its own list on its platform.","The total, the views and the conversion rate live on the Overview tab, which also shows the latest sign-ups — see “Measure views and conversion”.","On an in-person page this table is also your door, and each row gets a ⋯ menu — see “Check registrants in at the door” and “Correct or delete a registrant”.",{"prev":96,"next":120},{"feature":97,"category":6,"locale":7,"slug":98,"title":99,"lede":100,"purpose":101,"steps":103,"notes":112,"generatedFrom":119,"updated":70},"registrant-edit","correct-or-delete-a-registrant","Correct or delete a registrant","Fix a typo in someone’s answers, move which dates they hold, or erase them entirely.",[102],"A welcome desk spends its day on three things: printing a badge, fixing a name someone mistyped, and moving a person to another date. The ⋯ menu at the end of each row on an in-person page's Registrants tab holds the last two — plus the deletion you owe anyone who asks to be erased.",[104,106,108,110],{"text":105},"Open the “Registrants” tab of an in-person page, find the person, and open the ⋯ menu at the end of their row.",{"text":107},"“Edit info” opens their answers, each in the control it was collected with. Correct what is wrong, then “Save changes”.",{"text":109},"In the same dialog, “Sessions they attend” moves them between dates: tick the ones they hold now. At least one is required.",{"text":111},"“Delete registrant” erases them: every date they booked and every answer they gave. The confirmation names them, and it cannot be undone.",[113,114,115,116,117,118],"The email can't be changed: on a page the address IS the person — it folds their dates into one line, carries their arrival and signs their ticket.","The Livestorm terms consent isn't editable either: it records what the visitor themselves agreed to. Your own consent questions stay editable like any other answer.","Saving re-checks the same rules the public form applies, so a required answer can't be emptied and a dropdown only takes one of its own options.","Moving someone's dates keeps their registration date, their QR ticket and their arrival stamp. Answers to fields you have since removed from the form are kept too.","Deleting is the erasure you owe under GDPR: it also cancels any abandoned payment of theirs. Both editing and deleting are recorded in Settings → Audit.","A registrant anonymized by your data-retention policy has no answers left to correct, so the menu offers no edit for them — see “Set how long registrant data is kept”.","RegistrantEditDialog.vue · pages\u002F[id]\u002Fregistrants.vue (row menu) · i18n registrants.menu.* \u002F registrants.edit.*",{"feature":121,"category":6,"locale":7,"slug":122,"title":123,"lede":124,"purpose":125,"steps":127,"notes":143,"generatedFrom":147,"updated":148},"session-mode","session-registration","Register for the whole event or one session","Choose whether the page is about the whole event or a single session, and how visitors sign up.",[126],"A Livestorm event can have several sessions. Venue lets you decide what the page promotes — the whole event or one specific session (past included, for a recap page of a recording) — then how visitors register when several sessions are offered.",[128,131,134,137,140],{"text":129,"image":130},"On step 1 · Event, once the event data is pulled, find the “This page is about” block under the event card.","\u002Fsupport\u002Fsession-mode\u002Fen\u002Fstep-1.webp",{"text":132,"image":133},"Choose “The whole event” (the next upcoming session(s) drive the date shown) or “One session” to bind it to a specific session.","\u002Fsupport\u002Fsession-mode\u002Fen\u002Fstep-2.webp",{"text":135,"image":136},"In “One session” mode, pick the session from the list: upcoming sessions first, then past ones (tagged “Past”). A past session turns the page into a recap of its recording.","\u002Fsupport\u002Fsession-mode\u002Fen\u002Fstep-3.webp",{"text":138,"image":139},"On step 2 · Form, open the “Session” row’s config (the settings icon) to set “Sessions to offer” — how many upcoming sessions the page presents.","\u002Fsupport\u002Fsession-mode\u002Fen\u002Fstep-4.webp",{"text":141,"image":142},"Still in that config, set “Registration”: “Visitor picks a session”, “Visitor picks several”, or “Register to all sessions”.","\u002Fsupport\u002Fsession-mode\u002Fen\u002Fstep-5.webp",[144,145,146],"A page bound to a single session offers exactly that session — there is then no session counter and no registration picker.","The number of offered sessions is capped to the upcoming sessions actually available on the event.","A direct-link event (no fields or sessions) skips this step: visitors are sent straight to Livestorm.","EventStep.vue (binding) · FormBuilder.vue (sessions) · event-binding.ts · i18n wizard.event.binding.* \u002F wizard.form.sessions.*","July 16, 2026",[150,153],{"hreflang":151,"path":152},"fr","\u002Fsupport\u002Fpages\u002Fintegrer-sur-votre-site",{"hreflang":7,"path":154},"\u002Fsupport\u002Fpages\u002Fembed-on-your-site",{"connected":156},false,1787923385348]