At a busy exhibition, a visitor may scan a badge to enter a demonstration, request a product sheet or speak to a representative. Those are different acts. If all three become the same CRM record, the team will send irrelevant follow-ups and overstate what the activation achieved.
Messe Düsseldorf's Scan2Lead service shows the mechanics that many exhibitors buy: badge or card capture, conversation notes, ratings, questionnaires and CRM export. The service description establishes what the software can record. It does not establish that every scanned person was interested, authorized every type of contact or became a sales opportunity.
Archv's activation measurement guide considers whether an experience met its business goal. This article focuses on the operational moment when one visitor interaction becomes a specific, usable handoff to a person who can respond.
Give each action its own meaning
First define a participation event: the visitor tried the installation. That can be useful for operations and aggregate analysis, but it does not need to create a sales record. A capture means an identifier reached the approved collection system. A qualified follow-up means the visitor expressed a relevant need, a suitable route of contact is recorded, and the receiving team has enough context to continue. The organization should set its own eligibility and privacy rules before the event.
For example, a product-comparison booth might offer three endings: leave anonymously, email the comparison, or request a conversation about a specified product. A badge scan may speed up an opted-in request; it should not blur the difference between those endings. The visible prompt needs to tell visitors what will happen when they scan or submit a form. Review the actual event organizer's data-sharing terms and your own privacy requirements with the responsible team; this is an operational design question, not a legal conclusion from a generic blog post.
Specify the record before the event opens
This illustrative field map is a design example, not a record of an Archv event:
| Field | Why the receiving team needs it | Acceptance check |
|---|---|---|
| Source event and station | Tells the team where the request arose. | A test record names the correct event and booth station. |
| Visitor's selected product or question | Gives the representative a reason to respond. | A staff member can read the visitor's choice without decoding internal event codes. |
| Requested next step | Distinguishes “send information” from “arrange a meeting.” | The CRM task matches the visitor's chosen action. |
| Contact channel and permission state | Prevents an assumed contact route. | The recorded channel and timestamp match what the visitor saw and chose. |
| Staff note and owner | Preserves useful context from a conversation. | One named team receives the task; empty notes do not invent interest. |
Decide which fields are required, which are optional and which should never be copied into CRM. If the organizer supplies badge data, confirm the actual fields and transfer rights in its current agreement. Do not promise a field that the organizer cannot provide. A QR or NFC form may collect a different set of details; the same handoff test still applies.
Rehearse the exceptions, not just the happy scan
Test a visitor who declines follow-up, a visitor whose badge scan fails, a conversation with two product interests, a duplicate scan, and an offline station that uploads later. The operator needs a truthful fallback: for example, show the information on-screen or offer a clearly labeled manual request. Do not quietly create a sales task from an anonymous play session.
After a few pilot records, ask the receiving team to read them without the booth team explaining them. Can they tell who requested what, which item to send, which language to use and when to act? If not, adjust the interface labels or field mapping. A technically successful export is only a transfer of data; its quality is tested by whether the next person can deliver the promised response.
Report the stages separately
Count station participation, explicit contact requests, records with enough context to act, and completed follow-up as separate numbers. Explain the counting window and how duplicates are handled. This makes a modest, credible result more useful than a large scan total with no path to the buyer's question. The difference is particularly important when an entertaining installation attracts people who were never looking to buy.