Skip to main content

Meraki launches presence analytics API

Gavin WheeldonBy Gavin Wheeldon
7 May 2013
2 min read
Cisco Meraki Scanning API Simulator

Cisco Meraki presence analytics & footfall estimator

Model real-time probe telemetry, calculate passerby conversion rates, and project CRM lead capture with Purple WiFi Analytics.

15,000 sq ft (1394 m²)
2,000 sq ft75,000 sq ft150,000 sq ft
2,500 people / day
20015,00030,000
Recommended APs
3
Cisco Meraki MR46 units
Capture Rate
28%
700 daily entrants
Scanning Events
38/min
~17 KB/min webhooks
Monthly CRM Leads
+4,838
GDPR-compliant opt-ins

Simulated dwell time & visitor segmentation

Passersby (<5 min)45%
33,750 visitors/mo
Brief (5-20 min)25%
18,750 visitors/mo
Engaged (20-60 min)22%
16,500 visitors/mo
Extended (>60 min)8%
6,000 visitors/mo

Cisco Meraki Dashboard Webhook Integration

Purple ingests real-time JSON payloads via HTTPS POST from Meraki cloud controllers with automated SHA-256 MAC pseudonymization.

1. Enable Scanning API
In Meraki Dashboard navigate to Network-wide > General > Location and scanning.
2. Add Purple Webhook
Enter Purple receiver URL with validator token and shared secret key.
3. Radio Optimization
Enable dedicated WIDS/WIPS and BLE scanning radio on MR access points.
4. Ingest Analytics
View real-time footfall, dwell times, and heat maps in the Purple Portal.

Ready to turn Cisco Meraki WiFi into actionable venue intelligence?

Connect your Cisco Meraki estate to Purple in under 15 minutes with zero hardware changes.

As a Meraki Technology Partner  we were very excited when we got hold of the presence API several weeks ago. This is something we have been doing with our AirTight Networks integration for a while now so the capability within Meraki came as a very welcome piece of the puzzle.

On top of our integration with Social WiFi and the extensive reporting we are already able to provide, we are also now able to give wider insights about devices that are not authenticated onto the guest WiFi network. Termed as 'Presence Analytics' this booming market aims to give bricks and mortar businesses some of the rich analytical data that web properties, through programs like Google Analytics, have enjoyed for a long time.

Now there are a few other vendors working within Retail Analytics using presence, what you get with this is a lot of numbers, similar to Google Analytics, which is unbelievably valuable information. Things such as footfall, window conversion rates, engagement or bounce rates and heat mapping to mention a few. What we are able to do is layer on top of that data from authenticated users so you can then get a statistically significant sample of those users and see what the demographical make-up is. Do females of a particular age range convert better, spend more time or engage more with your venue?

You can slice it and dice it in any way you want and get real, actionable intelligence about how to improve your interactions with customers in the real world.

Frequently asked questions

What is the Cisco Meraki Presence API and how does it work?

The Cisco Meraki Presence API (now part of the Scanning API) is a real-time location telemetry feed provided by Cisco Meraki cloud-managed access points. The AP radios passively detect 802.11 probe requests and Bluetooth Low Energy (BLE) advertisements transmitted by nearby smartphones and client devices. The Meraki cloud calculates signal strength (RSSI), estimates spatial coordinates, and streams batched JSON payloads via HTTPS POST webhooks to receiver platforms like Purple.

What is the difference between Cisco Meraki Presence API v2 and Scanning API v3?

Scanning API v3 supersedes Presence API v2 by delivering unified telemetry for both WiFi clients and BLE beacons in a single webhook stream. Version 3 includes high-resolution floorplan coordinates (X/Y position and GPS latitude/longitude), confidence uncertainty radii, access point radio band tags, and support for IPv6 client addresses, providing higher location precision across enterprise estates.

How does the Meraki Scanning API calculate device location and dwell time?

When a device transmits probe requests, multiple Meraki access points record the Received Signal Strength Indicator (RSSI) and timestamps. The Meraki cloud location engine uses multi-point trilateration to estimate the physical coordinates of the device. Dwell time is measured by calculating the elapsed time between the first detected probe frame and the last observed frame within a defined venue boundary.

How does Purple handle MAC address randomization on iOS and Android devices?

Modern mobile operating systems use rotating, randomized MAC addresses during unassociated probe scans. Purple's analytics engine filters short-lived randomized probe bursts to ensure accurate aggregate footfall counts, and links returning visitors securely when they authenticate through the Purple captive portal using privacy-compliant one-way cryptographic hashing.

What network bandwidth and webhook infrastructure are required for Meraki Scanning API?

Meraki access points upload small JSON payloads to the Meraki cloud, which aggregates and delivers HTTPS POST requests to the Purple webhook receiver every 30 to 60 seconds. A typical 20-AP venue generates approximately 50 to 150 KB of webhook data per minute, imposing zero backhaul overhead on local venue internet links.

How does unauthenticated presence data combine with authenticated guest WiFi data?

Presence analytics captures 100% of nearby radio-emitting devices to measure total passerby traffic, exterior footfall, and window conversion rates. When visitors log into Purple Guest WiFi via the captive portal, their demographic data (age group, gender, marketing consent) is correlated with aggregate spatial trends to provide statistically significant customer demographic insights.

Ready to get started?

Book a demo with one of our experts to see how Purple can help you achieve your business goals.

Speak to an expert