[{"data":1,"prerenderedAt":167},["ShallowReactive",2],{"support-article-pages-acquisition-sources":3,"ls-connection":165},{"article":4,"related":36,"neighbors":103,"alternates":159},{"feature":5,"category":6,"locale":7,"slug":8,"title":9,"lede":10,"purpose":11,"steps":13,"notes":30,"generatedFrom":34,"updated":35},"page-acquisition","pages","en","acquisition-sources","See where your registrations come from","Break sign-ups down by referring site and by the UTM tags on the links you share.",[12],"Once the page is published, its Overview tab breaks your registrations down by where the sign-ups came from, under the Performance card's divider. It has two kinds of breakdown: the referring site, captured automatically from each visitor's browser, and the UTM dimensions (Source, Medium, Campaign, Term, Content) read from the utm_* parameters on the links you share.",[14,17,21,25,28],{"text":15,"image":16},"Open a published page, select the “Overview” tab and scroll to the acquisition breakdown, under the numbers in the Performance card.","\u002Fsupport\u002Fpage-acquisition\u002Fen\u002Fstep-1.webp",{"text":18,"image":19,"caption":20},"It opens on the Referring site breakdown, which lists the sites visitors came from, captured automatically with no tagging on your part.","\u002Fsupport\u002Fpage-acquisition\u002Fen\u002Fstep-2.webp","The Referring site breakdown is filled automatically from the visitor's browser.",{"text":22,"image":23,"caption":24},"Switch to a UTM breakdown: Source, Medium, Campaign, Term or Content. A hint reminds you these fill in only when you tag your links, so sign-ups that arrive with no UTM tag are grouped under \"Direct \u002F none\".","\u002Fsupport\u002Fpage-acquisition\u002Fen\u002Fstep-3.webp","On a UTM breakdown, a hint links here whenever it needs tagged links.",{"text":26,"code":27},"To populate them, add utm_source, utm_medium and utm_campaign (utm_term and utm_content are optional) to the page links you distribute by email, social or ads. For example:","https:\u002F\u002Fvenue.livestorm.app\u002Facme\u002Fspring-webinar?utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch",{"text":29},"Each breakdown ranks the top 8 values and groups the rest under \"Other\". A count is the number of distinct people who registered, not page views.",[31,32,33],"The acquisition breakdown only appears after publishing: a draft page has no sign-ups to break down.","UTMs are read at registration time from the page URL: there is no first-touch attribution kept across navigation, and views are never attributed, only registrations.","Untagged sign-ups fall under \"Direct \u002F none\", and every dimension shows its top 8 values plus \"Other\".","pages\u002F[id]\u002Foverview.vue (acquisition switcher) · usePages.ts fetchPageAnalytics · i18n overview.acquisition.*","July 31, 2026",[37,58,79],{"feature":38,"category":6,"locale":7,"slug":39,"title":40,"lede":41,"purpose":42,"steps":44,"notes":52,"updated":57},"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.",[43],"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.",[45,48],{"text":46,"image":47},"From the Pages tab, click “New page” to get started.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-1.webp",{"text":49,"image":50,"caption":51},"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.",[53,54,55,56],"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”.","July 30, 2026",{"feature":59,"category":6,"locale":7,"slug":60,"title":61,"lede":62,"purpose":63,"steps":65,"notes":74,"updated":78},"publish-page","publish","Publish your page","Take the page live at its public, crawlable and indexable address.",[64],"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.",[66,68,70,72],{"text":67},"On step 5 · Launch, check the preview of what visitors will get, and the search-engine visibility set on the Settings step.",{"text":69},"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":71},"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":73},"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”.",[75,76,77],"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":80,"category":6,"locale":7,"slug":80,"title":81,"lede":82,"purpose":83,"steps":85,"notes":98,"updated":78},"track-registrations","Track registrations live","See who signed up on the page, with the answers they gave.",[84],"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.",[86,88,90,92,94,96],{"text":87},"Open a published page and select the “Registrants” tab.",{"text":89},"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":91},"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":93},"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":95},"For a Livestorm or Zoom event, “Open in Livestorm” opens the event’s own full registrant list.",{"text":97},"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.",[99,100,101,102],"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":104,"next":131},{"feature":105,"category":6,"locale":7,"slug":106,"title":107,"lede":108,"purpose":109,"steps":111,"notes":125,"generatedFrom":130,"updated":78},"page-analytics","views-and-conversion","Measure views and conversion","Beyond the registration counter: track page views and your conversion rate.",[110],"Publishing unlocks a page's Overview tab: a set of cards holding its public address, the embed snippet, the newest sign-ups, and a Performance card — how many people saw the page, how many registered, and the conversion rate between the two. Enough to judge how well your campaigns are working.",[112,115,118,121,123],{"text":113,"image":114},"Open a published page and select the “Overview” tab.","\u002Fsupport\u002Fpage-analytics\u002Fen\u002Fstep-1.webp",{"text":116,"image":117},"In the “Performance” card (“Since publish”), read the three tiles: “Page views”, “Registrations” and “Conversion”.","\u002Fsupport\u002Fpage-analytics\u002Fen\u002Fstep-2.webp",{"text":119,"image":120},"Conversion is the ratio of registrations to views. Click “Refresh” to update the figures.","\u002Fsupport\u002Fpage-analytics\u002Fen\u002Fstep-3.webp",{"text":122},"Click the “Registrations” tile to open the “Registrants” tab and see who exactly signed up.",{"text":124},"Below the numbers, the “Latest registrants” card lists the five newest sign-ups with how long ago they came in — the page’s pulse, without leaving the tab. “See all registrants” opens the full list.",[126,127,128,129],"Overview and Registrants unlock at publication: a draft has no address, no views and no registrations, so both tabs stay disabled.","Conversion shows “—” while there are no views (the calculation would be meaningless).","The figures cover sign-ups made through this page; for a Livestorm or Zoom event, the full list also lives on that platform.","The public address and the embed snippet sit on the same tab, and they stay readable even if the numbers fail to load — a link you came to copy is never taken away by an outage.","pages\u002F[id]\u002Foverview.vue · usePages.ts fetchPageAnalytics · i18n overview.*",{"feature":132,"category":6,"locale":7,"slug":132,"title":133,"lede":134,"purpose":135,"steps":137,"notes":151,"generatedFrom":157,"updated":158},"version-history","Restore an earlier version","Browse your page’s history and roll back to any earlier version.",[136],"Every builder save is snapshotted, so a bad edit is never final. The history lets you preview an earlier version before deciding, and restoring is itself reversible: the state you left is saved as a version too.",[138,141,144,147],{"text":139,"image":140},"Open your page in the builder. Top right, the “Auto-saved” chip IS the entry point to the history (it is also in the ⋮ menu).","\u002Fsupport\u002Fversion-history\u002Fen\u002Fstep-1.webp",{"text":142,"image":143},"Click it to open the history: versions are grouped by day, newest first, each with its author and its kind — Auto, Manual, Published.","\u002Fsupport\u002Fversion-history\u002Fen\u002Fstep-2.webp",{"text":145,"image":146},"Select a version to preview it. Nothing is replaced at this point, so you can compare several before choosing.","\u002Fsupport\u002Fversion-history\u002Fen\u002Fstep-3.webp",{"text":148,"image":149,"caption":150},"“Restore this version” asks for confirmation, then replaces the current content.","\u002Fsupport\u002Fversion-history\u002Fen\u002Fstep-4.webp","The pre-restore state is saved as a version too, so you can undo the rollback.",[152,153,154,155,156],"A burst of autosaves reads as ONE entry: consecutive automatic saves by the same person within about a minute are merged.","Before a risky redesign, use “Save a checkpoint” and name it — a named version is the one you find again at a glance.","Automatic versions are pruned (the newest 50 per page, and after 7 days). Published, restored and named checkpoints are kept.","A published page cannot be restored to a version that would leave a required field empty: unpublish it or fix the fields first.","Templates and hubs have the same history and the same restore flow.","builder\u002FVersionHistoryDrawer.vue · useVersions.ts · i18n versionHistory.*","July 28, 2026",[160,163],{"hreflang":161,"path":162},"fr","\u002Fsupport\u002Fpages\u002Fsources-des-inscriptions",{"hreflang":7,"path":164},"\u002Fsupport\u002Fpages\u002Facquisition-sources",{"connected":166},false,1787923385348]