Analytics

Analytics (sidebar) shows what your screens have played and how many taps they have received. It appears in the menu once a screen of your company has sent data. It has two tabs: Playback and Taps.

Users who may view screens can open it, and each user only sees their own screens.

Playback

Each screen reports what it actually showed: which file, when and for how long (proof of play).

Choose From, To and Screen, and press Apply. The search box filters by content.
Summary: Playback count, Completed and Screen time.
Table by content: Content, Type (video or image, and whether it came from the local folder or a USB drive), plays, Total time and Devices.
Export CSV downloads the detail.
Times follow each screen's own clock. If a play ended early (unsupported format, decoding error or mode change), a note below the table says so.

Requires the Android agent 2.5.0 or later, or the Linux and Windows 2.0 agents. A screen without a connection reports once it is back online, and data can take a few minutes to appear.

Taps

How many times your touchscreens were tapped, in 30-minute slots, and in which area of the screen.

Requires the Android agent 2.5.2 or later. Taps are only measured in Web Kiosk mode: screens in Playlist mode show Playlist mode with Not measured by taps.

Choose From, To and, if you like, one or more Devices (with none selected, all are included), and press Apply. The longest period is two years.
Summary: Taps in total, Screens with taps, and how many screens have partial data, a wrong clock or incomplete data. A Touch line says how many screens have touch confirmed (a real tap has been seen), declared but unconfirmed, no touch, or no data.
Taps per 30-minute slot: a chart of the period, in each screen's local time.
A table per screen with Status, Taps, Slots reported and Alerts, and below it the Detail by screen with the area grid. The detail shows the screens with the most taps; the CSV files include all of them.

Statuses

Status	Meaning
(a number)	Taps counted in the period.
No taps	The screen is a touchscreen (taps have been seen before), it reported the whole period and nobody touched it. This is the only case where 0 is a measurement.
Touch unconfirmed	It reports, but no tap has ever been seen. Many devices declare touch input without having it, so we cannot tell whether nobody touched it or it cannot be touched.
No touchscreen	The device declares that it has no touch input.
Does not report taps	No agent has sent taps from this screen yet.
Playlist mode	The screen was in Playlist mode, which is not measured by taps.

Alerts

Alert	Meaning
Partial	The screen only reported for part of the period. Slots without data show as "—", not 0, and the total is a minimum ("≥").
Incomplete	The device dropped taps because its buffer filled up while it had no connection. The total is a minimum.
Clock doubtful / Clock unreliable	The device's clock was off. The total is right, but the split into slots may not be.
Rejected	The server rejected taps with impossible coordinates or dates.
Changed mode	The screen was in both Web Kiosk and Playlist mode during the period; only web-kiosk taps count.
Mode assumed	Part of the data predates the recording of the screen's mode; for that part its current mode is used.

Export

Export PDF — a printable report.
Export CSV — one row per screen, day and 30-minute slot. Column names are always the same and are not translated (pantalla, fecha, hora_local, toques…), so they do not change with the language.
CSV by area — taps per cell of a 10 × 10 grid.

Privacy

Taps are counted anonymously and in aggregate: RDS stores how many taps there were in each 30-minute slot and each grid cell, never the exact position or the sequence of one person's taps.