Skip to content

Exporting data ​

Your registration data is yours. BagEvent lets you export attendees, orders, form responses, and promo codes as CSV files you can open in any spreadsheet tool, hand to a partner, or load into another system. This page explains what you can export, how, and what the files contain.

What you can export ​

ExportWhereFile
Attendees (with their form responses)Attendees page → Exportevent-<id>-attendees.csv
OrdersOrders page → Export CSVorders-<id>.csv
Promo codesPromo codes page → Export CSVpromo-codes-<id>.csv

All exports are CSV, UTF-8 encoded. Form responses aren't a separate export — they come out as columns on the attendee export (see below).

TIP

Exporting is a plan-gated feature. If the Export button returns a permission message, it's tied to your subscription plan rather than a bug.

Exporting attendees ​

The attendee export is the main one, because it carries each person's details and their answers to your registration form.

  1. Open Attendees.
  2. Optionally narrow the list first — the export respects your current tab (Attending, Pending review, Rejected, and so on), your search, and the ticket filter. Export the Pending review tab to get just those awaiting approval, for instance.
  3. Choose Export.
  4. The export runs as a background job. When it's ready, the file downloads automatically and you'll see how many rows it contained.

Because it's a background job, a very large export may still be processing when you look — in that case BagEvent tells you it's still running and to try downloading again shortly.

WARNING

A single attendee export covers up to 10,000 rows. For larger events, filter by ticket type or tab and export in slices.

Exporting orders ​

From the Orders page, choose Export CSV. This downloads the order-level data directly — one row per order rather than per attendee. Use the attendee export when you need per-person detail and form answers; use the order export when you need the commercial picture (buyer, totals, payment, order numbers).

Exporting promo codes ​

From the Promo codes page, Export CSV downloads every code for the event with its kind, reward, ticket scope, used / max counts, remark, status, and — for invite codes — the invite link. See Discount codes for what those fields mean.

Format & fields ​

Attendee export columns ​

By default the attendee CSV includes these system columns:

Column headerContents
Modification IDAn opaque key identifying the attendee, used to re-import edits (see below). Always included.
Full nameAttendee's name.
EmailAttendee's email.
PhoneAttendee's phone.
Ticket codeThe barcode used at check-in.
TicketTicket type name.
Channel type / Channel codeThe registration channel, if any.
Promo codeDiscount code applied to the registration.
Invite codeInvite code used, if any.
Audit statusApproval state (approved, pending, rejected).
Check-in statusWhether the attendee has been checked in.
Check-in timeWhen they were checked in.
NotesInternal notes on the attendee.
Refund statusAny refund state on the registration.
Registered atWhen the registration was created.
Order numberThe order the attendee belongs to.

After the system columns come your form fields — one column per field on your registration form, headed with the field's label and filled with each attendee's answer. This is how form responses are exported.

TIP

You can tailor which columns appear by saving export field preferences, but the Modification ID is always kept so an exported file can be edited and re-imported safely.

The Modification ID and batch edits ​

The attendee export is also the first half of a round-trip edit: export → edit in a spreadsheet → re-import.

  • The Modification ID column tells BagEvent which attendee each row updates, so rows are matched by that key rather than by name or email.
  • Edit the columns you want to change (such as name, email, phone, or form answers), keep the Modification ID column, and re-import through Batch update on the Attendees page.
  • A batch update handles up to 10,000 rows at once, and reports how many succeeded and which rows failed.

WARNING

Don't remove or alter the Modification ID column when editing an export you intend to re-import — without it, BagEvent can't tell which attendee a row belongs to.

BagEvent Help Center