Digital signage analytics
Digital signage analytics shows what you can report to an advertiser, what make-good you owe, and which screens to fix first. Every figure comes from player logs, counted per screen per slot and set against the schedule.
Scheduled against played, example
94.7% of scheduled plays ran: offline screens caused 330 of 534 misses
Share of each day's scheduled slots played. A blank cell is 100%.
| Mon | Tue | Wed | Thu | Fri | Sat | Sun | Played of 1,260 | |
|---|---|---|---|---|---|---|---|---|
| Screen 1 | 100% | 100% | 100% | 100% | 100% | 100% | 93.3%, schedule error | 1,248 |
| Screen 2 | 80.0%, content missing | 100% | 100% | 100% | 100% | 100% | 93.3%, schedule error | 1,212 |
| Screen 3 | 100% | 100% | 100% | 100% | 100% | 83.3%, screen offline | 93.3%, schedule error | 1,218 |
| Screen 4 | 100% | 80.0%, content missing | 100% | 100% | 100% | 100% | 93.3%, schedule error | 1,212 |
| Screen 5 | 100% | 100% | 100% | 100% | 100% | 100% | 93.3%, schedule error | 1,248 |
| Screen 6 | 100% | 100% | 33.3%, screen offline | 0%, screen offline | 100% | 100% | 93.3%, schedule error | 948, 75.2% |
| Screen 7 | 80.0%, content missing | 100% | 100% | 100% | 100% | 100% | 93.3%, schedule error | 1,212 |
| Screen 8 | 100% | 100% | 100% | 100% | 100% | 100% | 93.3%, schedule error | 1,248 |
| Network | 1,368 | 1,404 | 1,320 | 1,260 | 1,440 | 1,410 | 1,344 | 9,546 of 10,080, 94.7% |
| Offline all scheduled hours: 180 slots missed, 15 hours down | ||||||||
| Schedule error: Sunday's schedule ended an hour early, 12 slots per screen | ||||||||
| Screen 1 | Screen 2 | Screen 3 | Screen 4 | ||
|---|---|---|---|---|---|
| Mon | 100% | 80.0%, content missing | 100% | 100% | |
| Tue | 100% | 100% | 100% | 80.0%, content missing | |
| Wed | 100% | 100% | 100% | 100% | |
| Thu | 100% | 100% | 100% | 100% | |
| Fri | 100% | 100% | 100% | 100% | |
| Sat | 100% | 100% | 83.3%, screen offline | 100% | |
| Sun | 93.3%, schedule error | 93.3%, schedule error | 93.3%, schedule error | 93.3%, schedule error | |
| Played of 1,260 | 1,248 | 1,212 | 1,218 | 1,212 |
| Screen 5 | Screen 6 | Screen 7 | Screen 8 | Network | |
|---|---|---|---|---|---|
| Mon | 100% | 100% | 80.0%, content missing | 100% | 1,368 |
| Tue | 100% | 100% | 100% | 100% | 1,404 |
| Wed | 100% | 33.3%, screen offline | 100% | 100% | 1,320 |
| Thu | 100% | 0%, screen offline | 100% | 100% | 1,260 |
| Fri | 100% | 100% | 100% | 100% | 1,440 |
| Sat | 100% | 100% | 100% | 100% | 1,410 |
| Sun | 93.3%, schedule error | 93.3%, schedule error | 93.3%, schedule error | 93.3%, schedule error | 1,344 |
| Played of 1,260 | 1,248 | 94875.2% | 1,212 | 1,248 |
Network: 9,546 of 10,080, 94.7%
Offline all scheduled hours: 180 slots missed, 15 hours down Schedule error: Sunday's schedule ended an hour early, 12 slots per screen| Slots missed | Share of shortfall | |
|---|---|---|
| Screen offline | 330 | 61.8% |
| Content missing | 108 | 20.2% |
| Schedule error | 96 | 18.0% |
| Total | 534 | 100% |
Show the numbers
| Screen | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Played of 1,260 |
|---|---|---|---|---|---|---|---|---|
| Screen 1 | 100% | 100% | 100% | 100% | 100% | 100% | 93.3% | 1,248 |
| Screen 2 | 80.0% | 100% | 100% | 100% | 100% | 100% | 93.3% | 1,212 |
| Screen 3 | 100% | 100% | 100% | 100% | 100% | 83.3% | 93.3% | 1,218 |
| Screen 4 | 100% | 80.0% | 100% | 100% | 100% | 100% | 93.3% | 1,212 |
| Screen 5 | 100% | 100% | 100% | 100% | 100% | 100% | 93.3% | 1,248 |
| Screen 6 | 100% | 100% | 33.3% | 0% | 100% | 100% | 93.3% | 948, 75.2% |
| Screen 7 | 80.0% | 100% | 100% | 100% | 100% | 100% | 93.3% | 1,212 |
| Screen 8 | 100% | 100% | 100% | 100% | 100% | 100% | 93.3% | 1,248 |
| Network | 1,368 | 1,404 | 1,320 | 1,260 | 1,440 | 1,410 | 1,344 | 9,546 of 10,080, 94.7% |
Digital signage KPIs: the numbers that run a screen network
Delivery rate counts plays against the schedule and uptime counts scheduled hours only, so every figure in an advertiser's report leads back to log rows.
| KPI | Formula | A good reading | The common mistake |
|---|---|---|---|
| Delivery rate | Slots played in full, from player logs ÷ slots scheduled, per screen per day |
Read per screen, with every missed slot given a cause | Taking the schedule as the record of play. A screen that was off still has a full schedule. |
| Uptime in scheduled hours | Scheduled hours the player was online and playing ÷ scheduled hours |
Read for each screen on its own, since a network figure can hide one screen that was down all week | Dividing by 24 hours a day, which counts a screen switched off overnight by design as a fault |
| Time to recover | Hours from the first missed heartbeat inside scheduled hours to the screen's next logged play, per fault |
Falling, and read by site and by cause | Starting the clock when someone reported the fault, which leaves out the hours before anyone noticed |
| Plays per screen per day | Slots played ÷ (live screens × days in the period) |
Steady by screen, with any drop matched to a cause in the delivery grid | Dividing by every screen on the asset list, including ones installed and not yet live |
| Fill rate | Slots booked by paying campaigns ÷ slots available for sale, by site and hour of day |
Read by site and hour, so the hours that sell out and the ones that don't are both visible | Counting house content and filler loops as booked |
| Make-good owed | Plays booked in a campaign's order − plays delivered on the booked screens and dates, from player logs |
Agreed in writing with the advertiser before the campaign report goes out | Counting plays on screens outside the booking toward the total, which hides a shortfall on the screens that were sold |
There are more examples in the KPI library.
A screen switched off overnight by design has not failed, so uptime is only ever measured in scheduled hours.
Where digital signage data usually lives
Analytics services for screen networks
Proof of play is only as current as the last upload, so data monitoring and support checks each day that every player's logs arrived and names the screens that have gone quiet.
A play counts only when the player's own log shows it ran to the end.
AI in digital signage analytics
AI-led analytics answers "which screens missed the most plays last week, and why?" once every missed slot already carries a cause in the data, such as offline, content missing or schedule error. Each answer shows its query.
Questions about proof of play and uptime
What counts as proof of play?
A row in the player's log for each slot, with screen, content file, start time and whether it ran to the end. Only full plays count, so one that stopped part way shows as missed.
How should screen uptime be measured?
In scheduled hours only. A screen set to switch off from 22:00 to 07:00 isn't down overnight, so those hours drop out of both sides. A fault's clock runs from the first missed heartbeat inside scheduled hours to the next logged play.
Can audience figures go in the same report as plays?
Yes, in their own column, marked as estimates with the source named. Plays are counted from logs, and audience figures are modelled from footfall, traffic data or a survey, so we never multiply the two into unlabelled impressions.
Do you build network reporting dashboards for digital signage?
Yes. The core view is the screen by day grid above, with the shortfall split by cause, beside uptime in scheduled hours, time to recover and make-good owed per campaign.
What happens to plays logged after a screen comes back online?
They're dated to when they ran, so an earlier day's figures can rise after you've reported them. The report states when it was run, and a campaign's figures close only once every screen in it has uploaded past the campaign's end.
Could you defend your proof of play to an advertiser?
On the call we set a week of your schedules beside the player logs and show where the missed slots went.