Mestra Player
Proof of play
Every time a screen shows a booking, it records a play. The screen sends its plays to Mestra, and Proof of play in the player web app shows them.
What counts as a play
A play is the screen’s own record that it showed a file, starting at a time, for a length of time. Each play holds:
- the booking and the screen that played it;
- when it started, in the screen’s own time and time zone, and in UTC;
- how long it showed, as measured, not as booked;
- the SHA-256 of the exact file the PC checked and showed;
- whether the main player or the backup player showed it;
- for a group member, whether it was in step with the others;
- a check state: Signed, Checked or Unchecked.
A play is recorded as it ends. A screen that was offline sends its plays when it is back, and each play is counted once even if it is sent twice. A screen records no plays while its panel is off.
See the plays
Open Proof of play.
- Choose a Period: Today, Last 7 days or Last 30 days. Days are counted in the screens’ own time zone, not your browser’s. For one screen that is its zone. For a site or all screens it is the zone most of them keep, and when they are in several zones the page says so under its title. See Time zones.
- Choose Group by: By day, By screen, By site, By booking or By customer. Filter by Site or Customer, or open one screen’s plays from its page.
- Read the totals for the period: time on screen, plays, and how many are Checked and Signed.
- Open Every play for one line a play, oldest first, from the start of the period.
If nothing played in the period, the page says so. Try a longer one.
By customer
A play names no customer. It names its booking, and the booking names the customer. Mestra joins them when you ask, so By customer and the Customer filter follow each booking’s customer as it is now. If you change a booking’s customer, its plays move to the new customer, and a customer renamed shows under its new name. Plays of a booking with no customer are grouped under No customer. A customer’s page shows its plays in the last 30 days and links to all of them.
Download the CSV
Select Download CSV. It holds every play for the period, site and screen you chose, with these columns: play_id, screen_id, screen_name, site_key, site_name, publication_id, item_id, entry_id, played_at_local, zone, played_at_utc, duration_ms, sha256, played_by, check_state, render_check_id, receipt_key_id, receipt_json, batch_id and, last, customer: the name of the customer of the play’s booking now, empty when it has none.
A play belongs to the site its screen was linked to when it played. Moving a screen to another site doesn’t move its earlier plays.
The same plays are available over the API and to an AI assistant with a Screens key. Plays are listed in the order Mestra stored them, not the order they were played, so a feed should come back later for plays from screens that were offline.
The check state
The check state is about the file, not the play. It says whether the file the screen showed is one that Mestra Studio made and checked. It doesn’t say whether the play happened: every play in the list was reported by the screen, whatever its state.
| State | Meaning |
|---|---|
| Signed | The file was published from a Studio run, and that exact file passed your approved rules. Mestra signed a receipt that says so. |
| Checked | The file was published from a Studio run, and that exact file passed its checks, but there is no receipt. This happens when the run had no rule set, so only the checks that need none were made (an empty panel, a cut-off photo subject, text contrast). |
| Unchecked | Mestra has no passing Studio check of that exact file. |
A play is Unchecked when:
- the file was uploaded straight to Content and booked, rather than published from Studio. Test videos, a customer’s finished artwork and anything else made outside Mestra are always Unchecked;
- the Studio run’s check of the file failed, or the check was discarded;
- the screen showed a different file from the one Studio checked.
Mestra matches the check when the play arrives, so a play’s state doesn’t change later. An Unchecked play is still shown and counted, never hidden. It only means Mestra can’t vouch for the file’s content. If your plays should all come from Studio, treat an Unchecked one as unapproved until you have looked at the file.
A signed receipt proves the file’s approval: that this exact file passed one version of your rules, for your organisation. Mestra’s public keys are published at /.well-known/mestra-receipt-keys.json, with no sign-in, so anyone can check a receipt.
What a play doesn’t prove
The play itself is the screen’s report over its signed-in connection. The signatures don’t prove that anyone saw the content, or that the screen’s report is true. Together, a play shows an approved file, reported played by this screen, and kept unchanged since.
Plays after a move
Rolling over from Doohly or Broadsign never imports the old system’s plays. Plays Mestra records for a booking it carried stay together on the Published page, linked to the booking they were carried from. See Move from Doohly or Broadsign.
Uptime
Each screen’s page shows Uptime over 30 days, with and without site power cuts, and a signed statement for each closed day.
- Showing approved content, the stop show, or an empty screen where nothing is booked counts as up.
- The backup player showing a live item counts as up, and is reported separately.
- The panel holding its own copy of the stop show during a restart counts as down, and is reported separately.
- Time the panel is off by its hours, or the organisation halted, is left out.
- A PC that is off, crashed, restarting or silent counts as down.
Uptime is the seconds up divided by the seconds counted. Totals over days, sites or the organisation add the seconds first and divide once. The minutes are the screen’s own report, checked by Mestra against when it heard from the screen.