Define the event
What should happen, for whom, and how will success be measured?
Independent guidance on Bluetooth beacons, NFC, QR, indoor navigation, location-based experiences, privacy and day-to-day operation.
The right technology depends on user action, distance, app requirements, environment, cost and privacy — not which option looks most advanced.
Can be detected by a compatible app or system.
Intentional tap at very short range.
Intentional camera scan.
Zone events, indoor context, repeated deployments.
Touchpoints, exhibits, assets and controlled actions.
Low-cost access to web content or forms.
Hardware placement, batteries, calibration and monitoring.
Physical labels, placement and destination control.
Print quality, placement and link maintenance.
Distance estimates vary with the environment.
Very short range and device/user behaviour.
Easy to copy or replace; verify sensitive destinations.
Start with the visitor, staff member or customer journey. Then decide whether proximity technology improves it.
Routes, accessible experiences, exhibit context, content updates and on-site support.
RETAILZones, consent, message frequency, offer relevance and measurement.
EVENTSRapid deployment, changing maps, peak loads, signs and post-event removal.
OPERATIONSMounting, identification, battery records, inspection and replacement procedures.
TOUCHPOINTSLower-complexity ways to connect physical places and objects to digital actions.
PRIVACYTransparent purpose, minimum data, retention, deletion and access controls.
A pilot should answer a small number of measurable questions before hardware and operational complexity spread.
The hardware purchase is only one line. Mapping, mounting, calibration, monitoring and privacy continue after launch.
What should happen, for whom, and how will success be measured?
Walls, entrances, power, traffic, interference and access constraints.
Test representative devices, positions, power and real visitor flow.
Identifiers, locations, mounting, owners, firmware and battery dates.
Failures, drift, content changes, privacy requests and replacement cycles.
Define purpose, consent, data flow, retention and deletion before collecting location-related data. Do not treat a generic compliance statement as evidence that a deployment is appropriate.
Technical enough to reveal limits, practical enough to improve a deployment brief.
RSSI, walls, people, device differences, calibration and why “distance” should be expressed as a range and confidence level.
Read the accuracy guide →Objective, map, mounting, calibration and monitoring.
Hardware, installation, application, content, analytics and support.
Intervals, power, temperature, records and replacement.
Consent, context, quiet hours, frequency and measurement.
Accuracy is described with conditions and uncertainty.
A controlled test comes before a broad rollout.
Location and consent claims require current authoritative checking.
The site is not the former product, platform or client portfolio.