Entrance Detection and Welcome Messages
Placing a beacon near a shop entrance lets a retailer's app detect when a known customer crosses the threshold. The signal itself is straightforward: the beacon broadcasts its identifier, the phone receives it, and the app checks whether the user has opted in to notifications. If the conditions are met, a welcome message is pushed.
The practical difficulty is deciding what that message should achieve. A generic "Welcome to [Store]" notification adds no value and trains customers to dismiss future alerts. Effective welcome messages tend to do one of three things: surface a relevant offer tied to the customer's purchase history, remind them of a loyalty balance or reward waiting to be used, or highlight something time-sensitive such as an event or limited stock in a specific department.
Placement at the entrance requires care. A beacon mounted directly inside the door frame may trigger only after the customer is several metres into the shop, while one placed outside on the street can fire before the person has decided to enter. Most deployments settle on a position just inside the vestibule or lobby area, then calibrate the transmit power and advertising interval so the detection zone extends roughly one to two metres past the physical entrance. This usually requires on-site measurement with the actual devices and a representative phone, because RSSI values shift with footfall density, metal shop fittings and seasonal changes in stock.
A common mistake is treating the entrance beacon as a simple on-off switch. In busy periods, multiple customers may cross the zone simultaneously, and the app needs logic to avoid sending duplicate welcomes within a short window. Setting a per-visit cooldown, typically tied to a session timer rather than a fixed number of minutes, prevents the same person receiving the message twice if they step out and back in to take a call.
Aisle and Zone-Based Offers
Retail spaces are naturally divided into departments, aisles and display areas, which makes zone-based offers an obvious application for beacons. Rather than broadcasting the same promotion across the entire shop floor, the system can present a wine discount when a customer lingers in the drinks aisle, or a skincare sample offer near the beauty counter.
Defining those zones on paper is easy; making them work reliably is not. Bluetooth signals do not respect the neat boundaries drawn on a floor plan. A beacon placed at the end of an aisle will also be detected in the perpendicular aisle, especially if shelving is low or the environment is open-plan. The realistic approach is to think in terms of proximity to a beacon rather than presence in a geometric zone. If the use case requires tight boundaries, additional beacons and trilateration logic can help, but this adds complexity and is still subject to the physical limitations of RSSI-based ranging.
Interference from the retail environment itself is a persistent factor. Metal shelving, refrigeration units, mirrored surfaces and dense product displays all attenuate and reflect Bluetooth signals differently depending on stock levels. A zone that works well when shelves are half-stocked may behave differently during a seasonal refill. Pilots should be run across different trading patterns, not just during a quiet midweek morning.
The content served in each zone needs to match the customer's immediate context. An offer for nappies triggered in the baby aisle is relevant; the same offer fired in the adjacent household cleaning aisle feels intrusive and suggests the system does not know where the person actually is. If the technology cannot reliably distinguish between two nearby aisles, it is better to serve a broader department-level message than to risk an obviously misplaced notification.
Loyalty Integration with Beacons
For retailers with an existing loyalty programme, beacons provide a way to bridge the gap between a customer's digital profile and their physical location in the shop. The most common integration points are: recognising the customer when they arrive, tailoring offers based on their tier or points balance, and logging visits or dwell time as part of a broader engagement score.
The technical integration typically involves the beacon platform passing the detected beacon identifier and a timestamp to the loyalty system via an API. The loyalty system then looks up the customer associated with that device and decides what, if anything, to send. This means the beacon infrastructure itself does not need to hold customer data, which simplifies privacy management, but it does require a reliable link between the two systems and clear error handling for cases where the loyalty service is slow to respond.
One practical limitation is that loyalty integration only works for customers who have both downloaded the app and logged into their loyalty account. In many UK retail contexts, that represents a minority of total footfall. Beacons should therefore be treated as a channel for deepening engagement with existing digital customers, not as a blanket solution for in-store personalisation.
When evaluating a beacon platform for loyalty integration, check whether it supports the loyalty system's existing identifier rather than requiring a separate user mapping. Some platforms insist on managing their own user database, which creates a synchronisation problem and can lead to mismatched opt-in states between the loyalty app and the beacon service.
Consent and Opt-In Strategies for Shoppers
A retail notification programme needs a documented lawful basis for any personal data processing, and the communication or device-access method may also fall within PECR. Consent is commonly used for promotional push notifications, but the correct analysis depends on the channel, purpose and relationship with the customer. Avoid pre-ticked boxes, bundled choices and vague wording, and check the current ICO guidance before launch.
The most effective opt-in strategies tie the permission request to a clear, immediate benefit. Asking for location and notification permissions at the point of app installation, before the customer has any reason to trust the service, typically yields low approval rates. A better approach is to defer the request until the customer is already engaging with a feature that needs it, such as viewing in-store offers or checking their loyalty points, and to explain precisely what they will receive in return.
Wording matters. "Allow us to send you relevant offers when you visit our shops" is more specific and honest than "Enable location services for a better experience." Some retailers also find it useful to show a preview of the kind of notification the customer will receive, so the permission request is concrete rather than abstract.
Preference management is an ongoing operational requirement. Customers should be able to change marketing and location choices without hunting through unrelated account pages. Withdrawal, objection and permission changes must propagate through the app, campaign platform and analytics pipeline; stopping a notification while continuing unnecessary individual-level tracking is not a complete opt-out.
Notification Frequency and Timing
Notification fatigue is the most reliable way to destroy a proximity marketing programme. Once a customer disables notifications or uninstalls the app, re-acquisition is expensive and often impossible. Frequency management is therefore not a nice-to-have but a core operational requirement.
A practical starting point is to set a maximum number of notifications per visit. For most retail environments, one to two contextual messages per trip is a reasonable ceiling, though this depends on shop size and dwell time. A large supermarket where a customer spends forty minutes can justify more touchpoints than a convenience store visit lasting five minutes. The key is that each notification should feel like a service, not an interruption.
Timing within the visit also affects perception. A welcome message on entry and a checkout-related prompt near the till are natural moments. Firing a promotion while the customer is actively browsing a different category feels disruptive. Some platforms support dwell-time triggers, where a notification is only sent after the customer has been in a zone for a defined period, which helps filter out pass-through traffic and targets people who are genuinely browsing.
Quiet hours and frequency caps across visits are worth implementing from the start. If a customer visits three times in a week, receiving the same welcome message each time quickly becomes annoying. Varying content, suppressing repeats within a rolling window, and reducing frequency for very frequent visitors all help maintain relevance. Monitoring opt-out rates and notification dismissal rates by frequency tier provides the data needed to tune these limits over time.
Measuring Retail Proximity Campaigns
Measurement in proximity marketing is less straightforward than in digital channels, because the physical environment introduces ambiguity. A notification was sent, but did the customer see it? They saw it, but did they act on it? They acted on it, but would they have bought the product anyway?
The metrics that can be measured directly include: notification delivery rate, notification open rate, and tap-through rate to a landing page or offer. These are useful for diagnosing technical problems and comparing message formats, but they do not prove commercial impact. A high open rate on a discount code means the message was relevant; it does not mean the discount drove incremental revenue.
To move closer to attribution, some retailers use redemption tracking, where a proximity-triggered offer carries a unique code that is scanned at the till. This provides a direct link between the notification and a transaction, though it still cannot prove the purchase would not have happened without the prompt. Lift studies, comparing behaviour between customers who received the notification and a comparable group who did not, offer stronger evidence but require a sufficiently large user base and careful experimental design.
Footfall and dwell-time analytics derived from beacon detections can provide context, such as whether a zone-based offer correlated with increased time spent in that department. However, these figures should be interpreted with caution. Beacon-detected footfall counts devices, not people; a customer carrying two Bluetooth-enabled devices will be counted twice, and visitors without Bluetooth enabled will not be counted at all. Changes in detected footfall may also reflect shifts in phone settings or operating-system behaviour rather than real changes in visitor numbers.
When setting up measurement, define the primary question before choosing the metric. If the goal is to test whether proximity offers drive incremental sales, redemption tracking and lift analysis are the relevant tools. If the goal is to understand whether the notification content is resonating, open and tap-through rates are sufficient. Mixing these levels of evidence without distinguishing between them leads to overclaiming and poor investment decisions.
