Where the project begins to go wrong
Beacon placement is the point where a deployment plan meets physical reality. The specification sheet may list a transmit power and an advertising interval, but those numbers describe what the hardware does in free space. Once a beacon is fixed to a ceiling, clipped to a shelf edge or tucked behind a display case, its radio signal behaves differently in every location. Most placement mistakes stem from treating beacons as if the surrounding environment does not matter.
The core problem is that Bluetooth Low Energy signals at 2.4 GHz are absorbed, reflected and scattered by common building materials, fixtures and even the people moving through a space. The received signal strength indicator (RSSI) that a phone or gateway records is therefore a product of the beacon's output plus every obstruction and reflection between it and the receiver. When placement ignores these factors, the system either triggers notifications in the wrong zone or fails to trigger them at all.
Placement errors tend to fall into predictable categories: ignoring what is near the beacon, ignoring what is between the beacon and the visitor, ignoring how the space is actually used, and assuming that a layout drawn on a floor plan will translate directly to reliable radio behaviour. Recognising these categories makes it easier to spot problems before they affect visitors.
A structured path from symptom to cause
Retail environments
In a shop, beacons are often placed to define zones around product displays, entrances or till points. A frequent error is mounting a beacon directly above a heavily stocked shelf unit made of metal framing. The metal acts as a reflector and absorber, creating an uneven signal pattern: strong directly below, weak to the sides, and unpredictable in adjacent aisles. The result is that a customer standing one metre from the shelf may not receive a notification, while someone two aisles away occasionally does.
Another retail mistake is placing beacons at varying heights without accounting for the difference in RSSI readings that height creates. If one entrance beacon sits at 2.5 metres and another at 4 metres, the signal attenuation over the extra distance, combined with the angle to a phone typically held at waist or chest height, produces noticeably different trigger distances. Consistent mounting height across beacons performing the same function is a straightforward principle that is often overlooked during rushed installations.
Planning note: Numeric examples are not performance guarantees; verify the same settings and receiver mix in the intended venue.
Museums and galleries
Museum deployments frequently attach beacons to exhibit cases or walls to trigger audio or text content. Placing a beacon directly against a glass case can cause the signal to reflect back into the case rather than propagating into the visitor space. Mounting it a short distance away, even ten to fifteen centimetres, often produces a more predictable coverage pattern.
Temporary exhibitions create a particular risk. Beacons added for a short-term show may be positioned ad hoc by curatorial staff without reference to the permanent beacon grid. If the new beacons share identifiers or advertising channels with the permanent installation, a visitor's device may receive conflicting triggers. Even when identifiers differ, overlapping signal footprints from poorly sited temporary beacons can degrade the reliability of the permanent system.
Venues and corridors
In conference centres and similar venues, long corridors with smooth walls create a waveguide effect. A beacon placed at one end of a corridor can produce a surprisingly strong signal much further down the corridor than the same beacon would achieve in an open room. This leads to zone boundaries that do not match the physical landmarks visitors use to navigate, such as doorways or junctions. The practical consequence is a notification that appears to belong to the wrong room.
Mounting beacons on movable partitions, temporary stands or freestanding signage introduces a different class of problem. Once the physical object is relocated, the beacon's zone moves with it, but the digital map and zone definitions in the backend system remain unchanged. Unless the asset register and floor plan are updated at the same time, the mismatch persists silently until visitors report incorrect triggers.
Prevent the same failure at the next rollout
Mounting on or inside metal enclosures
Placing a beacon inside a metal housing, behind a metal panel or directly against a metal structural beam severely attenuates the signal. In some cases the beacon becomes effectively invisible to devices more than a metre away. If a metal mount is unavoidable, the beacon should be positioned so that its antenna faces an open aperture, and the resulting range should be measured on site rather than estimated from the specification sheet.
Ignoring footfall and occupancy patterns
A zone that works perfectly in an empty room may behave differently when filled with people. The human body contains a significant amount of water, which absorbs 2.4 GHz signals. In a dense crowd, the effective range of a beacon can drop noticeably. For deployments in busy retail spaces or event venues, testing during realistic occupancy levels, not just after hours, is essential.
Assuming symmetrical coverage
Beacon antennas are not perfectly omnidirectional. Most consumer and commercial beacons have a slightly directional pattern, with a null along one axis. If that null happens to point towards the primary visitor approach path, the beacon will appear weak or intermittent even at close range. Rotating the beacon ninety degrees on its mount can resolve the issue, but this is rarely checked unless someone walks the approach path with a scanning tool during installation.
Overlooking nearby Bluetooth sources
Other Bluetooth devices in the same frequency band increase the noise floor and can cause packet loss. Wi-Fi access points operating on 2.4 GHz channels, Bluetooth audio speakers, point-of-sale terminals and even staff handheld devices all contribute. In a dense RF environment, a beacon that performs reliably in isolation may drop packets frequently enough that trigger latency increases or notifications fail to arrive within the expected window.
Cable and conduit routing
Running power or data cables directly past a beacon, particularly if the cables are metallic or run inside steel conduit, can alter the local signal pattern. The effect is difficult to predict without measurement and is easy to miss during a visual inspection of the installation.
Key checks before considering placement complete
- Walk every expected visitor approach path with a BLE scanning app and record RSSI at the points where triggers should fire and at the points where they should not.
- Compare beacons performing the same function to confirm that their RSSI profiles at equivalent distances are reasonably consistent.
- Test with the space occupied at a typical level, not empty.
- Verify that no beacon is mounted with its antenna null pointing towards the primary visitor path.
- Check that temporary fixtures, seasonal displays or movable furniture have not been positioned in front of a beacon since the original installation.
- Confirm that the physical location of each beacon matches its recorded position in the asset register and floor plan.
- Identify any 2.4 GHz Wi-Fi access points, Bluetooth speakers or other RF sources within five metres and note whether they correlate with unreliable triggers.
Placement is not a one-time task. Spaces change, fixtures move and occupancy patterns shift with seasons and promotions. A deployment that worked when commissioned will drift unless someone periodically walks the zones and compares what the scanning tool reports against what the system expects. The mistakes described here are not exotic edge cases; they are the routine consequences of installing radio hardware without measuring what the radio actually does in its specific surroundings.
