A real event page
The registration link opens a landing page built from sections — hero, speakers, agenda, FAQ, countdown — with the form as one of them. Register buttons scroll to the form or open it in a pop-up.
Event registration and ticketing
A public registration page, ticket types with their own limits and sale dates, the rules registration runs under, and the emails that follow. Everyone who registers becomes an attendee in the same app they will use on the day.
Summit 2026 · 12 March
Register
Why registration belongs in the app
That usually means an export, an import, and a gap in between where people fall out. When registration is part of the event app, the person who signs up is already the attendee.
A registration creates the attendee record directly. There is no second list to keep in step with the first.
The fields you ask for are the same fields on the attendee record and in the export. Change one and the others follow.
The confirmation email carries a link that opens the attendee's pass in the app. Nobody has to set a password.
Capacity, approval and open or closed are the settings you come back to. They sit on one screen, and every change can be restored.
For attendees
The registration link opens a landing page built from sections — hero, speakers, agenda, FAQ, countdown — with the form as one of them. Register buttons scroll to the form or open it in a pop-up.
Attendees choose from the ticket types on sale, each with its own description. When a type is down to its last 20 places, the form says how many are left.
The form asks what you have switched on, in the order you set. A follow-up question can appear only when an earlier answer calls for it.
Straight after registering, the screen can show their ticket, an Add to calendar button, and up to four links of your choosing — or send them to a page of your own.
The confirmation email carries their ticket reference and check-in code, and a link that signs them into the event app.
By default an email address can register once. Someone already on the list is told so and pointed to sign-in, rather than creating a second record.
How it works
One link to share, and one record per person from the moment they register to the moment they are scanned at the door.
Add ticket types with a quantity and sale dates, choose the fields the form asks for, and set capacity, approval and how people sign in afterwards.
They open your registration link, or the form embedded on your own website, choose a pass and fill in the form.
With approval on, a registration waits in a queue and the person is emailed that it has been received. Approve or cancel in bulk from the attendee list. Until then they are not in the app.
Your confirmation email arrives with their ticket and a link to their pass. The thank-you screen has already told them to look for it.
The link signs them straight into the event app. Later visits use the sign-in method you chose, and on the day their badge QR is ready to scan.
For the organizing team
The page, the passes, the questions, the rules and the emails are separate screens, because they are usually handled by different people at different times.
FAQ
Not at the moment. Registration in NookPass has ticket types, quantities and sale dates, but no checkout, so prices are not shown on the form. For paid events, EventNook, our registration platform, collects payment.
No. If you have not published a landing page, the registration link shows the form on its own, with your banner, event details and colours.
Yes. The form can be embedded in an iframe. Add your website to the form's list of allowed sites, and it will only load on the sites you name.
Registration closes on its own when capacity is reached, and the page says the event is fully booked. Raise the capacity to reopen it. Each ticket type can also have its own quantity, and a sold-out type simply stops being offered.
The confirmation email has a link that signs them straight into the event app. After that, they sign in with the method you chose: ticket QR, ticket QR with an emailed code, or an email magic link.
Yes. Turn on manual approval and each sign-up becomes a request. The person is emailed that it has been received, and is not in the app until you approve them. Approving sends your confirmation email.
By default, no: a repeat registration is refused and the person is pointed to sign-in. You can switch this off for cases such as an assistant registering several colleagues, but only the first registration on an address can sign in to the app.
Yes. Upload a CSV or paste rows from a spreadsheet, check the column mapping and flagged rows, then import. Attendees are matched by email, so re-importing a corrected file updates people rather than duplicating them.
For organizers
A landing page, ticket types with their own limits, capacity and approval, your own emails, and a link that takes every registrant into the app.