Skip to main content
Lead capture records who visited an exhibitor’s booth. A staff member opens the lead desk from their entry pass, enters a visitor’s badge code, and the visitor is recorded as a lead for the company — name, email, ticket type, and an optional note. The list is shared by the whole company. Leads belong to the exhibitor. They are not shown anywhere in the console, not even as a count. The organizer’s work is to put the prerequisites in place so the desk appears.

​
Prerequisites

  • The Exhibition module is enabled and the company exists as an exhibitor, pending or confirmed.
  • The staff member is on the company’s staff roster with a confirmed registration — typically by registering with the company’s badge code.
  • The event is published.
  • Visitors carry their badge code. When the event runs on-site check-in, the code is printed on their badge and shown on their entry pass. There is no camera scanning — the code is typed or pasted.
When any of these is missing, Lead capture does not appear on the staff member’s pass.

​
The lead desk

1

Open the desk

On the entry pass, a staff member of an exhibiting company sees Lead capture. Opening it asks for the email the pass was sent to, once per device — the same email check as every hosted page.
2

Capture a badge

Enter the badge code printed on the visitor’s badge, add a note if needed, and choose Capture. The result shows the visitor’s name, email, and ticket type, marked Captured — or Already on your list when a colleague recorded them earlier.
3

Read the list

Your leads lists every lead the company has captured at this event, newest first: name, email, ticket type, and note. Every staff member of the company sees the same list.

​
Rules to know

  • One lead per visitor per company. A repeat capture — by the same person or a colleague — is acknowledged, not duplicated. A note entered on a repeat capture replaces the earlier note. Capturing without a note leaves the earlier note in place.
  • Own staff are not leads. Capturing a badge that belongs to the company’s own roster is refused with “This badge belongs to your own staff.”
  • Only confirmed visitors can be captured, the same rule as check-in.
  • A badge code resolves within its own event only. A misspelt code, a code from another event, and a nonexistent code all answer “not valid”.
  • A lead carries name, email, and ticket type — nothing more. Form answers, orders, and stays are not included.
  • The organizer never sees leads. There is no console page, no export, and no count.
  • The trigger Captured as an exhibitor lead fires on the first capture only, about the visitor. For a follow-up email, see Automations.

Exhibitors

The company, its staff roster, and the badge code that fills it.

Hosted pages

The entry pass the lead desk opens from.

Badges

The visitor’s badge and the code printed on it.

Automations

Follow up on the captured-as-lead trigger.