What Is a WiFi Heatmap? Visualizing Guest Movement Data
Key Takeaways: A WiFi heatmap is a visual representation of device density and guest movement patterns within a physical space, generated by mapping signal data from access points onto a venue floor plan. Heatmaps show where guests cluster, how they move between zones, and which areas have the highest dwell time — using color gradients (red = high density, blue = low density). They're generated from WiFi presence analytics data (probe requests) and connected session data (RADIUS accounting), providing venue operators with spatial intelligence previously available only through expensive camera-based systems.
A WiFi heatmap takes the raw device detection data from your access points and paints it onto a map. Red zones where 200 devices cluster. Blue zones where 5 devices pass through. Green corridors connecting them.
It's the visual layer on top of WiFi presence analytics. Presence analytics tells you 847 devices were in the venue between 12-1 PM. The heatmap tells you 380 of them were in the food court, 210 were on the second floor, and 140 were near the entrance.
For venue operators, this is the difference between "we're busy" and "the west wing is underperforming." For resellers, it's the visual that sells the entire analytics package. Numbers on a spreadsheet are abstract. A heatmap on a floor plan is immediate.
How WiFi heatmaps are generated
Data sources
WiFi heatmaps pull from two data streams:
1. Probe request detection (passive) Every WiFi-enabled device broadcasts probe requests. APs in range detect these signals and record the device's MAC address, RSSI (signal strength), and timestamp. RSSI serves as a distance proxy — stronger signal means closer device.
2. RADIUS session data (active) Connected devices are tracked at the AP level through RADIUS accounting. The AP each device is associated with maps to a physical location.
The positioning process
- •AP placement mapping — each AP's physical coordinates are plotted on the floor plan
- •Signal collection — the system collects RSSI readings from probes and sessions
- •Trilateration — if 3+ APs detect the same device, the system triangulates approximate position using RSSI values and AP coordinates
- •Interpolation — algorithms smooth the data between known points to create a continuous density surface
- •Visualization — the density surface is rendered as a color gradient overlay on the floor plan
Accuracy by hardware tier
| Hardware | Positioning Method | Accuracy | Best For |
|---|---|---|---|
| Cisco Meraki (CMX) | Dedicated location engine, RSSI + time-of-flight | 1-3 meters | Enterprise venues, malls |
| Juniper Mist | AI-driven location with vBLE | 1-3 meters | Campus, hospitality |
| Aruba (ClearPass) | RSSI trilateration | 3-5 meters | Hotels, retail chains |
| Ruckus (SCI) | RSSI analytics | 5-10 meters | Stadiums, events |
| Ubiquiti UniFi | AP association only (no trilateration) | AP zone (~15-30m) | SMB venues |
| Standard SMB APs | AP association only | AP zone | Small venues |
Enterprise APs with dedicated location engines produce heatmaps with 1-3 meter resolution — accurate enough to distinguish between individual store zones, aisle sections, or seating areas. SMB APs produce AP-level zone maps — useful for multi-room venues but not fine-grained enough for aisle-level analysis.
What heatmaps reveal
Zone performance
The primary use case. Which zones attract the most traffic? Which are underutilized?
A shopping mall with 40 APs across 4 floors can see exactly which stores generate the most foot traffic, which corridors serve as main arteries, and which zones are dead spots. This data informs:
- •Lease pricing — high-traffic zones justify premium rent
- •Tenant placement — anchor tenants near low-traffic zones to pull visitors
- •Signage placement — directional signs at decision points where flow diverges
- •Promotional zones — pop-up events in high-traffic areas for maximum exposure
Traffic flow patterns
Time-series heatmaps reveal how visitors move through the space over time. A restaurant might see:
- •11:30 AM: density builds at entrance and bar area
- •12:00 PM: density shifts to dining room
- •12:45 PM: density peaks at both dining and outdoor patio
- •1:30 PM: density drops, shifts back toward entrance/exit
This temporal flow data helps venue operators optimize staffing schedules, table management, and promotional timing.
Dwell time by zone
Not just where people go, but how long they stay there. High-dwell zones indicate engagement. Low-dwell zones indicate passthrough.
| Zone | Avg Visitors/Hour | Avg Dwell Time | Interpretation |
|---|---|---|---|
| Main entrance | 340 | 45 seconds | Passthrough zone |
| Electronics dept | 85 | 12 minutes | Engagement zone |
| Checkout area | 120 | 4 minutes | Transaction zone |
| Back corner | 15 | 22 minutes | Destination zone (high engagement, low traffic) |
The back corner has the fewest visitors but the longest dwell time — indicating that people who find it are highly engaged. This might be the store's most valuable per-visitor zone, justifying better signage to increase traffic.
Heatmaps vs. other spatial analytics
Camera-based people counting
Camera systems (RetailNext, ShopperTrak, Axis) use video analytics to count people and track movement with high accuracy (±3-5%). They can detect demographics (age range, gender) that WiFi can't.
Pros over WiFi: Higher accuracy for entrance/exit counts, demographic detection. Cons vs. WiFi: $500-$2,000 per camera, installation complexity, privacy concerns (facial recognition regulations), no identity data capture.
Camera and WiFi heatmaps are complementary. Cameras count who enters. WiFi tracks what they do inside and captures their contact information.
Bluetooth beacon mapping
BLE beacons placed throughout a venue detect app-equipped devices with 1-3 meter accuracy. The resulting heatmaps are precise but limited to visitors with the venue's app installed — typically 2-5% of traffic.
A WiFi heatmap based on probe requests detects 70-90% of visitors (anyone with WiFi enabled). Lower spatial resolution, but orders of magnitude more coverage.
LiDAR and depth sensors
Used in high-end retail and smart building deployments for centimeter-level accuracy. Cost: $1K-$5K per sensor. Overkill for most venue intelligence use cases.
Deploying heatmaps as a reseller
Minimum hardware requirements
For meaningful heatmaps, the venue needs:
- •Minimum 3 APs for basic trilateration (more = better resolution)
- •AP spacing: 15-20 meters for zone-level mapping, 8-12 meters for section-level
- •Floor plan — a digital floor plan (PDF, PNG, or CAD drawing) to overlay the heatmap
Single-AP venues (small cafes, boutiques) can't generate spatial heatmaps — they get aggregate analytics only. Heatmaps become valuable at 3+ APs covering distinct zones.
Platform configuration
- •Upload the venue floor plan to the analytics platform
- •Plot AP positions on the floor plan (drag-and-drop)
- •Define zones (name each area: "entrance," "dining room," "patio," etc.)
- •Enable probe request collection and RADIUS accounting
- •Wait 24-48 hours for data to accumulate
- •View the heatmap — it updates in near-real-time on enterprise hardware, hourly on SMB
Pricing the service
Heatmaps are a premium add-on to base WiFi marketing packages:
- •Base WiFi marketing: $149-$199/month
- •WiFi marketing + heatmaps: $249-$349/month
- •WiFi marketing + heatmaps + monthly analysis report: $349-$499/month
The monthly analysis report is where the real value lives. Raw heatmaps are interesting; interpreted heatmaps with actionable recommendations ("move the promotional display from zone A to zone C based on traffic flow") are what justify premium pricing.
Heatmap limitations and honest caveats
MAC randomization degrades accuracy
Modern smartphones randomize their MAC addresses in probe requests. This means the same device appears as multiple "visitors" on the heatmap. Statistical deduplication corrects for this (±15% accuracy), but the heatmap shows density estimates, not exact person counts. Always present heatmap data as relative ("Zone A has 3x the traffic of Zone B") rather than absolute ("Zone A had exactly 847 visitors").
RSSI is a noisy signal
Signal strength fluctuates based on body position (phone in pocket vs. hand), environmental factors (wall materials, furniture, humidity), and device transmit power. This means device positions estimated from RSSI have inherent jitter. Heatmaps smooth this noise through interpolation, but individual device positions can be off by 3-10 meters on standard hardware.
Outdoor heatmaps are unreliable
WiFi heatmaps work best indoors where walls and obstacles create distinct signal zones. Outdoors, signals propagate unpredictably — RSSI-based positioning loses accuracy. For outdoor venues (events, markets, parks), use AP zone-level counts rather than interpolated heatmaps.
Data requires volume
A heatmap generated from 50 device detections is meaningless noise. Useful heatmaps require hundreds to thousands of data points over a meaningful time period (24 hours minimum, 7 days ideal). Low-traffic venues may need a full month of data before patterns emerge.
Frequently asked questions
Do guests need to connect to WiFi for heatmap data?
No. Heatmaps use probe request detection, which captures signals from all WiFi-enabled devices in range — connected or not. However, connected devices provide more precise data (AP association is definitive location, while probe RSSI is estimated). The best heatmaps combine both sources.
Can heatmaps track individual visitors?
With MAC randomization, tracking specific anonymous devices across time is unreliable. However, authenticated guests (who connected through the captive portal) can be tracked across visits using their verified MAC address. This enables per-guest journey mapping for your most valuable visitors.
How often do heatmaps update?
Enterprise platforms with CMX or Mist location engines update in near-real-time (every 30-60 seconds). SMB platforms update hourly or daily. For most use cases, hourly updates are sufficient — venue operators review heatmaps daily or weekly, not in real-time.
What's the difference between a WiFi heatmap and a signal strength heatmap?
A signal strength heatmap (used by network engineers) shows WiFi coverage — where the signal is strong vs. weak. A guest density heatmap (used for marketing and operations) shows where people are. Same visualization technique, completely different data. This article discusses guest density heatmaps.
Can heatmaps show historical data?
Yes. Platforms store probe and session data, allowing you to generate heatmaps for any historical time period. Compare Tuesday lunch vs. Saturday dinner. Compare this month vs. last month. Compare before and after a layout change. Historical comparison is one of the most valuable heatmap use cases.
Bottom line
A WiFi heatmap transforms raw device detection data into a visual representation of how people use physical space. Red zones show where crowds gather. Blue zones show dead areas. The gradient between them shows movement corridors.
For resellers, heatmaps are the visual that sells the analytics package. Venue operators immediately understand what they're looking at — no data literacy required. And the insights (zone performance, traffic flow, dwell time by area) lead directly to operational decisions that improve the venue's revenue.
Deploy heatmaps with 3+ APs, enterprise hardware for best resolution, and present the data as relative comparisons rather than absolute counts. Bundle heatmaps with WiFi analytics for a premium service tier that justifies $249-$499/month pricing.