Reports

Reports is where you find out what actually played on your screens, schedule recurring exports, and review previously generated reports.

Where to find it: sidebar → Admin group → Reports.

Three sections in one page

The page uses three tabs:

Tab	What it’s for
Proof of Play	Ad-hoc lookups: pick a date range and see what played, where, and for how long.
Scheduled Reports	Recurring exports that the system runs on a schedule and saves for you.
Saved Reports	The output of past scheduled report runs, ready to download.

Proof of Play

This tab answers questions like “did this ad actually run on the bakery display last Tuesday?” or “how many times did our sale promo play in October?”.

Filters

Filter	Notes
From / To	The date range to query. Defaults to the last seven days.
Type	What to summarize by — `Layout`, `Media`, `Widget`, or `Event`.
Display ID	Optional. Restrict to a single display.

The presets above the date pickers (Last 24 hours, 7 days, 30 days) are quick shortcuts.

Summary cards

Above the table, four cards show totals for the current filter:

Total Plays — sum of play counts across all matching rows.
Total Duration — total time on screen, summed.
Unique Displays — how many distinct displays contributed.
Unique Layouts — how many distinct layouts contributed.

The table

Columns shown depend on the type you picked:

Column	Meaning
Type	What kind of stat row this is (layout, media, widget, event).
Display	Which display played it. Always shown.
Layout	The layout it played on. Visible on medium screens and up.
Media	The specific media item, when applicable. Visible on large screens.
Start	When the play began. Visible on medium screens and up.
Duration	How long it played for.
Count	Play count when the row aggregates multiple events.

Exporting proof-of-play

Use the Export CSV button to download the currently filtered result set. Use this when an advertiser asks for evidence their content ran, or when you need to crunch numbers in a spreadsheet.

Scheduled Reports

A scheduled report is a recipe that says “run report X with these parameters every week and save the output”. Use these for anything you’d otherwise be exporting manually on a regular cadence (monthly proof-of-play for an advertiser, quarterly playback summaries, etc.).

The list shows each scheduled report’s name, the report type, the schedule cadence, and whether it’s currently enabled. Right-click a row for actions:

Edit — change the parameters or cadence.
Toggle Active — pause or resume runs without deleting the schedule.
Run Now — trigger an immediate run on top of the regular schedule.
Delete — remove the schedule. Existing saved reports it produced are kept.

Creating a scheduled report

Click the + button in the top-right of the page (visible while on this tab).
Pick the report type and fill in its parameters (date range definition, target displays, etc.).
Set the schedule (daily, weekly, monthly, with a specific time of day).
Save.

Output appears under Saved Reports each time the schedule fires.

Saved Reports

This tab is the archive of every scheduled-report run. Each row shows the report name, the date it was generated, and a download link.

Click a row to download the file. Right-click → Delete to remove a saved report you no longer need. Deleting a saved report does not affect the schedule that produced it — future runs continue.

Common tasks

”An advertiser wants proof their ad ran 200 times last month”

Open Proof of Play, set the date range to last month, set type to Media, search for the advertiser’s media name, and export the result. The Total Plays card on the summary row gives you the headline number; the CSV gives you the per-play detail.

”I want a monthly playback summary emailed to ops automatically”

Create a Scheduled Report with the right report type, set it to run on the first of each month, and configure delivery. Each run produces a file under Saved Reports.

”Numbers look low — am I missing data?”

Check that the displays in question have been checking in. The Displays page shows the last contact time. If a player has been offline, it can’t have reported its plays yet — they’ll show up after it reconnects and finishes uploading its log.