[{"data":1,"prerenderedAt":172},["ShallowReactive",2],{"support-article-settings-notification-center":3,"ls-connection":170},{"article":4,"related":29,"neighbors":108,"alternates":164},{"feature":5,"category":6,"locale":7,"slug":8,"title":9,"lede":10,"purpose":11,"steps":14,"notes":23,"generatedFrom":27,"updated":28},"notifications","settings","en","notification-center","Track issues in the notification center","A chronological, read-only feed of the problems detected on your pages — failed registrations, a broken connection, a full page.",[12,13],"The notification center is where Venue surfaces operational problems on the public-registration path: a rejected or missing Livestorm connection, a broken integration, a page that hit its registration limit, a throttled burst, and similar events. It’s the place to look when registrations aren’t coming through.","The feed is read-only and shows the newest events first. Each row is toned by severity so the things you must fix stand out from the purely informational ones.",[15,18,21],{"text":16,"image":17},"Open Settings → Notifications. Problems are listed newest first, each with a colored dot: red for an error to fix, amber for a warning, blue for information.","\u002Fsupport\u002Fnotifications\u002Fen\u002Fstep-1.webp",{"text":19,"image":20},"Use the “Type” filter to narrow to a single category — connection rejected, registration full, rate limited, and so on. The counter on the right shows how many notifications match.","\u002Fsupport\u002Fnotifications\u002Fen\u002Fstep-2.webp",{"text":22},"On a page-specific notification, click “View page” to open the affected registration page. A broken-integration notice points you to Settings → Integrations to reconnect.",[24,25,26],"The center is read-only and informational: there’s nothing to dismiss or acknowledge — fix the underlying issue and new events stop appearing.","Red errors need action (for example, reconnect your Livestorm account); amber warnings are usually transient or capacity-related; blue entries need no action.","A broken-integration notice is workspace-wide (not tied to one page) — a workspace admin reconnects it in Settings → Integrations.","SettingsNotificationsTab.vue · useNotifications.ts · i18n settings.notifications.*","July 22, 2026",[30,59,86],{"feature":31,"category":6,"locale":7,"slug":32,"title":33,"lede":34,"purpose":35,"steps":37,"notes":53,"generatedFrom":57,"updated":58},"page-access","access-and-privacy","Control access and privacy","Password-protect the page, set its visibility, redirect after registration, and cap sign-ups.",[36],"The Settings step gathers the page's access rules: who can find it (search-engine visibility), who can load it (password), where visitors go after they register, and how many people can sign up.",[38,41,44,47,50],{"text":39,"image":40},"Open your page in the builder, on step 4 · Settings. Each rule is its own block with its own switch.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-1.webp",{"text":42,"image":43},"In the visibility block, choose “Public” (crawlable and indexable by search engines) or “Unlisted” (hidden from search, reachable only via its direct link).","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-2.webp",{"text":45,"image":46},"Turn on “Password protection” to require a password before the page loads, then enter it — at least 8 characters. The eye button reveals it.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-3.webp",{"text":48,"image":49},"Turn on “Redirect after registration” and enter a full https:\u002F\u002F URL to send registrants to your own page — or leave the switch off to show the in-page confirmation.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-4.webp",{"text":51,"image":52},"Turn on “Registration limit” to cap sign-ups: set the maximum with the slider or the field. Once the limit is reached, the page shows a “registration full” message instead of the form.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-5.webp",[54,55,56],"An unlisted page is still reachable by anyone with the link: it is not protection, only a way to keep it out of search engines.","The password must be at least 8 characters and the redirect URL must start with https:\u002F\u002F — otherwise publishing is blocked on the Launch step.","These settings apply on publish: check them before taking the page live.","SettingsStep.vue (step 4) · i18n wizard.settings.*","July 16, 2026",{"feature":60,"category":6,"locale":7,"slug":60,"title":61,"lede":62,"purpose":63,"steps":66,"notes":80,"generatedFrom":84,"updated":85},"api-keys","Create and revoke API keys","Issue workspace keys to call the Venue API from your own code — then revoke them when you no longer need them.",[64,65],"API keys let workspace admins authenticate to the Venue API with a Bearer token (`vk_live_…`). A key carries the same access as a workspace admin, so treat it like a password: create it when you need an integration, copy the secret once, and revoke it as soon as it is unused.","Endpoints, Try-it, and code samples live in the in-app API documentation (`\u002Fdocs`).",[67,70,74,76,78],{"text":68,"image":69},"Open Settings → API keys. Only workspace admins can manage keys.","\u002Fsupport\u002Fapi-keys\u002Fen\u002Fstep-1.webp",{"text":71,"image":72,"caption":73},"The list shows each key’s name, prefix (`vk_live_…`), dates, and status. Filter Active \u002F All to hide or show revoked and expired keys.","\u002Fsupport\u002Fapi-keys\u002Fen\u002Fstep-2.webp","Switch to All to see revoked or expired keys alongside active ones.",{"text":75},"Click “Create key”, give it a name (e.g. “Production integration”), pick an expiration (30 days, 90 days, 1 year, or never), then confirm.",{"text":77},"Copy the secret immediately — it is shown only once. Tick “I’ve saved this key somewhere safe” before closing. You can open “Try in API docs” to paste it into the docs Try-it panel (it stays in this browser only).",{"text":79},"To stop a key, click “Revoke” on its row and confirm. Any integration using that key stops working right away — this can’t be undone.",[81,82,83],"Never commit API keys to source control or share them in chat or tickets.","Expired keys stop working automatically; revoked keys stay in the All filter for audit.","Non-admins see the tab but cannot create or revoke keys — ask a workspace admin.","SettingsApiKeysTab.vue · useApiKeys.ts · i18n settings.apiKeys.*","July 21, 2026",{"feature":87,"category":6,"locale":7,"slug":87,"title":88,"lede":89,"purpose":90,"steps":93,"notes":103,"generatedFrom":107,"updated":28},"data-retention","Set how long registrant data is kept","Choose a retention window for the personal data collected through your pages — or keep none on Venue at all.",[91,92],"Registrant data retention controls how long the personal data your pages collect (a registrant’s email and their form answers) is kept on Venue. It is a single, workspace-wide setting: it applies to every page in the workspace, and only workspace admins can change it. A daily backend job permanently deletes anything older than the window you pick.","Use it to match your own privacy policy or a legal requirement — keep data as long as you need it, or store none of it on Venue and rely on Livestorm as the system of record.",[94,97,101],{"text":95,"image":96},"Open Settings → AI & privacy. Registrant data retention is the second card, below AI page generation.","\u002Fsupport\u002Fdata-retention\u002Fen\u002Fstep-1.webp",{"text":98,"image":99,"caption":100},"Open the “Keep registrant data for” dropdown and pick a window: Unlimited (the default), 2 years, 1 year, 6 months, or 3 months. The change saves as soon as you pick.","\u002Fsupport\u002Fdata-retention\u002Fen\u002Fstep-2.webp","Data older than the selected period is permanently deleted.",{"text":102},"To store no registrant personal data at all, choose “Don’t store on Venue” — only anonymized analytics counts are kept, and a warning explains what that means.",[104,105,106],"The setting is workspace-wide and admin-only: it applies to everyone, and members see it but can’t change it.","Data older than the window (email and form answers) is deleted permanently by a daily job — this can’t be undone, so shorten the window deliberately.","“Don’t store on Venue” keeps zero registrant personal data; only anonymized counts remain for analytics.","SettingsAiTab.vue · useWorkspace.ts setRegistrantRetention · i18n settings.workspace.retention.*",{"prev":109,"next":133},{"feature":110,"category":6,"locale":7,"slug":111,"title":112,"lede":113,"purpose":114,"steps":117,"notes":128,"generatedFrom":132,"updated":28},"ads-tracking","ads-and-consent","Add ad pixels and the consent banner","Fire Meta, Google Ads, GA4, LinkedIn or GTM conversion pixels on every published page and hub — gated by a cookie-consent banner.",[115,116],"Ad tracking lets you add conversion pixels once, at the workspace level, so they fire on every published page and event hub — no per-page setup. Venue supports the Meta Pixel, Google Ads, Google Analytics 4, the LinkedIn Insight Tag, and Google Tag Manager.","A cookie-consent banner gates the pixels: nothing loads until a visitor accepts. It is Venue’s only consent mechanism, so it stays on by default. Tracking is admin-only, and lives inside Settings → Integrations.",[118,121,124],{"text":119,"image":120},"Open Settings → Integrations. The “Ads tracking” section sits at the bottom, collapsed; its summary line shows how many pixels are active and whether the consent banner is on.","\u002Fsupport\u002Fads-tracking\u002Fen\u002Fstep-1.webp",{"text":122,"image":123},"Click to expand “Ads tracking”, then enter the id for each platform you use — a Meta Pixel here is already configured. Google Ads needs both a conversion id and a label; a LinkedIn conversion id needs a partner id. Click “Save tracking” when done.","\u002Fsupport\u002Fads-tracking\u002Fen\u002Fstep-2.webp",{"text":125,"image":126,"caption":127},"Keep “Show the cookie-consent banner” on. Turned off, Meta, LinkedIn and GTM never load (they wait for an accept) and Google runs cookieless (Consent Mode stays denied).","\u002Fsupport\u002Fads-tracking\u002Fen\u002Fstep-3.webp","The consent banner is Venue’s only consent mechanism — leave it on for GDPR.",[129,130,131],"Each id is validated as you type: a badly formatted id is flagged before you can save, and an empty field simply clears that platform.","Pixels fire on every published page and event hub in the workspace, always gated by the consent banner.","Only workspace admins can change tracking. The section moved here from its own tab — the old Settings → Tracking link now opens Integrations.","SettingsTrackingTab.vue · SettingsIntegrationsTab.vue · i18n settings.tracking.*",{"feature":134,"category":6,"locale":7,"slug":134,"title":135,"lede":136,"purpose":137,"steps":140,"notes":154,"generatedFrom":162,"updated":163},"paid-registration","Charge for registration","Require a one-time payment before a visitor is registered.",[138,139],"A paid page turns payment into the last gate before sign-up: nothing is created in Livestorm and no registrant is recorded until Stripe confirms the charge. Useful for paid masterclasses, workshops and training sessions.","The money goes to your OWN Stripe account (direct charges): you are the merchant of record, you own receipts, refunds and disputes, and Venue takes no cut.",[141,144,147,150],{"text":142,"image":143},"Paid registration needs a connected Stripe account. Open Settings → Integrations and check that the Stripe row reads “Connected”.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-1.webp",{"text":145,"image":146},"Then open your page in the builder, on step 4 · Settings. The Payment group sits below the access rules.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-2.webp",{"text":148,"image":149},"Turn on “Paid registration”. Until a Stripe account is connected and able to take card payments, the card stays greyed out with a link to Integrations.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-3.webp",{"text":151,"image":152,"caption":153},"Enter the price and its currency, then optionally a line-item label — it is what buyers see on the Stripe checkout and receipt. Leave it empty to fall back to the event title.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-4.webp","A €49 ticket labelled “Masterclass ticket”, ready to publish.",[155,156,157,158,159,160,161],"The minimum price is 0.50 in the selected currency (EUR, USD or GBP).","The price is snapshotted by the server when a visitor submits, so it cannot be tampered with from the browser — and changing it later never re-prices a sign-up already in progress.","Someone who is already registered is not charged again: the form recognizes their email and skips checkout.","On a multi-session page, one payment registers every session the visitor picked.","Refunds and disputes happen in your own Stripe dashboard, not in Venue.","If a payment succeeds but Livestorm cannot be reached, the Launch step lists those visitors under “paid but not registered” so you can refund them.","Disconnecting Stripe stops paid pages from taking payments until you reconnect.","builder\u002Fsettings\u002FSettingsStep.vue · SettingsPaymentsTab.vue · usePayments.ts · i18n wizard.settings.payment.*","July 28, 2026",[165,168],{"hreflang":166,"path":167},"fr","\u002Fsupport\u002Fparametres\u002Fcentre-de-notifications",{"hreflang":7,"path":169},"\u002Fsupport\u002Fsettings\u002Fnotification-center",{"connected":171},false,1787923385348]