Skip to content

Lead Forms & Surveys

A lead capture form is the structured data captured alongside each scan. The form's questions are how sponsors qualify a participant: their level of interest, follow-up category, role, or anything else the sponsor wants to know.

This article focuses on the design side: what questions to include and how to think about lead qualification.

Forms exist per workflow, not per Event

Each lead capture form is tied to a specific Activity and a specific group of Collectors. An Event with several sponsors typically has several lead capture forms — one per sponsor, each with its own questions.

Two forms can ask different questions even when they capture leads from the same pool of participants. The questions reflect the sponsor's own qualification needs.

Common lead capture questions

Question What it asks Why it's useful
Interest level "How interested are you in our product?" (Hot / Warm / Cold) Triages follow-up priority
Role / title "What's your role?" (single choice) Helps sponsors route the lead to the right salesperson
Use case "What problem are you trying to solve?" Provides context for follow-up
Follow-up preference "How should we follow up?" (Email / Call / Demo / None) Respects participant preference
Free-form notes "Notes" (comment field) Captures anything the Collector wants to remember

Aim for five or fewer questions per form. Lead capture happens in a few seconds at a booth; long forms slow throughput and frustrate everyone.

Question types

Lead capture forms support the same question types Eventene offers elsewhere:

  • Single-choice (radio)
  • Multiple-choice (checkboxes)
  • Text (short answer)
  • Comment (longer free-form)
  • Yes/No
  • Rank choice (where useful)

For the general question model, see Question Types & Advanced Settings.

Tagging captured leads

A lead capture form can include a question whose responses categorize the lead for follow-up. Common patterns:

  • A "Follow-up Priority" single-choice question with values that map to a CRM
  • A "Topic" question that identifies which product line the participant is interested in
  • A "Hand-off" question that names the team or person who should pick up the lead

Captured responses appear alongside each lead in Track / Individual. When organizers share lead data with sponsors, the categorization helps sponsors filter and route follow-up. A dedicated lead-export feature is on the roadmap; today the handoff is manual.

Mapping lead responses to existing data

If a sponsor wants lead responses to persist beyond this Event — for example, marking that the participant is "Interested in Product X" in your Main Group — you can configure the form question to link to a Custom Field on the participant's Main Group profile.

This applies the same data-linking model used for registration Survey Questions. The participant's record carries forward across future Events. See What is a Group? for the persistent-people model.

Designing for Collector speed

A few practical tips:

  • Put the most important question first
  • Use single-choice over comment fields when you can
  • Avoid required questions that are hard to answer at a booth ("Annual budget?")
  • Make follow-up categories explicit choices rather than free text
  • Save "long" questions for post-Event surveys, not lead capture

If a sponsor insists on a long form, consider splitting it: capture only the essentials at the booth, then send a follow-up survey by email after the Event.

Privacy expectations

A lead capture form records data that the participant may not be able to see directly. Be deliberate:

  • Avoid questions that capture sensitive information without the participant's awareness
  • Be transparent with participants about why their badge is being scanned
  • Coordinate with sponsors on how the captured data will be used afterward

For Events with formal privacy requirements (GDPR, similar), ensure both the questions asked and the downstream use comply.

See Also