Operations · Analytics
See which ad played where and how many times, in numbers
At a glance · Ad Publish analytics
LUMA Ad Publish Analytics is a Proof of Play service where the device itself records exactly what ads and content were played on Store screens, then compiles those records into play count, play duration, number of Stores exposed, and completion rate. The same records also show device uptime, downtime, and playback errors, and you can send advertisers a time-limited report link that opens without login. It runs on LUMA Boxes publishing via LUMA AI CMS.
Who it's for
If this sounds familiar
Key features
Every time content plays on screen, the box records its own start and end times. This isn't a manually written log — it's a record of what actually played.
Records from offline periods are stored in the device until the connection returns, then uploaded. They're only cleared from the device after confirming they've been saved on the server.
Even if the same record is sent multiple times, it's only counted once. Overlapping playback segments are also calculated only once, so numbers don't get inflated.
Time when the device was off or records weren't uploaded is shown separately as a 'gap with no records'. Nothing is dressed up to look good, so it can be shown to advertisers as-is.
Press a button in the console to capture and upload a snapshot of the Store screen, so you can see with your own eyes what's playing right now.
View a table of how many times and how many hours each Program played today, in the last 7 days, or in the last 30 days. You can view all devices or select a single device.
The four numbers advertisers care about are shown as large cards, along with daily exposure trends and a ranking of exposure by Store.
Every number card also shows whether it's up or down compared to the same period before.
Dates are split by the time zone of the region where each Store is located. Viewing overseas Stores from Seoul headquarters won't throw off what counts as 'yesterday'.
Shows, by date, the percentage of time the device was on and connected, and the time it was disconnected.
Collects playback errors reported by the device by date, such as missing assets or the screen turning off.
Compare uptime, downtime, errors, and play count for every device in a single table to instantly spot which device needs attention.
Store manager accounts only see numbers for their own Store's devices. Headquarters accounts see everything.
Pick one ad and create a link to send to the advertiser. The advertiser sees only that ad's report, no account needed.
The shared report contains only that ad's numbers. Other ads, device names, and errors aren't hidden from view — they're never calculated in the first place.
Every link has an expiration date (one quarter by default), and when the contract ends, revoke it with one button. A revoked link won't open even if the address is known.
Each sent link keeps a view count and the last opened date, so you can tell whether the advertiser checked the report.
Instead of just saying it aired, we show you the record
Playback logs recorded directly by the device, one link for the advertiser · AI-generated videoEquipment
Publishes content while recording its own playback logs and uploading them to the server — applies to screens publishing via LUMA AI CMS
RequiredThe screen where ads actually play — connected to the LUMA box via HDMI
RequiredUploads logs to the server and refreshes reports — logs accumulate on the device while disconnected and upload once reconnected
RequiredHow it works
Use cases by industry
Franchise cafe/bakery headquarters
Check exposed store count and daily impressions per ad, and send partners a time-limited report link.
Replaces spreadsheet reporting of publish results with a single link.
Convenience store/supermarket retail chains
Check whether ads played to completion using per-store impression rankings and completion rate.
Answer “Did it actually play?” with the logs the device kept.
DOOH operators and ad agencies
Create a separate link for each advertiser so each only sees their own ads.
Report transparently without advertisers worrying about seeing each other's data.
Shopping malls · Multi-tenant stores
Check uptime, downtime, and errors per device daily on the operator screen.
Find screens that are off before customers do, reducing ad loss.
Hospitals · Banks · Government waiting areas
Check how many times and for how long a Program aired during a period using per-Program playback reports.
Use Publish records directly as internal reporting material.
Get started
Tell us your store size and the equipment you use, and we'll recommend the right setup and quote. We'll also check your existing screens and printers.
Specs
Works even better together
Frequently asked questions
Yes. Send a share link for a specific ad, and they can view that ad's report only, without logging in. No other ads or device info are shown.
Ad attention analytics, used together with LUMA Vision, is in preparation for launch.
Yes. Each time the LUMA box in a store plays content, it records the start and end times on its own and uploads them. Reports calculate impressions, play time, number of stores that showed the ad, and completion rate from these records alone. Even if the same record is sent several times or plays overlap, it is counted only once, so the numbers are never inflated.
No. Records from the time of the outage are saved on the device and uploaded once it reconnects. They are deleted from the device only after the server confirms they have been saved. Any time the device was powered off is shown separately as a “No-record period”.
Every share link has an expiration date. The default is 90 days, and you can set it up to 365 days. When a contract ends, you can revoke a link with a single button, and a revoked link will not open even if someone knows the address. You can also see the view count and the date each link was last opened.
Our team will help you work out the setup and quote.