Server-to-Server for Screens 27 DOOH Bid Flow SSP Server Prebid Server Demand Partners Physical Screen 1 on trigger 2 OpenRTB DOOH 3 bids 4 creative 5 display 6 confirm play P_
Server-to-Server for Screens DOOH Bid Flow 27 No browser, no app, no SDK. SSP fires 1 on the content loop; context shifts the trigger. dooh replaces site/app in OpenRTB 2 3 ; imp.qty.multiplier scales viewer count per play. Unlike 9 , render lags win by hours. 6 proof-of-play: async, ≤48h. FIELD NOTES → imp.qty.multiplier can be <1 (3 AM empty hall) or 100+ (Times Square) → Billing = (price/1000) x multiplier — not per-play → nurl fires at win; burl fires at render — split can be hours apart P_ atd.postindustria.com/27

How It Works

No browser, no app, no SDK. SSP fires [1] on the content loop; context shifts the trigger. `dooh` replaces `site`/`app` in OpenRTB [2][3]; `imp.qty.multiplier` scales viewer count per play. Unlike {9}, render lags win by hours. [6] proof-of-play: async, ≤48h.

Field Notes

  • `imp.qty.multiplier` can be <1 (3 AM empty hall) or 100+ (Times Square)
  • Billing = (price/1000) x multiplier — not per-play
  • `nurl` fires at win; `burl` fires at render — split can be hours apart

Questions about Server-to-Server for Screens?

Get expert guidance from our team. We'll help you implement it.