Badge Scanning: What Happens to Every Scan

Trade show halls have famously bad connectivity, and a booth cannot stop working while it waits for a signal. Survtapp is built for that: scanning is designed around the assumption that the network is not there. This article explains exactly what happens to a badge scan from the moment an exhibitor points a phone at it, so you know what your exhibitors can rely on.

A scan never waits for the network

When an exhibitor scans a badge, the lead is recorded on the device immediately. The star rating and the notes they type afterwards are saved on the device too. Nothing about that moment depends on having a signal — the exhibitor scans, scores, adds a note, and moves on to the next visitor.

The device syncs those captured leads to Survtapp as soon as it has a connection, whether that is a minute later on the hall wifi or that evening back at the hotel. Until the sync happens, the lead is already safely on the device.

What the badge itself contains

A Survtapp badge QR code contains one thing: a long, random, meaningless code. It carries no name, no email, no company — nothing an outsider could read by photographing a badge. Turning that code into an actual person is done by our servers, against your attendee list, at the moment the lead syncs.

This is also how exhibitor privacy works. An exhibitor sees an attendee’s contact details only for the people they personally scanned — scanning is what grants access. They never receive a copy of your attendee list, and they cannot look anyone up who has not visited their booth.

Scans of things that were never Survtapp badges

Booth staff scan whatever is put in front of them. Sometimes that is another show’s badge, a loyalty card, a poster QR code, or a badge from an event that has nothing to do with you. Those scans reach our servers and match no attendee on your list.

Where it can, the app catches those at the booth instead of afterwards. While an exhibitor’s device is online it quietly downloads a checklist of your event’s valid badges — scrambled, so it is a list of fingerprints rather than a list of people, and it contains no names, no emails and no company details. If a scan is taken with no signal and the device holds a complete, recent copy of that checklist, an unrecognised code is refused there and then and no lead is created. If the copy is incomplete or has gone stale, the app captures the scan anyway and lets our servers decide — deliberately, because refusing a genuine attendee who registered that morning would be far worse than accepting a scan we discard later.

When that happens the capture is deliberately discarded rather than kept. Nothing is stored against your event, and the app clears it from the device so it stops showing as an unresolved error. This is a deliberate choice: an exhibitor’s lead list should contain leads, not a growing pile of scans of things that were never badges — and a record with no attendee behind it can never become a lead, no matter how many times it is retried.

A real badge is never discarded

The rule above applies only to codes that match no attendee in your account. A scan of a genuine badge from your event is never thrown away — including the cases that catch other systems out.

• A lead scanned on the last afternoon of the show and synced that evening, or the next day, or the following week, is accepted. What matters is when the scan happened, not when the phone found a signal.
• A lead captured by an exhibitor whose booth access you have since switched off is kept, not deleted.
• A lead whose event you have already closed is kept.
• A lead the device cannot yet get confirmation for stays on the device and is retried, rather than being cleared.

To make late syncs verifiable, give your event a start and end date. Survtapp accepts a late-arriving lead when the scan itself happened inside those dates — which is what makes “scanned at 5pm, synced at 9pm” work without opening a loophole for scans taken after your show ended. If an event has no end date there is no window to check a late scan against, so the lead is held rather than accepted; adding the end date, or re-opening the event, lets it sync.

Duplicates and re-syncs

Scanning the same person twice at the same booth does not create a second lead, and it does not consume a second lead credit. A repeat scan simply brings the existing lead up to date — which is how a rating or a note added minutes after the scan reaches you at all, since it is entered after the badge was read.

What this means for you as an organizer

• Exhibitors can work a full day with no connectivity and lose nothing.
• Their lead lists stay clean — no phantom rows from mis-scans.
• Genuine leads survive a closed event, a revoked booth, and a week-late sync.
• Set your event’s start and end dates, and keep your attendee list uploaded before the doors open.