Skip to main content

Measuring the Business ROI of Guest WiFi and Location Analytics

This guide provides a technical and operational framework for measuring the business ROI of guest WiFi and location analytics. It details how to calculate value from hardware investments through dwell time uplift, operational efficiency, and first-party data capture across retail, hospitality, and public venues. IT managers, network architects, CTOs, and venue operations directors will find concrete measurement frameworks, real-world case studies, and compliance guidance to justify and maximise their WiFi investment.

📖 10 min read📝 2,284 words🔧 2 worked examples4 practice questions📚 10 key definitions

Listen to this guide

View podcast transcript
Measuring the Business ROI of Guest WiFi and Location Analytics. A Purple Platform Briefing. Approximately 10 minutes. INTRODUCTION AND CONTEXT - approximately 1 minute Welcome to the Purple Platform Briefing. I am your host, and today we are tackling a question that lands on the desk of almost every IT director and venue operations manager I speak to: how do you actually measure the return on investment of your guest WiFi? Not in theory. Not with a spreadsheet that assumes everything goes perfectly. In practice, with real numbers, real integration points, and a clear line of sight from the hardware you have already deployed to the revenue and operational value it can generate. This is a question that matters this quarter, not next year. Budgets are being set, infrastructure refresh cycles are being planned, and the IT team is being asked to justify spend that the business has historically treated as a cost of doing business. Over the next ten minutes, we will cover the technical mechanics of how value is generated from a guest WiFi deployment, the specific metrics that carry decision weight, two concrete implementation scenarios from hospitality and retail, the compliance shape you need to get right, and a clear set of next steps. Let us get into it. TECHNICAL DEEP-DIVE - approximately 5 minutes Let us start with the data model, because this is where most organisations have a gap in their thinking. A modern guest WiFi deployment generates two fundamentally different types of data. The first is presence data. The second is engagement data. They answer different questions, they run under different legal bases, and they drive different types of business value. If you conflate them, you will end up with a measurement framework that does not hold up under scrutiny. Presence analytics is what happens before a user connects to anything. When a mobile device enters your venue with its WiFi radio active, it broadcasts probe requests. These are the device asking the network: is there a network I know nearby? Every access point within range picks up that probe request. It contains the device's MAC address, which is a unique hardware identifier, and it contains signal strength data. By triangulating the signal strength across multiple access points, the analytics platform can estimate the physical location of the device. This is the foundation of footfall tracking and dwell time calculation. It is anonymous. It does not require the user to have done anything. And it is happening right now in your venue, whether you are capturing the data or not. Now, here is the complication that every serious analytics deployment has had to address since 2020. Since iOS 14 and Android 10, mobile devices use randomised MAC addresses for probe requests. The device no longer broadcasts a stable, unique identifier. It rotates through temporary addresses. If your analytics platform does not account for this, your visitor counts are wrong. Typically, they are overstated by a significant margin. Purple addresses this through statistical correction models calibrated against camera ground truth, maintaining accuracy within three to seven percent. If you are evaluating a platform and they cannot explain their MAC randomisation correction methodology, that is a red flag. Engagement analytics begins when a user connects to the guest WiFi network through a captive portal. The captive portal is the authentication gateway. It is also the primary mechanism for capturing first-party data. When a user authenticates, they transition from an anonymous device to an identified visitor profile. That profile is the core driver of marketing return on investment. The six metrics that carry the most decision weight are: footfall, which is the count of unique visitors in a defined zone over a time window; dwell time, which is the median and distribution of time spent in a zone per visit; return visit rate, which is the share of visitors who came back within a defined period; zone transitions, which show how visitors move between areas; new versus returning split; and capture rate, which is the percentage of detected devices that authenticate through the portal. Capture rate is particularly important because it is the bridge between your anonymous presence data and your identified engagement data. Industry benchmarks put capture rate at between fifteen and forty percent, depending on portal design and the incentive you offer. If you are sitting below fifteen percent, your portal flow needs attention. Let us talk about the architecture that underpins this. Purple operates as a cloud overlay. It integrates with your existing hardware from Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, and Fortinet. You do not need to replace your access points. You configure them to direct authentication traffic to the Purple cloud. The analytics engine processes the probe request data and session data, applies the MAC randomisation correction, and surfaces the results through a dashboard with sub-sixty-second freshness. The data then flows out via standard REST APIs or webhooks into your CRM, your point-of-sale system, or your business intelligence platform. This is where the ROI calculation becomes concrete. You are not just looking at a dashboard. You are correlating dwell time data with transaction values, measuring the conversion rate of email campaigns sent to WiFi-acquired contacts, and tracking the lifetime value of the customer cohort that first engaged with your brand through the captive portal. Harrods is a useful reference point here. By marketing to customers acquired through their guest WiFi network, they achieved a fifty-seven times return on investment from that specific cohort. That is not a theoretical number. It is the result of having a clean, consented, first-party data asset and a marketing automation workflow that could act on it. IMPLEMENTATION RECOMMENDATIONS AND PITFALLS - approximately 2 minutes Let me give you the three decisions that most directly determine whether your deployment delivers measurable value. First: access point placement for analytics, not just coverage. A network designed purely for connectivity will not give you the spatial resolution needed for zone-level analytics. You need overlapping coverage with access points positioned to create triangulation opportunities. The rule of thumb is one access point per one hundred and fifty to two hundred square metres in open-plan environments. Place access points on zone boundaries, not just in the centre of rooms. This is the single most common reason why analytics deployments underperform expectations. Second: the captive portal conversion rate. Your portal is your conversion engine. Keep the login flow to three steps or fewer. Ask for the minimum viable data. If you need an email address, ask for that and nothing else on the first visit. Use a tool like Purple Verify to validate the address at the point of capture, so you are not building a CRM full of invalid data. If you are deploying in a hospitality context, consider offering the premium bandwidth tier as a perk for loyalty program members. This drives sign-ups and gives you a direct revenue line from the WiFi investment. Third: integration with operational systems. WiFi analytics data sitting in a portal that nobody checks does not generate return on investment. The deployments that deliver value are the ones where the analytics outputs feed directly into operational workflows. Staffing schedules aligned to footfall patterns. Marketing campaigns triggered by visit frequency. Zone occupancy data feeding into digital signage. The integration layer is where most deployments stall, because it requires coordination between IT, marketing, and operations. Prioritise this work early. The most common pitfall I see is treating the captive portal as a compliance checkbox rather than a data asset. The portal is where you build your first-party database. Every visitor who authenticates is a potential long-term customer relationship. Design the portal experience with that in mind. RAPID-FIRE QUESTIONS AND ANSWERS - approximately 1 minute Can I measure return on investment if I do not have a point-of-sale integration? Yes. Start with CRM database growth and email campaign performance. These are measurable without a POS integration and give you a baseline ROI figure. How long until I see measurable results? Most hospitality and retail clients see measurable return on investment within six months. The first ninety days are typically about data collection and baseline establishment. The second ninety days are where the operational and marketing value starts to show. Do I need to replace my existing hardware? No. Purple is hardware-agnostic. It integrates with the access points you already have. What about GDPR? Your captive portal must obtain explicit consent for marketing communications. Presence analytics, which is anonymous, runs under legitimate interest with a completed Data Protection Impact Assessment and venue signage. Purple provides the templates and signage assets for both. SUMMARY AND NEXT STEPS - approximately 1 minute To bring this together: your guest WiFi infrastructure is already generating data. The question is whether you have the platform in place to capture it, structure it, and act on it. The return on investment of guest WiFi is not a single number. It is a combination of direct revenue from tiered bandwidth, operational savings from footfall-aligned staffing, and the long-term value of the first-party data asset you build through the captive portal. The three things to do this quarter: audit your current access point placement against analytics density requirements; review your captive portal conversion rate and simplify the flow if it is below twenty percent; and identify the one operational workflow where WiFi analytics data would have the most immediate impact. Purple runs across eighty thousand live venues, has processed four hundred and forty million logins in 2024, and has captured twenty-nine billion data points. The platform is ISO 27001 certified, GDPR and CCPA compliant, and B Corp certified. If you want to explore what a deployment looks like for your specific environment, the details are at purple dot ai. Thanks for listening.

header_image.png

Executive summary

Most organisations deploy guest WiFi as a cost of doing business - an expected amenity, a line item on the IT budget, and a source of support tickets. This perspective misses a fundamental shift in network capabilities. A modern WiFi deployment is a high-resolution sensor network that captures first-party data and spatial analytics at scale.

Purple operates across 80,000+ live venues, has processed 440 million logins in 2024, and has captured 29 billion data points. The platform runs as a cloud overlay on existing hardware from Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, and Fortinet. This guide details how to measure the ROI of that investment - moving beyond theoretical models to concrete frameworks for calculating value through dwell time uplift, CRM database growth, operational efficiency, and direct revenue from tiered access. Whether you manage a hotel group, a retail estate, or a public-sector facility, the measurement principles are the same.

Technical deep-dive: the mechanics of measurement

To measure ROI, you must first understand how the data is generated. The process relies on two distinct modes of data capture: presence analytics and engagement analytics. Conflating them produces a measurement framework that will not survive scrutiny.

Presence analytics

Presence analytics is what happens before a user connects to anything. When a mobile device enters your venue with its WiFi radio active, it broadcasts probe requests - the device asking the network whether a known network is nearby. Every access point within range detects that probe request. It contains the device's MAC address, a unique hardware identifier, and signal strength data expressed as RSSI (Received Signal Strength Indicator).

By triangulating the RSSI across multiple access points, the analytics platform estimates the physical location of the device. This is the foundation of footfall tracking and dwell time calculation. It is anonymous, requires no user action, and is happening in your venue right now whether you are capturing the data or not.

Here is the complication every serious analytics deployment has had to address since 2020. Since iOS 14 and Android 10, mobile devices use randomised MAC addresses for probe requests. The device no longer broadcasts a stable identifier - it rotates through temporary addresses. If your analytics platform does not correct for this, your visitor counts are wrong. Purple applies statistical correction models calibrated against camera ground truth, maintaining accuracy within ±3-7% (Purple platform data). If you are evaluating a platform and they cannot explain their MAC randomisation correction methodology, that is a red flag.

analytics_data_flow.png

Engagement analytics

Engagement analytics begins when a user connects to the guest WiFi network via a captive portal. The captive portal is the authentication gateway and the primary mechanism for capturing first-party data. When a user authenticates - whether through Microsoft Entra ID, Google Workspace, a social login, or an email form - they transition from an anonymous device to an identified visitor profile.

That identified profile is the core driver of marketing ROI. It links physical presence to digital identity. You can track the visit frequency of specific cohorts, measure the conversion rate of marketing campaigns, and integrate the data directly into your CRM. This is the data that Harrods used to achieve a 57x ROI by marketing to customers acquired through their guest WiFi network.

The six metrics that carry decision weight

WiFi analytics platforms can surface dozens of derived metrics. Six of them carry almost all the decision weight for ROI measurement.

Metric What it measures Primary use case
Footfall Unique visitors in a defined zone per time window Baseline venue volume, like-for-like comparison
Dwell time Median and distribution of time-in-zone per visit Layout optimisation, staffing, conversion correlation
Return visit rate Share of visitors who returned within N days Loyalty signal, marketing attribution
Zone transitions Origin-destination flows between defined zones Journey analytics, layout testing
New vs. returning split Acquisition vs. retention ratio Marketing channel attribution
Capture rate Share of detected devices that authenticate Portal effectiveness, data quality indicator

Capture rate deserves particular attention. It is the bridge between your anonymous presence data and your identified engagement data. Industry benchmarks put capture rate at 15-40%, depending on portal design and the incentive offered. Below 15% indicates a portal flow that needs attention.

Implementation guide: building for ROI

Deploying a system that generates measurable ROI requires specific architectural decisions. A network designed purely for coverage will not provide accurate spatial analytics.

Access point density and placement

Location analytics relies on triangulation. A device must be detected by at least three access points simultaneously to calculate an accurate position. In a typical retail or hospitality environment, this requires one access point per 150 to 200 square metres. Critically, place access points on zone boundaries, not just in the centre of rooms. If you only place access points in the centre of a space, the system cannot determine when a visitor crosses the threshold between zones. This is the single most common reason analytics deployments underperform.

For a 3,000 square metre retail floor, plan for 15 to 20 access points positioned to create overlapping coverage across department boundaries. Compare this to a coverage-only deployment, which might use eight access points placed for signal strength rather than triangulation accuracy.

Captive portal configuration

The captive portal is your conversion engine. Keep the login flow to three steps or fewer. Ask for the minimum viable data on the first visit. If your primary goal is CRM growth, require an email address and use Purple Verify to validate it at the point of capture - this prevents invalid data from polluting your database. For hospitality deployments, offer the premium bandwidth tier as a perk for loyalty program members. This drives sign-ups and creates a direct revenue line from the WiFi investment.

For venues that want to reduce friction for returning visitors, implement Passpoint (Hotspot 2.0). Passpoint allows authenticated devices to reconnect automatically on subsequent visits without presenting the portal again, while maintaining the session data needed for analytics. This is particularly effective in airports and hotels where repeat visitors are a significant cohort.

Data integration

Data sitting in a portal that nobody checks does not generate ROI. Integrate the WiFi analytics platform with your existing operational systems using standard REST APIs or webhooks. The integration layer is where most deployments stall, because it requires coordination between IT, marketing, and operations teams who do not typically share a data infrastructure. Prioritise this work early in the project.

For retail environments, the highest-value integration is with the point-of-sale system. Correlating zone dwell time with transaction data allows you to identify high-traffic, low-conversion zones - the areas where visitors are spending time but not buying. For hospitality environments, the integration with the property management system allows you to link WiFi session data to room bookings and food and beverage spend.

Best practices

Implement tiered bandwidth

Tiered bandwidth is the most direct method of generating revenue from guest WiFi. Offer a free, speed-limited tier for basic browsing and a premium, high-speed tier for a fee or as a loyalty perk. This approach offsets the cost of the network while driving loyalty sign-ups. AGS Airports implemented a tiered model and achieved an 842% return on investment (Purple customer data). The tiered model works because it converts a cost centre into a revenue line without degrading the experience for users who do not want to pay.

Segment your network

Do not mix guest traffic with corporate traffic. Use VLANs to isolate guest devices from your internal systems. This is a fundamental security requirement under PCI DSS for retail environments processing card payments. Purple provides the RADIUS infrastructure to manage these policies centrally across your estate, supporting IEEE 802.1X for port-based network access control and WPA3-Enterprise for the strongest available encryption standard.

For more detail on enterprise WiFi security architecture, see the Enterprise WiFi Security: A Complete Guide for 2026 guide.

Data privacy is not optional. If you operate in the UK or EU, you must comply with UK GDPR and EU GDPR. If you operate in California, you must comply with CCPA. Your captive portal must clearly state what data is collected, how long it is retained, and how visitors can exercise their rights. Obtain explicit consent for marketing communications. Presence analytics - which is anonymous - runs under legitimate interest with a completed Data Protection Impact Assessment (DPIA) and visible venue signage.

Purple is ISO 27001 certified, GDPR compliant, CCPA compliant, and Cyber Essentials certified. The platform ships DPIA templates and venue signage assets so you do not need to build the compliance infrastructure from scratch. For a detailed treatment of the compliance architecture, see the WiFi GDPR Compliance: How to Securely Collect Guest Data via Captive Portals guide.

Troubleshooting and risk mitigation

Inaccurate location data

If your heatmaps show visitors clustered in impossible locations or your zone-level counts do not match visual observation, the issue is typically access point placement or transmit power configuration. Verify that the access point locations on your floor plan match their physical locations exactly. Ensure that transmit power is not set too high - overpowered access points create large, overlapping coverage cells that reduce triangulation accuracy. Reduce transmit power and increase access point density to improve spatial resolution.

Low captive portal conversion

If a high volume of devices are detected but fewer than 15% authenticate, review the portal flow. Common causes include: too many required fields, a portal that does not load on the device's default browser, a lack of clear incentive to connect, or a portal that is not optimised for mobile screens. Test the portal on iOS and Android devices before deployment. Remove every field that is not essential. If you are not offering a clear value exchange - free WiFi, a discount, loyalty points - state it prominently on the splash page.

Integration failures

If data is not flowing to your CRM or POS system, check the API credentials and webhook configurations first. Verify that the data fields mapped in the WiFi platform match the corresponding fields in the destination system. Review the API logs for rate limiting or authentication errors. Most integration failures are configuration issues rather than platform bugs. Ensure your IT team has documented the field mapping before go-live.

MAC randomisation overcounting

If your WiFi visitor counts are significantly higher than your door counter or camera data, your platform is not correcting for MAC randomisation. This is a known issue with platforms that have not updated their analytics methodology since 2020. Ask your vendor for their correction methodology and the validation data. Purple's correction maintains ±3-7% accuracy versus camera ground truth (Purple platform data).

ROI and business impact

roi_calculation_framework.png

Measuring the ROI of guest WiFi requires a structured approach. You must quantify the costs and compare them against the measurable benefits across four categories.

The cost inputs

The total cost of ownership includes: hardware (access points, switches, cabling); software licensing (the Purple cloud overlay, available on Connect, Capture, and Engage plans); implementation services; and ongoing staff time for management and reporting. For a 200-room hotel deploying across five properties, a realistic total cost of ownership over three years includes hardware refresh, licensing, and integration work.

The revenue drivers

Industry data indicates that 62% of businesses report customers spend more time in their venue when free WiFi is available (BT Business WiFi Survey, 2025). In retail, increased dwell time correlates directly with increased basket size. A 10% increase in dwell time in a specific department that correlates with a 2% increase in sales for that category provides a clear, attributable ROI signal.

CRM database growth is the second major revenue driver. Calculate the value of a new email subscriber based on your average campaign conversion rate and average order value. If your email campaigns convert at 3% with an average order value of £80, each new subscriber is worth £2.40 in expected campaign revenue. A venue capturing 500 new subscribers per month generates £1,200 in expected monthly campaign revenue from that channel alone.

For venues implementing tiered bandwidth, direct revenue from premium tier subscriptions provides an immediately measurable return. AGS Airports achieved an 842% ROI from their tiered model (Purple customer data).

The operational savings

Footfall data aligned to staffing schedules reduces overstaffing during quiet periods. A venue that identifies a consistent 30% drop in footfall on Tuesday mornings can reduce staffing levels for that window, generating direct cost savings. For healthcare and transport environments, footfall data also informs queue management and capacity planning, reducing operational friction without additional headcount.

The ROI calculation

The standard ROI formula applies: ROI (%) = ((Net Benefit - Total Cost) / Total Cost) x 100. Net benefit is the sum of incremental revenue from dwell uplift, CRM campaign revenue, tiered access revenue, and operational savings. Total cost is the sum of hardware, licensing, implementation, and ongoing management.

For most hospitality and retail deployments, Purple clients see measurable ROI within six months. The first 90 days establish the baseline data. The second 90 days are where operational and marketing value starts to compound.



Further reading

Key Definitions

Presence analytics

The measurement of anonymous device activity based on probe requests and RSSI data, used to calculate footfall and dwell time without requiring user authentication.

Used by operations teams to understand total venue volume and layout efficiency. Runs under legitimate interest as the lawful basis under GDPR, with a completed DPIA and venue signage.

Engagement analytics

The measurement of identified visitor behaviour, captured after authentication via a captive portal. Links physical presence to a named contact record.

Used by marketing teams to build CRM profiles, track repeat visits, and measure campaign conversion. Requires explicit consent as the lawful basis under GDPR.

MAC randomisation

A privacy feature in modern operating systems (iOS 14+, Android 10+, Windows 11, macOS Sonoma) where a device broadcasts a temporary, rotating MAC address during probe requests rather than its permanent hardware identifier.

Requires analytics platforms to apply statistical correction to prevent artificial inflation of unique visitor counts. Platforms that have not addressed this will overstate footfall significantly.

Captive portal

A web page that a user must view and interact with before network access is granted. The primary mechanism for capturing first-party data and obtaining marketing consent.

The conversion engine of a guest WiFi deployment. Capture rate (the percentage of detected devices that authenticate) is the key performance indicator for portal effectiveness.

RSSI (Received Signal Strength Indicator)

A measurement of the power present in a received radio signal, expressed in decibels relative to one milliwatt (dBm). Used by analytics engines to triangulate device location within a venue.

The raw signal from which zone-level location data is derived. Access point density and transmit power settings directly affect the accuracy of RSSI-based location estimates.

Passpoint (Hotspot 2.0)

An IEEE 802.11u-based standard that allows mobile devices to automatically discover and connect to secure WiFi networks without manual authentication on return visits.

Reduces friction for returning visitors while maintaining enterprise-grade security. Particularly effective in airports, hotels, and any venue where repeat visitors are a significant cohort.

First-party data

Information a company collects directly from its customers through its own channels, which it owns and controls.

Captured via the captive portal, this data is the primary long-term asset generated by a guest WiFi deployment. It is not subject to the deprecation of third-party cookies and is fully compliant when collected with explicit consent.

Tiered bandwidth

A network configuration that offers different levels of speed or data allowance, typically providing a basic tier at no cost and a premium tier for a fee or as a loyalty perk.

The most direct method for venues to generate revenue from their WiFi infrastructure and demonstrate immediate ROI. Converts a cost centre into a revenue line.

Capture rate

The percentage of devices detected by the WiFi network (presence analytics) that proceed to authenticate through the captive portal (engagement analytics).

The bridge metric between anonymous and identified data. Industry benchmarks range from 15% to 40%. Below 15% indicates a portal flow that requires optimisation.

DPIA (Data Protection Impact Assessment)

A process required under GDPR for processing activities that are likely to result in a high risk to individuals. Documents the data collected, the purpose, the risks, and the mitigations.

Required for presence analytics deployments operating under legitimate interest. Purple provides a DPIA template as part of the platform onboarding.

Worked Examples

A 200-room hotel group wants to measure the ROI of upgrading their guest WiFi network across 5 properties. They currently offer a basic, open network with no captive portal and no analytics. How should they structure the upgrade to demonstrate measurable business value within 90 days?

Deploy Purple as a cloud overlay on the existing hardware (HPE Aruba in this scenario). Step 1: Implement a captive portal requiring an email address or social login, with a clear opt-in for marketing communications. Use Purple Verify to validate email addresses at capture. Step 2: Implement a tiered bandwidth model - 5Mbps free, 50Mbps for a daily fee or free for loyalty program members. Step 3: Integrate the WiFi platform with the property management system and CRM via REST API. Step 4: Define three measurement KPIs for the 90-day period: volume of new email addresses added to the CRM, revenue generated from the premium tier, and increase in loyalty program sign-ups attributed to the premium tier perk. Step 5: At 90 days, calculate ROI using the formula: (CRM campaign revenue + premium tier revenue + loyalty LTV uplift - total platform cost) / total platform cost x 100.

Examiner's Commentary: This approach transforms the network from a cost centre to a revenue driver within a single quarter. The tiered model provides immediate, directly attributable revenue. The captive portal builds the first-party data asset that compounds in value over time. The integration with the PMS allows the hotel to measure the long-term value of the acquired data by correlating WiFi sign-ups with repeat bookings.

A retail chain with 40 stores needs to justify the cost of increasing access point density to support zone-level location analytics. The current deployment provides adequate connectivity but insufficient spatial resolution for department-level dwell time measurement. How should the IT director build the business case?

Run a pilot in two representative stores - one high-performing and one underperforming by sales per square metre. Increase access point density in the pilot stores to one per 150 square metres, placing access points on department boundaries. Configure zones in the Purple analytics platform corresponding to specific departments. Run the pilot for 60 days, correlating zone dwell time data with POS transaction data. Identify departments where high dwell time does not correlate with high conversion - these are the zones where layout or merchandising changes are most likely to lift revenue. Present the pilot findings to the operations and merchandising teams with a specific recommendation: for example, 'The accessories department has the second-highest dwell time but the lowest conversion rate. Relocating the till point to the zone exit increases purchase friction reduction and is projected to lift conversion by 1.5% based on comparable store data.' Quantify the revenue impact of that 1.5% lift across the estate to justify the hardware investment.

Examiner's Commentary: This scenario demonstrates the importance of aligning IT investment with operational goals. The pilot approach reduces risk and produces evidence-based recommendations. By proving the value of the data in a controlled environment, the IT director shifts the conversation from hardware costs to revenue opportunity - a framing that resonates with the CFO and the commercial team.

Practice Questions

Q1. A retail client reports that their WiFi analytics platform is showing 40% more unique visitors than their door-counting cameras. What is the most likely technical cause, and how should it be resolved?

Hint: Consider how iOS 14 and Android 10 changed the way mobile devices broadcast their identity before connecting to a network.

View model answer

The discrepancy is caused by MAC randomisation. Devices are broadcasting multiple temporary MAC addresses as they probe for networks, and the platform is counting each unique MAC as a unique visitor. The resolution is to ensure the analytics platform applies statistical correction and device fingerprinting to account for randomisation, rather than relying on raw probe counts. A well-calibrated correction should bring the WiFi count within 3-7% of the camera count. If the vendor cannot demonstrate this correction, the footfall data is not reliable for business decisions.

Q2. You are deploying guest WiFi in a 15,000 square metre shopping mall. The marketing team wants to track how long shoppers spend in specific anchor stores and measure the flow between them. How should you design the access point placement to support this requirement?

Hint: Think about the difference between coverage requirements and analytics requirements, and what triangulation needs in terms of access point positioning.

View model answer

Access points must be deployed at a density of one per 150-200 square metres, with access points positioned on the perimeter of each anchor store zone rather than only in the centre of the mall. For a 15,000 square metre mall, this means 75 to 100 access points. Critically, access points must be placed at zone boundaries to define the entry and exit points of each store. Placing them only in the centre of the mall will not provide the spatial resolution needed to determine when a shopper crosses the threshold into a specific anchor store. Zone definitions should be configured in the analytics platform dashboard to match the physical boundaries.

Q3. A hospital wants to implement guest WiFi but cannot charge patients for access and has no point-of-sale system to integrate with. How can the IT director demonstrate measurable value from the deployment?

Hint: Consider what assets the hospital values beyond direct revenue, and how footfall data can drive operational savings.

View model answer

The hospital should focus on two value streams. First, operational savings: use presence analytics to measure footfall patterns in waiting areas and outpatient departments. Correlate this data with staffing levels to identify periods of overstaffing and understaffing. A reduction in overstaffing hours generates direct cost savings that can be quantified. Second, patient engagement: implement a captive portal that captures email addresses with opt-in consent. Use this to send appointment reminders, health information, and patient satisfaction surveys. The survey response rate from WiFi-acquired contacts provides a measurable improvement in feedback quality. Quantify the value of each survey response in terms of the operational improvements it enables.

Q4. A hotel group is considering implementing a tiered bandwidth model. The free tier would offer 5Mbps and the premium tier would offer 50Mbps for £5 per day. The hotel has 200 rooms and averages 75% occupancy. What information does the IT director need to calculate the projected ROI of the tiered model?

Hint: Think about the conversion rate from free to premium tier, the total addressable audience, and the cost of the platform.

View model answer

The IT director needs: the total addressable audience per day (200 rooms x 75% occupancy = 150 guests, plus day visitors); the projected conversion rate from free to premium tier (industry benchmarks suggest 10-20% for hotels); the average daily revenue from the premium tier (150 guests x 15% conversion x £5 = £112.50 per day); the annual revenue projection (£112.50 x 365 = £41,062); and the total annual cost of the platform including licensing and management. ROI = (£41,062 - total annual cost) / total annual cost x 100. This calculation covers only the direct revenue stream and does not include the value of the first-party data captured through the portal, which compounds over time.

Continue reading in this series

Integrating WeChat WiFi Login: Capturing Engagement via Social Captive Portals

This guide details how to integrate WeChat WiFi authentication into enterprise captive portals, covering the OAuth 2.0 architecture, RADIUS integration, and step-by-step deployment across Cisco Meraki, HPE Aruba, and Juniper Mist hardware. It gives IT managers and network architects a practical framework for capturing first-party data from WeChat's 1.3 billion users while driving engagement via Official Account follows and post-login redirects.

Read the guide →

WiFi GDPR Compliance: How to Securely Collect Guest Data via Captive Portals

This technical guide gives IT managers, network architects, and venue operations directors a practical framework for achieving GDPR compliance across guest WiFi deployments. It covers how captive portals collect personal data, how to secure explicit consent, and how to implement automated data retention policies that protect your organisation from regulatory fines of up to 4% of global turnover. Purple's guest WiFi platform maps directly to each compliance requirement, from consent logging to one-click data erasure.

Read the guide →

WiFi GDPR Compliance: How to Securely Collect Guest Data via Captive Portals

This technical guide gives IT managers, network architects, and venue operations directors a practical framework for achieving GDPR compliance across guest WiFi deployments. It covers how captive portals collect personal data, how to secure explicit consent, and how to implement automated data retention policies that protect your organisation from regulatory fines of up to 4% of global turnover. Purple's guest WiFi platform maps directly to each compliance requirement, from consent logging to one-click data erasure.

Read the guide →