The physical conditions shaping the result

When a beacon manufacturer quotes a range of up to 70 or 100 metres, that figure describes line-of-sight transmission in an open field with no obstructions, no competing radio signals and an ideal receiver. In a retail unit, museum gallery or conference hall, the usable range is almost always shorter, often considerably so. Understanding why requires separating two concepts that are frequently conflated: raw signal range and attenuation.

A technician mounting and testing a small wireless device near an entrance
Illustrative example of installation, identification and signal verification.

Planning note: Treat numeric examples as illustrative until the same configuration has been measured in the intended venue and operating conditions.

Signal range is the maximum distance over which a receiver can detect the beacon's broadcast at all. It is determined primarily by the beacon's transmit power setting and, to a lesser extent, by the receiver's antenna sensitivity. Most BLE beacons allow transmit power to be configured across several levels, typically from around -40 dBm up to +4 dBm. Lowering the power shrinks the bubble of detection; raising it expands the bubble.

Attenuation is the loss of signal strength as the radio wave travels through space and passes through materials. Free-space path loss alone reduces power with distance according to the inverse-square law. On top of that, every wall, shelf, display case, pillar and human body the signal passes through absorbs or reflects a portion of the energy. The cumulative effect is what turns a theoretical 70-metre range into a practical 10-metre one in a busy shop floor.

The metric you actually work with is RSSI (Received Signal Strength Indicator), expressed in negative decibels relative to a milliwatt. A value closer to zero means a stronger signal at the receiver. As distance increases and obstacles intervene, RSSI drops (becomes more negative). Because RSSI is the input your system uses to estimate proximity, anything that attenuates the signal also distorts that estimate unless you account for it through calibration.

A further complication is that RSSI readings are not stable. The same beacon, at the same distance, from the same phone, will produce a spread of values over successive advertising packets. This fluctuation comes from multipath interference (signals bouncing off surfaces and arriving out of phase), receiver-side noise and minor changes in device orientation. Any practical system must smooth or filter these readings rather than acting on a single packet.

A repeatable venue test

Material attenuation in real spaces

Different building materials attenuate BLE signals to different degrees. As a broad guide, a single layer of standard plasterboard on a timber stud might reduce RSSI by a few dB, whereas a brick or block wall can reduce it by considerably more. Glass with a metalised or low-emissivity coating causes more reflection and loss than plain glass. Metal racking, lift shafts, reinforced concrete and large water features (including fish tanks) are among the most disruptive elements you will encounter in commercial and cultural venues.

Human bodies also attenuate BLE, because we are largely water. A crowded aisle will produce noticeably lower and more erratic RSSI values than the same aisle when empty. This matters for queue-detection zones and high-traffic retail areas: the environment is not static, so the signal behaviour is not static either.

Using attenuation deliberately

Attenuation is not purely a problem. In many deployments, you want a beacon's detectable zone to stop at a specific point — at a doorway, at the edge of a display, or at the boundary between two exhibition rooms. Rather than reducing transmit power to a level that might be too weak to penetrate even light obstructions, you can sometimes use the natural attenuation of walls and fixtures to shape the zone. A beacon placed just inside a room may be reliably detected inside that room but not in the corridor beyond, because the wall provides enough attenuation to drop RSSI below your trigger threshold.

This approach works best when you have measured the actual attenuation of the specific wall at the frequencies and power levels you are using, rather than assuming a generic figure. It also requires that the zone on the other side of the wall does not need its own beacon at a similar power level, which could cause bleed-through in the opposite direction.

Environment-specific patterns

In museums and galleries, signal behaviour is dominated by display cases (often glass and metal), dense wall construction in older buildings and relatively low crowd density. A beacon mounted on a case may be detectable only a few metres away if the case contains significant metal, even at high transmit power. The upside is that the environment changes slowly, so once you have measured and calibrated, the behaviour tends to remain stable.

In retail, the challenges are movable shelving, changing stock levels and variable footfall. A zone that behaved consistently in January may shift in December when seasonal displays and crowds alter the RF landscape. Ranges need margin, and trigger thresholds need to tolerate some drift.

In warehouses, the dominant factor is metal racking and the goods stored on it. A beacon on a rack upright may have a clear line of sight along an aisle but be heavily attenuated through the rack itself. Ceiling-mounted beacons often perform more predictably than shelf-mounted ones in these environments, because the path down through the aisle is relatively unobstructed even when the racks are fully loaded.

Records and triggers for re-testing

Assuming stated range equals usable range

The single most common planning error is taking a manufacturer's maximum range figure and using it as the radius for zone design. If a beacon is rated to 70 metres and you place triggers at 15 metres, you might assume a comfortable margin. In practice, if that 15-metre path crosses a partition and a row of clothing rails, the signal may already be near or below your detection threshold. Always design zones around measured RSSI at the specific location, not around datasheet range.

Ignoring device variation

Two different smartphone models, held at the same spot, will often report different RSSI values for the same beacon. Antenna design, phone case material and the position of the antenna within the handset all play a part. If you calibrate using one device and then visitors arrive with a different model, your distance estimates and zone triggers may shift. Practical systems handle this by using wide enough thresholds and, where possible, by profiling multiple common devices during the pilot rather than relying on a single test phone.

Placing beacons near metal without testing

Mounting a beacon directly on a metal surface, or tucking it inside a metal fixture, can detune the antenna and dramatically reduce effective range — sometimes to the point where the beacon is only detectable within a metre or two. If a beacon must go on or near metal, use a spacer to create an air gap between the beacon's rear and the surface, and measure the actual RSSI at the intended detection distance before committing to the placement across the site.

Not accounting for environmental change

A calibration performed on a quiet Tuesday morning will not necessarily hold on a Saturday afternoon. If your use case involves triggering notifications at a precise zone boundary, test during representative conditions. For analytics use cases where you are measuring dwell times or broad zone transitions, some variation is tolerable, but you still need to understand the envelope of that variation so you can set sensible thresholds.

Key checks before scaling a deployment

  • Walk the space with a logging tool. Record RSSI at multiple points around each planned beacon position, not just at the ideal trigger spot. Note the minimum, maximum and typical values.
  • Test with more than one device. Include at least two different phone models from different manufacturers to gauge receiver variation.
  • Measure with obstructions in place. If shelving, displays or furniture will be present during operation, they should be in position during testing.
  • Check for co-channel interference. Use a BLE scanner to see how many other beacons and BLE devices are advertising in the same area. High device density raises the noise floor and can reduce effective range.
  • Verify at different times. If the venue experiences significant changes in occupancy, repeat key measurements during both quiet and busy periods.
  • Document the actual trigger threshold you choose and why. If you set a notification to fire at -75 dBm, record the reasoning (e.g., "measured -72 to -78 dBm at 3 metres with obstructions, using iPhone 14 and Samsung Galaxy S23") so that future adjustments have a baseline.

Signal range and attenuation are not theoretical concerns that resolve themselves once you purchase the hardware. They are the physical substrate on which every beacon-triggered notification, every zone transition and every dwell-time measurement depends. Measuring them properly during the pilot phase, and revisiting those measurements when the environment changes, is what separates a deployment that works reliably from one that produces inconsistent, unexplainable results.