Inputs, constraints and stopping rules
A proximity pilot succeeds or fails on the ground it covers and the people it includes. Selecting zones and segments is not a preliminary admin task; it determines whether your results will be meaningful enough to justify a wider rollout or too skewed to inform any decision.
The two choices are linked but distinct. A zone is a physical area where beacons, NFC tags or QR codes will operate. A segment is a group of visitors whose behaviour you will observe or interact with during the pilot. You can place hardware in a well-chosen zone but learn very little if the visitors passing through it do not match the audience you eventually want to reach at scale.
The purpose of a pilot is to expose real problems: signal behaviour in your specific building, visitor willingness to engage, staff workflows around the technology, and content relevance. That means the pilot zone needs to be representative enough to surface those problems, not so controlled that it hides them. A glass-fronted entrance atrium will produce different Bluetooth behaviour to a windowless stockroom, and neither may reflect what happens in a standard aisle.
Segment selection is equally practical. If your long-term plan targets families with children, a pilot that only captures data from weekday morning visitors—typically retirees or business travellers in many UK venues—will give you a false picture of engagement rates, notification acceptance and dwell times. The segment definition also ties directly to privacy obligations: the more tightly you define a group, the more likely you are to rely on data points that require explicit consent under UK GDPR and the Privacy and Electronic Communications Regulations (PECR).
Carry out the task without losing traceability
Choosing zones that test real conditions
In a retail environment, a common approach is to pilot in one department that has moderate footfall, a mix of fixture types and at least one physical obstruction such as a pillar or a partition. High-footfall entrance zones may seem attractive because they generate large data volumes quickly, but they often have atypical conditions: wide open spaces, high ceilings, heavy glass and constant door traffic. Results from an entrance zone rarely transfer cleanly to a confined footwear department.
Museums face a different set of constraints. A pilot zone in a high-traffic gallery may deliver plenty of signal readings, but if that gallery is a wide-open space with few exhibits, it will not test the accuracy challenges posed by dense display cases and narrow corridors. A more informative pilot might select a gallery with a mix of open sightlines and cluttered areas, even if footfall is lower, because it will reveal how the system copes with the conditions present across much of the building.
Event venues need to consider temporal variation as well as spatial factors. A conference room that is empty for most of the day then flooded with delegates for a single session does not allow continuous observation. For events, a useful pilot zone is one that experiences repeated cycles of arrival, dwell and departure—registration areas, catering zones or exhibition hall aisles—so you can observe the system across multiple occupancy states.
Defining segments without overreaching
The most robust segment definitions rely on observable or voluntarily provided characteristics: time of visit, ticket type, app installation status, opted-in marketing preference, or membership tier. These can be matched to proximity data without requiring facial recognition, Wi-Fi tracking or other intrusive methods that create significant compliance risk under current UK guidance.
For a museum pilot, segments might include weekday adult visitors, weekend family groups and pre-booked tour parties. Each group has different movement patterns, dwell behaviours and content needs. If your pilot only captures one segment, you will not know whether a notification strategy that works for adults also works for families—or whether it annoys them.
In retail, useful segments often include loyalty app holders versus non-app visitors, or shoppers who enter via a specific entrance versus others. The critical practical point is that you must be able to identify which segment a visitor belongs to without collecting more personal data than necessary. If segment membership requires scanning a loyalty card at the till, you will not be able to assign segment labels to proximity interactions that happen before that point.
Matching zones to segments
Some zones naturally filter for certain segments. A parent-and-child facility in a retail centre will predominantly capture family visitors. A premium department floor may predominantly capture higher-spending shoppers. This can be useful for targeted content testing, but it also means your pilot data for that zone cannot be generalised to the wider visitor population. If you need results that apply across segments, select at least one zone where multiple segments overlap.
Confirm the outcome before scaling
Picking the easiest zone rather than the most informative one
Operations teams sometimes select a zone because it is easy to access for installation, has convenient power sockets for monitoring equipment or is out of the way of customer-facing staff. These are legitimate logistical concerns, but if they dominate the selection, the pilot will test installation convenience rather than system performance. A zone that is slightly harder to access but physically representative of your wider estate will produce far more useful results.
Testing only one zone type
A single-zone pilot tells you whether the technology works in that specific room. It does not tell you whether it will work across your building. Wherever possible, select at least two zones with different physical characteristics: one open, one obstructed; one high-ceilinged, one low; one with heavy footfall, one with lighter traffic. This does not require doubling your hardware—most pilots can be staged sequentially—but it does require planning the zone selection upfront rather than treating the first room as the entire pilot.
Defining segments after the fact
Deciding which visitor groups to analyse after the pilot has run is a common temptation, but it leads to selective interpretation. If you do not plan segment definitions in advance, you will not have put the necessary consent mechanisms, data capture points or identification methods in place. Define your segments before the pilot begins, ensure your privacy notices cover the data required to assign visitors to those segments, and document the rationale for each segment choice.
Ignoring consent variation between segments
Different visitor segments have markedly different opt-in rates. Younger visitors and loyalty members may consent to location-based notifications at higher rates than older visitors or casual passers-by. If your pilot zone is dominated by a high-consent segment, your engagement metrics will look strong but will not reflect what happens when the system rolls out to a broader mix. Record consent rates by segment during the pilot so you can model the likely performance at scale.
Overlooking staff as a variable
In venues with floor staff—retail assistants, gallery attendants, event stewards—the pilot zone selection should account for staff presence and movement. Staff who carry Bluetooth-enabled devices or stand in fixed positions near beacons will generate signal readings that are not representative of visitor behaviour. Either exclude staff devices at the data level or select a zone where staff presence is consistent and can be factored into the analysis.
Key checks before finalising selection
- Does the zone include at least one physical characteristic (obstruction, narrow passage, reflective surface) that exists elsewhere in the building?
- Can you identify at least two distinct visitor segments within the zone without collecting additional personal data?
- Have you confirmed that your privacy notices and consent mechanisms cover the data needed to assign visitors to those segments?
- Is the zone accessible for installation and maintenance without requiring specialist access equipment that would not be available site-wide?
- Have you documented, before the pilot starts, why these zones and segments were chosen and what limitations they introduce?
- Does the selection allow you to distinguish between technology performance (signal reliability, accuracy) and content performance (notification relevance, engagement)?
Getting zone and segment selection right does not guarantee a successful pilot, but getting it wrong virtually guarantees misleading results. The time spent choosing representative physical spaces and clearly defined visitor groups is small compared with the cost of rolling out a system based on data that turned out to be unrepresentative.
