How to export footfall data to Excel: daily, hourly and day-of-week figures
Three ways to get measured footfall into a spreadsheet, which fields to keep, how to split the hourly profile into columns, and how to build a running weekly record.
Part of the guide Location intelligence automation
To export footfall data to Excel from xMap Flows, run a flow with the Mobility Footfall block and download that block's results as an Excel file from the run panel; for a file that refreshes itself, send each run's rows to Google Sheets or connect Excel to a live feed of your results. Each place becomes a row with its average day, busiest hour, hour-by-hour profile, busiest and quietest day and, if you ask for it, the trend on the week before.
This is a practical guide for analysts and managers who live in spreadsheets: which export route to pick, what each column means, how to turn the hourly text into 24 columns, a worked example, and the common mistakes. It ends with a flow that adds a fresh row for every store each week.
Three ways to get the figures out
| Route | Best for | How |
|---|---|---|
| Download from the run panel | A one-off analysis | Open the run, press See all on the Mobility Footfall block, pick the columns and press Download Excel |
| Rows sent to Google Sheets | A record that grows each week | Add the Google Sheets app block after Mobility Footfall, set to add a row per place |
| A live feed of results | A workbook that refreshes on open | On Results, make a Live feed and use its CSV address in Excel's From Web |
Ways to get Mobility Footfall figures into a spreadsheet.
The first route is described in See every item each block passed on; the third in Results in Power BI, Looker Studio or Excel. The second needs a Google Sheets connection; Excel opens the sheet's download as an .xlsx file.
What each column means
Mobility Footfall adds these fields to every place, depending on what you pick under Return:
- footfall_daily: the average day's people-hours of presence around the place in the window. It is an average, not a list of days.
- footfall_days, footfall_from, footfall_to: how many days had data and which. Keep these: they tell you how much weight a row can carry.
- footfall_peak_hour, footfall_peak: the busiest hour in local time and its average.
- footfall_by_hour: the whole average day as text, hour by hour: "00:00 1,240, 01:00 980, ...".
- footfall_morning_pct, footfall_midday_pct, footfall_evening_pct, footfall_night_pct: the share of the day in each part, as numbers ready to chart.
- busiest_day, quietest_day: the days of the week.
- footfall_trend, footfall_trend_pct: the latest 7 days against the 7 before, as words and as a number.
- footfall_timezone: the zone the hours are counted in, useful when stores span several countries.
Turning the hourly profile into columns
footfall_by_hour arrives as one cell so the export stays tidy. For a chart of the day you want 24 columns. Two easy ways:
- In Excel: select the column, use Data, Text to Columns, split on the comma followed by a space, then split again on the space after each hour. Power Query does the same and repeats it every time the file refreshes.
- Before the export: add a Custom code block after Mobility Footfall that splits the text into fields named h00 to h23, so every export already has 24 numeric columns.
A worked example
This example is made up. A coffee chain has twelve stores in Madrid and Bogota and wants a weekly sheet for the operations meeting. The flow runs every Monday with the window at the last 14 days and appends one row per store to a sheet, with the run date, footfall_daily, footfall_peak_hour, the four part shares, busiest_day and footfall_trend_pct. After six weeks, a pivot table shows two Bogota stores whose evening share keeps climbing while their trend stays positive, and the team extends their opening hours by an hour.
Note what the sheet can and cannot show. Each row is the average day of a two-week window, so consecutive rows overlap by a week and move smoothly. There is no row per calendar day: the block does not return a daily series. The weekly append is how you build history.
Mistakes to avoid
- Adding people-hours across stores and calling it customers. The sum is a measure of busyness, not a visitor count.
- Comparing rows with different windows. Keep the window and the circle the same for every run, or the columns are not comparable.
- Mixing time zones. Hours are each store's local time. Keep footfall_timezone in the sheet when stores span countries.
- Dropping footfall_days. A row built on a handful of days looks just like a full one once it is in a pivot table.
- Expecting last week to be in the sheet. Each day arrives about ten days later, and the data starts on 17 October 2026, so early runs cover fewer days than their window.
The flow that fills the spreadsheet
- Schedule: every Monday at 06:00.
- My data: your stores with a name and position.
- Mobility Footfall: 200 m, last 14 days, with Footfall, Busy hours, Busiest days and Trend.
- Custom code (optional): split the hourly profile into 24 columns and add the run date.
- Google Sheets: add a row per store to the weekly sheet.
- Email: a short note to the operations lead with the link.
Every Monday a new block of rows appears in the sheet and the email says which stores moved most. For network-wide reading, the monthly brief on your store network and What opens near my stores sit well beside it; see also Google Sheets, Docs and Drive, the retail page and the location intelligence automation guide.
Questions
Can I get footfall for each calendar day?
No. The block returns an average day over the window, plus the hourly profile and the busiest and quietest days. A weekly scheduled run that adds rows to a sheet builds a running record.
Which export keeps the file up to date?
Sending rows to Google Sheets on a schedule, or a live feed of your results opened with Excel's From Web. A download from the run panel is a one-off.
Why are the hourly figures in one cell?
To keep the export compact. Split them with Text to Columns or Power Query, or with a Custom code step before the export.
Are the hours in my time or the store's?
The store's own local time. footfall_timezone says which zone, which matters when your stores are in several countries.