How do I signal server-side ad insertion (SSAI) in a bid request?
Answer
Set imp.ssai, an integer added in OpenRTB 2.6 with default 0. Values: 0 = status unknown, 1 = all client-side (no server-side stitching), 2 = assets stitched server-side but tracking pixels fired client-side, 3 = all server-side (stitching and tracking). Buyers use it to judge tracker reliability and IVT risk, so send the honest value rather than leaving 0 on stitched CTV streams. Value 2 is the common CTV middle ground: the ad is in the stream but measurement still runs on the device.
Fields in this answer
| Field | Type | Since | Status in 2.6 |
|---|---|---|---|
imp.ssai | integer | 2.6-202204 | Current |
Go deeper
More questions on video, ctv, native, floors, deals, and macros
- How do I build an OpenRTB video bid request? Add an imp.video object to the impression; its presence is what marks the impression as video.
- What is plcmt in OpenRTB video? imp.video.plcmt declares the video placement subtype using AdCOM's Plcmt Subtypes list, which follows the updated IAB digital video guidelines.
- What plcmt value should I send for CTV inventory? Send imp.video.plcmt = 1 (instream) for CTV.
- Should I send placement or plcmt in a video bid request? Send both during the transition, but treat plcmt as authoritative.
- How does ad pod bidding work in OpenRTB 2.6? Each slot in the pod is its own imp, and a shared imp.video.podid ties them together.
- How do I signal rewarded inventory in OpenRTB? Set imp.rwdd = 1.
All 93 questions are listed in the OpenRTB FAQ.