xMap data

Mobility Footfall

Mobility Footfall shows how busy the area around each place is, from xMap’s own mobility data: footfall per day, the busiest hour and day of the week, how the day splits between morning, midday, evening and late night, the trend on the week before, and where visitors come from and how they travel. Footfall is people-hours of presence, scaled from a panel of devices to the whole population: someone who stays three hours counts three times, so it is a measure of how busy a spot is, not a count of unique visitors. Everything is an aggregate: never a person, a device or a single trip. Footfall covers most of the world from 17 October 2026 (not yet Australia), each day arriving about 10 days later; where visitors come from so far covers Sao Paulo. A place with no data yet says so, and costs nothing.

In the editor: How busy the area around each place is, from xMap’s own mobility data: footfall per day, the busiest hour and day of the week, how the day splits into morning, midday, evening and late night, the trend on the week before, and where visitors come from and how they travel (trips). Aggregates only, never a person or a device. Footfall is people-hours of presence scaled to the whole population, not a count of unique visitors. Footfall covers most of the world from 17 October 2026 (not yet Australia); each day arrives about 10 days later, so the time window ends 10 days ago; hours are each place’s own local time. Trips (where visitors come from) so far cover Sao Paulo. When the newest days are later than usual, it uses the newest days there are and says which; a place with no data yet says so.

Settings

Around each place (m)

A slider

How far around each place footfall is added up, in metres. Up to 200 m it is the place’s own block of the map (an H3 cell of about 0.1 km²); wider, every block whose middle is inside the circle.

The place’s own block of the map (an H3 cell of about 0.1 km²). Places that share a block share one search; at most 50 places a run.

Time window

Pick one

The days the figures cover. Each day’s footfall arrives about 10 days later, so the window ends 10 days ago, and never goes before 17 October 2026 (when the data starts). A window longer than a month is read a month at a time. When its days are later than usual, the newest days there are are used and the place says which.

Each day’s footfall arrives about 10 days later, so the window ends 10 days ago (the data starts on 17 October 2026). When the newest days are later than usual, the newest days there are are used, and footfall_from, footfall_to and footfall_note say which days.

  • Last 7 days
  • Last 14 days
  • Last 30 days
  • Last 90 days

Days

Pick one

All days, weekdays only, or weekends only. The weekend follows the place: Friday and Saturday in most of the Gulf, Saturday and Sunday elsewhere.

The weekend follows the place: Friday and Saturday in most of the Gulf, Saturday and Sunday elsewhere.

  • All days
  • Weekdays
  • Weekends

Return

Pick one or more

Which figures each place gets.

footfall_daily is the average day’s people-hours of presence.

  • Footfall Adds footfall_daily, footfall_days and the dates covered.
  • Busy hours Adds footfall_peak_hour, footfall_peak and how the day splits (footfall_by_part and a share for each part).
  • Busiest days Adds busiest_day and quietest_day.
  • Trend Adds footfall_trend: the last 7 days against the 7 before (needs 14 days or more).
  • Where visitors come from Reads the trips that end at the place: visitors_from, trip_modes, trip_purposes, avg_trip_km, avg_trip_min and ride_hailing_pct.

What comes out

Each item that leaves the block carries these fields, to use in the blocks after it as {{field}}.

Added to each place

Each field comes with the matching choice under Return. The place keeps all its own fields. A place with no data yet gets footfall_note instead, and empty numbers.

  • footfall_daily: The average day’s footfall: people-hours of presence around the place, scaled to the population.
  • footfall_days: How many days had data (footfall_from and footfall_to: the first and last of them, in the place’s own time).
  • footfall_timezone: The place’s time zone, in which the hours and days are counted.
  • footfall_peak_hour: The busiest hour of the day, in the place’s own time.
  • footfall_peak: The average footfall in that hour.
  • footfall_by_part: How the day splits.
  • busiest_day: The busiest day of the week, and quietest_day the quietest.
  • footfall_trend: The last 7 days against the 7 before; footfall_trend_pct as a number.
  • visitors_from: The districts the trips that end there come from, with their share (groups of 5 trips or more).
  • trip_modes: How those trips travel.
  • avg_trip_km: How far they come, on average (avg_trip_min: how long they take).
  • footfall_note: Why a place has no figures (no data here yet, no location, not measured), or which days the figures are from when they are fewer than asked or the newest days there are.

How to use it

Real estate

Footfall next to the competitor count

Footfall sits next to the competitor count for xMap LLM to score the site: a busy spot with few rivals scores high.

Retail

Staff where the people are

A chain wants to compare the busiest hours of its stores to plan its staff shifts.

Before: The same shifts in every store.

With the flow: Each store’s busiest hour and day in the sheet, ready to plan shifts from.

Banking and payments

Where to put the next ATM

Sort and limit on footfall_daily puts the busiest candidate sites first.

Marketing agencies

Busy hours around a client’s stores

xMap LLM reads footfall_peak_hour, footfall_by_part and footfall_trend and writes a suggestion for each store.

Healthcare

Where patients would come from

A clinic group is choosing between three sites and wants to know how busy each is and where people around it come from.

Footfall, trips and residents side by side for each site.

Events

Weekend against weekday

Two Mobility Footfall blocks, one for weekends and one for weekdays: how much busier each venue gets at the weekend.

Good to know

  • Footfall is people-hours of presence scaled to the whole population, not unique visitors: compare places with each other, not with ticket counts.
  • Footfall covers most of the world from 17 October 2026 (not yet Australia); trips (where visitors come from) so far cover Sao Paulo. Hours are each place’s own local time, and Weekends follow the place (Friday and Saturday in most of the Gulf).
  • Each day’s footfall arrives about 10 days later, so a window of the last 7 days covers the 7 days up to 10 days ago. When those days are later than usual, the block uses the newest days there are and says so in footfall_note, with footfall_from and footfall_to. A place with no data yet says "No footfall data here yet"; it is not zero people, and it costs nothing.
  • Aggregates only: no person, device or single trip ever leaves xMap, and a group of fewer than 5 trips is not shown.
  • Places close together share one search (the same block of the map), and a search is charged only when it found data.
  • At most 50 places a run; a long window or a wide circle takes more calls, and a search that would be very long is cut short and says so.
  • Do not use it to single out or follow anyone: the Terms forbid it.

Works well with

  • Nearby places: Places around a point from xMap’s own places database (300M+ places, refreshed every month): pick the types of place (more than 5,000, such as Restaurant, Cafe, Pharmacy, Hospital or Gas station, or a whole group of them) and how far to look.
  • Demographics: Who lives in an area: the number of residents, men and women, and nine age groups, from xMap’s population grid (hexagons of about 0.1 km², about 100 countries).
  • Traffic Flow: How the traffic is moving on the roads around each place, right now: the current speed and the free-flow speed in km/h, how jammed the roads are (a jam factor from 0, free, to 10, standstill), the congestion as a percentage, the level in words, how many roads were measured and closed, and the busiest road.
  • xMap LLM: Tell the AI what to do in plain words.
  • Sort and limit: Puts the items in order, and can keep only the first ones: the 10 best rated, the 20 nearest, the highest fit scores.
  • Filter: Keeps only the items that match a rule.
  • My data: Brings in a table you uploaded or a list you saved on the My data page: your stores, customers, target accounts or sites.
  • Email: Sends one email per run with all the items, or one email per item.

Stories with it

Help articles

Guides and terms

  • Foot traffic data: Estimates of how many people visit a place, usually from mobile devices.

Try it

Build a flow with Mobility Footfall on the home page, no account needed, or book a call. Try it live