Mall visitor analytics measures how many people enter a centre, where they go, how long they stay and which tenants they pass or enter. Accurate measurement requires distinguishing entrance counts from tenant footfall from unique visitors — three different numbers — and choosing a counting technology that still works: Wi-Fi probe analytics has been substantially degraded by MAC address randomisation on modern phones.

Footfall is a landlord's inventory. If the number cannot survive a tenant's scrutiny in a rent review, it is not an asset — it is an argument waiting to be lost.

  • Entrance, tenant and unique visitor counts measured separately
  • Honest position on Wi-Fi analytics after MAC randomisation
  • Dwell time and capture rate per zone and unit
  • Anonymous counting, without facial recognition
Shoppers in a mall corridor
Counting people is straightforward. Explaining why they turned left is the part with commercial value.

Three different numbers, all called footfall

Footfall enters commercial conversations as though it were one figure, and it is at least three. Entrance counts include staff, cleaners, delivery personnel and the same person returning from the car park. Tenant footfall — how many people passed or entered a specific unit — is a different measurement with different sensors. Unique visitors is different again and is the hardest of the three to establish honestly. When a landlord quotes one and a tenant hears another, a rent review becomes an argument about definitions.

Underneath is a technology problem that many centres have not been told about. Wi-Fi probe-based analytics, which measured phones as they searched for networks, was widely deployed and is now substantially degraded: modern iOS and Android randomise device MAC addresses, so the same phone appears as many devices and repeat-visit analysis becomes unreliable. Centres are still receiving reports from these systems, and the trends in them reflect changes in operating system behaviour as much as changes in shopper behaviour.

  • Entrance counts, tenant footfall and unique visitors are conflated into one figure.
  • Staff, cleaners and re-entries inflate headline numbers.
  • Wi-Fi probe analytics has been degraded by MAC address randomisation.
  • Repeat-visit and dwell metrics from Wi-Fi systems are no longer dependable.
  • Tenants dispute landlord footfall figures because the definitions are unstated.

Solution overview

Swedish Technology begins with definitions, because the commercial value of footfall depends entirely on whether the number means what both parties think. Entrance counts, tenant passing traffic, tenant entries, dwell and unique visitors are measured and reported as distinct metrics, with staff and re-entry effects handled explicitly rather than left inside the headline. A number that a tenant can interrogate and still accept is worth more than a larger number they dispute.

On technology, we recommend what still works. Camera-based and 3D sensor counting at entrances and unit thresholds is accurate, well understood, and unaffected by phone behaviour. Zone and journey analysis follows from a sensor network rather than from device probing. We will say plainly where Wi-Fi analytics remains useful — connected-network sessions, where a device has actually joined — and where it no longer is, which is the passive probe measurement most centres bought it for.

And we design for anonymous measurement. Facial analysis products offering demographic estimates exist and are widely marketed; they process biometric data about people who did not choose to be measured, their demographic inference is less reliable than the marketing implies, and the commercial questions a mall actually needs answered — how many, where, how long, which units — do not require identifying anyone.

How the solution works

  1. 1
    Define the metrics first Agree what entrance count, tenant footfall, entries, dwell and unique visitors each mean, and how staff and re-entries are handled. This is a commercial decision before it is a technical one.
  2. 2
    Place sensors by question Entrances, atria, corridors, unit thresholds and vertical circulation, chosen from the questions the asset team actually asks rather than for uniform coverage.
  3. 3
    Count anonymously Camera or 3D sensor counting that produces counts rather than identities, with no facial recognition and no demographic inference.
  4. 4
    Measure zone flow and dwell Movement between zones and time spent, which is what turns a count into an explanation of tenant performance.
  5. 5
    Separate staff and re-entry Staff entrances and car park re-entries identified and reported separately, so the headline is defensible when a tenant examines it.
  6. 6
    Report to the audience Asset management, leasing and tenants each need different views. A tenant report that only shows centre-wide footfall answers nothing they care about.
Mall entrance
Entrance counts and tenant footfall are different numbers, and conflating them is where lease disputes start.

Key capabilities

Multi-metric measurement

Entrance count, tenant passing traffic, entries, dwell and unique visitors as distinct figures rather than one contested number.

available

Anonymous counting

Counts without identities — no facial recognition, no demographic inference, no biometric processing of shoppers.

available

Zone and journey analysis

Movement between zones, circulation patterns and dead areas, which is what explains tenant performance differences.

available

Capture rate per unit

Passing traffic against entries per tenant — the metric that separates a location problem from a shopfront problem.

available

Staff and re-entry handling

Non-shopper traffic identified and reported separately, so figures survive tenant scrutiny.

available

Tenant reporting

Views built for leasing conversations and tenant relationships rather than a single centre-wide number nobody can act on.

available

Reference architecture

A sensor network with counting performed at the edge, so what leaves a camera is a number rather than a picture of a shopper.

Deployment options: Edge counting with a central analytics platform. Counts continue and buffer locally during a network interruption, and sensor health is monitored because a silently failed counter produces a footfall trend that is a hardware fault.

Hardware options

Counting sensors chosen for accuracy at the specific measurement point, which varies more than vendors suggest.

DeviceWhere it is usedSelection notes
3D stereo counting sensorsEntrances, unit thresholdsThe accuracy standard for threshold counting. Handles groups, direction and height filtering to exclude children where a centre chooses to, and produces counts rather than images.
Camera-based counting with edge analyticsCorridors, atria, zonesWider area coverage where threshold counting is impractical. Counting performed at the edge so images are not retained or transmitted.
Overhead sensors for queue and occupancyFood courts, service points, high-density areasOccupancy and dwell in open areas where directional counting does not apply.
Existing CCTVWhere geometry suitsSometimes usable for zone-level counting; rarely accurate enough for threshold counting where the commercial figures come from. Worth assessing rather than assuming.
Wi-Fi infrastructureConnected-network measurement onlyStill useful for sessions where a device actually joins the network. Passive probe counting is substantially degraded by MAC randomisation and should not be the basis of commercial figures.

Swedish Technology supplies and integrates counting sensors from established manufacturers, specified per measurement point.

AI capabilities

Applied to counting accuracy and to explaining patterns, not to identifying shoppers.

  • Accurate counting in crowds — Distinguishes individuals in groups, families and pushchairs at busy thresholds, which is where simple beam counters fail badly and where mall traffic actually is.
  • Staff and re-entry inference — Identifies patterns consistent with staff movement and car park re-entry from timing and route, so headline figures can be normalised defensibly.
  • Anomaly and sensor health detection — Flags counts inconsistent with historical patterns, which is how a failed or obscured sensor is caught before it becomes a quarter of misleading trend data.
  • Pattern explanation — Relates footfall changes to events, weather, holidays and trading hours so a decline is attributed correctly rather than to whichever change was most recent.

Integrations

These can be designed within project scope.

SystemIntegration point & data exchangedDirection
Property and lease management systems Footfall by unit and zone alongside lease data, which is where the number becomes a commercial instrument rather than a report. bi-directional
Tenant sales reporting Where tenants share sales data, conversion can be measured — though tenant willingness to share is usually the constraint rather than the integration. inbound
Car park systems Vehicle entries and dwell to relate parking to footfall and to identify re-entry effects. → Smart Parking for Residential Communities inbound
Marketing and campaign platforms Footfall response to campaigns and events measured at zone level rather than asserted from centre totals. outbound
BMS and facilities systems Occupancy informing cleaning schedules, air conditioning and staffing, which is an operational return alongside the commercial one. → Facility Management bi-directional
Digital signage and screens Content scheduled against measured traffic patterns rather than a fixed loop. → Retail Interactive Games & Gamification outbound

The integrations above are designed and implemented within project scope using vendor APIs, webhooks or standard connectors. They do not imply partnership, certification or endorsement by the system owner unless stated on that vendor's official pages.

Dashboards & analytics

  • Centre performance — Footfall by entrance, hour, day and period with staff and re-entry effects reported separately.
  • Zone and circulation — Movement between zones, dwell and dead areas — the analysis that explains tenant location performance.
  • Tenant reporting — Passing traffic, entries and capture rate per unit, in a form that can be shared with tenants.
  • Sensor health — Coverage and counting confidence, so a trend is never a failed sensor mistaken for a market change.

Security & deployment

Counting is performed at the edge so that what leaves a sensor is a number rather than an image of a shopper. That is a deliberate architectural choice: it limits what can be misused, reduces bandwidth, and makes the anonymity claim verifiable rather than a promise in a policy. Sensor health monitoring matters more than it sounds — a silently failed or obscured counter produces a footfall decline that will be interpreted as a market signal and acted on commercially, so counting confidence is reported alongside the counts themselves.

Data privacy

Retail analytics has a poor reputation in privacy terms, largely earned by two practices: passive device tracking without meaningful notice, and facial demographic estimation. We avoid both. Counting produces counts — no identities, no faces, no device identifiers retained — and the questions a mall needs answered are all answerable that way.

Where a centre wishes to understand repeat visits, the honest options are consented ones: a loyalty programme, an app, or a connected Wi-Fi service where the shopper has actually opted in and knows what that means. Passive repeat-visit measurement was always weakly consented and is now technically unreliable as well, which removes the last argument for it. Under UAE Federal Decree-Law No. 45 of 2021, biometric data is sensitive personal data, and facial analysis of shoppers is a substantially higher bar than most retail deployments could justify — while signage explaining that anonymous counting is in use is straightforward and should be present regardless.

Industry use cases

Regional shopping centre

Defensible footfall definitions used in rent reviews, with tenant-level capture rate replacing arguments about centre-wide totals.

Centre replacing Wi-Fi analytics

Sensor-based counting deployed after MAC randomisation made the existing reports unreliable, with the discontinuity in the trend explained honestly.

Asset manager assessing tenant mix

Zone flow and dead-area analysis informing leasing strategy and unit reconfiguration rather than intuition about the centre's layout.

Mall running events and activations

Zone-level footfall response measured against the activation rather than inferred from a centre total that moves for many reasons.

Community or neighbourhood centre

A smaller sensor set answering the few questions that matter, without the cost of a full journey-analytics deployment.

Mixed-use development

Retail, leisure and office traffic distinguished, since a lunchtime office population is not the same commercial audience as a weekend shopper.

UAE & GCC considerations

Malls occupy a different social position here than in many markets: they are primary destinations for dining, leisure and family time rather than purely retail, which shapes every pattern in the data. Traffic concentrates heavily in evenings and at weekends, dwell times are longer, and a substantial share of visits are not shopping trips at all — so a capture-rate analysis that assumes shopping intent will misread whole zones.

Seasonal patterns are pronounced and worth modelling explicitly. Summer drives traffic indoors and lifts daytime footfall; Ramadan reshapes the trading day entirely with late evening peaks; Eid and school holidays produce their own profiles; and tourist share varies sharply by season and by centre. A year-on-year comparison that ignores the movement of Ramadan through the calendar produces conclusions that are simply wrong, which is a reporting design decision rather than a data problem.

Implementation approach

  1. 1
    Metric definition workshop Agree with asset management and leasing what each number means and how staff and re-entries are treated. Doing this after deployment means renegotiating figures already used commercially.
  2. 2
    Question-led sensor design Place sensors to answer the specific questions the asset team asks, rather than deploying uniform coverage and hoping the analysis emerges.
  3. 3
    Baseline and validation Manual validation counts against sensor output at each type of location, which establishes accuracy claims that will later be challenged.
  4. 4
    Historical reconciliation Where replacing Wi-Fi analytics, explain the discontinuity rather than presenting a step change as a market movement.
  5. 5
    Reporting design Separate views for asset management, leasing and tenants, because a single report serves none of them well.
  6. 6
    Seasonal calibration Build Ramadan, Eid, school holiday and summer patterns into the reporting model so comparisons are meaningful in this market.

Why Swedish Technology

  • We tell you that Wi-Fi probe analytics has been degraded by MAC randomisation, which many centres are still paying for without being told.
  • Metric definitions are agreed before deployment, because a footfall number that a tenant disputes has no commercial value.
  • Counting is anonymous and performed at the edge — no facial recognition, no demographic inference, no images leaving the sensor.
  • Sensor health is reported alongside counts, so a failed counter is never mistaken for a market decline.
  • Ramadan, Eid and summer patterns are built into the reporting model, because year-on-year comparisons here are otherwise wrong.

Limitations & prerequisites

  • Unique visitor measurement is genuinely hard without consented identification. Any vendor quoting confident unique-visitor figures from passive sensing should be asked how, particularly after MAC randomisation.
  • Wi-Fi probe analytics undercounts and cannot support reliable repeat-visit analysis on modern devices. Connected-session measurement remains valid; passive probing largely does not.
  • Counting accuracy varies by location type. Threshold counting is highly accurate; wide-area counting in crowds is less so, and the difference should be stated per measurement point.
  • Conversion analysis requires tenant sales data, and tenant willingness to share it is usually the constraint rather than the technology.
  • Footfall explains traffic, not intent. A busy zone is not necessarily a commercially productive one, which is why capture rate matters more than passing counts.
  • References to data protection obligations are general guidance, not legal advice.

FAQ

MAC address randomisation. Modern iOS and Android devices present a different, randomised hardware address when probing for networks, so one phone appears as many devices. Counts are inflated in some configurations and depressed in others, and repeat-visit analysis — the main reason centres bought these systems — is no longer dependable.

Sensor-based counting: 3D stereo sensors at thresholds and camera-based counting with edge analytics for wider zones. It is unaffected by phone behaviour, considerably more accurate at entrances, and produces counts rather than device identifiers.

Whichever you have defined and can defend — and it should not be the entrance count. Tenant passing traffic and entries are what a tenant can act on, and a capture rate tells them something useful about their shopfront. A centre-wide total invites a dispute about staff and re-entries.

No. Facial demographic estimation processes biometric data about people who did not choose to be measured, its inference is less reliable than the marketing suggests, and the commercial questions a mall needs answered do not require it.

By identifying them explicitly and reporting them separately rather than leaving them in the headline. Staff entrances, service routes and car park re-entry patterns all inflate raw counts, and a figure that survives a tenant's scrutiny is worth more than a larger one that does not.

Where tenants share sales data, yes — capture rate and conversion by unit are the most useful analyses available. In practice tenant willingness to share is the constraint, and it is worth addressing as a leasing conversation rather than a technical one.

Sometimes for zone-level counting, rarely for threshold counting where your commercial figures come from. Security cameras are positioned for identification and coverage, which is a different optimisation from accurate counting.

Explicitly, as its own pattern. It reshapes the trading day with late-evening peaks and moves through the Gregorian calendar each year, so a naive year-on-year comparison produces conclusions that are simply wrong. That belongs in the reporting model rather than in a footnote.

Discuss your site with an engineer

Tell us the venue, the expected visitor volume and the systems you already run. We reply with a technical view, a realistic scope and the next sensible step — a site survey, a working demonstration, or a full technical and commercial proposal.

+971 56 404 6555 · info@swedishtechnology.com

Sources & evidence

  1. UAE Federal Decree-Law No. 45 of 2021 — Personal Data Protection Law — Governs collection, retention and cross-border transfer of visitor personal data in the UAE.
  2. Apple — Wi-Fi privacy and private Wi-Fi addresses — Documentation of MAC address randomisation behaviour that affects Wi-Fi based footfall measurement.
  3. UAE Government portal — data protection — Overview of UAE personal data protection requirements applicable to visitor measurement.

Vendor and product names are trademarks of their respective owners; references are for technical context and do not imply partnership, certification or endorsement.