Data & Exports

CSV reference.

Every column read on import and written on export.

Every column this platform reads on import and writes on export, in one place.

Guest import

A sample is downloadable per ticket tier from the guest list, under Tools, then Upload CSV. Each row names its own tier in ticket_id, so one file can carry several. See importing guests.

Column Required Notes
ticket_id Yes The tier's numeric id. Pre-filled in the sample.
ticket_type Yes The tier's name, for readability.
billing_first_name Yes The contact responsible for the registration.
billing_last_name Yes
billing_email Yes Must be a valid email address.
attendee_first_name Yes The person attending.
attendee_last_name Yes
attendee_email Yes Must be a valid email address.

After those, one column per question in that tier's fieldset, headed by the field key rather than the label. Select answers must match one of the option values.

If the attendee paid for themselves, repeat the same values in both sets of columns.

Schedule import

Downloaded from the schedules page. See schedules.

Column Required Notes
name Yes The session name.
location_id Yes The numeric id of a saved location, not its name.
start_date Yes YYYY-MM-DD.
end_date Yes YYYY-MM-DD.
start_time Yes 24-hour time.
end_time Yes 24-hour time.
details No Notes shown with the schedule.
is_published No Whether it appears on the public page.
is_check_in_enabled No Whether the scanner accepts it.
sort_order No Display order, lowest first.

Guest sheet export

One CSV per ticket tier, inside a zip. See exports.

Column Contents
first_name, last_name, email The attendee.
ticket The tier name.
qr_code_url The address of this guest's QR code.
source How the guest arrived: the event site, or manual.
registration_date When the guest record was created.
amount_paid The amount, in major units to two decimal places.
payment_status The payment state of the registration.
archived Yes or No.
One per fieldset question Headed by the question's label.
checked_in: <schedule name> The check-in time for that schedule, blank if they did not attend.

Schedule attendance export

Downloaded per schedule from the door desk.

Column Contents
first_name, last_name The attendee.
email Blank where no email is on file.
ticket The tier name.
checked_in_at When they were checked in.

General rules

  • Files are comma separated, with a header row.
  • The header row must match exactly. Extra columns the importer does not recognise are treated as custom fields.
  • Blank optional values are allowed. Leave the cell empty rather than writing null.
  • An import shows you a preview of every row, with problems flagged, before anything is created. Use it. Re-uploading a corrected file costs nothing.