With custom fields, you can obtain additional information from your registrants.

Contents:

• Adding a New Custom Field
• Field Type and Field Label
• Display Settings
• Reporting Label and Saving Your Field
• A Note on Field Security

 

Adding a New Custom Field

To create a custom field for your auction, navigate to your your auction form control panel and select Event Custom Fields.

Next, select the Add New Field button. This displays the custom field creation interface.

 

Field Type and Field Label

First, select the Field Type from the drop-down menu.

You can choose to insert a Text Box where registrants can type in an answer to a question. When this is selected, a field appears that allows you to place a character limit on the text box.

Instead of a text box, you can elect to insert a Text Area to create a larger version of a text box. This is good for when registrants are going to need multiple lines to reply to a custom field question. When you select Text Area, you’ll also see the option to limit the maximum characters of the response.

Select the Checkbox option if you want this custom field to be required to complete the form.

The last option is Dropdown. This allows you to offer registrants a choice of several options in a drop-down menu. The default number of options is three.

If you wish to add additional options, click the Add Option button to the right above the first option.

To remove an option select the Remove Option Button, the red X, to the right of the option.

To reorganize your options, click the image of three lines to the left of the Option you want to move. Then drag the option up or down to reorder the choices.

Next, enter a Field Label. This is the name given to the custom field you want to add to the auction registration form.

 

Display Settings

Once you’ve selected the custom field type, determine the field's Display Settings.

If the field should display for every ticket purchased, select Per Ticket. For example, if you want to ask about meal choice for every attendee, you would want to select Per Ticket for that field.

If you'd like to ask a question once for each package purchased, regardless of the number of tickets in a package, select Per Package. 

If you select Per Transaction, the custom field question will only be asked once for the whole transaction, regardless of the number or combination of packages purchased by a single registrant.

If you select Per Ticket or Per Package, you can choose to associate the custom field question with a specific package. When you choose to Associate Field With Specific Package(s), only certain registration packages will be asked the question. For instance, if a certain registration package includes a shirt, selecting only the t-shirt registration option would be good if the custom field question was to select a shirt size.

To offer this question to all registration packages, click Select All.

If you'd rather apply the field only to specific packages, you can click Deselect All to clear the text box that reads, “This custom field will be applied to all packages.” When you click Select Package in the empty text box, you’ll see existing packages. Select which ones to include and then all but those selected will be excluded.

 

Reporting Label and Saving Your Field

Finally, enter the Reporting Label. This is the name that will appear in place of the Field Label as the column header for exported CSV files and in reporting.

When your settings for the custom field are set, select Add New Event Field to save changes. If you don’t need this custom field or don’t want to save changes, select Cancel to be returned to the Event Custom Fields menu.

Your saved custom fields will appear in the main Event Custom Fields table. The name and some details of the field are shared.

You can edit or delete a custom field at any time from the main Event Custom Fields listing.

 

A Note on Field Security

When creating a custom field, make sure you’re not asking for sensitive information, such as credit card numbers, Social Security numbers, Tax Payer IDs, protected health data, and so on.

Custom fields are not set up to securely collect and store sensitive data, and using them in this way is a violation of Qgiv’s Terms of Service. If you attempt to set up a custom field to collect sensitive information, you may see an error message that prevents the field’s creation.