Platform
See what played, and the orders beside it
A play log shows that an item started. It does not, by itself, show that the screen made the sale. Proof keeps those two ideas apart.
Use cases
You need to know the loop ran
Each time a screen starts an item, Proof stores the name and the seconds set on that item. Logs older than 90 days are dropped. Download the CSV. Growth and Enterprise can pull the same numbers from the API.
You want the orders next to the loop
Connect a till and pull it. Proof shows the average order and the add-on rate for the last 14 days. It also compares hours when an item played with hours when it did not. The difference is not proof the screen caused the sales.
You want a count of people, not a picture
Turn sensing on for that screen. The desk stores visits and dwell seconds for the hour. No picture is stored. Leave it off and nothing is counted.
On this desk
- Proof of play for the last 14 days, with a CSV download.
- Average order value and add-on rate after a till pull.
- Hour-by-hour order value while an item was on screen, beside hours when it was not.
- Read marks on floor notices.
- Optional on-device counts and dwell. No picture.
Not on this desk
- This is not a controlled sales-lift study and it does not use a hold-out store.
- QR scans, coupon redemptions, and short links are not tracked per screen.
- Sensing does not recognise a face and does not send a picture.
Questions
Does Proof prove the screen increased sales?
No. It shows what played, and the average order in hours when an item played compared with hours when it did not. The page says the difference does not show that the screen caused the sales.
Are pictures of the audience stored?
No. Sensing stores a count and dwell time for the hour, and only on screens where you turned it on.
Start a 14-day trial Read the how-to guide