Imp.displaymanager
Name of the SDK, mediation partner, or player that will render the ad, typically in apps and video players. The spec recommends it for video and app inventory.
Field facts
- Path
imp.displaymanager- Object
- Imp
- Type
- string
- Requirement
- Optional
- Added
- OpenRTB 2.0
- Spec section
- 3.2.4
How it is used
Buyers read it together with Imp.displaymanagerver to judge which creative formats and measurement scripts will work in that renderer. Send a stable identifier for the rendering technology rather than a free-text description.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"displaymanager": "prebid-mobile"
}
]
}Common mistakes
- Sending the app's own name instead of the rendering SDK tells the buyer nothing about how the ad will render.
Version history
Added in OpenRTB 2.0, and present in the latest snapshot. The table shows how each version's spec text types the field.
| Versions | Type in the spec | Required | Deprecated |
|---|---|---|---|
| 2.0 to 2.1 | string | No | No |
| 2.2 | string | No | No |
| 2.3 to 2.4 | string | No | No |
| 2.5 to 2.6-202606 | string | No | No |
Related fields
Other Imp fields
audiobannerbidfloorbidfloorcurclickbrowserdisplaymanagerverdtexpextidiframebusterinstlmetricnativepmpqtyrefreshrwddsecuressaitagidvideo
For a walkthrough of the whole object, read Bid request anatomy.