Short answer: proof of play is the record of which content played on which screen, when it started and ended, and whether it played to the end. It is how you show an advertiser, a branch manager or yourself that a campaign really ran. GoVista collects these records from every player and shows them in reports by content, store and time.
This guide covers what a playback record contains, how to read the reports, and which questions the reports cannot answer.
What exactly does proof of play prove?
Proof of play records that the player played the content. Content appearing in a schedule and content actually playing are not the same thing: the screen may have been off, the device may have been offline, the content may have been cut short. The schedule shows the intent; proof of play shows what happened.
What it does not prove matters too: proof of play does not tell you who stood in front of the screen or how many people looked at it. GoVista has no camera and does not measure viewers, nor personal attributes such as age or gender. Measuring what happens with products in a store is a different product's job: GOTONOM's GoTrack (gotrackgo.com).
That is why proof of play does two jobs for anyone running a screen network: a document for the outside world and a fault detector on the inside. If scheduled content is missing from the report, the problem is the device, the connection or the schedule, and the records let you tell which.
What is in a playback record?
Each playback record in GoVista holds:
- Which content played and which playlist it came from
- Which device and store it played on, and which zone of the screen if there is more than one
- Start and end time, and the played duration in milliseconds
- Whether the play came from a schedule
- Whether it played to the end or was skipped, and the reason if it was skipped
- Whether the screen was blacked out from the dashboard at the time
That last item matters when you read a report. Plays that happen while the screen is blacked out from the dashboard (brightness zero) are flagged in the record and kept out of every total shown to the customer, the per-content play counts and the monthly reports. An ad that plays on a dark screen does not count as played.
How do you read GoVista's reports, step by step?
- Choose the date range and the scope: the whole network, one store or one piece of content.
- Look at play count and total played time per content item: did the campaign you scheduled play as often as you expected?
- Check the completion rate: does the content play to the end, or is it cut short by the layout or the schedule?
- Look at play volume by hour and by day: did the morning content play in the morning and the evening content in the evening?
- Compare stores: if one branch has clearly fewer plays, the problem is usually the device, not the content.
- Export the data as CSV if you need it, or send the monthly report by email.
What do completed, skipped and failed plays mean?
Reports split plays into four groups. A completed play is one where the content was shown to the end. A skipped play is one where the content was passed over for a reason, and the record carries that reason; the breakdown of skip reasons shows which problem happens most. Plays that neither reached the end nor were marked as skipped count as failed. Plays during a blackout sit in a separate group and are not added to the totals.
The practical reading: content with a low completion rate usually does not fit the duration of its zone; shorten it or give it more time in the schedule. If skips cluster on one device, the problem is that device, not the content.
What should you do if a report has gaps?
A playback record is created on the player and shows up in reports once it reaches the server. Records from a device that lost its connection may reach the reports late or appear incomplete. When you see a gap in a store's chart, look at the device's health data first: GoVista also tracks uptime, panel temperature, bandwidth, signal strength and sync status. A correct clock on the device matters too, because the timestamps depend on it.
On the Android player, playback records are stored on the device first and sent to the server every 5 minutes while the device is online; while it is offline they wait on the device and go out with the first send after the connection returns. Records the server has received are deleted from the device after 7 days. The player also reports its status to the server every minute, and while offline it checks the network every 30 seconds. So a short outage does not lose records; they only reach the report later.
Who are proof-of-play reports for?
Four typical users:
- Businesses that sell screen time: show the advertiser which screens, which hours and how many times the content played.
- Multi-branch chains: confirm that a campaign prepared at head office really ran in every branch.
- Agencies and integrators: hand the customer a concrete playback report at the end of the month.
- Operations teams: find screens that are not playing before a customer notices.
How do you present a playback report to a customer?
When you send the month-end report to an advertiser or to head office, we suggest this order:
- Scope: which screens, which stores, which date range.
- Result: play count and total played time per content item.
- Quality: completion rate and skip reasons, with an explanation for a low rate.
- Exceptions: devices that were offline, blackout hours, and the note that these are not in the totals.
- Raw data: a CSV file for anyone who wants it.
This order says what the number is and why it can be trusted on the same page. Stating the exceptions plainly answers an objection before anyone raises it.
Why is a play count not a view count?
"This ad played 1,200 times" is a true sentence you can prove; "1,200 people saw this ad" is not. Saying so plainly when you present a report to an advertiser makes the numbers more credible. GoVista's playback reports prove the first sentence; the second one needs an audience-measurement method, and GoVista does not do that.
Where playback data is kept and how to export it is covered in the proof-of-play articles in the support center. Setup guides for your screens are on the Downloads page.

