The practical problem behind the topic
Stakeholder reports for proximity campaigns sit in an awkward middle ground between technical operations and marketing outcomes. The data you are drawing on comes from physical infrastructure — beacons, NFC readers, QR scans — operating in environments where signal behaviour, consent rates and device variability all introduce noise. A report that presents these figures as clean, precise marketing metrics will mislead its audience and erode trust the moment someone asks a follow-up question.
Different stakeholders need different things from the same dataset. An operations manager wants to know whether beacons are broadcasting, batteries are holding and dead zones exist. A marketing director wants to know whether notifications triggered engagement and whether zones correlated with dwell time or conversion. A finance lead or board member wants a cost-justification narrative, not a technical log. A single report rarely serves all three well, and trying to do so usually means each audience gets a document that is partly irrelevant to them.
The starting point for any useful report is understanding what your data actually represents. A zone entry logged by a beacon does not mean a person stood in that zone looking at the associated display. It means a Bluetooth-enabled device with the relevant app installed and location services active passed through an area where the received signal strength indicator (RSSI) crossed a threshold you defined. The gap between that event and a meaningful human action is where most reporting errors originate.
Under UK data protection law, you can only report on data collected with a valid legal basis and appropriate consent. If your privacy notice covers campaign analytics but not individual movement profiling, your report must not drift into the latter. This is not a theoretical constraint — it shapes which metrics you can legitimately include and at what level of granularity.
From requirement to verifiable operation
Retail environments
In a retail setting, stakeholders typically want to understand whether proximity-triggered offers influenced behaviour. A practical report structure separates infrastructure health from campaign performance. The infrastructure section covers beacon uptime, battery status and any zones where signal dropouts were detected during the reporting period. The campaign section covers notification delivery counts, opt-in rates and, where a redemption mechanism exists, conversion from notification to sale.
The critical nuance is framing the denominator. If 12,000 people passed through the entrance zone but only 1,800 had the app installed, 920 had Bluetooth enabled and 410 had consented to notifications, then the realistic audience for a push notification is 410 — not 12,000. Reporting the delivery rate against the total footfall inflates the apparent reach and sets unrealistic expectations for future campaigns. State each filter stage explicitly so the stakeholder can see where the audience narrows.
Museums and galleries
Museum stakeholders are often less focused on conversion and more on visitor flow, exhibit engagement and accessibility. Reports here typically cover dwell time by zone, trigger rates for audio or content delivery, and route patterns through the space. The practical challenge is that dwell time inferred from beacon RSSI is an approximation. A visitor who stands near a sculpture for four minutes reading a label generates a similar signal pattern to someone who left their bag against the wall while visiting the café. Reports should flag zones where this kind of ambiguity is likely and, where possible, cross-reference beacon data with manual observation from a pilot period.
Events and temporary venues
Event reporting has a compressed timeline. Stakeholders need findings quickly, often within days of the event closing. The practical approach is to agree the report structure and key metrics before the event, not afterwards. Pre-agreed metrics might include zone capacity at peak times, flow between stages, QR scan rates at specific touchpoints and notification engagement per session. Because event infrastructure is temporary, the report should also cover whether beacons were removed and reconciled against the deployment record — missing hardware is a cost and a data integrity issue that stakeholders need to see.
Structuring the narrative
Regardless of venue type, a useful report follows a consistent internal logic. State the campaign objective first, then the methodology — what hardware was deployed, where, and with what configuration. Present the results with clear denominators and confidence qualifiers. Then address limitations explicitly: what the data cannot show, where sample sizes were small and where environmental factors may have skewed results. Stakeholders who see you acknowledge limitations are more likely to trust the figures you do present.
Handover, monitoring and improvement
Overclaiming precision
Stating that a visitor spent "4 minutes and 12 seconds" in a zone implies a level of measurement precision that RSSI-based proximity does not support. Report in bands — "approximately 3 to 5 minutes" — or clearly label precise figures as inferred from signal data, not directly observed. If a stakeholder asks why two reports show different dwell times for the same zone, the honest answer is usually that RSSI fluctuates with device orientation, body absorption and nearby movement.
Conflating delivery with engagement
A notification delivered to a device lock screen is not an engagement. Reporting "10,000 notifications sent" without also reporting how many were opened, acted on or dismissed creates a misleading impression of campaign impact. Where your analytics platform distinguishes between delivery, open and action, report all three. Where it does not, say so.
Ignoring consent bias
Visitors who opt in to location services and notifications are not representative of your total audience. They tend to be more engaged, more tech-comfortable and more likely to respond to prompts. If you report that "68% of visitors who received a notification visited the promoted zone," the stakeholder needs to understand that this is a subset of an already self-selected group, not a population-level finding.
Comparing proximity metrics to online metrics without context
A 4% click-through rate on a proximity notification might look weak next to a 12% email open rate, but the two are not comparable. Proximity notifications reach people in a physical context where attention is divided, timing is opportunistic and the trigger is based on approximate location. If you must make cross-channel comparisons, explain the methodological differences rather than presenting the numbers side by side as equivalent.
Omitting infrastructure performance
Stakeholders who only see campaign metrics without infrastructure context cannot assess whether poor results reflect weak creative or broken hardware. If three beacons in a key zone had depleted batteries for half the reporting period, that belongs in the report. It shifts the narrative from "the campaign underperformed" to "the campaign underperformed because the infrastructure was not maintained," which is a different management conversation.
Key checks before submitting any report
- Have you stated the consent rate and explained its effect on the data?
- Have you distinguished between delivered, opened and acted-upon notifications?
- Have you reported dwell times and zone entries with appropriate precision qualifiers?
- Have you noted any beacon failures, battery issues or signal interference during the period?
- Have you explained what the data cannot show, not just what it shows?
- Have you compared the period against a comparable baseline rather than an unrelated timeframe?
- Have you kept individual-level data out of the report unless specifically agreed under your privacy notice?
Running through these checks before distribution catches the majority of reporting errors that damage credibility. The goal is not to make the results look better or worse — it is to make sure the stakeholder understands what actually happened and what the numbers reliably represent.
