# Attendee details — collect extra information per ticket after checkout — MijnEvent

 Module Available 

# Attendee details

Company name, dietary needs, size or weight — collected per ticket after checkout, with reminders that keep going until it is complete.

 [Get in touch](https://mijnevent.nl/en/contact) [From checkout to completed form ↓](#how-title) 

 Per ticket instead of per order: two of ticket A and two of ticket B produce four separate forms One link for the buyer, with a forward button per ticket so the guest fills in their own form Reminders keep running automatically until a form is complete, on a deadline you set 

  The follow-up list in the dashboard: what each attendee is still missing, how often they were reminded and the deadline 

 ![The follow-up list in the dashboard: what each attendee is still missing, how often they were reminded and the deadline](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/screenshots/beheer-deelnemersgegevens-opvolglijst.webp) 

  The attendee details module collects, per ticket type, the information you only need after the sale: company name and registration number for a conference, weight for a balloon flight, dietary needs for a dinner, size for a starter pack or the workshop choice in a multi-day programme. The request hangs on the ticket, not on the order: buy two of ticket A and two of ticket B and you get four separate forms — each of which the buyer forwards to the guest it belongs to in one click. The buyer receives a single link showing everything still outstanding, and reminders keep running by themselves until it is complete. When your deadline passes, you get an alert email listing who is missing what, how often they have been reminded and how to reach them — nothing is cancelled behind your back. In your dashboard you watch the responses come in live and export the lot in one go to your caterer, balloon operator or workshop host. Sensitive fields such as weight and diet are handled separately: stored encrypted, visible only to team members with that permission, and wiped automatically once your event no longer needs them.

   See it in action

## Collecting dietary needs and attendee details after the ticket sale

    Video in Dutch.

The questions come after checkout, per ticket instead of per order. Watch the buyer forward a form to their guest, see who is still missing after the deadline — and that cancelling stays your call.

   How it works

## From checkout to completed form

1. 1 Set per ticket type which fields you need, which are mandatory and when the deadline falls
2. 2 The buyer pays and immediately receives one link to every form in their order
3. 3 Per ticket they either fill it in themselves or forward it to the guest concerned
4. 4 Anyone who has not responded gets a reminder automatically; you watch the responses live in your dashboard
5. 5 After the deadline you get an alert email with who is still missing — you call, extend or cancel for good
6. 6 Export the details to your caterer or supplier; after the retention period the system wipes them automatically

  ![The follow-up list in the dashboard: what each attendee is still missing, how often they were reminded and the deadline](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/screenshots/beheer-deelnemersgegevens-opvolglijst.webp) The follow-up list in the dashboard: what each attendee is still missing, how often they were reminded and the deadline   ![Setting up the form: which ticket types it applies to, when the deadline falls and what happens once it passes](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/screenshots/beheer-deelnemersgegevens-formulier.webp) Setting up the form: which ticket types it applies to, when the deadline falls and what happens once it passes   ![What the attendee sees: why you are asking, what happens to a sensitive answer, and the button to forward the ticket to somebody else](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/screenshots/deelnemersgegevens-invulpagina.webp) What the attendee sees: why you are asking, what happens to a sensitive answer, and the button to forward the ticket to somebody else  

   What you get

## What is included

- Per ticket instead of per order: two of ticket A and two of ticket B produce four separate forms
- One link for the buyer, with a forward button per ticket so the guest fills in their own form
- Reminders keep running automatically until a form is complete, on a deadline you set
- Deadline passed? You get an alert email with who is missing what, how often they were reminded and how to reach them — you decide, not the system
- Automatic cancellation is possible but off by default; "cancel for good" refunds minus the transaction costs already incurred
- A notes field per attendee, so what you agreed on the phone sits with the right person instead of in a side list
- Conditional fields: ask "which diet?" only of those who said yes to the question before it
- Sensitive fields flagged separately: a mandatory purpose statement, explicit consent, encrypted storage and a separate permission to view them
- Export per event or per ticket type to your caterer or supplier — after the retention period the data is wiped automatically, with an audit trail

   Pricing

## Low flat fees — never a percentage

- Your very first event with attendee forms is free. After that a single flat €50 per event, however many forms, fields and attendees you collect — never a percentage and never per form. Adjustable per organisation, down to €0.

All amounts incl. VAT and excluding the transaction fees Mollie charges — those run directly through your own Mollie account, outside MijnEvent. Every fee is a flat amount per unit and can be tailored per organisation.

   Availability

## Available on request

This module is available. Interested? Get in touch and we will activate the module for your organisation.

# Prefer the story from the other side?

A separate page explains how you get your attendees' dietary needs, company numbers and weights in without calling everybody — with four recognisable situations, the overview of who is still missing what, and exactly what does and does not come back when you cancel someone.

 [Collecting details after the sale](https://mijnevent.nl/en/post-purchase-data-collection)

   Same foundation

## Everything on one account and one dashboard

Every module runs on the same backbone as your ticket sales: payments through your own Mollie account with direct payouts, one customer base, one dashboard, passwordless login and WCAG AA accessibility. No separate tools to stitch together.

   Frequently asked questions

## Frequently asked questions

## Why collect the details after checkout instead of during it?

  Because the buyer usually does not have them yet. Somebody booking four seats at a dinner does not know their guests' dietary needs off the top of their head — and a checkout that asks anyway costs you sales. So paying stays short, and the questions start afterwards, with all the time up to your deadline.

## What if a ticket is meant for somebody else?

  The buyer forwards that single form to the guest, in one click from their own overview. The guest fills in only their own form, without an account and without seeing anyone else's answers. The buyer still sees what is outstanding.

## What happens when somebody never fills in their details?

  First the reminders simply keep going. Once your deadline passes, you get an alert email with who is missing what, how often they were reminded and how to reach them. You can call and record the outcome as a note, extend the deadline, or cancel for good — which refunds the ticket minus the transaction costs already incurred. Service fees, order costs and any donation are never refunded. Automatic cancellation can be switched on, but is off by default.

## How do you handle sensitive details such as weight and diet?

  You mark those as sensitive fields, which brings stricter rules: you must state what you need them for, the attendee gives explicit consent, the answers are stored encrypted, and only team members with that specific permission can view them. They also go earlier than the rest: seven days after your event instead of thirty. So we do store the data — for exactly as long as your event needs it and not a day longer, with an audit trail of the deletion.

## Can I show a field only when it is relevant?

  Yes. With conditional fields, "which diet?" only appears for those who said they have dietary needs, and "which workshop on day two?" only for those who bought a two-day ticket. That keeps the form short and stops you collecting what you will never use.

## What does the attendee details module cost?

  A single flat €50 per event where you collect details, and your very first event is free. The amount is independent of the number of forms, fields or attendees — never a percentage and never per form. Adjustable per organisation, down to €0.

## Who is this module for?

  Business conferences that need invoicing details, dinners and galas with dietary needs, sporting and active events where weight, size or an emergency contact matters, workshops with choice rounds, and anyone who still needs something from each individual attendee after the sale.

   Keep reading &amp; watching

## Help, videos and articles for this module

     Tutorial video · 0:19  [Handling a GDPR request: access and erasure in your dashboard](https://mijnevent.nl/en/blog/handling-gdpr-requests)  

 [  ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/privacy-email-masking.webp)   Article · 3 min read Why MijnEvent masks buyer e-mail addresses in the dashboard  ](https://mijnevent.nl/en/blog/privacy-email-masking) 

# Other modules

 [          Rentals &amp; reservations ](https://mijnevent.nl/en/modules/rentals) [                     Reserved seating &amp; floor plans ](https://mijnevent.nl/en/modules/reserved-seating) [          Event feedback ](https://mijnevent.nl/en/modules/attendee-feedback) [          Merchandise &amp; web shop ](https://mijnevent.nl/en/modules/merchandise) [             Local vouchers &amp; city cards ](https://mijnevent.nl/en/modules/city-cards) [               Food trucks &amp; mobile catering ](https://mijnevent.nl/en/modules/food-trucks) [        Safety &amp; permit ](https://mijnevent.nl/en/modules/safety-permit) [            Parking &amp; camping pitches ](https://mijnevent.nl/en/modules/parking) [          Memberships &amp; season passes ](https://mijnevent.nl/en/modules/memberships) [           Newsletter integration ](https://mijnevent.nl/en/modules/newsletter-integration) [          Attendee mailings ](https://mijnevent.nl/en/modules/attendee-mailings) [           Courses &amp; workshops ](https://mijnevent.nl/en/modules/courses) [           Donations &amp; fundraising ](https://mijnevent.nl/en/modules/fundraising) [          Minty — AI chat assistant ](https://mijnevent.nl/en/modules/minty) [              Consumptions &amp; cashless ](https://mijnevent.nl/en/modules/cashless) 

# Interested in this module?

Get in touch — we will discuss what fits your organisation and activate the module together.

 [Get in touch](https://mijnevent.nl/en/contact) [View all modules](https://mijnevent.nl/en/modules)
