The landing page is your event's public page: the one that opens when somebody clicks the button in the invitation, and where they answer. It lives on your domain, wears your look, and what it collects comes straight back onto your guests.
You find them under Landing pages in the main menu.
Creating one
From the create button, picking the event it belongs to. Every landing page is tied to an event and inherits its name, dates, venue and image: there is nothing to retype.
It starts as a draft, visible only to you until you publish it.
The look
The editor works in blocks, with a preview beside it. You can set colours, typography, images, spacing and alignment, and for the awkward cases there is a custom CSS field.
Two things always worth checking before publishing:
- How it renders on a phone. Most answers come from one, often while the person is standing somewhere.
- That the confirm button is visible without scrolling. If a guest has to hunt for it, a share of them will not.
The form fields
You decide what to ask for and what is required: phone, gender, date of birth, country, city, company, role and the other contact fields.
First name, surname and email are always there: without those there is no knowing who is answering.
The data collected updates the contact in your address book: the landing page is not just an answer form, it is also how your records keep themselves tidy.
Privacy consents
The consents enabled on the event appear here, under the form. What a guest ticks is recorded along with their answer, with the time and the version of the text: see Privacy, consents and unsubscribes.
The address
A landing page answers at an address made of a domain and an alias:
https://events.yourbrand.com/gala-dinner-2026The domain is picked from those on your account enabled for landing pages; the alias you write yourself, and it is the last part of the address. The application tells you straight away if it is already taken.
If you do not have a landing domain yet, you can use the managed subdomain we assign when your account is created: see Set up your sending domain.
The opening window
You can set when the page opens and when it closes.
Closing is the more useful of the two: after that date the page is still reachable but no longer accepts answers. It is there to stop confirmations once catering needs final numbers, without deleting the page or leaving a dead link.
There are three states: draft, published, closed.
Meta and social preview
The title, description and image the page shows with when the link is shared on WhatsApp, LinkedIn or Slack.
Worth filling in: plenty of invitations get forwarded between colleagues, and a link that opens with a considered preview is clicked far more than one showing an empty rectangle.
Publishing
Publishing requires a verified domain. While the domain is pending you can save the draft but not make it public, and the application shows you which DNS records are missing.
Once published, the address is live. Try it from a browser where you are not logged in — that is the only way to see what a guest will see.
The link from the invitation
In the invitation template, the answer button has to use the {{rsvp}} placeholder: that is what leads to the landing page and tells the page who is answering.
Never paste the address copied out of the browser bar: the page would still open, but without recognising the guest, and every answer would come back attributed to the same person. It is the most expensive mistake you can make in an invitation.
Then
How answering works from the guest's side is in RSVP and confirmations.