Task · Attendees

Import a list of attendees

Bring in a spreadsheet of people already coming, and fix what the file got wrong before anything is created.

8 steps · About 5 minutes · Needs: A CSV or spreadsheet of names

1. From the attendees list, select Add, then Import a file

   Your eventAttendees

2. Upload your file

   Download the template gives you the columns it expects. Only a name is required. You can also send an email address, an identifier, a ticket type, a price, and a column for any of your own fields.

   go.tito.io/acme/summer-fete/admin/attendees?import=1

3. Choose the Default ticket type

   Rows that don't name a type of their own get this one. A row's own ticket_type has to match a ticket type's name.

4. Under Default price, choose Complimentary (free) or Published price, paid offline

   Rows that name a price of their own use that instead.

5. Select Check the file

   This reads your file and shows you what it found. Nothing is created yet.

6. Read the counts along the top

   Rows is what was in the file. Adding and Updating are what the import would do. Skipped is the rows it can't take as they stand, and Names to check is the names that could be read more than one way.

7. Fix anything under Skipped

   A skipped row keeps its place in the list with boxes you can type in, and the reason beside it: No name, Invalid email, Invalid price, or that no ticket type has the name the row sent. Correct it there and tick the row to include it.

8. Read the summary, then select the Import button at the foot of the page

   It counts the ticked rows, so a file of 25 with every row ticked reads "Import 25 attendees". Untick rows and the count drops to match, and the button turns itself off when nothing is left to bring in. This is the step that creates people.

   A ticked row with a problem still in it stops the whole import.

   The page says nothing has been imported yet and asks you to fix or untick those rows. Everything else waits until you have.

Checking how the names read

Where a name could be split more than one way, Check how these names read lists it with the readings offered side by side. The one already selected is what the import will use, so you only need to touch the ones that are wrong.

A name your account has read both ways before arrives with neither reading selected, and says so. Pick the one that fits this person.

Warnings you can import past

The import runs with a warning on it.

• More people than the ticket type has left. The warning names the type, how many are left and how many the ticked rows add, and offers to untick enough rows to fit.
• A ticket type that's off sale, or outside its sales window. Importing adds attendees to it anyway.
• Rows that already have a ticket under the same email address, or that repeat an address used earlier in the file. Those are marked Already here, and one action unticks them all.
• Rows with no email address. Those can't be checked for duplicates, and the page says how many there are.
• Rows that would change an existing attendee's ticket type or price. An import keeps the ticket type and the money they already have.

Good to know

• Every imported person gets an order of their own, holding their one ticket.