How to Choose Shopping Center Analytics

A leasing director sits across from an anchor tenant demanding a rent reduction. The tenant's argument: "Your mall traffic is down, our sales prove it." The leasing director has a footfall report from the entrance counters — but no way to show whether traffic past that tenant's storefront actually dropped, or whether the tenant is simply converting fewer of the shoppers who walked by. That gap between building-level counts and unit-level truth is where most analytics purchases either pay for themselves or quietly fail.

If you have already read the generic advice — "define your KPIs, compare vendors, ask for a demo" — this article assumes you are past that. What follows is what actually separates a shopping center analytics platform you will still be using in year four from one that becomes an unread dashboard by month six.

Start with the disputes you need to win, not the dashboards you want to see

Analytics vendors sell visualisation. Mall operators buy evidence. Before evaluating any platform, list the five recurring arguments in your center that currently get settled by opinion: turnover rent disputes, CAM allocation pushback, marketing spend attribution, lease renewal negotiations, and zone-level rent pricing. Then ask each vendor to show you — with their real interface, not slides — exactly how their data would resolve each one.

This test kills weak platforms fast. A system that only counts mall entrances cannot tell you whether a corridor renovation shifted traffic toward the food court. A system without tenant sales integration cannot distinguish a traffic problem from a conversion problem — which is precisely the distinction that decides whether the tenant gets a rent concession or a performance conversation.

Interrogate the accuracy claim, because most of them are marketing

Every vendor claims high accuracy. Almost none will put it in the contract. That is the tell. Ask three questions:

• Is accuracy contractually guaranteed, and at what floor? A serious provider commits to a minimum — Vemco Group, for example, contracts at a 96% minimum, with typical real-world performance of 98–99% where lighting, entrance layout and visitor behaviour allow. Note the honesty in that phrasing: conditions matter, and any vendor promising a flat 99% everywhere has not measured a mall entrance with a revolving door, a stroller cluster and low winter light.
• How is accuracy validated after installation? Manual count audits against sensor data should be part of commissioning, not an optional extra you discover you needed later.
• What happens when a sensor drifts? Occlusion, re-merchandised entrances and seasonal decorations all degrade counts over time. Ask who monitors data health and how quickly anomalies are flagged.

Why does a few percentage points matter? Because turnover rent, per-capita spend and conversion benchmarks are all ratios built on the count. A 10% counting error does not produce a 10% error in your conclusions — it can flip a tenant from "underperforming" to "outperforming" and invalidate the negotiation you built on it.

Tenant sales data is the half of the equation most platforms ignore

Traffic alone tells you where people went. Traffic combined with tenant revenue tells you what that traffic was worth — and that is the number leasing and asset management actually need. The practical problem is collection: most malls still gather tenant sales through monthly spreadsheets, emailed late, formatted inconsistently, and impossible to reconcile against daily traffic patterns.

This is where platform architecture matters more than dashboard aesthetics. A combined setup like VemCount with VemTenant automates tenant revenue reporting alongside traffic, so conversion, sales per visitor and engagement can be benchmarked across tenants on a consistent basis. That benchmarking capability changes leasing conversations structurally: instead of comparing a tenant against their own last year, you compare them against the traffic they actually received and against comparable units in the same zone. A fashion tenant converting at half the rate of its corridor neighbours, on identical footfall, has a store operations problem — not a landlord problem.

When evaluating, ask specifically: how do tenants submit revenue data, how much manual chasing does it require, and can the system enforce submission deadlines? The answer predicts whether you will have usable cross-tenant benchmarks or a database full of gaps.

A practitioner's warning: sensor placement decisions are lease decisions

Here is something implementers know and buyers rarely consider: the sensor placement plan you approve at installation determines which questions you can answer for the next five to seven years. Operators routinely instrument main entrances and skip inter-zone transition points — the escalator landings, corridor junctions and car park connections — because they seem secondary. Then, two years later, asset management wants to justify differentiated rent per zone or measure how a new anchor redistributed flow, and the data simply does not exist. Retrofitting those points mid-lease-cycle costs more and, worse, leaves you without the historical baseline. Bring your leasing team into the sensor layout meeting. It sounds bureaucratic; it is the cheapest decision insurance you will buy.

Evaluate the vendor for year four, not month one

Shopping center analytics is a long relationship. Entrances get remodelled, tenants churn, reporting requirements change with each new asset manager. Weight your evaluation toward longevity signals:

• Multi-property scale. If you operate a portfolio, demand centralised benchmarking across centers, not per-site logins. A provider processing millions of data points daily across global sites has already solved the aggregation problems you will hit at scale.
• Sensor flexibility. Hardware-agnostic platforms let you mix technologies per location and swap sensors without losing historical continuity. Vendor lock-in at the hardware layer is where analytics budgets go to die.
• Data ownership and export. Confirm in writing that historical data is yours, exportable via API, and survives contract termination. Ask for the API documentation before signing, not after.
• Reference sites that resemble yours. A vendor whose references are all standalone stores has not dealt with multi-entrance atriums, shared corridors or tenant data politics.

The decision framework in one paragraph

Choose the platform that can resolve your five most expensive recurring disputes with contractually guaranteed accuracy, that automates tenant revenue collection rather than assuming spreadsheets will arrive, that lets your leasing team benchmark conversion across tenants and zones, and whose sensor plan was designed with your five-year leasing strategy in the room. Everything else — dashboard colours, AI buzzwords, demo polish — is secondary to those four capabilities.

If you are comparing shopping center analytics providers and want to see how combined traffic counting and automated tenant revenue benchmarking would work in your specific center — zone by zone, tenant by tenant — talk to the Vemco Group team at vemcogroup.com/contact-us and bring your hardest leasing dispute to the conversation. That is exactly the kind of question the platform was built to answer.