How the Advertising Interval Works
Every Bluetooth Low Energy beacon broadcasts small data packets at a set rhythm. The gap between one packet and the next is the advertising interval, measured in milliseconds. This single parameter determines how quickly a passing smartphone or scanner notices the beacon, how reliably it does so, and how fast the beacon's battery drains. It is one of the most consequential settings in any deployment, yet it is frequently left at the factory default without consideration for the specific physical space.
typically a smartphone application, gateway or dedicated BLE scanner
This matters most when the visitor is moving. Someone walking briskly through a shop doorway may spend only two or three seconds in a beacon's detection zone. With a 1,000 ms interval, the beacon might broadcast twice during that window, and if either packet collides with interference or misses the phone's scan cycle, the visitor passes through undetected. Shorten the interval to 200 ms and the same passage now sees roughly ten to fifteen transmission opportunities, making a missed detection far less likely.
so a shorter interval normally increases energy use and reduces expected battery life. The exact relationship depends on the radio, firmware, payload, transmit power and sleep behaviour
It is also worth understanding that advertising interval does not act alone. The receiving device's scan interval and scan window—settings controlled by the operating system and, to a limited degree, the application—determine how often and for how long the phone listens. A beacon broadcasting every 100 ms will still be missed if the phone only scans for 30 ms every two seconds. In practice, iOS and Android manage background scanning differently, and neither gives the application full control. This is why real-world detection is always less predictable than a simple interval calculation suggests.
Matching the Interval to the Visitor Journey
Retail entrance detection
A shorter interval may be appropriate in these positions, but 100–300 ms should be treated only as an illustrative test range, not a universal setting
Museum exhibit zones
Visitors in a gallery typically spend thirty seconds to several minutes near a single exhibit. Here, an interval of 500 ms to 1,000 ms often proves sufficient. The visitor is stationary long enough that even with a longer gap between packets, detection is highly probable. The battery savings across dozens of beacons in a large museum can be substantial over a year-long cycle, reducing maintenance workload.
Event wayfinding and session tracking
Conference and exhibition environments combine fast movement in corridors with longer dwell in session rooms. Corridor beacons guiding foot traffic may need intervals in the 200 ms range, whilst beacons inside seminar rooms can comfortably sit at 700 ms or above. The complication at events is density: hundreds of devices scanning simultaneously in a confined space increase the chance of packet collisions, which a shorter interval can partially mitigate—though it cannot eliminate the problem entirely.
Asset and equipment location
When beacons are attached to movable assets in a warehouse or venue, the interval depends on how often location needs to be refreshed. If the requirement is simply to find a piece of equipment when requested, a long interval of 1,000 ms or more may be adequate because the scanning device can linger until it picks up the signal. If the system needs to log continuous movement along a corridor, a shorter interval becomes necessary, and the battery implications must be factored into the maintenance schedule.
Indoor navigation positioning
Navigation systems rely on detecting multiple beacons in quick succession to estimate position. Inconsistent detection—where one beacon in a cluster is missed—degrades the position fix and can cause the blue dot to jump. For navigation-critical beacons, intervals below 300 ms are common, and some deployments go as low as the hardware permits. This is one of the most demanding use cases for battery budgeting and justifies careful measurement before committing to a fleet-wide setting.
Detection and Battery Trade-offs
Leaving the factory default unchanged
Most beacons ship with an interval around 1,000 ms. That default suits a moderate-dwell use case but is rarely optimal for every position in a deployment. A common pattern is to install beacons, observe patchy detection, and assume a hardware or interference problem when the actual cause is simply an interval that is too long for the dwell time at that specific spot. The first check should always be whether the interval matches the physical context.
Confusing interval with transmit power
Advertising interval controls how often the beacon transmits. Transmit power controls how far the signal reaches. They are independent settings, but their effects can look similar: a weak, infrequent signal and a strong, rare signal can both produce unreliable detection. When troubleshooting missed detections, check both parameters rather than adjusting one in isolation. (Transmit power trade-offs are covered in the next guide in this series.)
Ignoring the receiving side
Background behaviour and permission requirements vary by operating-system version, application state and implementation. Test the exact target devices and permission states instead of assuming foreground results will carry into background use
Assuming linear battery impact
Halving the advertising interval does not precisely halve battery life. The beacon's microcontroller and radio have baseline power consumption independent of transmitting, and the radio's ramp-up and ramp-down phases consume fixed energy per transmission. In practice, moving from 1,000 ms to 500 ms might reduce battery life by slightly less than half, whilst moving from 200 ms to 100 ms can have a disproportionately larger effect because the radio spends a greater proportion of its time in active states. Manufacturer datasheets usually provide battery life estimates at specific interval and power settings—consult those rather than estimating from first principles.
Not measuring in the actual environment
Interference from Wi-Fi access points, other beacons, metal fixtures, and human bodies all affect whether a transmitted packet arrives at the receiver. An interval that works reliably in an empty room may fail in a crowded corridor at peak hours. The only robust approach is to set a candidate interval, deploy a small number of beacons, walk the space with test devices under realistic conditions, and review the detection logs. Adjust and repeat until the hit rate meets the operational requirement.
Key checks before finalising an interval setting
- Measure the typical dwell time at each beacon position for the expected visitor behaviour.
- Set the interval short enough that at least three to five transmission opportunities occur within that dwell time.
- Verify detection rates with the actual smartphone models, OS versions, and app permission states your visitors will use.
- Check the manufacturer's battery life estimate at the chosen interval and transmit power combination.
- Confirm that the chosen interval is within the hardware's supported range—some beacons have minimum intervals that are longer than you might assume.
- Document the interval setting per beacon or zone in your asset register so that future maintenance does not inadvertently reset devices to a different value.
Advertising interval is not a set-and-forget parameter. It ties directly to how reliably your system detects people and assets in a given physical context, and it dictates a significant portion of your ongoing battery replacement workload. Choosing it deliberately, testing it in situ, and recording the decision for each zone is a basic discipline that separates deployments that work from those that quietly underperform.
