[{"data":1,"prerenderedAt":169},["ShallowReactive",2],{"support-article-pages-recover-failed-registrations":3,"ls-connection":167},{"article":4,"related":37,"neighbors":106,"alternates":161},{"feature":5,"category":6,"locale":7,"slug":8,"title":9,"lede":10,"purpose":11,"steps":14,"notes":27,"generatedFrom":35,"updated":36},"failed-registrations","pages","en","recover-failed-registrations","Recover registrations the event platform refused","Find the people your event platform turned away, fix the cause, and enroll them without asking them to register again.",[12,13],"Sometimes the event platform refuses a registration for a reason the visitor cannot fix: a disconnected account, a spent contact allowance, an outage, a form that no longer matches the event. Venue keeps those registrations instead of losing them, tells the visitor their registration is in hand, and lists them in a Failed view of the Registrants tab.","Those rows retry on their own, waiting longer between each attempt. Your job is to fix the cause; the Failed view shows you who is waiting and lets you push them through the moment it is fixed.",[15,18,20,22,25],{"text":16,"image":17},"Open the page’s “Registrants” tab. The “Failed” view appears beside the other views as soon as someone is stuck, with a red count.","\u002Fsupport\u002Ffailed-registrations\u002Fen\u002Fstep-1.webp",{"text":19},"Read each row: the email, the “Why” column with the platform’s reason (and how many attempts so far), then the answers the person gave.",{"text":21},"Fix the cause on your side: reconnect the platform in Settings → Integrations, raise its contact allowance, or adjust the event’s registration form, depending on what the row says.",{"text":23,"image":24},"Then click “Retry all” to push every row again, including the ones that stopped retrying on their own. “Retry” on a row pushes that one person.","\u002Fsupport\u002Ffailed-registrations\u002Fen\u002Fstep-2.webp",{"text":26},"“Discard” gives up on a row: that person is not registered, and the row leaves the Failed view.",[28,29,30,31,32,33,34],"A row tagged “Paid” was charged before the platform refused it. Retrying enrolls someone who already paid; discarding means you owe them a refund, in your Stripe dashboard.","A row tagged “Approved” is someone you had already approved, on a page that requires approval: the platform refused them at that moment.","A promotion from the waiting list that the platform refuses lands here too.","Automatic retries stop after five attempts. The row then loses its own Retry, and a line above the table says so: “Retry all” starts it over.","Someone who registers again themselves in the meantime closes their row, so nobody is enrolled twice.","Nothing is kept while registrant retention is set to “Don’t store on Venue”: the visitor gets the platform’s error instead.","The notification center reports the same failures, naming the platform, and points you to this view. See “Track issues in the notification center”.","pages\u002FFailedPushTable.vue · pages\u002FRegistrantsViewSwitcher.vue · composables\u002FuseApprovalQueue.ts · i18n registrants.failedPush* \u002F registrants.retryAllFailed","September 23, 2026",[38,59,85],{"feature":39,"category":6,"locale":7,"slug":40,"title":41,"lede":42,"purpose":43,"steps":45,"notes":53,"updated":36},"page-create","create-from-an-event","Create a page from an event","Start from a Livestorm, Zoom or Microsoft Teams event: Venue pulls its details to pre-fill the page.",[44],"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.",[46,49],{"text":47,"image":48},"From the Pages tab, click “New page” to get started.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-1.webp",{"text":50,"image":51,"caption":52},"On step 1 · Event, choose the source (Livestorm, Zoom or Microsoft Teams once connected) then the event to promote. Search for it by name, or narrow the list: for Livestorm with “Status”, “From date” \u002F “To date” and “Event owner” (“Owned by me” keeps yours); for Zoom with “Event type” (Webinars or Meetings); for Teams with “Hosted by me”.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-2.webp","A source that is not connected yet offers “Connect” on its card.",[54,55,56,57,58],"Venue pre-fills the page with the event's data: you move straight on to the form, then the design.","You need a connected account to see your events. See “Connect your Livestorm account”, “Connect Zoom” and “Connect Microsoft Teams”.","The Livestorm event does not exist yet? Create it from this same step, without leaving the builder. See “Create a Livestorm event from Venue”.","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":60,"category":6,"locale":7,"slug":61,"title":62,"lede":63,"purpose":64,"steps":66,"notes":79,"generatedFrom":84,"updated":36},"livestorm-event-create","create-a-livestorm-event","Create a Livestorm event from Venue","The event your page promotes does not exist yet? Describe it on the Event step and Venue creates it in Livestorm.",[65],"A page is always backed by an event. When that event is not in Livestorm yet, you do not have to switch to Livestorm, create it and come back to pick it: the builder’s Event step creates it for you, sessions included, and links the page to it.",[67,70,73,75,77],{"text":68,"image":69},"On step 1 · Event, pick Livestorm as the source, then click “Create a Livestorm event”, above the list of your events. The same button is offered when the list comes back empty.","\u002Fsupport\u002Flivestorm-event-create\u002Fen\u002Fstep-1.webp",{"text":71,"image":72},"The form takes the place of the list. Under “Event details”, fill the “Event name”, a “Description” and the “Event owner” (you by default, or another member of your Livestorm team). The “Slug”, the event’s address in Livestorm, follows the name until you edit it.","\u002Fsupport\u002Flivestorm-event-create\u002Fen\u002Fstep-2.webp",{"text":74},"Under “Sessions”, set the “Time zone”, then “Add a session” for each date: a date, a start time and an optional name.",{"text":76},"Adjust the “Room settings” if you need to: chat, questions, polls, whether everyone can speak, automatic recording and the replay for registrants. “Copy the settings of an existing event” takes them from one of your events instead, along with its registration form and emails.",{"text":78},"Click “Create event and continue”. The event is published in your Livestorm workspace, the page is linked to it and its details are pulled in like any picked event. The event card carries a “Created from Venue” tag.",[80,81,82,83],"Livestorm only: Zoom, Microsoft Teams and in-person events have no create button here.","Registration stays on your Venue page, so the Livestorm registration pages of the new event are switched off.","Registration fields, emails and the room design use your Livestorm defaults. Adjust them in the event settings in Livestorm, then re-pull the event on this step so the page follows.","If Livestorm refuses a session or a session name, the confirmation under the event card lists each one with Livestorm’s answer. Add or rename it in the event settings before you share the event.","EventPicker.vue · event\u002FLivestormEventForm.vue · event\u002FCreatedEventBanner.vue · i18n wizard.event.create.*",{"feature":86,"category":6,"locale":7,"slug":87,"title":88,"lede":89,"purpose":90,"steps":92,"notes":101,"updated":105},"publish-page","publish","Publish your page","Take the page live at its public, crawlable and indexable address.",[91],"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.",[93,95,97,99],{"text":94},"On step 5 · Launch, check the preview of what visitors will get, and the search-engine visibility set on the Settings step.",{"text":96},"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":98},"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":100},"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”.",[102,103,104],"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",{"prev":107,"next":130},{"feature":108,"category":6,"locale":7,"slug":108,"title":109,"lede":110,"purpose":111,"steps":113,"notes":124,"updated":36},"track-registrations","Track registrations live","See who signed up on the page, with the answers they gave.",[112],"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.",[114,116,118,120,122],{"text":115},"Open a published page and select the “Registrants” tab.",{"text":117},"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":119},"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":121},"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":123},"For a Livestorm event, “Open in Livestorm”, above the table, opens the event’s own full registrant list.",[125,126,127,128,129],"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 to print a badge, edit the answers or delete the registrant. See “Check registrants in at the door” and “Correct or delete a registrant”.","More views can sit beside the list: Waiting and Declined when the page requires approval, Waiting list when it keeps one, and Failed when the event platform refused someone. See “Recover registrations the event platform refused”.",{"feature":131,"category":6,"locale":7,"slug":132,"title":133,"lede":134,"purpose":135,"steps":137,"notes":152,"generatedFrom":159,"updated":160},"manual-event","in-person-event","Create a page for an in-person event","Describe an event that happens in a room, with no connector, and let Venue collect the registrations.",[136],"Not every event lives in a webinar tool. On the Event step you can pick “In-person event” instead of a connected platform, type the details and the venue yourself, and Venue owns the registration form. What you publish is the same crawlable, indexable registration page as any other, with the address on it and a calendar file for the people who sign up.",[138,140,143,146,148,150],{"text":139},"On step 1 · Event, choose the “In-person event” card instead of a connected platform. There is nothing to connect: pick the card, then “Describe your in-person event” to open the form.",{"text":141,"image":142},"Fill in the event details: name, description and event language. The registration page is published in the language you pick here.","\u002Fsupport\u002Fmanual-event\u002Fen\u002Fstep-1.webp",{"text":144,"image":145},"Under “Sessions”, set the time zone, then add one session per date you run the event. Each one can carry its own name. Sessions are edited one at a time: click a line (or “Add a session”) to open its date and times in place, then “Done”. Type a start and an end time, or pick them from the list: the end time list shows how long each choice makes the session run. Visitors always see the times in the venue’s time zone.","\u002Fsupport\u002Fmanual-event\u002Fen\u002Fstep-2.webp",{"text":147},"Under “Venue”, start typing the venue name and pick it from the suggestions: the street, postal code, city, region and country fill themselves in. Type the address yourself if the place isn't found. A suggestion is a shortcut, never a requirement.",{"text":149},"“Getting there” (metro line, which door, the bell to ring) and a map link are optional. With no map link, the page links to a map search for the address you gave.",{"text":151},"Create this event, and continue to the form. Step 1 stays this form for the life of the page: come back to it whenever a date, the venue or the copy changes, and your edits are saved as you type.",[153,154,155,156,157,158],"Venue sends no confirmation email for an in-person event: people see a confirmation on the page itself, with their QR ticket and a calendar file. Check who is coming on the Registrants tab, and scan those tickets at the door. See “Scan tickets at the door”.","Venue search is a per-deployment option. Without it, the venue name is a plain text field and you fill the address in yourself, nothing else changes.","Editing the details later is safe. The page follows. Removing a date from a published page keeps the registrations already taken for it, but the date disappears from the page.","The address always shows in the event details on the page. To give it a block of its own, add the “Venue” section on the Design step.","You own the registration form on an in-person page. See “Fields on an in-person page”, and the day itself: check people in, scan their tickets and print badges from the Registrants tab.","Everything else works as usual: design, brands, templates, paid registration, hubs and analytics do not care where your event happens.","ManualEventForm.vue · EventPicker.vue (in-person source card) · i18n wizard.event.manual.*","September 9, 2026",[162,165],{"hreflang":163,"path":164},"fr","\u002Fsupport\u002Fpages\u002Frecuperer-les-inscriptions-refusees",{"hreflang":7,"path":166},"\u002Fsupport\u002Fpages\u002Frecover-failed-registrations",{"connected":168},false,1790164944419]