FooEvents Custom Attendee Fields

Collecting a name and email address is rarely enough for an event. FooEvents Custom Attendee Fields adds extra questions to the attendee registration process, giving organisers a way to request information that varies from one event to the next. Clothing sizes, meal preferences, demographic details and waiver approval are all examples supplied by the developer. The plugin is built around FooEvents, so its value lies in extending an existing event registration workflow rather than replacing the event system itself.

What it adds

The central feature is a custom field builder for event registration forms. Fields can be added for the information an event needs, with support for text inputs, dropdowns, checkboxes and other field types. The vendor describes the field allowance as unlimited, which gives an organiser room to collect several categories of attendee information within one registration process.

This is a practical distinction from asking attendees to send extra details by email after purchasing or registering. The required information is requested at the point where the attendee signs up, keeping event records closer to the registration itself. It also gives the organiser a defined place to ask the same question consistently across registrations.

Useful field controls

The feature set covers more than simply adding blank text boxes. The main controls include:

• Text fields for open-ended answers such as sizes or other attendee details.
• Dropdowns for presenting a fixed set of choices, such as meal options.
• Checkboxes for confirmations and selections, including approval of a waiver.
• Required-field validation to prevent incomplete registration forms.
• Conditional logic that shows or hides fields according to earlier selections.
• CSV export for reviewing and retaining collected attendee data outside the registration screen.

Conditional logic is particularly relevant when different attendees need different questions. A meal selection can lead to a related dietary question, for example, while a general attendee can see a shorter path through the form. The supplied information does not define every available field type or rule, so organisers with unusually specialised forms should check those details before committing to a particular layout.

From form to records

Validation gives the organiser a way to mark important questions as required, while conditional fields keep irrelevant questions out of view. Together, those controls support forms that adapt to an attendee’s answers instead of presenting every possible question to everyone.

CSV export adds a useful hand-off after registration. Event teams can take the collected answers into a spreadsheet for planning meals, ordering clothing, sorting demographic information or checking waiver responses. The plugin also lists compatibility with translation plugins, which is relevant for events serving attendees in more than one language.

What to weigh

The first limitation is structural: this is an extension for a FooEvents-based event workflow, not a general-purpose form plugin. Sites that do not already use FooEvents will not get the same value from a tool designed to add attendee fields to that system.

The second trade-off comes from the breadth of the field model. Unlimited fields and conditional rules provide room for detailed registration, but they also make it easy to build a long or complicated form. Every additional question creates more information to review, export and maintain. A form that asks for meal choices, sizes, demographic details and consent in one sitting needs a clear structure, or the registration experience becomes harder for attendees to follow. The vendor copy also does not describe advanced reporting beyond CSV export, so the exported data remains the main stated route for deeper analysis.

Who it suits

FooEvents Custom Attendee Fields suits organisers whose events need more than basic contact details and whose questions change by event. It is a good fit for registrations involving catering, merchandise sizing, demographic information or consent checks. The strongest case is an existing FooEvents setup where the organiser wants structured attendee data, required answers and selective questions without maintaining a separate collection process.