Heatmapping vs Presence Analytics: Technical Differences

[Intro] Hello and welcome to the Purple Technical Briefing. I'm your host, and today we're diving into a topic that frequently causes confusion at the intersection of IT infrastructure and business intelligence: WiFi Heatmapping versus Presence Analytics. If you're an IT director, a network architect, or a venue operations lead, you've likely had marketing or operations teams ask you for heatmaps when what they actually want is visitor behavioural data. Today, we're going to unpack the technical architectures of both, explain why they are fundamentally different, and discuss how to deploy them effectively to drive real ROI. [Technical Deep-Dive] WiFi Heatmapping is your diagnostic layer. It is entirely focused on the infrastructure. When we talk about heatmapping, we're talking about measuring Received Signal Strength Indicator — or RSSI — Signal-to-Noise Ratio, and channel interference. Think of it as an X-ray of your physical space. You're using active or passive surveys to visualise how radio frequency waves propagate through your environment. Are the signals bouncing off the metal shelving in your retail warehouse? Is the concrete elevator shaft creating a dead zone in your hotel lobby? Heatmapping answers these questions. It is the prerequisite for a healthy network. Now, contrast that with Presence Analytics. Presence Analytics is the behavioural intelligence layer. It doesn't care about the health of the access point; it cares about the devices moving beneath them. The architecture here is entirely different. Presence analytics relies on capturing probe requests — those are the tiny packets your smartphone sends out constantly, asking: are there any networks I know nearby? The analytics engine captures these probe requests, anonymises the MAC addresses at the edge using secure hashing like SHA-256 to ensure GDPR compliance, and then feeds that data into a trilateration engine. Trilateration is the magic word here. By comparing the signal strength of a single smartphone across three or more access points, the system calculates the device's X and Y coordinates. It maps the device to a physical zone. This is where the friction often occurs between IT and Operations. Operations will say: we have great WiFi coverage, why can't you tell me how long people dwell at the end-cap display? The answer is: Coverage does not equal Context. You can have fantastic coverage with just two access points blasting signal down a corridor. But to perform accurate trilateration for presence analytics, a device must be heard by at least three access points simultaneously, ideally with a signal strength better than minus seventy-five dBm. This means a network designed for presence analytics requires a significantly higher access point density, and different placement strategies — like perimeter mounting — compared to a network designed just for basic coverage. [Implementation Recommendations and Pitfalls] Now let's talk about implementation. How do we do this successfully? First, never deploy presence analytics without a baseline heatmapping survey. You must understand your RF environment first. This is non-negotiable. Second, utilise a hardware-agnostic platform. Purple's architecture ingests data via API from Cisco, Aruba, Ruckus, and others simultaneously. This prevents vendor lock-in and allows you to standardise your analytics even if your physical hardware is fragmented across different sites. The biggest pitfall? MAC Randomisation. Modern iOS and Android devices rotate their MAC addresses to prevent passive tracking. If you rely solely on passive probe requests, your data will become fragmented. One visitor might look like three different people over the course of an hour. The mitigation strategy is robust authentication. By deploying a captive portal — Purple's Guest WiFi solution, for instance — you encourage users to authenticate. Once they log in, the system can track the associated device, bypassing the OS-level randomisation and providing highly accurate, deterministic data. [Rapid-Fire Q&A] Let me run through a quick rapid-fire Q and A. Question one: Do I need proprietary sensors for presence analytics? No. Modern platforms leverage your existing enterprise access points. You just need to ensure the density is sufficient. Question two: How often should I run a heatmapping survey? At minimum, annually. But ideally, whenever the physical environment changes significantly. Question three: Can presence analytics track employees versus guests? Yes, by filtering out devices connected to the corporate SSID, or by excluding MAC addresses with dwell times exceeding a typical guest visit duration. Question four: What spatial resolution can I expect? With a well-designed network, typically three to five metres. With BLE augmentation, this can improve to one to two metres. [Summary and Next Steps] To summarise the key takeaways. Heatmapping is the X-ray of your network infrastructure. Presence Analytics is the MRI of your visitor behaviour. The Rule of Three at minus seventy-five: for accurate presence analytics, a device must be visible to at least three access points at minus seventy-five dBm or better. Coverage does not equal Capacity, and Capacity does not equal Context. MAC randomisation is the biggest challenge to passive analytics. Captive portal authentication is the most effective mitigation. Hardware-agnostic platforms prevent vendor lock-in and allow unified analytics across mixed environments. By treating heatmapping as the foundational diagnostic and presence analytics as the strategic business layer, IT leaders can transform their wireless networks from a pure cost centre into a revenue-optimising asset. For more detailed deployment architectures, check out the full technical guide accompanying this briefing on the Purple website. I've been your host, thank you for listening to the Purple Technical Briefing.