How to export a guest list from Luma

Luma exports a guest list as a CSV from the event’s Guests tab. You need host or manager access on the event, the download takes about thirty seconds, and the file includes every registration along with the answers to any questions you asked at sign-up.

Below are the steps, what each column contains, and which fields are worth keeping once the event is over.

Export the list

1. Open the event as a hostSign in at lu.ma and pick the event from your calendar. A guest-level ticket does not give you this; you need to be the host or a manager on the event itself.
2. Go to the Guests tabThis is the list of everyone who registered, with their approval status and, if you used check-in, whether they actually turned up.
3. Download the CSVUse the download or export control on the guest list. Luma generates the file immediately rather than emailing it, so it lands in your downloads folder.
4. Check the row count before you close the tabOpen the file and confirm the number of rows matches the registration count Luma shows on screen. If you have registration approval turned on, decide whether you want everyone who applied or only the guests you approved.

Luma moves its controls occasionally. If the export is not where you expect it, it is on the guest list itself rather than in the event settings.

Exporting across a whole calendar

The steps above give you one event. If you run a series and want everyone who has ever attended, do it from the calendar rather than the event: open the calendar you manage, go to its People view, and export from there. That file is deduplicated by person, so someone who came to six of your events appears once.

For measurement, both exports are useful for different reasons. The per-event file is what you report on. The calendar file is what tells you who your regulars are.

What is in the file

Column names shift slightly over time, but a Luma export gives you:

• Name and email. The two fields everything downstream depends on.
• Registration date. Useful for judging whether your promotion worked early or the room filled in the last 48 hours.
• Approval status. Present when you gate registrations, and worth keeping so your headcount does not silently include people you declined.
• Ticket type. Which tier or guest list someone came in on, if you sold more than one.
• Check-in status and time. Only populated if you actually checked guests in at the door. This is the difference between who registered and who came.
• Answers to your registration questions. Every custom field you added, one column each, including social handles if you asked for them.

Which fields to keep

Keep all of it. The temptation after an event is to strip the file down to names and emails for a mailing list, and that throws away the columns that make the next report possible.

Check-in status is the one people regret losing. Registration numbers are a marketing metric and attendance is an event metric, and once the file is gone you cannot reconstruct which of the two you were looking at. Ticket type is the second, because it is usually the only record of how someone got into the room.

What to do with it

A CSV of names and emails is where most post-event reporting stops, and it is also where the useful part starts. The people in that file posted about your event, brought other people to it, and some of them have been to three of your events already. None of that is in the export.

Best Guests takes the file as it comes out of Luma and resolves each row to the person behind it, then finds what those guests published about the event and builds the report from both. If you want the detail: guest list enrichment is the matching step, content capture is the content, and earned media value explains the number the two of them produce together.