What is event registration?

Registration is where somebody becomes an attendee: a form, some details, sometimes a payment, and a confirmation. It produces the list that everything downstream depends on.

In practice at an event

A registration system typically handles ticket types and pricing, custom questions, discount codes, group bookings, payment processing, confirmation emails and a reporting view of who has signed up. Its output is a list, usually exportable as CSV.

That list then flows into the event app as an import, and from there into invitations. The two systems are usually different vendors, and the handover between them is a real integration point worth checking before you commit to either.

What to look for

The most consequential thing to know is that registration and the event app are different categories with different prices. Products that do both are full event-management suites, and they cost several times what an attendee app costs, because you are also buying the transaction machinery.

If you already have registration you are happy with, buying a suite means paying twice for it.

Where event67 stands

event67 does not do registration, ticketing or payments. There is no sign-up form, no ticket type, no discount code and no payment processing for attendees. This is a stated boundary rather than a gap.

What it does is take the list you already have: import attendees from CSV, send invitations with per-recipient delivery tracking, and bill only on the people who claim an invitation and open the app. Whether the list came from a ticketing platform, a corporate directory or a spreadsheet makes no difference to it.