Proof of play reporting you can put in front of an advertiser

Why proof of play matters

If you are billing advertisers by the play, running a DOOH network, or simply need to show a stakeholder that a promotion actually ran as scheduled, "the content was in the playlist" is not the same claim as "the content played." Proof of play is the difference between those two claims, backed by a real record rather than an assumption.

A play-log entry captures the media asset, the associated campaign and schedule, the actual start and end timestamp, how long it played, and whether it completed, was interrupted, or errored out. That is enough detail to reconstruct exactly what an advertiser or stakeholder saw, when they saw it.

Recorded on-device, synced later

The record is written to the device's own local storage the moment a play finishes, not buffered only in memory and not dependent on a live connection at that instant. This is the same design principle behind offline playback: a screen that loses power or connectivity mid-play should never lose more than the single in-progress event, and even that gets logged as interrupted rather than silently dropped.

Once the device reconnects, buffered play logs upload automatically. Each event carries a unique ID generated on the device, so a retried upload after a dropped connection can never double-count the same play in your reports.

What you get in the dashboard

Play logs are queryable and exportable from the dashboard, filterable by screen, campaign, and date range, which is what turns a raw log into something you can hand to a finance team or an advertiser as evidence of delivery. Anomalies, like an implausibly short play duration, are flagged for review rather than silently accepted into a billing report.