Bluetooth beacons do not measure distance. They broadcast a radio signal at a configured power, and a receiving device estimates how far away the beacon might be based on the strength of that signal. That distinction matters because it underpins every practical decision about accuracy in a real deployment.

Technology specialists reviewing a floor plan during a venue site survey
Illustrative example of a site survey before equipment placement.

How Accurate Are Bluetooth Beacons?

There is no single accuracy figure that applies to Bluetooth beacons in the way a tape measure has a known tolerance. A beacon's perceived accuracy depends on the hardware, the receiving device, the physical environment and the method used to interpret the signal. Manufacturer specifications typically quote performance in open-air, line-of-sight conditions with a single receiver at a fixed height—conditions that rarely match a retail floor, museum gallery or event hall.

In practice, most deployments that rely on simple proximity detection—triggering a notification when a phone comes within range of a beacon—work reliably because they do not require precise distance. The system only needs to distinguish between "in range" and "out of range." Problems arise when a project expects beacons to deliver sub-metre positioning without the infrastructure, calibration and environmental control to support it.

If a supplier promises a specific accuracy figure, ask under what conditions it was measured, with which receiver hardware, and whether the claim is backed by a documented test in a space similar to yours. Without that context, the number has limited operational value.

Factors That Affect Proximity Accuracy

Several variables influence how accurately a receiving device can estimate its distance from a beacon. Some are within your control; others are inherent to the technology and the environment.

  • Transmit power: A beacon broadcasting at maximum power will be detected from further away, but the signal-to-noise ratio at any given distance changes, which can reduce the consistency of distance estimates at close range.
  • Advertising interval: More frequent broadcasts give the receiver more data points to average, smoothing out random fluctuations. Less frequent broadcasts save battery but introduce more variance between readings.
  • Receiver hardware: Different smartphone models use different Bluetooth antennas and chipsets. Two phones held at the same spot next to the same beacon can report noticeably different signal strengths. This variation is unavoidable and must be accounted for in any system that relies on precise thresholds.
  • Receiver orientation: The antenna in a phone is not omnidirectional. Holding the device in portrait versus landscape, or with the screen facing towards versus away from the beacon, changes the received signal strength.
  • Beacon firmware consistency: Some beacons drift in output power over time or between firmware updates. If accuracy matters, verify that your chosen hardware maintains consistent transmit power across units and over its service life.

These factors combine in ways that are difficult to predict without on-site measurement. A configuration that delivers consistent results in one corridor may behave differently in another that appears identical.

Accuracy Classes: Near, Immediate and Far

The iBeacon specification defines three proximity zones—immediate, near and far—as a way to categorise the estimated distance between a receiver and a beacon. These are not precise distance bands; they are rough classifications intended to support simple trigger logic.

  • Immediate: Typically interpreted as within a few centimetres. In practice, this zone is narrow and can be unreliable because signal strength at very close range is affected by antenna near-field effects and the exact position of the phone relative to the beacon.
  • Near: Roughly in the range of one to three metres. This is the most commonly used zone for triggering content or notifications, as it corresponds to a natural interaction distance—close enough to be looking at an exhibit or product display.
  • Far: Beyond the near threshold. The upper boundary is effectively the maximum detection range, which depends on transmit power and obstructions.

The thresholds between these zones are determined by the receiving operating system and are not directly configurable by the app developer in a standard iBeacon implementation. Different OS versions may shift the boundaries slightly. For this reason, zone-based triggers work best when the physical layout provides clear separation between beacons, rather than relying on sharp zone boundaries in a crowded space.

Protocols other than iBeacon may expose identifiers or telemetry without defining Apple-style proximity labels. In every case, the application remains responsible for interpreting signal measurements. Protocol choice does not remove the need for environmental testing, device comparison and conservative thresholds.

Walls, Furniture and People: How They Affect Bluetooth

Bluetooth Low Energy operates at 2.4 GHz, a frequency that is absorbed and reflected by common building materials and the human body. Understanding how specific physical elements affect the signal helps you set realistic expectations and plan placement accordingly.

Walls and partitions. A single internal stud wall with plasterboard will attenuate the signal by a modest amount, often reducing the effective range but not eliminating detection. A dense material such as brick, concrete or glass with metallic coatings can reduce the signal far more significantly. A beacon on one side of a thick brick wall may not be reliably detected on the other side at all, regardless of transmit power.

Metal surfaces. Metal reflects 2.4 GHz signals rather than absorbing them, which creates multipath effects—the receiver sees multiple copies of the same signal arriving at slightly different times. This can cause the reported signal strength to fluctuate rapidly, making distance estimates unstable. Shelving units, display cases and ceiling grids with metal components are common sources of this problem in retail and museum environments.

Furniture and fixtures. Wooden furniture has a relatively minor effect, but dense materials or large objects positioned between a beacon and the receiver will reduce signal strength. The effect is cumulative: a beacon signal passing through a partition, then past a large display case, will be weaker than one passing through either obstacle alone.

People. The human body contains a high proportion of water, and water absorbs 2.4 GHz radiation effectively. A crowded aisle or a person standing directly between a beacon and a phone can cause a noticeable drop in received signal strength. In a busy retail environment during peak hours, this effect alone can shift a phone from the "near" zone to the "far" zone without either the beacon or the phone moving.

These effects are not theoretical. They are predictable enough to plan around, but only if you measure them in your specific space rather than assuming a flat signal decay curve.

Calibrating Beacons for Your Environment

Calibration in this context means measuring the actual signal strength a receiving device reports at known distances from each beacon in its installed position, then using those measurements to set appropriate thresholds for your application. It is a manual, site-specific process—there is no universal calibration value that transfers between environments.

A practical calibration workflow involves the following steps:

  1. Install the beacon in its final position. Signal behaviour changes with mounting height, nearby surfaces and the presence of fixtures. Calibrating a beacon on a desk and then moving it to a ceiling mount invalidates the results.
  2. Choose a reference receiver. Use a representative smartphone or a dedicated Bluetooth scanner. If your system will serve a mix of devices, consider calibrating with a mid-range Android phone and a recent iPhone to understand the variance between platforms.
  3. Take measurements at defined distances. Record the received signal strength at 0.5 m, 1 m, 2 m, 3 m and so on, along the expected approach paths. Take multiple readings at each point and note the range and average.
  4. Identify the stable zones. Look for distances where the readings are consistent and where the variance between readings is small. These are the distances at which your triggers will be most reliable.
  5. Set thresholds with margin. If you need a trigger at roughly two metres, set the threshold based on your measurements at that distance, then add a margin to account for device variation and body absorption. A threshold set at the exact average reading will trigger for roughly half of your visitors and miss the other half.

Calibration should be repeated if anything in the environment changes significantly—new shelving, a rearranged layout, or a shift in the beacon's mounting position. It is also worth spot-checking calibrated beacons periodically, as firmware updates or battery voltage changes can subtly alter transmit power.

When to Use Trilateration vs Proximity Zones

Trilateration estimates a device's position by measuring its distance from three or more beacons and calculating the intersection point. Proximity zoning simply triggers an action when a device enters the detection range of a single beacon. The choice between them depends on what you actually need to achieve.

Proximity zones are the appropriate choice for most retail, museum and event use cases. If the goal is to display information about a specific exhibit when a visitor is nearby, or to send a promotion when a shopper enters a particular aisle, a single beacon per zone is simpler to install, calibrate and maintain. It is also more tolerant of signal variation because the system does not need to calculate a precise position—only whether the device is roughly in the right area.

Trilateration is worth considering when you need to track a device's path through a space, display a moving dot on a map, or distinguish between two closely spaced points that a single beacon cannot separate. However, trilateration introduces significant complexity:

  • It requires at least three beacons within range of the device at all times, which increases hardware count and placement constraints.
  • It is far more sensitive to signal inconsistency, because small errors in each distance estimate compound into a larger position error.
  • It typically requires filtering algorithms—such as Kalman filtering—to smooth the raw position estimates into something usable on a map.
  • It demands more rigorous calibration and more frequent maintenance, as a single misbehaving beacon can distort positions across a wide area.

In most indoor environments with walls, furniture and people, trilateration without additional positioning sources—such as Wi-Fi round-trip-time measurements or ultra-wideband anchors—rarely delivers the sub-metre accuracy that is often assumed. If a project requires that level of precision, Bluetooth beacons alone are unlikely to be sufficient, and a hybrid approach or a different technology should be evaluated early in the planning stage.

For the majority of deployments, starting with well-calibrated proximity zones and refining from there is the more practical path. If zone-based triggers meet the operational requirement, the added complexity of trilateration delivers cost and maintenance overhead without a corresponding benefit.