How many were here — choosing the right people report

"How many people were on Level 2 yesterday?" sounds like one question. Omaya has several reports that each answer a different version of it, and they give different numbers because they count different things: tags, door crossings, heads in a room, named people. None of them is wrong. This guide is about picking the one that answers the question you were actually asked, and reading it the way it was meant.

Start from the question

The question	The report	What it counts
How many were in this place on a day, and which place is busiest?	Reports › Footfall	The tags people carry, each counted once per place per day and split into staff, visitors and unassigned tags, beside the doors' entries and the most inside at once
How many came through the doors, and how many are inside now?	Reports › Enter / Exit	Crossings at doors that have a people counter, by direction and hour; people inside is entries minus exits since midnight
How full was this room, hour by hour?	Reports › People Count	The most people at once and the average in each hour, per zone, from a counting sensor or from the tags present
Which rooms are too big or too small?	Reports › Space Utilisation	Each zone's share of its opening hours with someone in it, its typical and peak headcount against capacity
Who was in, when did they arrive and leave?	Reports › Attendance	Named people on the Entity page: first in, last out and time on site, per person and day
How much were our assets used, and which are missing?	Reports › Asset Utilisation	Asset entities only: hours seen, time in use, moves, and the assets not seen for over 3 days
Do the same people keep coming back?	Reports › Loyalty	Registered devices per day, new or returning, and how long since each was last here
Is this place busier than that one, or than last month?	Reports › Zone compare	The same figures for two zones, or one place over two periods, with the change
How many are in there right now?	Monitor › Right Now	Live, not a report: see Watching people and assets

Two shortcuts. A figure for a landlord, a board or a monthly pack is almost always Footfall. A question about a person by name is always Attendance.

Devices, not people

Most of these reports start from tags: the badges, key fobs and asset tags you have registered on the Devices page. Three things follow.

Only registered tags are counted. When a gateway hears a Bluetooth device that is not registered to your organisation, Omaya does not keep it, so a visitor's phone or a passer-by's watch is never in Footfall, Loyalty or Attendance. Before October 2026 the Footfall page said it counted those devices too; it never did.

A visitor without a tag is seen only by something that counts bodies. That is a people counter on a door (Footfall's came in, Enter / Exit) or a counting sensor in the room, such as a radar (People Count, Space Utilisation, Right Now). If your visitors carry nothing, those are the only figures that include them.

A tag is a radio, not a person. Someone carrying two tags counts twice; someone who left their badge at home counts zero; a badge left on a desk overnight is "here" all night. Read every tag figure as tags, and say so when you pass it on.

People's tags and asset tags are counted apart. A tag bound to an asset on the Entity page, such as a trolley or a wheelchair, is an asset tag; every other registered tag, bound to a person or to nobody, is a person's. Footfall's People heard counts people's tags only, the same rule as the TV Dashboard's People seen today, and shows asset tags beside it as "+ N asset tags". So set each trolley and wheelchair up as an Asset on the Entity page, or it will be counted as a person (see People and assets).

A tag is sorted by what it was bound to at the time, hour by hour: a badge moved from a person to a trolley counts as a person's before the move and an asset's after. Days before 6 October 2026 were counted before the split existed and keep every tag under People heard.

Footfall's totals show per person heard: door crossings for every person's tag the gateways heard. When it climbs, more of the people coming through the doors are carrying nothing Omaya can hear.

Staff, visitors and unassigned tags

Footfall can split People heard three ways, by who held each tag at the time:

Group	Who is in it
Staff	Tags held by a person on the Entity page who carries your organisation's staff label
Visitors	Tags held by any other person on the Entity page, such as a badge handed out at visitor check-in
Unassigned	Registered tags bound to nobody

The three add up to People heard. Asset tags stay apart, as before.

The split needs one setting: which entity label marks staff. Until it is set, Footfall shows people as one figure and says People are not split into staff and visitors — no staff label picked.

Choose the label that marks staff

You need a role with Edit Organisation to change it (Admin, as shipped). Anyone else can see which label is chosen, but not change it.

1. Make sure your staff carry one label on the Entity page, for example Staff or Employee. See People and assets.
2. Open Reports › Footfall.
3. Click Staff label at the top right, beside Export CSV.
4. Under Which label marks staff?, pick the label. Each one shows how many people carry it. None — don't split people turns the split off.
5. Press Save.

Check it worked. The button now reads Staff: and the label's name, and the message under the list says Saved. The last 30 days are being recounted — reload in a few minutes. After a few minutes, reload the page: the people card shows staff, visitors and unassigned, the chart stacks them, and the tables and the CSV have Staff, Visitors and Unassigned columns.

Three things to know about the split:

• The label is read as it is today. When the last 30 days are recounted, a person labelled staff today counts as staff on those days too. Who held which tag on each day still comes from the binding history.
• Older days are not split. Splitting a day needs that day's list of tags, which Omaya keeps for 30 days, so days more than 30 days before you chose or last changed the label show people as one figure. The chart draws them as People (not split), and the staff and visitor averages say how many of the days they cover.
• A visitor without a tag is in the door counts only. Visitors appear in the split only when they are given a tag that is bound to them as a person.

The same split is in AI Reporting and in the footfall figures of the API.

Counted once per place

Footfall counts each tag once per place per day, however many rooms it went through.

At Northwind Tower, Mei Ling Tan arrives on Level 2, sits in the open office, goes to the pantry twice and spends the afternoon in Meeting Room 2A. In Footfall she is one person on Level 2 that day, one for Northwind Tower, and one in each of the three zones she was in. Add up Level 2's zones and you would count her three times.

That is why Footfall replaced Devices Detected in October 2026: Devices Detected added up its zones, and one floor read 16 for 10 devices. Two rules follow for every people figure:

• Places do not add up. A venue's figure is not the sum of its zones, and a location's is not the sum of its venues. Ask Footfall for the place itself: set Location, Venue or Zone to that place, and choose Rows by to break it down beneath.
• Hours do not add up to a day. Someone here all afternoon is in every one of those hours, and once in the day. Use Per: Day for daily figures.

What does add up is days. Footfall's Visits in the totals are each day's people added together, so a tag here on five days is five visits. That is the right figure for "visits this month", and the wrong one for "different people this month".

Door counts, and the most inside at once

Came in and left are the crossings counted by the people counters on the doors of the place. They count everyone, tagged or not, but only at doors that have a counter: a way in with no counter is invisible to them. Someone who steps out for coffee and comes back is two entries.

Most inside at once is entries minus exits, running hour by hour from midnight, never below zero. It is only as complete as the doors: a missed exit makes it too high until midnight, when it starts again. A counter that counted only one direction in the range is left out of it, and named above the table. A place with no door counter says so instead of showing 0.

Enter / Exit has the same figures per door and per hour, with People Inside Now when the range includes today (entries minus exits, running from midnight, never below zero).

Against capacity, and per 100 m²

A large floor will always hear more tags than a small meeting room. Footfall's totals put the two on the same footing in two ways.

Most inside as a share of capacity. A zone uses its own capacity. A venue uses the Capacity (people) on its form under Space › Venues, or, when that is empty, its zones' capacities added up. A location's capacity is its venues' added up. The whole organisation has none. Set the venue's figure when the zones' sum is not the real one: the fire certificate figure for a floor is usually higher, because corridors and open floor have no zone capacity. See Setting up a site.

People a day per 100 m². A zone's area is the area set on it, or the outline drawn on the floor plan. A venue's is its floor plan's scaled size, and a location's is its venues' added up. A place with no known area shows no figure.

Comparing periods, and a typical week

Compare with on Footfall puts the same place beside an earlier period: The period before (the same number of days just before your range) or Same dates last year. The cards show the change, the chart draws the earlier period behind yours, and the totals get a row for it.

A typical week averages each weekday and hour over the days of that weekday in your range, for People heard or Came in. It answers "when do we need reception staffed?" better than any single week. Pick at least four weeks so that each weekday has a few days behind it.

To put two places side by side, or one place over two periods of your choosing, use Reports › Zone compare. Its devices a day are once-per-place tags, asset tags included, its entries come from door counters only, and its people present come from a counting sensor where the room has one, else the tags seen there.

Missing days and older days

No data received. When the gateways of a place send nothing at all for a day, usually because of power or the network at the site, Footfall says No data received instead of showing nobody there. A day with data for less than half its hours carries a data for N of 24 h mark, and those days are named above the table. Attendance marks the same days no data, and the dashboard's visitor chart leaves a gap. An empty building still counts as reporting as long as its fixed sensors are still being heard.

— older than 30 days. Counting once per place needs that day's list of devices, which Omaya keeps for 30 days, so the count is made while the list still exists. Footfall started on 5 October 2026 and filled in the 30 days before, so it reaches back to early September 2026. For days before that, a zone's own figure and any hour are still exact, but a venue, a location or the whole organisation shows — rather than a sum that would count people several times. The same days are left out of the dashboard's visitor chart and of Impact Events' per-day rate.

Footfall takes up to 92 days at a time. Today is refreshed every 15 minutes, and a day is final the night after.

Data health on Space Utilisation and Attendance

A report can only count what reached Omaya. When a sensor's battery dies or a gateway loses power, the hours it missed are not empty rooms or absent people: they are hours nobody knows about. Space Utilisation and Attendance say how much of the data behind the dates on screen actually arrived, in a line under the headline figures. Space Utilisation also has a Data health tile beside Occupied, Seats needed and the cost figure, with the same answer as one percentage.

The line appears after the report has loaded, and follows the Venue and the dates you chose. It covers up to 92 days.

What it checks

Fixed sensors. The devices that stay in one place: sensors and beacons, not the tags people and assets carry, which leave the site every evening. Each one is expected to be heard at least once in every stretch of its own Silent threshold (minutes), rounded up to whole hours (on the device's form, under Advanced Settings; blank means 120 minutes). A sensor is not expected before the hour after it was added. The figure is the share of those stretches in which it was heard.

Only stretches that hold an opening hour on an open day are counted, the same hours the reports judge. A door counter or a switch speaks only when something happens, so a quiet night is not missing data. Opening hours come from System › Configuration, Opening hours card, or a venue's own; while Apply this schedule to reports is off, every hour of every day counts. See Organisation settings.

Gateways. How much of the time the gateways in the selection were up, from the same figures as Reports › Gateway Availability: every hour of the dates, leaving out the hours set as a gateway's Expected silence (quiet hours).

What each state means

The colour and the first words follow the worse of the two figures.

What you see	What it means	What to do
Green dot, Data health good.	At least 95% of expected sensor readings arrived, and gateways were up at least 95% of the time	Nothing. Read the report as it stands
Amber dot, Some data missing.	The worse figure is 80% to just under 95%	Read the line under it: it names the devices with gaps. Treat the figures that depend on them as a minimum, and open the devices named
Red dot, Much of the data is missing.	The worse figure is under 80%	Do not pass the figures on as they are. Find what went quiet (below), fix it, and run the report again for dates after the fix
Grey dot, Data health unknown.	There was nothing to judge: no fixed sensor was expected in the hours chosen and no gateway was counted. The line then says No fixed sensors or gateways in this selection.	Check the Venue and the dates

The rest of the line gives the figures behind the state, for example 82% of expected sensor readings arrived (14 fixed sensors) · gateways up 99.6% of the time (6). When the state is amber or red it adds Gaps are unknown, not empty: figures from those devices are a floor. A room whose counting sensor missed half the afternoon was at least as busy as the report says, possibly busier.

Worst: names up to five sensors under 95% and up to three gateways under 99%, worst first, with roughly how many opening hours each sensor missed or how many hours each gateway was down, and and N more when there are others. On Space Utilisation the tile adds how many devices have gaps.

Find what went quiet

1. On the data health line, press Device status. It opens Reports › Sensor Status, which shows each sensor's hours one by one.
2. Look at the sensors named after Worst:. A run of empty hours that starts on one day and never ends is a sensor that stopped: check its battery and that it is still in place. Empty hours every night or at the same time each day point at something switched off on a timer, or at a threshold that is too short for how often the sensor reports.
3. If the line names a gateway, press Gateway availability. An outage that hit several gateways at once is usually power or the network at the site; one gateway on its own is usually that unit.
4. For a sensor that only reports when something happens and is marked down for quiet hours inside opening hours, raise its Silent threshold (minutes) on Device → Sensor, under Advanced Settings, to the longest quiet spell you expect. The same setting decides when the sensor is reported silent elsewhere in Omaya.

Check it worked. Run the report for a day after the fix. The dot turns green and the device is no longer named after Worst:. Days before the fix keep their gaps: data that never arrived cannot be filled in later.

Having them emailed

System › Schedule Report sends a report on a schedule, so the weekly figure arrives without anyone remembering to run it. Your role needs Schedule Reports.

1. New schedule. Give it a name and choose the Report type: Footfall, Enter / Exit, People Count, Dwell Time or Space Utilisation for the people figures, Attendance for named people, Asset Utilisation for assets, among others. The form says in one line what each attachment holds.
2. Format: CSV for a spreadsheet, PDF to read.
3. Window (days): how far back it looks, 1 to 90. The people reports cover whole days on your organisation's clock, ending yesterday.
4. Venue: all venues, or one. Only that venue's figures go in the attachment.
5. Frequency and send at: daily, weekly on a weekday, or monthly on a day from 1 to 28, at an hour on your organisation's clock.
6. Recipients: administrators from the list, and any Extra emails outside Omaya. Extra addresses get the report but cannot open Omaya.

If you choose nobody, the report goes to your organisation's first administrator: the earliest Admin account that is active and has an email address. The form names that person before you save. If no such account exists, nothing is sent, and the form says so. Before October 2026 a schedule with nobody chosen never sent at all, so a schedule you had forgotten about may start arriving.

Each schedule's card has Test, which sends it now to its recipients, and Pause / Resume.

The mini apps' reports (Facility Management, Toilet Hygiene, Visitor Management, Energy) are scheduled here too, or from inside each app by the people who run it: see Scheduled reports from the mini apps.

Attendance has one row per person and day they were on site — first in, last out, minutes on site, visits and floors, with Operating day Yes or No — then a section per person: days present out of days counted, and the rate. Days counted follow your operating week when one is set (the venue's own week when the schedule is for one venue), the same as Days counted: Operating on the page. Because it names people, only a role with View Attendance Report is offered it, and it is sent only to chosen administrators whose role has that permission; anyone else chosen is left out and the card says so. Extra addresses you type in still receive it.

Every new organisation is given a monthly summary, sent on the 1st to the first administrator. It covers the last 30 full days: visits, door entries, the most inside at once, the most people and the most tags in one room, the top zones by visits, rules fired, and gateway health.

Who can see what

Each report has its own permission, so a role can be given exactly the pages it needs under System › Roles:

Report	Permission
Footfall	View Footfall Report
Enter / Exit	View Enter/Exit Report
People Count, Space Utilisation	View People Count Report
Attendance	View Attendance Report
Asset Utilisation	View Asset Utilisation Report
Loyalty	View Loyalty Report
Schedule Report	Schedule Reports

Attendance shows named people's times on site, which is why it is separate: the person who keeps the register can have it without seeing anything else, and a role that reads footfall need not see who was in.

Questions and problems

Footfall and Enter / Exit give different numbers for the same day. They count different things: tags heard anywhere in the place, against bodies crossing the doors that have counters. If came in is far above people heard, most visitors carry no tag. If it is far below, some doors have no counter.

The zones add up to more than the venue. They should. People move between rooms; the venue counts each of them once.

People Count says 12 and Footfall says 40 for the same room and day. People Count is the most at once; Footfall is everyone who was there at any time that day.

A day shows No data received. The gateways sent nothing that day. Check Gateways on the dashboard and the site's power and network. It is not a day nobody came.

Space Utilisation says Some data missing but every room looks normal. One or more fixed sensors were not heard for part of the opening hours. The line names them after Worst:. A room fed by one of them may have been busier than it shows. See Data health on Space Utilisation and Attendance.

Data health is red only because a gateway is off at night. Gateways are measured over every hour, not only opening hours. Set Expected silence (quiet hours) on the gateway (Device → Gateway, edit) so that planned silence is left out.

A venue shows — for a day in August. That day is before Footfall's once-per-place count began. Group by zone, or use Per: Hour.

A scheduled report never arrives. Its card shows when it was last sent, and an error marker with the reason if the last attempt failed. With nobody chosen it goes to the first administrator, who needs an email address on their account. Test sends it now.

Footfall's a-day figure went up when I set an operating week. With Days counted: Operating, Footfall divides by open days only, so an office that is empty at weekends is no longer averaged down by them. The note above the table says what the closed days held; All days gives the calendar-day figure.

Attendance says 5 / 10 days. Five days present out of the ten days counted. With an operating week set, Days counted: Operating counts only open days, so a Mon–Fri office over two weeks counts ten. A day the gateways sent nothing is not counted against anyone. A visit on a closed day shows as + 1 closed day; switch to All days to see it in the table.

Attendance marks someone late who was on time. Late is the first time a gateway heard their tag, so it reads late when they came in through a door no gateway covers, or left their badge in a bag at reception. The margin under Late / early after forgives the walk from the door; Don't mark turns the marks off. Days the gateways were not sending at opening time are never marked.

Someone with a badge is missing from Attendance. Attendance lists people on the Entity page, through the tags bound to them. A tag that is registered but not bound to a person is in Footfall and not in Attendance. See People and assets.

Footfall does not show staff and visitors. No staff label has been chosen yet, or the days you are looking at are older than the split. See Choose the label that marks staff.

Everyone shows as a visitor. The label chosen is not the one your staff carry, or your staff carry no label on the Entity page. Check the label under Staff label: it shows how many people carry each one.

Many unassigned tags. Those tags are registered but bound to nobody. Bind each badge to its person on the Entity page, and it counts as staff or visitor from then on.

Footfall's People heard includes our trolleys. Their tags are not bound to an Asset entity, so they count as people's. Set each one up on the Entity page as an Asset; from then on it shows under "+ N asset tags".

A supervisor with a limited role sees everyone in the reports. Limiting a role to some labels (Entity access on System › Roles) narrows the Entity pages and the Entity Tracker, not reports. Give that role only the report permissions it should have.

→ Report glossary for every figure on each page · Occupancy: which number is which for the live counts · The dashboard for the visitor tiles.