Create registration form — events, courses, workshops

Double opt-in means: after registration, the user receives a confirmation email with a link, and only after clicking is the registration valid. For newsletters this is effectively mandatory in Germany — case law requires proof of voluntary consent, and only double opt-in provides this cleanly documented.

For pure event or course registrations, it is often counterproductive. Anyone paying or booking a fixed date has clearly stated their intent — an additional email confirmation only costs conversions because it lands in spam or is forgotten. Here, the receipt confirmation as information is enough.

Rule of thumb: double opt-in whenever the registration leads to recurring contact (newsletter, updates, promotional mails). Single opt-in for one-off events like event tickets, webinar spots or paid bookings. If you need both, couple two fields: a mandatory checkbox for the registration itself and an optional one for the newsletter — the latter then with double opt-in.

The welcome email decides the first impression after registration. It should arrive immediately after submission — not 10 minutes later and certainly not the next day. Email marketing studies show open rates of 50 to 70 percent in the first hours, after which attention drops steeply.

Three content blocks are mandatory: a concrete confirmation of the action ("You are registered for the workshop on March 5, 2:00 PM"), next steps ("You will receive the access link 24 hours in advance") and a contact path for questions. A generic "Welcome!" without substance looks unprofessional.

For events, an ICS attachment is worthwhile so the date lands directly in the calendar. For multi-stage registrations (early bird → reminder → event), a sequence makes sense: confirmation immediately, reminder 7 days in advance, reminder 24 hours before. A webhook to a mail provider (Brevo, Postmark) automates this without manual sending.

Both have different jobs — they do not replace but complement each other. The confirmation page (thank-you page) confirms in the same moment that the registration arrived. That is psychologically important: without visible reaction the form feels swallowed, and users often press "submit" a second time.

The email confirmation, in contrast, is the lasting proof. It lands in the inbox, remains searchable and ideally contains the ICS appointment or a receipt. A confirmation page alone is not enough — the user has no proof if they are unsure later.

The thank-you page is also the best place for tracking pixels (Google Ads Conversion, Meta Pixel) and for gentle cross-selling: a hint to related events, a request for referral or a link to the calendar with more dates. But it should never become pushy — the primary message remains: "Everything worked, you are in."

Registrations typically process personal data — name, email, often address or date of birth. GDPR applies. Three duties are indispensable: a privacy notice on the form (not a hidden footer link), clear purpose limitation ("to carry out the event") and a documented legal basis — usually Art. 6(1)(b) (contract) or (a) (consent).

If you want to use the data later for marketing or newsletters, you need separate, voluntary consent — as an optional checkbox, never required. The prohibition of coupling (Art. 7(4) GDPR) forbids tying registration to newsletter consent.

Retention: event data may typically be kept 6 to 12 months after the event for follow-up, after that it must be deleted or anonymized. An automatic deletion routine saves later work on access and erasure requests. With EU hosting (Hetzner, OVH), the tricky Schrems II discussion on third-country transfer is avoided.

Complex registrations — multi-day conferences, workshops with tracks, training with pre-qualification — overwhelm in a single form. The solution is splitting into logical steps: basic data first, depth later.

A proven pattern: step 1 captures mandatory data (name, email, preferred date) and secures the spot. Only once the registration is binding does step 2 ask for details (track selection, dietary wishes, travel). Advantage: you already have the lead even if the user abandons step 2.

For really long registrations, a save-and-continue-later mechanism via magic link pays off. The user gets a mail and can resume the form the next day where they left off. Conditional logic shows follow-up questions only when relevant — e.g. "traveling with companion?" → "name of companion". The form becomes multi-stage but feels shorter per user than one long block.