Proof of play reporting that answers "did it actually run?"

Why proof of play reporting matters

Scheduling content is only half the job. Sooner or later someone asks whether it ran: the marketing lead who paid for a promotion in the shop window, the facilities manager checking that the fire drill notice was on every floor, or a client who wants evidence before paying an invoice.

CompleteVantage answers from the players themselves. A play is recorded when a screen actually shows something, not when the server thinks it should have. If a screen was unplugged, the report shows the gap.

Reports by content, screen or day

The Reports page starts with the last seven days and a summary of total plays, total play time and how many screens took part. Pick a date range and choose how to group the plays:

• By content: each image, video, layout or playlist, with its play count, total time, number of screens, and first and last play. Useful for "how often did the summer offer run?"
• By screen: each screen and its location, so you can compare the lobby with the canteen, or spot a screen that has gone quiet.
• By day: a day-by-day total, useful for checking a campaign ran every day it was booked.

Filter to a single screen or a single piece of content to narrow it down. Dates are in your organization's time zone, and days are counted correctly across daylight saving changes.

• Any date range, defaulting to the last seven days
• Plays, total time and screens for each row
• Filter by one screen or one piece of content
• Plays from screens you later removed still count

Export every play to CSV

When a summary is not enough, export the range as CSV. You get one row per play with:

1. The start time in your organization's time zone
2. How many seconds it played
3. The screen name and location
4. The content, its type, and the layout and playlist it was part of
5. Why it played: assigned content, a schedule, or a broadcast

The file opens cleanly in Excel and Google Sheets. It is the record you send to an auditor, a client or an advertiser, and it shows not just that something played, but whether it played because of a schedule or an emergency broadcast.

Plays recorded offline, uploaded later

Screens do not stop playing when the network drops, and they do not stop counting either. The player keeps its play records on the device while it is offline and uploads them when the connection comes back. Your report fills in the missing hours without anyone touching the screen.

Uploads over a poor connection sometimes get sent twice. Each play carries its own key, so the server stores a repeated play once. Your counts stay honest. Read more about how screens keep running in offline playback.

• Plays kept on the device while offline
• Uploaded automatically after reconnecting
• Repeated uploads are stored once

How long play history is kept

Play history is kept for 400 days by default, so you can compare this year's campaign with last year's. Older plays are removed automatically in the background.

Plays are stored per organization. Someone in one organization, or one client of a reseller, never sees another's reports.