Why aren’t badge scans and footfall enough to prove exhibition ROI?
By Donghui Qian (Milo)Updated 3 October 20263 min read
Short answer
Scans and footfall measure presence and proximity, not interest, fit, or pipeline. Treat them as reach: then separate consented leads, qualified conversations, and meetings held — and judge ROI against the promise you sold the exhibitor, not against a hall-wide total.
After a show, someone will ask whether the floor “worked.” The easiest numbers to pull — door counts, aisle cameras, badge scans at a stand — feel objective. They are also the numbers most likely to start a fight, because they look like ROI while answering a different question.
This guide is for organisers and exhibitor managers who need a report sponsors will renew on. Useful whether or not you scan with BagEvent.
Three things people conflate
| Number people quote | What it actually is | What it is not |
|---|---|---|
| Footfall / door count | Bodies that entered a space | Buyers, or people who saw your stand |
| Badge scans at a stand | Moments a badge was read near that stand | A conversation, a lead, or consent to follow up |
| Unique visitors | Different people recorded at least once | Qualified interest — repeats and prize-hunters inflate or distort it |
ROI for an exhibitor is closer to: did we meet people worth a next step, and can we prove it. Scans can support that story. They cannot be the whole story.
How scans lie — even when the hardware works
- Incentive traffic. Stamp trails and draws produce scans from people collecting proof, not demos. Count them; do not call them leads.
- Staff and neighbours. Organiser badges, neighbouring exhibitors, and cleaners get scanned by accident or habit.
- Double scans and device lag. The same person scanned twice is not two prospects. Unique people matter more than scan totals.
- No note, no question. A scan with nothing attached is a timestamp. Sales cannot prioritise it.
- Consent missing. A scan is not permission to email. Reporting “leads” that cannot be contacted is how renewals die in legal review.
A stack of numbers that can defend a renewal
Keep these on separate rows. Never add them into one “engagement score” you cannot explain in a sentence.
| Layer | Definition | Use it to answer |
|---|---|---|
| Reach | Unique people recorded at the stand or activation | “Did the audience pass us?” |
| Qualified stops | Scans with a rating, note, or answer to the stand’s own question | “Did anyone actually talk?” |
| Consented leads | People who agreed to share details with this exhibitor | “Can sales follow up?” |
| Meetings held | Booked conversations that happened (not just requested) | “Did we sit down with the right accounts?” |
| Post-show pipeline (exhibitor-owned) | Opportunities the exhibitor attributes after the show | True ROI — organiser can enable capture, not invent closed revenue |
Hall footfall belongs in the organiser’s operations report. It belongs in an exhibitor ROI slide only if you sold them “people in the building,” not “people at our stand.”
Agree the promise before you defend the number
Most scan arguments are contract arguments in disguise. Before the show:
- Write what “a lead” means in the package — scan only, scan + question, or consented export.
- Say whether stamp-trail scans count toward the package total.
- Name what the organiser does not control: stand staffing, whether reps scan, whether sales calls anyone.
- Pick the report format and the send-by date while both sides still remember the deal.
What to change on the floor if scans look “good” but sales is quiet
- If reach is high and qualified stops are low
- Traffic is real; the stop is not. Fix staffing, demo, or the incentive that fills the queue with collectors.
- If qualified stops are fine and consented leads are low
- You are talking without capturing permission. Fix the ask at the stand, not the scanner.
- If one aisle’s reach is a fraction of another’s
- Layout problem — see the booth-traffic guide. No CRM fix will move bodies into a dead corner.
- If meetings were booked but few happened
- Matchmaking or diary problem, not a scan problem.
A one-page exhibitor report that does not pretend
- Reach (unique) by day/hour — not raw scan count alone.
- Qualified stops and consented leads as separate lines.
- Meetings requested vs held, if you offered that.
- One sentence on what the organiser controlled vs what the stand controlled.
- No invented revenue. If the exhibitor shares pipeline later, that is their number with your capture underneath.
Frequently asked questions
They measure that a badge was read near a stand. That is reach (and sometimes a starting point for a lead). ROI needs consented follow-up data and, usually, the exhibitor’s own pipeline after the show. Reporting scans alone as ROI is how both sides lose trust.
Yes — for organiser operations and for packages that sold “audience in the hall.” It is weak evidence for a single stand’s performance. Prefer unique visitors at that stand, then qualified and consented layers.
Design incentives so the stamp or entry requires stand staff to engage, require a short question for a “qualified” count, and report incentive scans separately from conversation scans. Rotating codes beat static posters that get shared in group chats.
The numbers you defined in the package — typically reach, qualified stops, and consented leads — within a week. Not the full attendee list unless people agreed to share. See the sponsor reporting guide.
Read next
- Booth traffic: getting attendees to the standsFloor plan and incentives — how reach gets created.
- Sponsor and exhibitor reportingAgree the promise, then prove it.
- Matchmaking at a conferenceWhen the goal is meetings held, not scans.
- Software for exhibitions and trade showsVisitors, exhibitors and the floor on one platform.