If you are hosting an event in which registrants can bring guests, or you want to allow for a registrant to order several tickets on behalf of a group, there are various ways you can set up your ticket configuration to allow for this. Additionally, you can collect information from each guest/attendee in addition to the primary registrant.
Option 1: Configure multiple tickets based on ticket holder type
Option 2: Create single ticket for registrant and guests/additional attendees
Option 3: Configure paid ticket for registrant and free ticket for guests
See the guest/attendee information for each primary registrant
 | Important: If you choose to collect an email address from each attendee, it does not give you or Constant Contact explicit permission to mail these users. Only the primary registrant can be sent event-related email. If you plan on adding the email addresses collected from each attendee to a list, you must have explicitly received this request from each email address holder. |
You can allow for guests to attend your event by creating multiple tickets for each ticket holder type. For example, you can create a ticket named "General Admission - Member" and another ticket named "General Admission - Guest". Set the "Limit per order" quantity to 1 for the "General Admission - Member" ticket and to the allowable number of guests per registrant for the "General Admission - Guest" ticket.
When checking out, the registrant would select the "General Admission - Member" ticket for themselves and a "General Admission - Guest" ticket for each guest they are bringing. In the below example, the registrant is purchasing a ticket for themselves and tickets for two guests:
On the registration form, the first name, last name, and email will be collected from the primary registrant. You can further customize your form by adding additional form fields. When adding a field, you can indicate whether to collect the information from the primary registrant or not, and which ticket types the field applies to.
In the example below, we've added the "First name" field and applied it to the "General Admission - Guest" ticket. This means that in addition to collecting the first name, last name, and email from the primary registrant, we will also collect the first name from each guest/attendee.
Let's say you'd also like to collect certain info from each guest/attendee, but not collect that info from the primary registrant. In the following example, we've added a custom field asking for the relation of the guest/attendee to the primary registrant. We have not applied it to the primary registrant and we have applied it to the "General Admission - Guest" ticket. This means that in addition to collecting the first name, last name, and email from the primary registrant, we will also collect the first name and "relation to primary registrant" from each guest/attendee.
You can allow for the registration of multiple attendees within a single order, or allow registrants to bring guests, by creating a single admission ticket that the registrant selects for both themselves and their guests/additional attendees. For example, if the registrant wants to bring two guests to your event, they would select three tickets during checkout. When creating the ticket, set the "Limit per order" quantity to the total number of allowable guests/additional attendees plus one.
On the registration form, the first name, last name, and email will be collected from the primary registrant. You can further customize your form by adding additional form fields. When adding a field, you can indicate whether to collect the information from the primary registrant or not, and which tickets the field applies to.
In the example below, we've added the "First name" field and applied it to the "General Admission" ticket. This means that in addition to collecting the first name, last name, and email from the primary registrant, we will also collect the first name from each guest/attendee. Keep in mind that because the primary registrant is also registering for a General Admission ticket, they would fill out their first name in the "Contact Information" section, and within the ticket-specific section.
In this scenario, there is not a way to apply certain fields to only the guests/additional attendees, because the primary registrant is also registering for a "General Admission" ticket. However, you could add a custom field that allows the primary registrant to not answer for themselves. For example, you could add a "Relation to primary registrant" custom field, apply it to the General Admission ticket, and include an answer option such as "N/A - primary registrant". Therefore, when filling out ticket-level fields, the primary registrant would answer "N/A - primary registrant" for themselves and then choose the appropriate answer for each guest/attendee.
You can allow for guests to attend your event by creating a paid ticket for registrants and a free ticket for guests. Let your contacts know that with the purchase of a paid ticket, it includes "X" number of guests that they can bring. For example, you can create a ticket named "General Admission - Member" for $30 and another ticket named "General Admission - Guest" for free. Set the "Limit per order" quantity to 1 for the "General Admission - Member" ticket and to the allowable number of guests per registrant for the "General Admission - Guest" ticket.
When checking out, the registrant would select the "General Admission - Member" ticket for themselves and a "General Admission - Guest" ticket for each guest they are bringing. In the below example, the registrant is purchasing a ticket for themselves and three guests:
On the registration form, the first name, last name, and email will be collected from the primary registrant. You can further customize your form by adding additional form fields. When adding a field, you can indicate whether to collect the information from the primary registrant or not, and which tickets the field applies to.
In the example below, we've added the "First name" field and applied it to the "General Admission - Guest" ticket. This means that in addition to collecting the first name, last name, and email from the primary registrant, we will also collect the first name from each guest/attendee.
Let's say you'd also like to collect certain info from each guest/attendee, but not collect that info from the primary registrant. In the following example, we've added a custom field asking for the relation of the guest/attendee to the primary registrant. We have not applied it to the primary registrant and we have applied it to the "General Admission - Guest" ticket. This means that in addition to collecting the first name, last name, and email from the primary registrant, we will also collect the first name and "relation to primary registrant" from each guest/attendee.
Keep track of your primary registrants and additional attendees by utilizing the registrant list and the Attendee Report.
To see a list of your primary registrants, navigate to the "Registrants" section of the event dashboard. Here you can see the full name and email address of the primary registrant, as well as the number of tickets they registered for:
Next, to see the details of the additional guests/attendees, export and review the Attendee report. When you run the Attendee report it will display all ticket-specific information collected from your form.
For ticket set up options 1 and 3:
In options 1 and 3, we collected first name and "relation to primary registrant" from each "General Admission - Guest" ticket holder. So the report will look like this:
We know that Leigh is the primary registrant, and that Marsha and Chip are her guests.
For ticket set up option 2:
In option 2, we collected first name and "relation to primary registrant" from "General Admission" ticket holder. So the report will look like this:
Because we collected info from each "General Admission" ticket holder, and Leigh, our primary registrant, registered for that ticket type, she appears on the report, as well. And we know that Marsha and Chip are her guests.
Copyright © 2025 · All Rights Reserved · Constant Contact · Privacy Center