| With online event registration systems, it's easy to | | | | asking for, then they may just make up data, which |
| add fields to your form, but before you start adding | | | | is worse than not having it at all. Special points on |
| them consider these points. | | | | forms selling tickets |
| Each field that you add to your form adds a little bit | | | | If you have an online ticket sales form, you should |
| more complexity. On their own, a few extra fields | | | | give some special consideration to asking people to |
| may not seem like much, but how easy your form | | | | submit the names of each ticket holder. For planning |
| appears to use at first glance is a factor in how | | | | purposes it would be great to know all of the names |
| many people actually complete it. | | | | of each ticket holder before the event, but for many |
| If your form appears long, cluttered or asks for | | | | events, the more important goal is to get the tickets |
| irrelevant details, people can be turned off and | | | | sold. |
| abandon their registration. Some may intend to come | | | | If you are expecting or hoping for people to buy |
| back when they have more time, but many never | | | | several tickets or a full table at a time, asking them |
| do. | | | | to enter all of the names could be seen as too much |
| When you're setting up your form, consider these | | | | trouble. In cases like this, people may not even know |
| points before adding a field: | | | | the names of the people using the tickets at the |
| | | | time of purchase and if names are entered, there is |
| 1. Do I really need this information? It might be nice | | | | no guarantee that those will be the people showing |
| to collect demographic details, such as how many | | | | up to the event since tickets may get passed |
| employees are in a company, but will knowing this | | | | around. |
| help you to put on a better event? | | | | In general, try to keep your forms as short as |
| 2. Am I really going to use this information? For | | | | possible, but also consider the people you are inviting, |
| example, you probably don't need to ask for the | | | | the type of event and how you expect people to |
| names of each ticket holder on a ticket sales form if | | | | use the form when deciding on the fields. |
| you aren't printing name badges for the event. | | | | If you have any questions about fields you are |
| 3. Will this field cause registrants to be concerned | | | | thinking about adding to your form, please contact us |
| about how you are using the data? For example, | | | | and we will be happy to discuss them with you. |
| asking for age or home phone number when it's a | | | | PS - A field that we recommend dropping from |
| business related event. | | | | forms is fax number. When is the last time you |
| 4. Will I get good data from this field? If people don't | | | | needed to fax people attending your events? |
| want to provide certain information that you are | | | | |