AppSeptember 22, 2026 9 min read

Getting the right people to meet: what actually works at a trade show

At a trade show, what gets the right people to meet is neither luck nor a directory. It is a relevant suggestion at the right moment, a legitimate reason to walk up to someone, and the certainty that they are still on site. Everything else — walls of profiles, "connect" buttons, exhaustive lists — produces a lot of activity and very few meetings.

Why is open networking not enough?

Because a trade show is a search problem, not a volume problem. A thousand people in a hall, maybe twelve of whom actually matter to you. With no help, the day goes to whoever is most accessible: the person at your table, the booth near the entrance, whoever you met at the coffee break. That is why most attendee directories disappoint. They are accurate, complete, well built — and unusable. A list of a thousand profiles does not reduce uncertainty, it relocates it. The attendee scrolls for two minutes, closes it, and goes back to chance. The second reason is social. Even when the right profile has been identified, there is still a step to take: approaching a stranger with no pretext. That cost is real, and tools almost always underestimate it. Plenty of event apps solve the search problem and ignore the pretext problem. Meetings happen when both are solved.

What makes a matchmaking suggestion good?

Three inputs, and they are not equal. The first is declared: what the attendee says they are looking for. It is essential and insufficient, because it is filled in before the event, often quickly, sometimes by whoever handled the registration. Custom fields built for your industry beat a generic form: at an industrial trade show, the useful question is not "your job title" but "what are you here to source." The second is behavioral: what the attendee looks at, who they message, which meetings they accept. It is more honest than the first, and it sharpens hour by hour. The third is physical: who is within reach, right now. That is where the Smart Ruby badge comes in. It is a Bluetooth beacon worn on a lanyard, detected by the phones of other attendees, and it geolocates the other attendees to within a meter with no infrastructure to install in the venue. A relevant but distant suggestion does not turn into a meeting. A relevant and nearby suggestion does. The badge stays optional: an event works with or without it. What it changes is the nature of the suggestion, which goes from "you two should talk" to "you two should talk, and you can right now."

Why does a meeting challenge beat a "connect" button?

Because a connect button asks an attendee to carry the initiative alone, and most will not. A meeting challenge moves the responsibility: you are not walking up to a stranger, the event asked you to. The pretext is provided, and the awkwardness disappears. The effect is mechanical and visible on site. The most introverted attendees benefit the most, because the challenge gives them exactly what was missing: a legitimate, public, low-stakes reason. This is not an icebreaker gimmick. It is the answer to the one problem technology does not solve — the first sentence. Across 100+ events equipped, our setups have produced more than 12,000 accepted matchmaking connections (V1 export, December 2, 2021). "Accepted" is the operative word: these are not profile views, these are two people who said yes. A few principles that make the difference. A challenge has to be understandable in one sentence. It has to be doable in a few minutes, not require a scheduled meeting. It has to be specific to your event, or it reads like a team-building exercise imported from somewhere else. And it has to stay rare: five well-placed challenges in a day beat twenty.

What is check-in for, beyond the attendance sheet?

Check-in and check-out are the neglected part of event apps. They are also what makes everything else usable. First, they keep you from suggesting a meeting with someone who has left. That is the number one source of frustration at a trade show: a suggestion sent at 5:10 p.m. to an attendee who handed back their badge at 4:30. Check-out looks like a formality. It protects the credibility of the whole system. Second, they give you real attendance, room by room and session by session. The gap between registrations and actual check-ins is one of the most useful numbers an organizer can have, and one of the least examined. It tells you where you over-provisioned, which slot emptied the room, which speaker held their audience to the end. Third, they make the rest readable. A satisfaction survey without check-in data mixes the opinions of people who were there with those of people who were not. Cross-referenced with actual attendance, the same survey becomes a decision-making tool.

What does event data actually tell you?

Five signals are enough. You read them in the organizer dashboard and export them to Excel or PDF. App download rate — What it tells you: whether your community follows you. Everything else depends on it. — What you do with it: measure it before the event, not after. There is still time for a reminder by SMS and email. — Benchmark: at a SPIE seminar in 2018, 94% of attendees had downloaded the app; across our events equipped with badges, we measure roughly 85% download and usage (internal measurement, 2018). Accepted matchmaking connections — What it tells you: the one meeting metric that cannot be gamed — two people said yes. — What you do with it: compare it edition to edition, at constant format. The gap between registrations and check-ins — What it tells you: how reliable your forecasts are, room by room. — What you do with it: resize rooms, breaks, and catering for the next edition. Live questions that went unanswered — What they tell you: what your program failed to cover. — What you do with them: the table of contents for next year. The satisfaction survey, cross-referenced with check-in — What it tells you: what the people who were actually there thought. — What you do with it: retire the formats nobody defends. A word on what this data is not. These are not dashboard numbers to admire. Each one has to be able to trigger a specific decision, otherwise there is no point measuring it.

How do you know whether it worked?

By picking the metric before the event, and picking one. If your goal is internal cohesion, the metric is accepted matchmaking connections between people from different departments or sites. If your goal is commercial, it is meetings held between visitors and exhibitors. If your goal is club retention, it is the share of attendees who come back next edition. Those three goals are not measured by the same number, and trying to track all of them means tracking none. Two methodological precautions. Compare at constant format: a change of venue, duration, or audience invalidates the comparison. And be wary of activity metrics — profile views, messages sent, time in app. They go up easily and tell you nothing. An accepted connection is a fact. A profile view is an intention. The organizer finds these numbers in the organizer dashboard, with Excel and PDF exports, and a documented REST API for organizations that want to process them in their own tools.

What does not work

The failures are worth naming. The exhaustive directory with no hierarchy. A thousand profiles presented flat produce nothing. That is not a design problem, it is a quantity problem. The app announced the day before. Download rates are built in the two weeks beforehand, by SMS and email, with a clear reason to download. An app revealed at the registration desk arrives after the battle. Too many notifications. One relevant suggestion is a service. Five suggestions an hour are a nuisance, and the first casualty is the credibility of the next one. Badges without the app. This is the most expensive mistake. A proximity badge is detected by the phones of other attendees, so below a certain install rate it stops measuring anything useful. The badge amplifies existing adoption. It does not create it. And the most common one: counting on the venue’s connectivity. Convention center basements and saturated exhibition halls are the norm, not the exception. That is why full offline mode is not a checkbox: the agenda, the attendee list, messages, and meetings all have to stay available when the network drops.

Frequently asked questions

It combines three inputs: what the attendee says they are looking for, how they behave in the app, and physical proximity when the event is equipped with Smart Ruby badges. A suggestion is only useful if it is both relevant and reachable, which is why proximity changes a great deal.

It is an invitation in the app to go meet a given profile. Its value is not search, it is pretext: the attendee no longer has to carry the initiative of approaching a stranger alone. That is the most common reason meetings do not happen, and the one technology alone does not solve.

Check-in and check-out give you real attendance. They keep you from suggesting a meeting with someone who has already left, reveal the gap between registrations and actual presence room by room, and make satisfaction surveys interpretable by limiting them to the people who were actually there.

Five are enough: app download rate, accepted matchmaking connections, the gap between registrations and check-ins, live questions that went unanswered, and the satisfaction survey cross-referenced with check-in. All of them are available in the organizer dashboard and export to Excel or PDF.

No, they are optional. The app handles matchmaking, meeting challenges, messaging, meetings, and check-in without badges. The Smart Ruby badge adds proximity between attendees, accurate to within a meter, with no infrastructure to install in the venue. It amplifies existing adoption rather than replacing it.

All articles