Creating a landing page

Updated on 2026-10-19

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 speaks the event language, whatever the visitor's browser uses. 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, VAT number, tax code and the other contact fields.

First name, surname and email are always there: without those there is no knowing who is answering.

You can also ask for companions, with a switch of their own: the maximum number and the named-companions rule set on the event apply, as on the answer page. It works with slots too: named companions go into the same slot as the person bringing them. If the event allows no companions, the switch cannot be turned on.

The account's custom fields have a section of their own, with the same switch and the same required option.

In the Consents section you decide which privacy checkboxes the form shows. The privacy notice and the required additional consents are always there and cannot be switched off. You can switch off Receives emails, that is the checkbox about invitations and measurement, and each optional additional consent of the account and of the event: that way two landings of the same event can ask different things. Everything starts on, a consent created after the landing was saved included. See Privacy consents.

The answers land on the contact's record. Company, role, VAT number, tax code and custom fields left empty do not wipe what the contact already had.

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

When the account has set its default privacy policy, the subscribe form shows first two checkboxes managed by Eventleash, with standard wording:

  • "I have read the privacy notice of…", with the link to your policy: it is required to sign up;
  • the checkbox about invitations and open and click measurement: it is optional and never ticked to start with. Whoever ticks it will receive the invitations to your next events and is measured individually; whoever does not still signs up, but only receives the confirmation of their registration, no campaign, not even of this event. If you switch off Receives emails in the form fields the checkbox disappears: whoever signs up from that landing comes in without invitations, like somebody who leaves it unticked.

The exact texts and the rules are in The checkboxes on forms.

Below them come the additional consents of the account and of the event: the required ones always, the optional ones unless you switched them off in the form fields. The answers are saved on the guest; the privacy notice acknowledgement and the two choices of the second checkbox are kept on the contact, with the date they were last accepted or refused: see What gets recorded.

Visitors coming from an email

Links in emails sent by Eventleash that point to one of your landings automatically get a personal code of the recipient. You do not have to do anything: the link only needs to lead to one of your account's landing domains.

When the recipient opens the landing from that link, the page recognises them:

  • first name, last name and email are already filled in; the other fields stay empty, because the link may reach someone else through a forward;
  • a line says "We filled in the form with the details of…" followed by their address, with a Not you? link;
  • if the person has already given the privacy notice and the invitations, the two default checkboxes do not show: in their place there is a line with the date they accepted the privacy notice, the link to the notice and Manage your consents, leading to their preferences page. Consents are changed there only, the notice included (withdrawing it means deleting all the data). If the person has the invitations but not the measurement, a measurement-only checkbox, unticked, also shows below the line, except when your account measures everyone individually.

If whoever is filling in changes the email address, or clicks Not you?, the prefilled data goes away and the checkboxes go back to unticked, as for any visitor: that is what you need when an email is forwarded to a colleague.

The code is removed from the address bar as soon as the page opens: if somebody copies the address to share it, whoever receives it does not find the form filled in with someone else's details. Reloading the page empties the form again.

Visitors who arrive without a link from your emails — from social media, WhatsApp, an address typed by hand — see an empty form and both checkboxes.

The address

A landing page answers at an address made of a domain and an alias:

https://events.yourbrand.com/gala-dinner-2026

The domain is required and 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.

A landing containing the subscribe form also needs the account's default privacy policy, link or text, set under Account › Privacy consents: the form shows it to whoever signs up. Without it the landing stays a draft; landings already published stay online. See Your default privacy policy.

During a free trial without a card publishing also takes a payment method: until you add one from the Billing page the landing stays a draft that only you and your team can see.

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.

Then

How answering works from the guest's side is in RSVP and confirmations.

The whole guide