From Visitor Moment to Physical Zone
A location zone is the physical area where a visitor's device should receive a particular notification. Defining that area on a floor plan is straightforward; making the real-world signal behaviour match that intention is where the work lies.
Bluetooth beacons broadcast a signal that attenuates with distance, but the attenuation is not uniform. Walls, shelving units, display cases, and the people standing between a beacon and a phone all affect the received signal strength indicator (RSSI). A zone that looks like a neat circle on a plan will, in practice, be an irregular shape that shifts as the environment changes. Stock levels in a retail unit, a temporary exhibition wall in a museum, or a crowd near a stage at an event all alter the signal path during normal operations.
Zone definition therefore starts with the physical space and its fixed features, but it cannot end there. You need to understand which features are permanent, which change on a predictable cycle, and which are entirely unpredictable. That distinction determines how reliably a zone will perform over time and how often you will need to revisit the boundaries.
the organisation should establish the channel-specific marketing and data-protection position before a zone can trigger a message. A clear user choice is usually the safest product design, but the legal analysis depends on the message, subscriber, data flow and any applicable exception
A further distinction worth establishing early is the difference between a beacon's maximum broadcast range and the usable notification zone. A beacon set to a high transmit power may be detectable at 30 metres in open air, but the RSSI values at that distance will be inconsistent and easily confused with readings from beacons in adjacent zones. Practical zones are almost always defined well inside the maximum detection range, using an RSSI threshold that provides a stable trigger rather than the outer edge of detectability.
Testing Boundaries in Real Spaces
Retail environments
In a shop, zones typically map to customer journey stages: entrance, category aisle, promotional end-cap, and till area. The entrance zone serves a different purpose from an aisle zone. At the entrance, the visitor is transitioning from outside to inside, and a welcome message or a summary of current offers can be relevant. In an aisle, the visitor is already browsing, so the notification needs to relate to the products immediately around them to feel useful rather than intrusive.
A common practical approach is to define the entrance zone with a generous buffer so the notification fires reliably as someone walks through the door, but to keep aisle zones tighter, sometimes using two beacons per zone to confirm that the device is genuinely in that aisle rather than picking up a signal from the next one over. Shelving units in retail environments are particularly effective at containing Bluetooth signals, which is an advantage for zone definition: a well-stocked aisle can act as a natural signal barrier, reducing bleed between zones.
Museums and galleries
Museum zones usually correspond to exhibits, rooms, or thematic sections. The challenge here is that exhibit density varies. A single large sculpture in an open room may need a broad zone, whereas a cluster of small artefacts in a case may require a narrow zone to avoid triggering the wrong audio or text content.
Temporary exhibitions add another layer. Walls, partitions, and display structures that were not present during the initial beacon deployment will change signal propagation. If the museum reconfigures spaces on a regular cycle, the zone definitions need to be treated as part of the exhibition installation process, not as a one-time setup. The person commissioning the exhibition fit-out should be aware that beacon placement and zone calibration are part of the physical infrastructure, not an afterthought once the displays are in place.
Events and venues
Event spaces present a different set of constraints. The infrastructure is temporary, the environment changes rapidly during build-up and breakdown, and peak-time crowd density can significantly affect signal behaviour. Zones at an event are often defined around functional areas: registration, main stage, breakout rooms, catering, and exits.
Because the deployment window is short, event zone definition tends to rely more on on-site testing and less on prolonged observation. A practical approach is to define zones conservatively during planning, then walk the venue with test devices during the build-up phase, adjusting RSSI thresholds and, if necessary, beacon positions before the doors open. The key check is whether a person standing in the intended zone receives the correct notification, and whether someone standing just outside it does not.
Zone overlap and buffer areas
Where two zones meet, there will be an area where a device could receive notifications from either zone depending on signal fluctuation. In some cases, this is acceptable: a transition zone between a museum's ancient Egypt gallery and its Roman gallery might trigger either set of content, and the visitor is contextually close enough to both. In other cases, overlap causes problems: two competing retail offers firing in quick succession will confuse the visitor.
Buffer areas, where no notification triggers, are an underused tool. A one-to-two-metre buffer between zones gives the system time to stabilise its RSSI readings and prevents rapid-fire notifications as someone walks along a boundary. The trade-off is physical space: in a small venue, buffers may not be practical, and the alternative is to design the notification logic so that receiving one notification suppresses others for a defined period.
Trigger Rules, Consent and Failure Modes
Assuming zones are circular
Floor-plan tools often draw zones as circles or rectangles, which can create a false mental model. In a real environment, a zone defined by a single beacon's RSSI threshold will be distorted by obstacles, reflections, and the presence of people. If the zone definition process begins and ends with drawing shapes on a plan, the deployed system will not behave as expected. The plan is a starting point for physical testing, not a substitute for it.
Defining zones without on-site measurement
Signal behaviour in one building does not predict signal behaviour in another, even if the floor plans look similar. Construction materials, ceiling height, furniture, and the number of active Bluetooth devices in the vicinity all differ. Zone definitions should be verified with the actual beacons, in the actual space, using the same device types that visitors will carry. If the target audience is likely to use a mix of Android and iOS devices, test with both, because Bluetooth scanning implementations differ between operating systems and can produce different RSSI readings for the same physical position.
Making zones too large for the message
If a notification is relevant only to someone standing in front of a specific product or exhibit, but the zone extends five metres in each direction, the message will reach people for whom it has no context. This erodes trust and increases the likelihood that visitors will disable notifications or revoke location permissions. The zone should be no larger than the area where the notification remains clearly relevant to the person receiving it.
Ignoring vertical signal spread
Bluetooth signals propagate in three dimensions. A beacon mounted on a ceiling to serve a ground-floor zone may also be detected on the floor above, particularly if the floor construction is lightweight. In multi-storey retail units or museum buildings, zone definition must account for vertical bleed. This can be mitigated by reducing transmit power, adjusting the RSSI threshold, or, in some cases, using physical barriers to contain the signal.
Not documenting zone boundaries and their rationale
When the person who defined the zones moves on, or when a new integrator takes over maintenance, the absence of documentation means the zones have to be reverse-engineered or redefined from scratch. Each zone should have a record that includes: the beacon or beacons serving it, the RSSI threshold used, the physical area it is intended to cover, any known environmental factors that affect it, and the date it was last verified on-site. This record is part of the broader installation documentation and should be treated as operational infrastructure, not a one-time design artefact.
Key checks before going live
- Walk every zone boundary with a test device and confirm that the notification triggers inside the zone and does not trigger immediately outside it.
- Test at different times of day if the environment changes, for example a retail space during quiet morning hours versus busy afternoon periods.
- Verify that overlapping zones behave as intended, with either clean handoff or an acceptable buffer.
- Confirm that the consent mechanism covers the level of location inference implied by the zone design.
- Check that zone documentation is complete enough for someone who was not involved in the original deployment to maintain and adjust the system.
Zone definition is an iterative process. The initial plan sets a starting point, on-site measurement reveals what the signals actually do, and adjustment brings the two into alignment. Treating it as a one-time configuration step rather than an ongoing operational task is the most common reason proximity notification projects underperform relative to expectations.
