Importing attendees & contacts

There are two kinds of import in BagEvent:

• Attendees — people registered for one event, with a ticket. Import them when registrations happened somewhere else (a partner list, a previous system, walk-ins recorded on paper).
• Contacts — your organization's address book, kept across events. Import them to send invitations to people who haven't registered yet.

Import attendees from a CSV file

Open the event's Attendees page and choose Import CSV. You need the Import attendees permission.

1. Pick a Default ticket — used for any row that doesn't name a ticket.
2. Choose Download CSV template. The template has the columns ticketId, fullName, email and phone, plus one column for each field on your registration form. It includes one sample row — delete it before you import, or it will be imported too.
3. Fill in the file and save it as CSV (Excel .xlsx isn't accepted).
4. Choose the file under CSV file.
5. Tick Send confirmation email if imported attendees should get the registration confirmation email. It's off by default.
6. Choose Validate. BagEvent shows how many rows are valid and lists the problems in the others ("Row N: …").
7. Choose Import N valid. Only valid rows are imported; the result lists any row that failed and why.

Columns

Columns are matched by name, whatever their order:

Column	Also accepted as	Notes
ticketId	ticket	A ticket's name or id. Blank uses the default ticket.
fullName	name	Split into first and last name if your form asks for them separately.
email	emailAddress
phone	mobile, tel
notes	note, remark	Internal notes. Optional.

Any other column is saved as the answer to the registration-form field with that key. Each row needs a ticket and at least a name or an email.

What an imported attendee is

• Each row becomes its own complimentary registration — a free, confirmed order — on the chosen ticket. Nobody is charged.
• If the ticket requires approval, the attendee starts as Pending review.
• Imports use up ticket stock, and count toward your plan's attendees-per-event limit. A row fails if the ticket has no stock left.
• There's no duplicate check. Importing the same file twice registers everyone twice, so import each list once.

Add one attendee by hand

On Attendees, choose Add. Pick the Ticket (and, if you want, a sales channel, invite code or discount code), fill in the registration form, and Submit. It creates a complimentary registration. Tick Send ticket email to email them their ticket.

Contacts

Your contacts live under Contacts in Resources in the left navigation, and are shared by every event in the organization. Each email address is one contact; saving an address that's already there updates it. You need the Contact list permission.

Organize contacts into Groups — those are what you pick when you send an invitation.

Import contacts

Choose Import. There are two ways in:

• Paste or CSV — paste rows from a spreadsheet or CSV file into Rows, one person per line. BagEvent finds the email wherever it is in the line, and picks up a name before it and a company after it. Lines without an email (such as a header row) are skipped.
• From an event — choose an event to add everyone who registered for it, so they're still reachable once the event is over.

Tick the groups to add them to under Add to groups, then Import N. Up to 5,000 rows per import. The result shows how many were added, updated or skipped, and why.

Only email, name and company are imported. An address already in the book is updated rather than added twice, and anyone who unsubscribed stays unsubscribed — unsubscribed contacts are always left out of invitations.

Only import people you may email

BagEvent doesn't ask for consent on import. Make sure the people you import have agreed to hear from you, under the rules that apply to you and them.

Related

• Exporting data — including batch updates with the Modification ID.
• Broadcasts & email credits — send invitations to contact groups.
• Tickets & inventory — stock that imports use up.
• Approving attendees