Adding Tickets in Batch

This guide walks you through creating a batch of tickets, either by entering them manually or importing from a spreadsheet.

Creating a New Batch

1. Go to Manage > Batches
2. Click Create
3. Give your batch a name (e.g., "Event Ticket Import")
4. Select the Tickets tab

Adding Tickets Manually

Click Add to open the ticket form. Fill in the required fields and any optional information.

Campaign & Context

Field	Description
Campaign	The campaign this ticket belongs to (required)
Ticketing Form	The ticketing form for the ticket (required)
Ticket Tier	The tier/level for the ticket (required)
Site	Optionally associate with a specific site

Ticket Details

Field	Description
Status	Ticket status — defaults to "unredeemed" (required)
Created Date	When the ticket was created — defaults to now (required)

Ticket Holder

Field	Description
First Name	Ticket holder's first name (required)
Last Name	Ticket holder's last name
Email	Ticket holder's email address (required)

Additional Fields

Field	Description
Contact	Link to an existing contact (optional — a new contact is created if not linked)
Tags	Add ticket tags
Custom Fields	Any custom fields configured for tickets

Editing and Removing Rows

• Edit: Click anywhere on a row to open the form and make changes
• Delete: Click the trash icon on the right side of a row

Importing from Spreadsheet

For large ticket lists, importing from a spreadsheet is faster:

1. Click Import from Spreadsheet at the bottom of the batch
2. Select your CSV or Excel file
3. Map your columns to the correct fields (if needed)
4. Review the imported rows

See Importing from Spreadsheet for detailed instructions on the import process.

Supported CSV Columns

Below is the full list of columns supported when importing tickets from a CSV or Excel file.

Required

Column	Description
first_name	Ticket holder's first name
email	Ticket holder's email address
campaign_id	Campaign ID (GUID)
ticketing_form_id	Ticketing form ID (GUID)
tier_id	Ticket tier ID (GUID)

Optional

Column	Description
last_name	Ticket holder's last name
status	Ticket status (defaults to "unredeemed")
created_at	Created date in YYYY-MM-DD format (defaults to now)
site_id	Site ID (GUID)

Custom Fields (numbered, via column mapping)

Add custom field values using numbered columns:

Column	Description
ticket_custom_field_1	Value for the first ticket custom field
ticket_custom_field_2	Value for the second ticket custom field

Add more numbered columns (_3, _4, etc.) as needed.

Tags (numbered, via column mapping)

Apply tags using numbered columns:

Column	Description
ticket_tag_1	Tag name to apply to the ticket
ticket_tag_2	Second tag for the ticket

Add more numbered columns (_3, _4, etc.) as needed.

TIP

Custom fields and tags use numbered suffixes (_1, _2, etc.) and require the column mapping step during import. When you upload your file, map each numbered column to the correct field.

How Contacts Are Linked

When a ticket row has no contact_id but has an email:

• Email matches an existing contact → the ticket is linked to that contact.
• Email doesn't match any existing contact → a new contact is created using the row's name and email.
• Multiple rows in the same batch share the same unmatched email → rows 2..N are flagged with a warning on the review screen, and all of them link to the single new contact created by the first row.

TIP

Email lookup happens at upload time. Adding a contact through the UI after uploading but before processing won't retroactively link the batch to it. See Importing from Spreadsheet for details.

Processing the Batch

When you're ready to finalize:

1. Review all ticket information
2. Click Process Batch
3. Confirm the action

Important

Batch processing cannot be undone. Once processed, each ticket becomes a permanent record. Double-check your data before processing.

After Processing

Once processed:

• Tickets appear in the ticketing section of the associated campaign
• A contact is created or linked for each ticket holder
• Tags are applied to tickets
• Custom field values are saved

Tips and Best Practices

1. Verify IDs - Ensure campaign_id, ticketing_form_id, and tier_id are correct GUIDs from your system
2. Use valid emails - Email is required and must be properly formatted
3. Test first - Import a small sample before the full file
4. Check tier availability - Ticket tiers must exist on the selected ticketing form