Why device makers did it
The hardware MAC address is globally unique and was historically broadcast in the clear every time a device scanned for networks. That made it a durable tracking identifier: any party with sensors in multiple places could follow a phone between them without the owner ever connecting to anything. Randomisation removes that capability by presenting a synthetic address, typically stable per network so a saved WiFi connection keeps working, but different across networks and sometimes rotated over time. It is on by default across current mobile platforms.
What it breaks
Anything that treated a MAC address as a person now misbehaves. Unique-visitor counts inflate, because one phone can appear as many devices over time. Returning-visitor detection under-reports, because the same person looks new. Dwell sessions fragment when an address rotates mid-visit. MAC-based allow-lists and "remember this device" auto-login features become unreliable, occasionally locking out a regular or, worse, silently granting a new device someone else's session state.
How to build around it
The durable answer is to stop identifying people by hardware and start identifying them by consent. An authenticated portal session tied to an email address survives randomisation entirely, because the guest tells you who they are. That means designing the login to be low-friction enough that guests actually complete it, keeping sessions long enough that regulars are not re-prompted every visit, and reporting on identified guests as your primary metric with device presence as a secondary, clearly-labelled estimate. Presenting randomised device counts as visitor numbers without that caveat produces confidently wrong reporting.
See mac address randomisation in a live portal
VoqadoWiFi runs branded guest portals on TP-Link Omada and Ubiquiti UniFi networks. The Starter plan is free forever: one location, 25 logins a month, consent logging included.
MAC Address Randomisation — common questions
Can I ask guests to turn randomisation off?
You can, and some venues show instructions when a device fails to reconnect, but expect low compliance and treat it as a support workaround rather than a strategy. Design your analytics to work with randomisation on.
Does randomisation stop guests being remembered between visits?
It breaks device-based recognition. Recognition based on an authenticated login still works, which is why login-based identity is the more durable foundation.
Related terms
MAC Address Randomisation rarely comes up on its own. These are the entries operators usually read next.
Footfall Analytics
Footfall analytics is the measurement of visitor volume and patterns in a physical space. WiFi-based footfall infers counts from d…
Dwell Time
Dwell time is how long a visitor remains inside a venue, measured in WiFi analytics from when a device is first detected to when i…
Captive Portal
A captive portal is the web page a network forces a device to load before it grants internet access. The network intercepts the fi…
First-Party Data
First-party data is information a business collects directly from its own customers with their consent, such as an email address g…
More in Networking