Event Lead Capture
Choose what you ask
Contact fields, qualifier questions, conditional logic.
Each booth decides what it asks. Open the event, find the booth, and choose Capture fields.
Everything here lives inside Event Lead Capture — you don't need the Forms module, and booth questions never appear alongside your forms.
The contact five
A new booth starts with name, email, phone, company and job title. These are special: they're mapped to the lead's own columns, so they show up as proper fields in the inbox and get their own columns in your CSV export.
The saves to dropdown next to a field is what controls that mapping. Leave a question unmapped and its answer is stored as a custom answer instead — still exported, just in its own column.
Question types
| Type | Good for |
|---|---|
| Short text / Paragraph | Names, free-text notes |
| Email / Phone | Contact details, validated on submit |
| Number / Date | Budget, headcount, install date |
| Dropdown / Radio | One choice from a list |
| Multi-select | "Which products interest you?" |
| Checkbox | A single yes/no |
| Star rating (1–5) | Rep's gut feel on the lead |
| Scale (0–10) | NPS-style questions |
| Consent | Opt-in wording you need on record |
| Section heading | Breaking a longer form into parts |
Keep it short. A visitor standing at your stand will finish four or five questions; they will abandon fifteen. Ask what you need to route the lead, and save the rest for follow-up.
Scoring your qualifiers
If your plan includes lead scoring, each question gets a score box. Put a weight on the answers that predict a good lead and every submission scores itself.
- On a rating or scale question the weight is multiplied by the answer — weight 4 on a 5-star rating contributes 20.
- On any other type it's a flat score for having answered.
- On multi-select it's multiplied by how many options they picked.
A "when are you buying?" question weighted 8 will sort a ready buyer to the top of the inbox without anyone tagging them by hand.
Conditional questions
A question can be set to appear only when an earlier answer matches — for example, ask "which platform do you run?" only when someone picked Platform / DevOps as their role.
Hidden questions are never required and are not stored, so a conditional branch can't block a submission the visitor never saw.
Editing safely
- Reorder by dragging the handle on the left.
- Rename a question at any time — existing answers stay attached.
- Removing a question hides it from the capture page but keeps answers already collected, so past exports stay complete.
- A question's type can't be changed after it's created. Answers are stored against it, and switching type would silently invalidate them. Remove it and add a new one instead.