WiFi Analytics for Commercial Property: What Landlords and Asset Managers Need to Know

The Property Intelligence Gap

Landlords of retail parks, food halls and mixed use buildings usually work from three sources: door counters, the sales figures tenants report, and the occasional visitor survey. Door counters tell you how many people came in. They say little about where people went, how long they stayed or whether they came back.

Guest WiFi in the common areas can fill part of that gap. Be clear about which kind of WiFi data you mean, because there are two, and they behave very differently.

Login data. People who join the guest network and pass the login page. You know these are real visitors, you can see when they come back, and if they agree, you can contact them. You only see the share of visitors who connect.

Device presence data. Some systems count phones that are nearby, including ones that never connect, by listening for the signals phones send while searching for networks. This covers more people but is much less reliable (see below) and raises more privacy questions.

VoqadoWiFi works with logins on TP-Link Omada and Ubiquiti UniFi guest networks. It sees people who connect, not passers by.

What Aggregate WiFi Data Tells a Property Manager

Used carefully, aggregate WiFi data can help you answer questions like these:

Does the anchor tenant pull people through? If access points are spread across the property, you can compare connections near the anchor with connections near the smaller units on the same days. A drop at the anchor followed by a drop next door suggests shared traffic. Treat it as a pattern to investigate, not proof of cause.

Do food and drink areas keep people on site longer? Session length for guests who connect in the food court, compared with guests who only connect elsewhere, gives you a rough read. It is a sample of the people who connected, so check it against what your door counts and tenants tell you.

Where are the quiet spots? If an access point in one corridor consistently sees far fewer connections than its neighbours, that is worth a walk round. It may be a wayfinding or signage problem. It may also be a coverage problem, so check signal strength there before blaming the tenant mix.

Two limits apply to all of this.

First, phones no longer show the same hardware address everywhere. Apple devices use a different private address for each WiFi network by default, and on a network with weak or no security (which describes many open guest networks) newer versions default to an address that rotates every 2 weeks (Apple Support). Android 10 and later use a randomised address by default (Android Open Source Project). Any "returning visitor" figure built only on device addresses will undercount repeat visits. Repeat visits tied to a login (the same guest account) hold up much better.

Second, the people who connect are not a random sample. Office workers on a lunch break and tourists without data roaming connect more than locals with good mobile signal. Compare like with like over time rather than treating WiFi numbers as total footfall.

Cross-Tenant Visit Behaviour

If access points are dense enough to tell one tenant zone from another, you can in principle see sequences: people who connect near the gym and later near the food court, for example. That is useful for tenant mix discussions.

It is also the point where aggregate statistics turn into tracking individual people around a building. Following one device or one guest from unit to unit is processing personal data, even if you never know a name. The UK regulator lists MAC addresses among the online identifiers that may be personal data (ICO). Tell visitors you do it, have a lawful basis, keep it no longer than you need, and report only aggregates to anyone outside the team that runs the network.

Tenant level figures are commercially sensitive too. Agree in writing what each tenant will and will not see before you publish anything about their unit.

GDPR Implications of Multi-Tenant WiFi Data Sharing

This is general information, not legal advice. Take advice on your own set up, particularly before sharing anything that identifies people.

Who is responsible. Whoever decides why and how the WiFi data is used is the controller. A landlord running common area WiFi is the controller for that data; a tenant running its own guest WiFi is the controller for its data. If landlord and tenant decide the purposes and means together, the GDPR treats them as joint controllers and they need an arrangement setting out who does what (GDPR Article 26). A WiFi platform working on your instructions is a processor, and Article 28 requires a contract (or other legal act) governing that work.

Tell people at the point of collection. Article 13 requires you to give the purposes and the legal basis when you collect the data. If you plan to share login data with tenants, the login page and privacy notice must say so then, not afterwards. Our guest WiFi privacy notice template is a starting point.

What is usually safe to share. Counts and averages that cannot identify anyone: connections per zone per day, average session length, the share of logins from returning guests at property level.

What needs much more care. Anything that identifies a person or a device across zones, contact details, and marketing lists. A tenant cannot simply use a list of people who agreed to hear from the landlord. Marketing consent given to one business does not carry over to another.

The practical split. Use WiFi data for property level decisions (layout, leasing, operations). Keep each business's contact list and opt in records with the business that collected them. The two can run side by side on the same building without crossing data protection lines, provided the reporting you share is aggregate.

Using WiFi Data in Lease Negotiations

WiFi figures can support a conversation with a tenant. They are weak as a contractual measure. Some ways to use them sensibly:

• As context in rent reviews. A trend in connections over two years, alongside door counts, says something about how busy a scheme is. It is not a substitute for sales evidence.
• To back up service charge spend on marketing or events. Show connections before, during and after an event. Be honest that weather, school holidays and tenant openings move the same numbers.
• In regular reports to tenants. A short monthly report of aggregate figures builds trust, as long as every tenant gets the same definitions.

When not to do it: do not tie rent or turnover clauses to WiFi counts. The share of visitors who connect changes with phone settings, mobile signal and how prominent your login page is, none of which reflects how a tenant is trading. If a number could move because of an operating system update, it does not belong in a lease.

Setting up guest WiFi in a shared area? Start with the controller guides for Omada or UniFi.