The physical conditions shaping the result
Bluetooth Low Energy beacons do not broadcast on a single frequency. Each advertisement packet is transmitted on three specific channels—37, 38 and 39—set at 2402 MHz, 2426 MHz and 2480 MHz respectively. These channels were chosen by the Bluetooth specification to sit in gaps between the most heavily used 2.4 GHz Wi-Fi channels, reducing the chance of direct interference from Wi-Fi access points. A receiving smartphone or gateway scans across all three channels, accepting the first copy of the packet it detects.
Congestion in this context means that multiple devices are trying to use the same advertising channels at the same time, causing packet collisions. When two advertisements overlap in time on the same channel, a receiver may fail to decode either one. The beacon does not know this has happened because advertising is a one-way, unacknowledged broadcast. From the beacon's perspective, it transmitted successfully. From the receiver's perspective, the beacon simply was not there.
This distinction matters because congestion does not reduce the beacon's signal strength or change its measured RSSI value. It reduces the probability that a given advertisement is received at all. In a quiet environment, a receiver might detect nearly every packet. In a congested one, it might detect only a fraction, which manifests as delayed zone entry events, missed notifications or erratic indoor-positioning jumps.
What Causes Congestion
The most obvious source is other beacons. A retail floor with eighty beacons in a relatively compact area will produce a steady stream of advertising traffic on channels 37, 38 and 39. But beacons are rarely the only devices involved. Visitors' phones are also advertising—Apple devices broadcast for AirDrop and Find My, Android devices broadcast for nearby sharing and location services, and wireless headphones and fitness trackers send their own advertisements. In a busy venue, the number of active BLE advertisers can far exceed the number of deployed beacons.
Wi-Fi is a secondary but relevant factor. Although BLE's three advertising channels avoid the centre frequencies of Wi-Fi channels 1, 6 and 11, Wi-Fi signals are wide and leak into adjacent spectrum. A strong Wi-Fi access point on channel 1 will raise the noise floor on BLE channel 37. If the venue's own Wi-Fi infrastructure uses channel 1 or 11, this overlap is predictable and can be assessed during planning.
Other sources include microwave ovens, certain models of LED lighting controllers and legacy Bluetooth audio devices that use wider bandwidth. In most commercial environments, however, the dominant congestion source is simply the aggregate of many BLE devices advertising simultaneously.
Control the variables you can control
Assessing the RF Environment Before Deployment
Before committing to a beacon density, scan the environment with a BLE sniffer or a dedicated scanning app on a smartphone. Record the number of distinct advertisers detected on each of the three channels over a representative period—typically at least ten minutes during expected peak traffic. If the environment already shows high advertising activity from visitor devices, the headroom for additional beacons is reduced.
Simultaneously, check which Wi-Fi channels are in use and at what power levels. If the venue's Wi-Fi uses channel 1 heavily, expect elevated noise on BLE channel 37. This does not rule out beacon deployment, but it means that channel will be less reliable than channels 38 or 39 for initial detection.
Dense Retail and Warehouse Deployments
In large retail spaces or warehouses where beacons are placed every few metres for aisle-level positioning, congestion is a genuine operational concern. The standard mitigation is to increase the advertising interval—sending packets less frequently. A beacon advertising at 100 ms intervals produces ten packets per second across three channels. The same beacon at 500 ms intervals produces two. In a deployment of two hundred beacons, the difference between these two settings is 2,000 packets per second versus 400, a substantial reduction in channel occupancy.
The trade-off, which is covered in detail in the neighbouring article on transmit power settings, is that longer intervals increase the time before a receiver first detects the beacon. For proximity-triggered notifications, a 500 ms interval may still be acceptable because a visitor approaching a display will be in range for several seconds. For real-time positioning, where updates need to be frequent, the interval requirements are tighter and congestion becomes harder to manage.
Museums and Exhibition Spaces
Museum deployments tend to use fewer beacons per square metre than retail or warehouse setups, often one per exhibit or zone. Congestion from the beacons themselves is usually low. The more variable factor is visitor density. A special exhibition opening with several hundred visitors, each carrying an active smartphone, can raise the advertising floor significantly compared to a quiet weekday morning. If the museum's wayfinding or audio guide system relies on rapid beacon detection, it is worth testing under both conditions rather than assuming a consistent RF environment.
Events and Temporary Installations
Event spaces present a particular challenge because the RF environment changes rapidly. During setup, the venue may be quiet and beacon detection reliable. Once attendees arrive with phones, headphones and other BLE devices, the channel occupancy can increase by an order of magnitude within minutes. For event wayfinding, a practical approach is to design the system to tolerate missed packets—using smoothing algorithms that require several consistent detections before triggering a zone change, rather than acting on a single packet.
Interpreting variation without false precision
Assuming More Beacons Always Improve Accuracy
Adding beacons to fix perceived accuracy problems can backfire if the root cause is congestion. If a receiver is already missing a significant proportion of packets due to channel collisions, adding more beacons increases the collision rate further. Before increasing beacon density, verify that existing beacons are being detected reliably. If they are not, the solution may involve reducing advertising intervals, adjusting placement or addressing Wi-Fi overlap rather than adding hardware.
Confusing Congestion with Poor Placement
Missed detections have several possible causes: the beacon is too far away, a wall or fixture is attenuating the signal, the transmit power is set too low, or congestion is causing packet loss. These produce similar symptoms—intermittent zone entries, delayed notifications—but require different remedies. A structured troubleshooting approach is to first check RSSI levels at the point where detection fails. If RSSI is strong but detection is still inconsistent, congestion is the more likely explanation.
Ignoring Wi-Fi Channel Planning
If the venue's facilities team controls the Wi-Fi access points, coordinate on channel selection. Using Wi-Fi channels 3, 4, 8 or 9—rather than 1, 6 or 11—can reduce overlap with BLE advertising channels. This is not always possible, particularly in managed office buildings or shopping centres where Wi-Fi is provided by a third party, but where coordination is feasible it is a low-cost mitigation.
Not Testing Under Load
A pilot conducted in an empty venue will not reveal congestion problems. Any meaningful pilot for a beacon system should include testing during periods of realistic visitor or device density. If that is not possible during the pilot phase, at minimum simulate load by having several phones actively advertising in the space while testing beacon detection reliability.
Overlooking Manufacturer Channel Options
Some beacon hardware allows advertising on a subset of the three channels—for example, using only channels 37 and 39 and skipping 38 if that channel is known to be noisy. This reduces total channel occupancy but also reduces the probability that a receiver scanning in a round-robin pattern will pick up the packet quickly. It is a useful option in specific interference scenarios but should be validated with measurement, not applied speculatively.
Key Checks Before Going Live
- Scan all three advertising channels during peak expected traffic and log the number of distinct advertisers and approximate packet rates.
- Confirm which Wi-Fi channels are active and at what power, noting any that overlap with BLE channels 37, 38 or 39.
- Measure packet detection rate at representative receiver positions—how many of the beacon's transmitted packets are actually received.
- Verify that missed detections are not being misattributed to placement or power issues by checking RSSI at the failure points.
- If channel skipping is available on the beacon hardware, test whether disabling a congested channel improves overall detection reliability or simply shifts the problem.
- Document the advertising interval settings and the rationale for them, so that future adjustments are made with reference to a known baseline.
