How to prove a sponsor's advert played on your screen

The moment you accept money from a local business to show their advertisement on your screen, verbal confirmation stops being enough. Advertisers want data-backed evidence that their paid media reached the physical screen. In the advertising trade, this evidence is called proof of play. It is a log showing exactly how many times a specific spot ran and for how long.

What proof of play actually means

Proof of play is a playback log generated by your media player software. When the player executes a scheduled item, it records a timestamped history of its internal actions and sends it back to the cloud. Media buyers lean on these logs to confirm a spot ran, with the caveat the industry keeps repeating: a schedule and a delivery are not the same thing. Without these logs, operators face immediate billing disputes and demands for free compensatory ad runs.

However, proof of play is a record of software intent, not physical outcome. If the screen loses power, an HDMI cable fails, or a staff member changes the TV input, the player will still log a successful play internally.

Enterprise networks solve this blind spot with proof of display, using independent hardware like optical sensors or external cameras to verify the screen output physically. Vojo, which sells one such sensor, lists player licences from £15 a month per screen on a 24-month term, with Harvester licences priced by volume in a quote. The sensor itself has no published price, which tells you roughly where it sits. For a small operator, that hardware is too expensive. You have to rely on software logs.

The hidden cost of keeping every log

Storing a raw database row for every single time an image plays across every screen is incredibly expensive for software vendors. Engineering analyses show that storing one terabyte of logs per day on standard observability platforms can cost approximately $219,000 annually.

Because of these cloud storage economics, digital signage vendors restrict access to granular data. Major digital signage platforms offer robust, feature-rich ecosystems, but they must manage their backend costs. OptiSigns requires an upgrade to their premium Pro Plus or Enterprise tiers to enable proof of play logging. ScreenCloud lists proof of play and QR code metrics among the features on its fourteen-day Pro trial, which is a good indication of which tier they live in once the trial ends. Yodeck calls Playback Reports a premium feature and states that original playback reports are stored for up to three months before deletion. Check both on the vendor's own pricing page before you promise a sponsor a report.

The own loop strategy for small operators

If you cannot afford enterprise software tiers, you need an operational workaround. Software platforms designed for small businesses manage their server costs by rolling up granular playback data.

For example, Pico Sign folds individual asset playback data into per-sequence daily totals after roughly 48 hours. The database stops tracking that a specific image played at 09:01. Instead, it records that the entire sequence played 400 times on Tuesday for a total of 1.5 hours. This specific architecture allows the software to retain daily figures indefinitely for you, but it removes your ability to prove a specific slide within a large playlist actually aired.

To fix this, you must put each paid spot in its own isolated sequence. Do not bury a sponsor's advertisement inside a general 50-slide lobby playlist. If you dedicate a sequence entirely to one sponsor, the sequence-level reporting generated by the software becomes exactly the asset-level reporting the sponsor needs.

How to structure your monthly reports

When you pull the daily sequence total at the end of the month, the math is unambiguous. The total plays logged for that specific sequence equals the total plays for the sponsor.

Pico Sign provides a per-screen report of plays and total duration per sequence per day, which you can export as a CSV file. The system generates these reports one screen at a time on demand. When you export this data, note that the timestamps are in UTC. You must explain this to your sponsor, as the reported dates will align with global time rather than your local trading hours.

One last thing to check before you invoice. A power schedule that darkens the panel does not stop playback underneath it — the sequence keeps running and keeps logging. A screen scheduled off overnight will therefore still show plays for those hours, so reconcile the report against your operating hours before you bill anyone for them.

Send this report on a set schedule. In the Japanese advertising market, networks like Aeon Town strictly stipulate that operators submit a formal broadcast report to the sponsor by the middle of the month following the campaign. Adopt this habit. Sending the same report every month builds trust and prevents sudden demands for data you no longer have.

What to do next

Create a new sequence in your content management system. Name it clearly after your sponsor. Add only their advertisement to this sequence. Schedule it to play interchangeably with your main content loop. Finally, agree on the reporting period and timezone with your sponsor before they pay their first invoice.