Exhibitor lead capture
Published
Event Tech Notes Exhibitor lead capture
Lead capture is a three-party transaction dressed up as a gadget rental. The attendee, the exhibitor, and the organizer each think the badge scan means something different, and the contracts rarely settle it.
The badge scan is the fundamental commercial gesture of the trade-show floor: attendee presents badge, exhibitor scans it, a record changes hands. Simple at the booth, and genuinely contested everywhere else, because three parties have claims on that record and only one of them was asked.
How the machinery works
Lead capture is usually sold by the registration or badging vendor as an exhibitor product: an app or rented device that decodes the badge and returns some portion of the attendee's registration record. Two architectures exist, and they differ in ways that matter. If the badge encodes only an ID and the scanner looks the record up from the registration database, the organizer controls exactly which fields exhibitors receive, and revoked or updated records stay current. If the badge encodes the data itself (a QR code that literally contains name, email, employer), then anyone with a camera captures everything in it, the organizer's field controls are theater, and third-party "free scanner" apps can harvest badges the licensed product was supposed to monetize. Ask your badging vendor which architecture you are buying; it determines whether your data promises are enforceable or decorative.
Scanner licensing is a revenue line: exhibitors pay per device, per app seat, or per bundle, typically priced by the vendor with a commission or markup in the event's favor. What drives exhibitor grumbling is not the fee but the value: what fields come back, whether qualifying notes and custom questions attach to the scan, and when they get the data. All of that is negotiated in your vendor contract, mostly by default, mostly without anyone reading it on the exhibitor's behalf.
Who owns the scanned data
The honest answer: it depends on three documents, and they are usually inconsistent. The attendee agreed to your privacy notice. The exhibitor signed a booth contract. The vendor's terms sit underneath both. If the privacy notice never mentioned that presenting a badge shares the attendee's record with the exhibitor, the whole chain is built on an assumption.
Settle it deliberately. The privacy notice should state plainly that allowing a badge scan shares named categories of data with that exhibitor, who then processes it for their own purposes under their own privacy obligations. The exhibitor contract should mirror this: the exhibitor becomes independently responsible for scanned data, may use it only per the disclosed purpose, and may not resell it. The vendor contract should state that the organizer, not the vendor, owns the aggregate scan data, and say what the vendor may do with it, which should be approximately nothing.
Consent, meanwhile, is behavioral as well as legal. An attendee holding out a badge for a demo queue understands the trade. An attendee whose badge was photographed from a lanyard while they ate lunch did not consent to anything. Where you land legally varies by jurisdiction; where you land reputationally does not.
Why rented scanners produce junk CSVs
Every sales team recognizes the post-show file: duplicates from double scans, test scans of the booth staff's own badges, fields misaligned because custom questions shifted the columns, qualifying notes in a free-text blob, and no indication of which conversation mattered. The mechanism is straightforward. The data was entered once, by the attendee, at registration, under whatever validation existed that day; the scan simply copies it, plus whatever the booth staff typed with their thumbs between conversations. Garbage flows downstream intact, and the rented scanner adds its own layer: unfamiliar hardware, returned at show close, with the export handled later by whoever collects the devices.
Exhibitors defend themselves by testing the export before the show opens (scan a staff badge, read the file), by insisting on same-day data access rather than a post-show file drop, and by writing qualifying questions into the scanner configuration instead of free text. Organizers defend the event by treating exhibitor data quality as their problem too: clean registration data and a sane export format are what your show is actually selling at the booth, and they are worth a line in your vendor RFP.