GC Events - Ticket Packages – GiveCampus University

Create ticket packages that include multiple attendees for a single price. An excellent option if you need to sell a foursome for a golf tournament or a table of eight at a gala!

Keep in mind:

Ticket packages provide a group of two or more event-level attendees at a single price; packages with zero or one attendee included are not currently supported.

Sponsorships and special cases that need 0 or 1 tickets

If you offer sponsorship levels that don’t meet the package requirements (for instance, a $500 Driving Range sponsor with 1 ticket or a $250 Hole sponsor with no tickets), use one of the following workarounds to keep them grouped in your admin view while complying with package rules.

Quick facts

Ticket packages must include at least 2 tickets; they cannot be created with 0 or 1 ticket.
For single-ticket sponsorships, use individual ticket types instead of packages.
For non-attending sponsors, create a "Not Attending" ticket type priced at the sponsorship level.
Complex events support add-ons for non-ticket sponsorship components.
Simple events offer fewer configuration options for these scenarios.
Clearly name individual ticket types to group sponsorship levels in admin views.
Use hidden ticket types for sponsorship tiers that should not appear in public registration.

Recommended approaches and examples

1) Single-ticket sponsorship (one attending guest)

Create an individual ticket (select Ticket on the Ticketing step) priced at the sponsorship level.
Set an appropriate guest limit to ensure only the intended number of sponsor spots are sold.
Mark the ticket as hidden if you prefer it not to appear in the public flow; manage it via backend registration.
Use clear naming (for example, "Sponsor — Driving Range ($500) — includes 1 ticket") to group sponsorships in the admin view and reports.

2) Non-attending sponsorship (zero tickets)

Create an individual ticket type (such as "Sponsor — Hole Sponsor (Not Attending) — $250") with the sponsorship price.
Remove or make optional any attendee fields since the sponsor is not attending.
Optionally hide this ticket type from public registration and handle it via backend registration.

3) Sponsorships with non-ticket components (e.g., signage, dinner, auction table)

In complex events, use add-ons to represent non-ticket elements (for example, sponsor swag or dinner add-ons).
For sponsorships that include one ticket along with additional components, combine an individual ticket with one or more add-ons.
For simple events needing add-on flexibility, consider converting the event to a complex event configuration.

4) Organizing and reporting on sponsorship levels

Adopt a consistent naming format (for example, "Sponsor — [Level] — [Attending/Not Attending] — $[amount]") to group sponsorship entries.
Apply ticket limits to control the sponsorship inventory.
Use hidden ticket types for private or invitation-only sponsorships; these remain visible in admin views but are not shown during public registration.

Additional considerations

Attempting to create a package for a single ticket will fail because packages require at least 2 tickets.
To allow sponsors to register without immediately providing guest information, make attendee fields optional and enable registration edits.
For advanced sponsorship configurations involving add-ons or hidden tickets, a complex event setup offers greater flexibility.

Ticket packages can be purchased without requiring attendee names at the time of purchase; if registration edits are enabled, registrants can return and add or edit guest names at a later date or administrators can add or edit guest names on behalf of the registrant.
Ticket packages that automatically include activities or add ons in complex events are not currently supported.
Ticket packages require an exact number of tickets to be included in a package; partial packages (i.e. up to 6 guests) are not currently supported.
Registrants can select a mix of individual tickets and/or packages, up to the maximum number of attendees permitted per registration.
Registrants can only select a ticket package if there are sufficient remaining tickets available for the overall event; otherwise the ticket package will be unselectable during registration (i.e. a ticket package of 8 tickets cannot be selected if an event has 48 of 50 available tickets already sold).

FAQ — My package is missing or greyed out in the public flow (per-registration limit)

Issue: The package's selectable quantity is the lower of the event's per-registration cap and the package's remaining inventory. If a package's ticket count exceeds the event’s Max guests per registration value, its effective selectable maximum becomes 0, causing the package to appear greyed out or unselectable during registration.
Why it matters: This limit is separate from the overall event guest limit. The overall guest limit determines if enough seats are available to sell the package, while the per-registration cap controls how many tickets a single registrant can purchase in one checkout.
Examples:
- An 8-ticket package will be unselectable if the event's Max guests per registration is set to 4.
- For a package that includes 6 tickets, Max guests per registration should be set to 6 or higher.
Diagnosing the issue:
1. Open the event in admin and click Edit Event.
2. Navigate to the Ticketing step and check the Max guests per registration value.
3. Compare this value with the number of tickets per package configured.
4. If the package requires more tickets than allowed by the per-registration limit, it will be unselectable.
Fixing the issue:
- Option A — Raise the per-registration cap: Increase Max guests per registration to at least match the ticket count in your largest package.
- Option B — Reduce the package size: Lower the number of tickets per package so it does not exceed the per-registration limit.

Remember, the per-registration limit applies to the total number of tickets and packages selected in a single registration.

Building ticket packages:

On the Ticketing step of your event settings, adding a ticket type presents you with the option of a ‘Ticket’ or a ‘Package’.

Ticket: These tickets are priced per attendee.
Package: These are priced to allow a specific number of attendees per package.

Select ‘Package’ and complete the fields below:

Package Name (50 character max): Required, shown to registrants
Package Description (150 character max): Optional, shown to registrants
Price: Required, set to 0 if free
Fair Market Value: Required, reflected in tax receipt
Number of tickets per package: Required, number of tickets included in this package, 2 minimum, 50 maximum
Package Limit: Required, enter the maximum number of this package available for the event, not per registration or check ‘Unlimited’
Restrict Package: Optional, packages can be restricted based on affiliation (if collected) of the registrant or each individual guest
Hidden Package: Optional, hidden packages cannot be seen by registrants in the registration flow but are visible in the admin view

On the Guest Information step, fields added to the Attendee Form will be collected from guests added to a ticket package, just as they are for guests who select individual tickets.

Attendee questions vs. custom fields: which to use for package guests

Use attendee questions when the same field should be repeated for every person included in a package (for example, capturing golf foursome member names). These questions appear in the Guest Information step under the Attendee Questions header and automatically generate fields based on the number of tickets in a package.

Custom fields can be added in two areas:

Registrant Questions: Captures information once for the primary registrant.
Attendee Questions: Appears for each individual attendee. For example, adding a First Name and Last Name field here will generate separate entries for each ticket in a package (a package of 4 will produce four sets of name fields).

Tips:

Mark attendee fields as optional if you want to allow package purchases without immediately providing guest names.
Adding a custom field under Registrant Questions captures data only once for the registrant, not per guest.
The attendee form dynamically generates fields based on the ticket selection, regardless of whether the ticket is part of a package or an individual ticket with guest entries.

Before publishing, verify that:

Custom fields for guest data are added under Attendee Questions.
The Attendee Questions header is visible in the Guest Information step.
The registration flow generates the expected number of guest fields when a package is selected.

All fields on the Attendee Form can be made optional (unstarred) if you would like to allow registrants to purchase a ticket package without having to enter guest information at the time of purchase. If registration edits are enabled for the event, registrants can return to edit or add attendee names using the edit registration link provided in their confirmation, summary, or reminder email. Administrators can also edit or add attendee information on behalf of the registrant.

Collecting guest information for ticket packages

Use attendee questions to gather details for each person in a ticket package. When a package is selected, the system automatically generates one set of fields per ticket (for example, a 4-person package creates four sets of fields for name, handicap, meal choice, or other data).

Best practices for collecting guest details

Add per-person fields such as First name, Last name, and Handicap as attendee questions. The system will create one set of these fields for every ticket in the package.
If you want purchasers to reserve a package without entering all guest information immediately, mark attendee fields as optional.
When a specific format is needed (for example, a whole number for a handicap), use a short text or number field and provide a placeholder or helper text (e.g., "Enter handicap as a whole number").

Allowing purchasers to add guest details later

Enable Registration Edits so that purchasers can update guest information after purchase using the edit-registration link provided in their confirmation, summary, or reminder emails. Administrators can also update guest details via the admin registration screens.

Other tips and gotchas

The attendee form dynamically generates fields based on the ticket quantity. Test the flow to confirm the correct number of guest fields are displayed.
Ticket packages require an exact number of seats; you cannot offer a package that allows "up to" N guests.
If you expect all guest details at checkout, set attendee questions as required; otherwise, mark them optional to allow later updates via Registration Edits or admin edits.

Examples

Golf foursome: Create a 4-ticket package and include attendee questions for First name, Last name, and Handicap. The registration flow will display four sets of these fields when the package is selected.
Sponsor table with named seats: Create a package for the table size and add attendee questions for seat assignments and meal choices. If sponsors should provide details later, mark these fields as optional and enable Registration Edits.

Selecting a ticket package as a registrant:

When ticket packages are added to an event, registrants will be shown a “Tickets & Packages” section following the fields collected on the Registrant Form.

Adding an ‘Individual Ticket’ will present the registrant with a dropdown to select the individual ticket type for each attendee.

Adding a ‘Package’ will automatically generate attendee fields for the number of tickets included in the package. The registrant will be assigned to the first included package ticket unless they indicate they are not attending and registering on behalf of someone else.