Illustrative playback check and sample event poster. Reporting software and compatibility must be verified separately.
A campaign was uploaded on Monday. The dashboard says the player is online. Does that prove the campaign ran on the screen?
Not necessarily. Digital signage proof of play is a record of playback events under a system's own reporting rules. It can help operations teams check delivery, investigate missing content and prepare campaign reports. It is not automatically proof that the physical screen was visible—or that anyone looked at it.
Before buying displays or choosing a content management system (CMS), ask for a demonstration that connects the content file, the player, the screen and the exported report. A sample spreadsheet is useful; a repeatable test on your intended configuration is better.
Why reporting deserves its own buying decision
Centralized management remains a visible industry priority. Samsung's September 3, 2026 overview of VXT and LYNK Cloud describes remote content and display management across business environments. That provides current context for a practical question: once a team manages screens remotely, what evidence does it receive about playback?
The presence of a CMS does not answer that question. Reporting may require a particular player version, subscription, activation setting or integration. A display specification such as size or memory does not establish which playback events the software records.
This guide treats the reporting workflow as something to verify, not a feature to assume. Vendor examples below illustrate differences between systems; they are not compatibility claims for KEINONE equipment.
Separate four kinds of evidence
A schedule records intention
A playlist or campaign calendar says what the system was instructed to play. It does not, by itself, show that the media reached a player, decoded correctly or completed its allotted time.
A playback log records a defined event
Find out whether an event means a file started, a duration elapsed or a complete item finished. Also ask whether the record refers to a whole layout, one media item or a zone within a layout. These are not interchangeable units.
Screen checks add physical context
A software screenshot can help show what a player rendered at one moment. Depending on how it is captured, it may not show that the panel was powered on, set to the correct input or unobstructed. Combine available device status with an on-site visual check during acceptance testing.
Audience measurement answers a different question
A play count is not a viewer count. Audience estimates need their own method, assumptions and reporting labels. Do not rename “1,200 plays” as “1,200 people reached.” For the broader distinction between delivery and audience metrics, see our in-store retail media guide.
Ask what counts as a successful play
Start with a short video and ask the supplier to explain what happens if it is interrupted halfway through. Does the report show a partial event, a failed event, a completed play or no entry? Repeat the question for still images and web-based content.
Definitions vary. Broadsign's POP Log documentation, for example, defines success using the full ad-copy duration with a stated tolerance. It also distinguishes its daily log export from a near-live reporting option. Those are rules for that product, not a universal definition of proof of play.
Get the definition in writing alongside the demonstration. Otherwise two systems can produce different totals for the same apparent sequence without either total revealing why.
Use this reporting checklist in a supplier demo
Ask the supplier to show the following information or explain how an equivalent record is obtained. Treat missing items as questions to resolve, not as evidence that all deployments require the same report format.
- Content identity and revision: Can you distinguish the old poster from an updated poster with a similar filename?
- Player and screen mapping: Can an operator connect the log entry to a specific physical unit and location? One player may not always correspond to one screen.
- Event definition: Does a row describe a start, completion, interruption or aggregated total?
- Time information: Which time zone is used, how are clocks maintained, and are upload time and playback time separate?
- Reporting delay: When should an event become visible, and how do you distinguish late data from missing data?
- Export and retention: Can you obtain the records in a usable format, and will they remain available for your reporting cycle?
- Access and cost: Who may view or export records, and which license or service tier is required?
Aggregation is especially easy to overlook. Xibo's CMS settings documentation describes individual, hourly and daily statistics, with collection and aggregation settings affecting the records returned. If you need to investigate a particular minute, ask whether an hourly total contains enough detail. Do not assume a summary can later be expanded into individual events.
Run a small acceptance test before rollout
The sequence below is an original test plan, not a claim that any named product has passed it. Use a non-production display and agree on the test conditions with the supplier.
1. Establish a visible baseline
Prepare two clearly labeled assets: a still image called TEST-A and a short video called TEST-B. Record their versions and planned durations. Observe a few complete cycles and note the local time. Export the matching report after its documented reporting interval.
2. Compare the record with what happened
Can you identify both assets and the correct device? Do the event rules explain the observed counts? For a controlled example, 12 completed plays of a 10-second clip equal 120 seconds of reported clip time. That arithmetic alone says nothing about unique viewers or whether the screen was visible for every second.
3. Test interruption and delayed reporting
With permission, briefly interrupt the test player's network connection, then restore it. Ask whether playback records are stored locally, how much can be retained, and whether they upload afterward without being counted twice. A blank live report during the outage should be investigated, not automatically labeled “zero plays.”
Test playback continuity separately from log recovery. Our offline digital signage guide covers what content may remain available when connectivity drops; this test asks whether the record of that activity can be recovered.
4. Verify a version change and the handover
Replace TEST-A with a visibly different revision. Check how the old and new versions appear in the export. Then have the person who will operate the system—not just the demonstrator—retrieve the report and explain it. Save the agreed definitions and any unresolved limitations with the acceptance notes.
Match the reporting requirement to the hardware setup
A KEINONE 43-inch floor-standing signage kiosk can provide a portrait format for visitor information or advertising. The current listing offers touch and non-touch configurations. Choosing touch changes how people may interact with the display; it does not establish a proof-of-play reporting capability.
Before ordering, identify the exact operating system, player application, CMS, software version and license. Ask which component generates the record and which component stores it. If a third-party or external player is proposed, test that complete combination rather than relying on a demonstration performed on different hardware.
For basic internal information, a simpler workflow may be enough. For campaigns requiring detailed delivery records, make the reporting test part of procurement. Do not add audience-sensing equipment merely to obtain ordinary playback logs; those are separate requirements.
Frequently asked questions
Is proof of play the same as proof of display?
Not necessarily. Vendors may use the terms differently. Ask whether the evidence comes from the playback application, panel status, a screen capture or physical observation, and what each method can miss.
Can proof of play work while a player is offline?
Some systems may store records locally and upload them later. Confirm storage limits, timestamps and recovery behavior on your exact setup. Do not assume offline playback also guarantees offline logging.
Does a screenshot replace a playback report?
A screenshot is evidence of one captured moment. It is not a continuous history and may not establish the physical state of the panel. Use it as supporting evidence with clearly stated limits.
Does every digital signage display include reporting?
No such assumption should be made. Verify the player and CMS capabilities, required settings, subscriptions and export options independently of the screen specifications.
0 comentários