When creating an event ticket, an admin must make a choice. Should the ticket require the attendee name or should the field be optional?
AE Tip™: Once you have started registering people for an event, we highly recommend that you don't switch from the attendee required to attendee not required. Technically, this is doable, but your reporting will suffer for it.
To ensure that your association has the best data, you will want to require an answer for the attendee. When it is likely that an attendee will be registering him or herself, this is an easy choice. Everyone knows his or her own name... I hope. :-)
Attendee Not Required
When there is a good chance that one person will be registering lots of people, you might want to consider not requiring attendee names. In many cases, the person doing the registration doesn't know exactly who will be attending. In this case, we believe that you're better off having no data than fake data. At least it's easier to spot. And who wants to force their member to type "n/a" or "I don't know" into 30 ticket spots only for your staff to have to replace it later?
The clear downside to not requiring attendee names at the time the form is filled out is that you very well could end up staring at an attendee roster with missing names. Perhaps that's why you're reading this article. If you are faced with this, you will want to look to the purchaser.
AE Tip™: If you don't require an attendee name, make sure to restrict the purchase of the ticket to Logged-In Members. If you do this, we recommend that you bring lots of blank name badge stickers to the event.