How the problem appears in a live venue
Proximity marketing is frequently discussed in terms of its potential, but its practical boundaries are determined by physics, operating system behaviour and human consent. Understanding these constraints early prevents wasted budgets and failed pilots. The limitations are not minor technical glitches; they are structural characteristics of how Bluetooth Low Energy (BLE), NFC and QR codes interact with physical spaces and mobile devices.
Signal Physics and Environmental Interference
BLE beacons operate in the 2.4 GHz spectrum, which is shared with Wi-Fi, Zigbee and various consumer devices. In a busy retail environment or a venue with dense Wi-Fi coverage, this shared spectrum causes interference that degrades signal stability. Furthermore, the 2.4 GHz frequency is heavily absorbed by water, meaning that dense crowds of visitors can significantly attenuate signals. A beacon deployment that performs reliably in an empty room after hours may behave erratically during a Saturday afternoon peak.
Radio signals also do not travel in neat, predictable circles. They reflect off metal racking, glass display cases and concrete pillars, creating multipath interference. A receiving device might detect a strong signal not because it is close to the beacon, but because it is standing in a spot where reflected signals converge. This makes precise, consistent indoor positioning difficult without extensive on-site calibration.
Operating System Restrictions
The hardware is only half the equation; the smartphone operating system controls what the app can actually do. Both iOS and Android have introduced increasingly strict background processing limits to preserve battery life. On iOS, background BLE scanning is heavily throttled, meaning a user walking past a beacon with their phone in their pocket might not trigger a notification until they open the app, by which point they have left the zone. Android behaviour varies significantly between manufacturers, with some aggressively killing background processes for apps that are not frequently used.
Web Bluetooth was intended to solve the app requirement by allowing websites to interact with beacons directly. In practice, Web Bluetooth requires a secure context (HTTPS), user gesture activation and explicit browser permissions. It remains unsupported on iOS Safari entirely, rendering it ineffective for a large portion of UK smartphone users.
The App and Consent Barrier
For beacon-based proximity marketing to function, the visitor must have the venue’s app installed, Bluetooth enabled, location permissions granted and, on modern operating systems, precise location access allowed. Each of these steps represents a point of friction where users drop off. If the app does not offer sufficient ongoing value beyond the proximity notifications, download and retention rates will be too low to justify the hardware investment.
Test likely causes in a sensible order
How these limitations manifest depends heavily on the specific physical environment and the operational goals of the venue.
Retail Environments
In supermarkets and large retail stores, the primary limitation is physical layout volatility. Promotional ends and stock displays move frequently. A beacon calibrated to trigger a notification for a specific product display becomes useless the moment the display is relocated, requiring a physical visit to move the beacon and update the backend campaign logic. Additionally, metal shelving units act as signal shields and reflectors. A beacon placed on a metal shelf may broadcast strongly down one aisle but be entirely undetectable on the opposite side.
Museums and Heritage Sites
Museums present a different set of challenges. Thick stone walls and historic building materials severely restrict BLE signal propagation, often necessitating a higher density of beacons than a modern, open-plan venue. Glass display cases can cause unpredictable reflections. In these settings, visitors also move slowly and spend time in close proximity to a single exhibit. If the system relies on dwell time to trigger content, it must be carefully tuned to avoid firing the same notification repeatedly, which requires sophisticated filtering logic on the app side.
Events and Temporary Venues
For conferences and exhibitions, the limitation is time and density. Deploying a permanent calibration is impossible when the venue layout changes daily. The sheer density of thousands of attendees in a conference hall creates a high-absorption environment for 2.4 GHz signals. Event organisers must also account for the fact that attendees are unlikely to download a dedicated app for a one or two-day event, making app-dependent beacon campaigns impractical unless integrated into a widely used event platform.
Confirming the fix and preventing recurrence
Most proximity marketing failures stem from treating the technology as a set-and-forget system rather than an operational infrastructure requiring ongoing management.
- Trusting spec sheet accuracy: Manufacturer-stated ranges assume an open field with no interference. In a real venue, a beacon rated for a 70-metre range may only achieve a reliable 15 metres. Always conduct an on-site RSSI survey before finalising placement.
- Ignoring battery behaviour in cold environments: Coin-cell batteries used in most beacons perform poorly in cold temperatures. A venue with poor heating, or an outdoor event in winter, will see significantly reduced battery life and potentially erratic transmit power.
- Deploying without a maintenance schedule: Beacons do not fail gracefully; they simply stop broadcasting when the battery dies. Without an asset register and a routine battery replacement schedule, silent beacons will create dead zones that go unnoticed until visitors complain or analytics show a sudden drop in zone entries.
- Over-notifying: Triggering a push notification every time a device enters a zone, even if the user is walking back and forth, causes rapid notification fatigue. The app logic must include cooldown periods and frequency caps.
- Neglecting the consent audit trail: Under UK GDPR and the Privacy and Electronic Communications Regulations (PECR), you must be able to demonstrate that a user actively consented to receive location-based marketing. Relying on a buried setting in the app profile is unlikely to satisfy this requirement.
Before committing to a deployment, verify three specific things. First, test the exact notification delivery speed from beacon trigger to lock screen appearance on both iOS and Android devices while the phones are locked and in pockets. Second, measure the signal consistency at peak occupancy versus empty rooms. Third, confirm that your content management system allows you to tie a specific campaign to a specific physical beacon identifier without requiring a developer to rewrite code. If any of these checks fail, the system will not perform reliably in live operation.
