Registrants and Ticket Holders - What’s the Difference?
The first step to collecting custom information during your event’s registration is understanding who you want to collect the information from: Registrants or Ticket Holders. This article will help you to identify who the appropriate PheedLoop stakeholder is based on your unique registration characteristics.
Contents
- What is a Registrant?
- What is a Ticket Holder?
- Examples of Registrant/Ticket Holder Relationships
- Common questions to ask Registrants and Ticket Holders
- Conclusion
What is a Registrant?
A Registrant is the individual who is completing the registration order and processing payment. For events utilizing tickets, the Registrant can purchase tickets for themselves and/or for others when group registration is enabled.
What is a Ticket Holder?
A Ticket Holder is any individual who has either completed the registration process themselves or has been registered by someone else and possesses at least one Ticket as a result. As such, they are also individuals who are attending your event.
Once a Registration Order is completed, Attendee Profiles are automatically created for each Ticket Holder in the Event Dashboard.
Examples of Registrant/Ticket Holder Relationships
To better understand the relationship between registrants and ticket holders, we will go over some common scenarios during event registration.
| Scenario 1 | If you accessed the Registration process and purchased a Ticket for yourself, you would be both the Registrant and a Ticket Holder. |
| Scenario 2 | If you accessed the Registration process and purchased a Ticket for your friend, you would be the Registrant and your friend would be a Ticket Holder. |
| Scenario 3 | If you accessed the Registration process and purchased a Ticket for both yourself and your friend, you would be the Registrant and a Ticket Holder, and your friend would also be a Ticket Holder. |
Common questions to ask Registrants and Ticket Holders
Another important feature of PheedLoop’s registration process is the ability to ask questions to Registrants and Ticket Holders. To fufill this requirement, many events embed questions into the registration process for Registrants and Ticket Holders to answer.
Here are a few examples of common questions that may be asked to each stakeholder:
Registrants
- Payment processing questions: Since the Registrant is the individual who processes payment, you may need to ask the Registrant to answer a payment processing question or check a box that they agree to your event’s terms and conditions.
Ticket Holders
- Meal preferences: Since meal preferences are individual, you may want to collect meal preference information from each Ticket Holder at your event. In this scenario, we recommend including Dietary Restrictions as a fillable field from the Category settings.
- Consent information: If you are sharing an Attendee list with Sponsors post-event, you will likely want to collect this consent from each Ticket Holder at your event. In this scenario, we recommend creating a ticket form.
Conclusion
After reviewing this article you should have a better understanding of how Registrants and Ticket Holders are defined in PheedLoop. You should also have an idea of the types of custom information that is commonly collected from each stakeholder.