Events present a distinct set of conditions for proximity technology: the infrastructure is temporary, visitor density fluctuates sharply, and campaigns often need to be live for just a few days. Unlike permanent retail or museum installations, an event deployment must be planned, calibrated, activated and removed within a compressed timeline, frequently by a team that does not manage the venue day to day.
This guide covers the practical considerations specific to using Bluetooth beacons, NFC and QR codes at conferences, exhibitions and trade shows.
The visitor or operational moment to support
One of the stronger use cases for proximity at events is helping attendees find relevant sessions or connect with other delegates. A beacon placed outside a breakout room can trigger a notification with the session abstract, speaker details and a link to add the session to a personal schedule. In a networking context, beacons worn by delegates or placed at stands can feed an opt-in discovery feature within the event app, showing nearby attendees who have also consented to be visible.
The practical limitation here is the app requirement. For a beacon to push a session reminder or a networking prompt, the attendee must have downloaded the event app, granted location and notification permissions, and left Bluetooth enabled. At a typical UK trade show, app adoption rates vary considerably. If fewer than a quarter of attendees have the app active with the right permissions, the reach of any beacon-driven feature is inherently constrained.
NFC and QR offer an alternative path. A QR code on a session room door or a delegate badge can deliver the same information without requiring an app install, though it does require the visitor to take the deliberate step of scanning. NFC tags on lanyards or badges allow a quick tap-to-connect action, which works well for exchanging contact details between two people, but the organiser needs to supply the NFC reader hardware or rely on attendees' own phones having NFC enabled.
When planning networking or session features, the key questions are:
- What proportion of the audience is realistically going to have the event app installed with full permissions?
- Does the feature still deliver value if only a subset of attendees can use it?
- Is a passive beacon trigger actually better than a visible QR code that the attendee chooses to scan?
Sponsor Activation Through Proximity
Sponsors pay for visibility, and proximity technology offers a mechanism to extend that visibility beyond the physical stand. A beacon at a sponsor's stand can trigger a notification with a specific offer, a competition entry or a link to a product demo page. NFC tags on stand furniture allow visitors to tap and receive digital collateral rather than carrying printed brochures.
The trade-off is between subtlety and intrusiveness. A notification that arrives as someone walks past a stand can feel relevant if the content is genuinely tied to that moment — for example, a live demo starting in two minutes. A generic brand message pushed to everyone within a ten-metre radius is more likely to be dismissed and may contribute to the visitor disabling notifications entirely.
For sponsor activations, practical considerations include:
- Content specificity: The notification should relate to what is physically happening at that stand or in that zone, not a general brand advert.
- Frequency caps: A visitor who walks past the same stand four times in a day should not receive the same notification four times. The platform needs to enforce a per-device cap within a defined window.
- Sponsor agreements: The contract should specify what the sponsor is actually getting — number of beacons, guaranteed impressions, notification copy approval, and what happens if the attendee has not opted in. Overpromising reach without accounting for opt-in rates is a common source of friction.
- Fallback mechanisms: If the beacon notification does not fire because the app is not installed, what is the visible alternative? A well-placed QR code or NFC tag ensures the sponsor still has a touchpoint.
Temporary Campaign Setup and Teardown
Event proximity deployments differ from permanent installations in that the hardware is typically hired, the environment is unfamiliar until load-in, and the window for calibration is narrow. A conference organiser may have access to the hall for only 24 hours before doors open, during which time the beacons must be placed, powered on, verified and connected to the campaign platform.
Placement challenges at events
Exhibition halls are large, open spaces with high ceilings, temporary partition walls and a density of metallic structures from stand builds. These conditions affect Bluetooth signal propagation in ways that are difficult to predict from a floor plan alone. Temporary walls, particularly those with metal frames, can attenuate signals significantly. A beacon intended to cover a specific aisle may bleed into an adjacent sponsor's zone, or fail to reach the far side of a stand.
The practical approach is to treat the floor plan as a starting point, not a definitive guide. During setup, the installation team should walk the venue with a scanning app, checking RSSI values at the boundaries of each zone and adjusting beacon placement or transmit power accordingly. This on-site calibration step is frequently skipped when timelines are tight, and it is the most common cause of zones that are either too large or too small on the first day of the event.
Hardware logistics
For a multi-day event, battery life is usually not a concern — a standard beacon running at a moderate advertising interval will last well beyond a three-day conference. However, the logistics of tracking which beacon is where matter more when the hardware is hired and needs to be returned. Each unit should be labelled, logged in an asset register with its assigned zone and campaign, and checked off during teardown. Beacons left behind in stand furniture or packed into the wrong crate create inventory discrepancies and potential hire charges.
Teardown and data
When the event ends, the beacons are collected, the campaign is paused or ended in the platform, and the engagement data is exported. It is worth clarifying with the platform provider what happens to the data after the event: where it is stored, how long it is retained, and whether it is automatically deleted after a defined period. Under UK data protection guidance, location data collected for a specific event should not be retained indefinitely if there is no ongoing purpose.
Measuring Event Proximity Engagement
Measurement at events is complicated by the short duration and the fact that attendees are moving through multiple zones in quick succession. The metrics that matter depend on the campaign objective, but some common measures and their limitations include:
- Notification delivery rate: The number of notifications sent versus the number of eligible devices detected. This tells you about technical reach but nothing about whether the content was useful.
- Notification tap-through rate: The proportion of delivered notifications that the attendee actually opened. This is a stronger signal of relevance, though a low rate can also indicate poor timing or notification fatigue.
- Zone dwell time: How long a device was detected within a beacon zone. This can indicate interest in a stand or session, but it is an imprecise measure — a person standing near a zone boundary to take a phone call will register as dwell time without any engagement intent.
- NFC or QR scans: These are deliberate actions and therefore a more reliable indicator of interest than passive beacon detection. However, they only capture the visitors who chose to interact, not those who noticed the stand but did not scan.
- Post-event conversions: If the notification or scan led to a trackable action — a form submission, a brochure download, a meeting booking — this is the most meaningful metric, but it requires the campaign platform to be connected to whatever system captures that conversion.
A common mistake is reporting total beacon detections as "footfall" or "visitors". A single device moving through a zone may generate dozens of detections over a few minutes. Without deduplication — counting unique devices rather than raw detection events — the figures are misleading. Any reporting from the platform should be checked for whether it presents unique devices or raw pings.
For sponsor reporting, the practical question is what the sponsor was promised and whether the metrics actually support that claim. If a sponsor was told their stand would receive a certain number of "impressions", clarify whether that means unique devices or notification deliveries, and what proportion of attendees that represents relative to total event footfall. Setting realistic expectations at the contracting stage avoids difficult conversations when the post-event report arrives.
