Why footfall is not sales, and what to put next to it
A busy street does not mean busy tills. Why footfall and sales part ways, which other figures close the gap, and how to compare footfall with your own sales fairly.
Footfall tells you how many people-hours are spent around a place; sales tell you how many of those people bought something from you. The two are linked but not the same, and they part ways for ordinary reasons: the crowd is passing through, it is the wrong crowd, it is there at the wrong hour, a rival catches it first, or your door is hard to find. Use footfall as the size of the opportunity, then put your own sales, the competition and the people who live nearby next to it before you decide anything.
This is for store managers, franchise and expansion teams, landlords and analysts who are tempted to rank sites or judge a branch by footfall alone. It lays out the gap, the figures that help explain it, a made-up example, the mistakes, and an AI employee that brings footfall and your sales into one weekly view.
Where footfall and sales part ways
- Presence, not visitors. Mobility Footfall counts people-hours: a commuter waiting 20 minutes for a bus adds a third of an hour; an office worker at her desk all day adds eight. Neither is a shopper by default.
- Passing through. A street between a station and offices can be packed at 08:30 with people who will not stop.
- The hour does not match. If the busiest hour is 08:00 and you open at 10:00, the crowd is gone.
- The wrong crowd. Students around a premium jeweller, or office workers around a toy shop.
- Someone else gets there first. Ten cafes on a busy corner share the same people.
- The site itself. A unit up a flight of stairs or hidden by scaffolding converts poorly whatever the street does.
The figures that close the gap
No single number replaces sales, but a few together explain much of the difference:
| Question | Figure | Where it comes from |
|---|---|---|
| How busy is it, and when? | footfall_daily, footfall_peak_hour, footfall_by_part | Mobility Footfall |
| Who shares the crowd? | nearby_count and the nearest rivals | Nearby places around each site |
| Who lives here, not just passes? | population and age groups | Demographics, in the countries it covers |
| What did we sell? | your own sales by store and week | My data or your database |
What to put next to footfall when you judge a site or a store.
Population is not available everywhere: it covers countries such as France, Canada, India, Thailand, Egypt and Australia, but not the United Kingdom or the United States. Footfall covers most of the world from 17 October 2026, though not yet Australia. Each day of footfall arrives about 10 days later.
How to compare footfall with your own sales
The useful number is a ratio you work out yourself: sales for a period divided by the footfall around the store over the same days. It is not a conversion rate (people-hours are not people), but it lets you compare your own stores fairly and follow each one over time.
- Pick a period footfall has already arrived for, ending about 10 days ago.
- Read footfall_daily for each store over exactly those days, with the same distance around each (200 m is a good start).
- Take your sales for the same days from your own records.
- Divide sales per day by footfall per day for each store, and rank the stores by it.
- Look hardest at the extremes: busy streets with a low ratio and quiet streets with a high one.
A made-up example in Sao Paulo
Invented figures for illustration. A pharmacy chain compares four of its branches in Sao Paulo over the same 14 weekdays:
| Branch | Weekday footfall, 200 m | Sales per weekday (reais) | Sales per 1,000 people-hours | Pharmacies within 500 m |
|---|---|---|---|---|
| Avenida A | 48,000 | 19,000 | 396 | 9 |
| Shopping street B | 22,000 | 17,600 | 800 | 3 |
| Residential C | 9,500 | 11,400 | 1,200 | 1 |
| Station D | 61,000 | 12,200 | 200 | 6 |
Invented figures for illustration; not real figures for Sao Paulo or any chain.
Station D has the most footfall and the weakest ratio: its busiest hour is 07:00, before the branch opens, and six rivals sit inside the station's reach. Residential C has the least footfall and the best ratio: one rival, regular local customers. Ranking by footfall alone would have put D first for investment and C last. The chain instead tests longer morning hours at D and looks for more residential corners like C.
Mistakes to avoid
- Calling the ratio a conversion rate. It divides sales by people-hours, not by people who walked in.
- Mixing periods. Footfall for October against sales for November tells you nothing. Use the same days.
- Different distances. A 500 m circle around one store and 200 m around another makes the ratios incomparable.
- Judging a new site by footfall alone. Add rivals, residents where they are measured, and the hours the street is busy.
- Ignoring the hour. Compare footfall_peak_hour with your opening hours before blaming the street.
Put it in front of you with an AI employee
- Schedule: every Monday at 08:00.
- My data with your stores and their last fortnight's sales (or Database query from your own database).
- Mobility Footfall: 200 m, 14 days, with Footfall and Busy hours.
- Nearby places around each store, set to count your kind of rival within 500 m.
- Calculated field: the sales divided by footfall_daily, per 1,000 people-hours.
- Sort and limit by that ratio, lowest first.
- Email the list to the operations team.
What lands each Monday is every store with its footfall, busiest hour, rival count and ratio, the weakest first, with the dates covered. Make sure the sales you load cover the same days as the footfall window. For site decisions rather than store reviews, the templates where to open next and where to open my next cafe put competition and people next to each candidate.
Questions
Is high footfall a good sign for a new shop?
It is a sign that people are around, not that they will buy. Check the busiest hour, the rivals nearby and, where measured, who lives there before you sign.
Can I work out a conversion rate from footfall?
Not a true one. Footfall is people-hours of presence, not people who entered. Sales divided by footfall is still useful to compare your own stores over the same days.
Why does my busiest store by footfall sell the least?
Common reasons are a crowd that is passing through, a peak hour outside your opening hours, many rivals sharing the crowd, or a unit that is hard to see or reach.
Can xMap Flows read my sales automatically?
Only from a source you connect: a table in My data, a Google Sheets file, or your own PostgreSQL, BigQuery or Snowflake database.