CSV exports
Export your registration data as a CSV file from the Registrations table. The file contains one row per ticket, including all standard fields and any custom question responses.
Updated May 26, 2026
From the Registrations table, click the download icon in the toolbar to export all registration data for the event as a CSV file. The file downloads immediately in your browser as [event-slug]-attendees.csv.
What the file contains
The export is one row per ticket, not one row per registration. A single registration with three tickets produces three rows, each sharing the same registration_id but with distinct ticket_id and ticket_code values.
Every export includes these columns in this order:
registration_idticket_idticket_codestatusfirst_namelast_nameemailphoneticket_typeprice_tierregistration_pathsubtotaldiscount_amounttotal_amountdiscount_codepayment_statusstripe_payment_intent_idattendee_confirmed_atchecked_in_atcreated_atcancelled_atemail_marketing_consentsms_transactional_consentsms_marketing_consent
Custom questions in the export
After the static columns, the file adds one column per custom question in the order they appear on your registration form. The column header matches the question's display label.
PII columns and permissions
Questions marked as PII (personally identifiable information) get (PII) appended to their column header in the CSV. Operators without the View PII permission have those columns omitted from their export entirely — the column does not appear at all, blank or otherwise.
Filters are not applied to the export
The export always includes every registration for the event, regardless of what filters are active in the table. If you filter to status = Confirmed and then click Export, the CSV still contains cancelled, refunded, and pending rows.
The export button is disabled only when the table has no rows at all. Any other table state — filtered, sorted, searched — does not change what goes into the file. Filter in your spreadsheet tool after downloading.