Proof of play in digital signage is a record, kept by the player, of what content actually played on which screen and when. It answers a simple question that a schedule cannot: did the campaign really run? A schedule says a promotion should play every ten minutes from Monday to Sunday in twelve stores; proof of play shows whether it did, on every screen, or whether three screens were offline on Tuesday. This guide explains what proof of play records, why it matters for marketing, operations and advertising, how to verify screen delivery with and without dedicated reporting, and the questions to ask any vendor before you rely on its numbers.

Scheduled is not the same as played

Between the moment you publish a playlist and the moment it appears on a screen, many things can go wrong. The player may be offline. The TV may be switched off or set to another input. A file may still be downloading. A local manager may have unplugged the screen to clean it. Without a record from the player itself, the dashboard only knows what you asked for, not what happened.

That gap matters more as a network grows. With one screen you can walk past and look. With dozens of screens in many locations, you need data.

What a proof of play log records

A useful proof of play record usually contains the same core fields.

Screen and location. Which display played the content, and where it is.

Content item. The exact file or playlist item that played, ideally with its version.

Start time and duration. When playback started and how long it ran, so you can compare it with the schedule.

Player status. Whether the player was online, when it last synced and whether it reported errors.

Some systems also record whether the display was on, which is harder to know from software alone. Ask how the vendor measures it.

Why proof of play matters

Marketing. A campaign report is only credible if you can show that the content ran where and when it was planned. Proof of play turns "we scheduled it" into "it played this many times, in these stores, at these times", with real data from your own network.

Operations. Gaps in the log show screens that drifted: a player that stopped syncing, a screen that is always off in the morning, a location where content arrives late. Fixing those raises the value of every screen.

Advertising and supplier media. If you sell screen time to brands or suppliers, proof of play is the basis for fair billing. Partners will expect a delivery report.

How to verify screen delivery without dedicated reporting

Not every platform offers detailed proof of play reports. You can still build confidence in delivery with a few habits.

Watch screen status. A dashboard that shows which screens are online and when they last connected catches most problems early. Pilosign shows every screen in one dashboard so you can see the network at a glance.

Spot checks. Ask local teams to send a photo of key screens at the start of an important campaign. Simple, and it catches wrong inputs and switched-off TVs.

Schedule sanity checks. Before a campaign starts, preview the schedule per screen group and confirm the right content sits in the right time slots.

Reliable hardware. Players that power back on after an outage and keep the app in the foreground reduce silent failures. Our digital signage player guide covers what to look for, and the supported players page lists the devices Pilosign runs on.

Questions to ask a vendor about proof of play

Where is the log created? On the player, from real playback, or estimated from the schedule? Only player-side logs prove delivery.

What happens offline? Does the player keep logging while the network is down and upload the records later?

How long is data kept, and can you export it? Campaign reports often need raw data in a spreadsheet.

Can you filter by campaign, screen group and date? A report you cannot slice is hard to use.

Does it detect display power? Ask how the vendor knows whether the TV itself was on.

Using proof of play in reports

A good delivery report for a campaign shows planned plays against actual plays per location, the screens with gaps and the reason, and a short note on what was fixed. Keep it simple: stakeholders want to know whether the campaign ran and what you did about the exceptions.

Over time, the same data shows patterns. If a location always loses plays on Monday mornings, the cause is local: cleaning routines, power schedules or network outages. Fixing patterns like these is where proof of play pays back, even when you do not sell advertising.

Proof of play across many locations

The larger the network, the more value delivery data has, because nobody can check every screen in person. For multi-site teams, combine three things: one dashboard for screen status, consistent player hardware across sites, and clear ownership of each location's screens. Our pillar guide on digital signage software for multi-location teams explains how to set up that control model, and the digital signage software page shows the platform that runs it.

Setting up a delivery check for a campaign

You can run a simple delivery check for any campaign, even before you have full reporting. Treat it as a short routine around the launch.

Before launch. Confirm the campaign sits in the right playlists, for the right screen groups and time slots. Check the start and end dates. Make sure every screen in the target groups is online.

Launch day. Ask each location to confirm the campaign is visible, with a quick photo of one screen. Check the dashboard for screens that went offline overnight.

During the campaign. Look at screen status every morning. A screen that drops offline during the campaign is the most common reason for missing plays. Fix it the same day.

After the campaign. Write a short delivery note: which screens ran the campaign, which had gaps and why, and what you changed. If you have player-side logs, add planned versus actual plays per location.

This routine takes little time and makes every campaign report more credible.

Common causes of missing plays

When delivery data shows gaps, the cause is usually one of a few things.

Network outages. The player cannot sync new content. Wired connections and players that keep playing downloaded content reduce the impact.

Power and display settings. TVs with sleep timers, energy-saving modes or a cleaning routine that switches them off. Check the TV settings on every screen in the campaign.

Wrong input. Someone switched the TV to another HDMI input or a broadcast channel. Labelling the correct input helps local teams.

Late uploads. Large video files that arrive after the campaign starts. Upload content a day early.

Scheduling errors. The campaign was assigned to the wrong group or time slot. A preview per screen group before launch catches this.

Proof of play for supplier and advertising campaigns

When a supplier or advertiser pays for screen time, the delivery report becomes part of the deal. Agree the rules before the campaign starts: which screens and locations are included, how many plays per hour, which hours count, and how missed plays are handled. Share a delivery summary at the end, with planned and actual plays and any screens that were offline. Clear rules up front avoid disputes later and make partners more willing to book again.

FAQ

What is proof of play in digital signage? A record, created by the player, of which content played on which screen and at what time. It proves delivery rather than intention.

Is a schedule report enough? No. A schedule shows what should play. Only player-side logs show what did play.

Do small networks need proof of play? Less urgently. With a few screens, screen status and spot checks are usually enough. It becomes important for campaigns across many locations and for any screen time you sell.

Can proof of play show whether the TV was on? Only if the system can detect display power. Ask the vendor how it measures this.

Want to see your screens' status in one place? Start with free digital signage software, or contact us to discuss reporting for a larger network.