When you buy a digital out-of-home campaign, you cannot see most of the screens yourself. You depend on a record, supplied by the media owner and the platforms in between, that your ad appeared where and when it was meant to. That record is called proof of play, and it is the closest thing DOOH has to a delivery receipt.
In short: proof of play is a log showing that a specific ad played on a specific screen at a specific time. It is generated by the screen's content player, passed to the supply platform and then to the buyer's demand platform, where it feeds campaign reports. Proof of play confirms the ad was shown. It does not confirm that anyone saw it. Common gaps include missing logs, delays, mismatched screen IDs and playback that happened without audience present, so buyers should know how to check the data and what to ask when it looks wrong.
1What Proof of Play Is
Each screen in a network runs on a content management system and a media player. When an ad is scheduled, the player requests or retrieves the creative, displays it for its set duration and records the event. The record usually includes the screen identifier, the creative identifier, the start time and the duration. Together these entries make up the proof of play log.
In programmatic buying, the same event also triggers an impression record in the buying platform. This is how a demand-side platform such as Hivestack, Vistar Media or The Trade Desk can report impressions against a deal. If you are new to how the pieces connect, our guide on what programmatic DOOH is sets out the roles of each platform.
This guide covers the practical side: how the record is created, how to test it and what to do when it does not add up. The aim is not to distrust every report, but to give buyers a reasonable way to check delivery without slowing the campaign.
It also helps to remember that proof of play serves more than one purpose. It supports billing, because buyers pay for delivered plays. It supports optimization, because the pattern of plays shows where a campaign is strong or weak. And it supports measurement, because outcome studies need to know where and when the ad ran. A record that is wrong at the source affects all three.
Players differ in quality. Some networks run modern systems that report plays almost as they happen, while others rely on older equipment that uploads logs at set times. Neither is wrong, but the difference affects how soon you can check delivery and how confident you can be in the numbers. Ask about it during planning and not after the first report arrives.
2How Proof of Play Reaches Your Report
The path from screen to report has several steps, and each can introduce delay or error. The player records the play. The media owner's system sends it to the supply platform. The supply platform passes it to the demand platform. The demand platform aggregates it into the campaign dashboard or export you see.
- Screen player: logs each play with time, screen and creative.
- Media owner system: collects logs, usually in batches.
- Supply platform: matches logs to bids and deals.
- Demand platform: counts impressions and reports delivery.
- Agency or brand report: combines the data with other channels.
Because logs are often sent in batches, delivery figures can lag behind real playback. Reports for the most recent days may be incomplete, which is worth remembering before you act on early numbers.
Differences between platforms are also normal. A supply platform and a demand platform may count impressions at slightly different moments, for example when the bid is won versus when the play is confirmed. A small gap is expected. A large or growing gap points to a problem with logs, identifiers or timing and deserves a closer look.
Time zones deserve special attention in multi-market campaigns. A campaign planned in one region and played in another can show plays at odd hours if the report is set to the wrong zone. Confirm the reporting time zone with the platform at setup, and note it on every export you share.
3How Proof of Play Is Verified
Logs on their own are only as reliable as the systems that produce them. Verification adds a second source. Options include photo or screenshot proof, where the media owner supplies images of the ad running on the screen; third-party verification vendors that audit logs against a separate feed; and spot checks by field teams or by the buyer's own staff.
| Method | What it shows | Limits |
|---|---|---|
| Player log | That the system recorded a play | Does not prove the screen was on or visible |
| Photo proof | The ad on a real screen at a given time | Samples only, not every play |
| Third-party audit | Logs checked against an independent feed | Adds cost and may not cover every network |
| Field spot check | Playback and screen condition in person | Time-consuming and limited in scope |
Industry bodies such as the DPAA and Geopath publish guidance on measurement and audience data, and these are worth reading when you write verification requirements into a contract. Ask each media owner which methods they support before you commit.
Photo proof deserves a note. It is persuasive because it shows the real screen, but it is a sample, and a single image cannot show how many times an ad played. Treat it as a way to confirm the creative looks right and the screen is working, not as a substitute for the full log. For large or sensitive campaigns, combine methods so that each covers the weakness of another.
4Proof of Play Is Not Audience Proof
This is the point that causes the most confusion. A proof of play log says the ad was displayed. It does not say a person was nearby, looking or paying attention. Audience figures come from a separate source, such as Geopath data, mobile location panels or sensors, and are modeled estimates of how many people could have seen the screen.
Pricing in pDOOH is usually based on a CPM adjusted for the audience a screen reaches, so the two datasets work together: proof of play tells you how many plays took place, and audience data tells you what each play was worth. If either is weak, the cost per impression you calculate will be unreliable. Our DOOH measurement and attribution page explains how we treat each source, and the guide to programmatic DOOH pricing covers the pricing logic.
Another distinction is between plays and impressions. A single play can be counted as multiple impressions when the audience model estimates several viewers per play. When you read a report, check which of the two is being shown and how the multiplier was calculated. Without that detail, two reports with identical delivery can appear to show very different results.
5Common Gaps and What Causes Them
Proof of play problems rarely mean a media owner is acting in bad faith. Most come from technical and process issues, and they are easier to resolve if you know what to look for.
- Missing logs: a player lost connection and did not send its records.
- Delayed logs: batches arrived after the report was generated.
- Screen ID mismatch: the platform and the media owner use different identifiers for the same screen.
- Creative not played: the file failed a check or was never downloaded to the player.
- Playback with no audience: the ad ran when the venue was closed or the screen was off its normal schedule.
- Time zone errors: plays are logged in one time zone and reported in another.
Many of these show up as unexplained differences between the plan and the report, or between two platforms reporting the same campaign. They are also a reason for careful trafficking, which is covered in our pDOOH buying workflow.
It helps to keep a short checklist of the questions to ask when a mismatch appears: which screens, which dates, which creative, and which system reported the difference. With those four answers, most issues can be traced in a single exchange. Without them, discussions tend to go back and forth for days while the campaign continues to run.
6What to Ask For Before You Buy
Put reporting requirements in the plan, not in a dispute after the fact. Ask the media owner or platform for the log format and fields, how often logs are delivered, how missing plays are handled and whether makegoods are offered when a screen fails to play. Ask whether screen-level data is available or only aggregated totals, because screen-level detail makes it far easier to find problems.
Also decide how you will reconcile numbers. Choose one source of truth for billing, usually the demand platform or a third-party audit, and agree acceptable variance between systems. When comparing platforms, the DOOH and pDOOH platform comparison includes reporting transparency among the points to check.
Where the contract allows it, include a clause on what happens if plays fall short, whether through a replacement schedule, a credit or a refund. Buyers who set this out in advance rarely need to rely on it, because media owners know it will be checked.
7Reviewing Reports and Escalating Problems
Review delivery weekly during a campaign instead of waiting for the final report. Look for screens or venues with no plays, plays at unusual hours and sharp changes in daily delivery. Compare the pattern against the plan and against the previous week.
When something looks wrong, send the screen IDs, dates and creative IDs to the platform or media owner, and ask for the raw log for those items. Keep a record of the issue and the response. A partner who handles campaign operations day to day can take this on, and our guide to choosing a pDOOH campaign management partner covers what to expect. For the wider service, see our programmatic DOOH advertising page.






