If you're new to Funraise Events, we recommend taking a look at our overview of all things related to Events: Event Management 101.
Create a Ticket
1. In the sidemenu > click Events > select an Event
2. In the Event profile > Click Tickets > click Add Ticket
3. After configuring the Ticket (described below), click Save
☝️ Tickets are sold on a Giving Form
After creating Tickets, you'll add your Tickets to a Giving Form to sell them online.
Ticket Settings — General
In the General tab, you'll configure details about the ticket:
Ticket settings
Ticket Name | Public name for the ticket. Displayed on the Giving Form and in ticket confirmation emails. |
Description | Public description for the ticket. Displayed on the Giving Form. |
Quantity | The maximum number of tickets available. If this number is reached, this ticket will display "Sold Out" on the Giving Form. |
Limit Per Transaction | Limit the number of this ticket that can be purchased in a single transaction. Leave blank for no limit. |
Registrations Included | The number of registrations included with each ticket. Use this to create ticket bundles.
|
Ticket payment
Payment | Select whether this is a Paid or Free ticket. |
Ticket Cost | If this is a paid ticket, you can configure the cost of the ticket. |
Tax Deductible Amount | The tax-deducible portion of the ticket cost. For example, if a ticket costs $50 and $25 of that goes towards the meal, you might enter $25 as the tax deductible amount. When the transaction receipt is sent to the ticket purchaser, they will see their total transaction amount and the tax deductible amount on the receipt email. |
Ticket Settings — Registration Info
In the Registration tab, you'll configure the information you'd like collected with each Registration.
Registration settings
Registration Name | Require a name for each registration? |
Registration Email Address | Require an email address for each registration? |
Registration Phone Number | Require an phone number for each registration? |
Some helpful definitions:
Public order — When a ticket is sold on a Giving Form online
Platform order — When a ticket added to an order offline (in the platform)
Registration Questions
Custom questions can be added to a ticket. For example, if you need to know the guest's meal preference or T-shirt size. Adding questions to the ticket means that questions will be asked for each registration.
☝️ It's good to know that you can add Questions to both Tickets and the Giving Forms. If you need responses from each Registrant, for example, "What is your t-shirt size?", you'll need to add your Questions to the Ticket — These questions will then be asked for each Ticket in an Order. If you just want to ask a general Question to the purchaser, like "How did you hear about us?", you'll want to add that Question to the Giving Form.
Good to know!
☝️ Tickets are sold on a Giving Form
After creating Tickets, you'll add your Tickets to a Giving Form to sell them online.
Promo Codes
Create promo codes your guests can use to purchase discounted tickets.
Ticket bundles
You can create ticket bundles, or sponsorship tickets, that include multiple registrations for a single ticket. When creating the ticket, enter the number of registrations that should be included for each ticket. For example:
For a general admission ticket, Registrations Included should be set to 1.
A sponsorship ticket might include multiple registrations. For instance, a table sponsorship ticket might have 10 registrations included.
A pickle ball team ticket might include 2 registrations.
Duplicate tickets
When creating similar tickets for the same event, you can duplicate a ticket:
Should you require Registration contact information?
For sponsorship tickets that that include multiple registrations, we do not recommend require registration contact information or custom questions, as the sponsor (purchaser) may not have those details at the time of purchase. If Registration contact information and custom questions are not required for a ticket, guests can skip these fields when purchasing tickets.
In most cases, and especially for events with family participation we recommend always requiring registration name so that you can know which family member the registration should be assigned to.
Here's why: If an email address is provided for a registration, that registration will create or be matched with a supporter in the platform. This means if the a ticket purchaser provides a single email for each registration in the order, those registrations will all be assigned to the same supporter — this is common when parents obtain tickets for their family. If you require a registration name, you can use that information to create or assign a supporter record for each registration as needed.