FlowsBook a callSign inCreate free accountSign up
Footfall and mobility

Foot traffic at convention centres: the rise on show days and the streets that feel it

How to see a trade show in the streets: measure the halls, the hotel rows and the quiet blocks behind them, week by week, and read who gains when a big event is on.

Part of the guide Location intelligence automation

By the xMap team · · 6 min read

Foot traffic at convention centres jumps on show days, but the jump is not shared evenly. The halls and the walk from the nearest station swell first, the hotel and restaurant streets within a few hundred metres take a second wave in the evening, and blocks further out often barely move. You can see all three by measuring several points around the venue every week with the Mobility Footfall block and laying the weeks side by side.

This guide is for venue operators, hotel revenue teams, restaurant owners near an exhibition ground, and the councils and transport teams who deal with the crowd. It explains what to measure, how to spot a show week in the figures, a worked example, the traps, and an AI employee that keeps the record for you.

What footfall can and cannot say about a show

Mobility Footfall reports people-hours of presence around a point: a delegate who stays six hours in the halls counts six times. That makes it a good measure of how crowded an area felt, and a poor stand-in for badge scans or ticket sales. The organiser's registration list tells you how many came; footfall tells you how heavily the surrounding streets were used while they were there.

Two limits shape everything below. Each day arrives about ten days after it happens, so a show that ends on a Thursday appears in the figures the week after next. And the data starts on 17 October 2026, so you cannot pull last year's edition of a show for comparison yet: the record builds from now on.

Choosing the points around a venue

One point on the venue's roof with a wide circle mixes the halls with car parks and side streets. Several small points tell a clearer story. A sensible set for one exhibition centre:

  • The entrance or main hall, with the circle at 200 m so it reads the venue's own block of the map.
  • The walk from the station or bus terminal, where queues form before doors open.
  • The hotel row, usually within 500 m, where the evening wave lands.
  • The nearest food street, which feels lunchtime overflow when the halls' own catering is busy.
  • A control block 1 to 2 km away with no link to the venue, so a city-wide busy week does not fool you.

Put these in a table on the My data page with a name and a latitude and longitude for each. The My data block brings them into the flow as places.

Reading a show week

Because the block reports an average day over a window, the cleanest way to isolate a show is a weekly series: run the flow every Monday and keep each run's figures in a row. With the window at the last 14 days, the Trend field sets the newest 7 days against the 7 before, so the week that contains the show stands out against the weeks around it. Look at three things together:

  1. The size of the rise at each point. Divide the show week's footfall_daily by the average of the two quiet weeks before it.
  2. The shape of the day. footfall_peak_hour and the morning, midday, evening and late night shares show whether the crowd stayed for dinner or went straight back to the station.
  3. The control block. If it rose by the same share, something else was going on in the city that week, a holiday or a festival, and the show was not the cause.

A worked example

The figures in this example are made up to show the reading. An exhibition centre in Singapore hosts a three-day industry fair from Tuesday to Thursday. The weekly flow measures five points. In the fair's week, the main hall's average day is roughly two and a half times the two weeks before; the station walk is about double; the hotel row rises by around half, with its evening share climbing from a third of the day to nearly half; the food street rises a little at midday only; the control block is flat.

Three readings follow. The hotel row, not the food street, is where delegates spend their off-hours, so a restaurant group would open its second branch there. The station walk carried most of the crowd before 10:00, which is useful for the transport team planning extra staff next time. And the flat control block confirms the rise belongs to the fair.

In Sao Paulo, where xMap also measures trips, the same flow can add Where visitors come from for the month of a big show at an expo centre: the districts the trips set off from and how people travelled. That part is not available in other cities yet.

Mistakes to avoid

  • Calling people-hours attendees. Report it as how busy the area was, never as a head count.
  • Expecting the figures next morning. Plan the review for about ten days after the show closes.
  • Using one huge circle. At 500 m around a big venue you average halls, a motorway and a park into one number.
  • Skipping the control point. Without it, a school holiday week looks like a successful show.
  • Comparing a show against last year. There is no last year in this data yet; compare against the weeks around it instead.

Let an AI employee keep the record

A small flow keeps the weekly series going without anyone remembering to run it:

  1. Schedule: every Monday at 08:00 in the venue's time zone.
  2. My data: the five points around the venue.
  3. Mobility Footfall: 200 m around each point, last 14 days, returning Footfall, Busy hours, Busiest days and Trend, which compares the latest 7 days with the 7 before.
  4. Traffic Flow (optional): live speeds and the jam factor on the roads around each point at the moment of the run, useful when the flow also runs during a show.
  5. xMap LLM: a short note, read from the trend, saying which points moved most against the week before.
  6. Email to the events and hotel teams, and a row per point added to a shared file in Google Sheets.

What lands in the inbox each Monday is a table of the five points with their average day, their busiest hour and their evening share, and two lines of plain words. After a season of shows, the sheet becomes the venue's own record of which events actually filled the district. For related flows, see Hotels near the convention centre for room blocks and Road closures around the venue, for guests on the day, the events and venues page, and the wider location intelligence automation guide.

Questions

Can footfall tell me how many delegates attended?

No. It measures people-hours of presence around a point, so long stays count more. Use your registration data for attendance and footfall for how busy the area was.

How soon after a show can I see its effect?

Each day arrives about ten days later, so plan the review for the week after next.

Can I compare this year's show with last year's?

Not yet. The footfall data starts on 17 October 2026, so compare a show week with the weeks before and after it until a full year has built up.

Which streets usually gain most?

It varies by venue. Measure the hotel row, the food street and the station walk separately and let the figures say; a control block further away tells you whether the rise is the show's.

Templates that do this

Read next

More on footfall and mobility · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.