Sovrn's Ad Exchange is built on OpenRTB 2.5 as its core spec, with full passthrough support for oRTB 2.6 and all 2.x fields. That means if you send a field that only exists in a newer 2.x version — like plcmt for video or sua on the Device object — Sovrn will pass it through to demand unchanged. You don't need to strip newer fields from your requests to stay compatible.
For CTV and mobile app integrations specifically, Sovrn requires that you include the attributes defined as required in the oRTB 2.6 spec.
What does "passthrough" mean in practice?
Sovrn will include newer 2.x fields in the bid request it sends to buyers without modifying or dropping them. This means buyers who support those fields can act on them. A few examples of commonly used 2.6 fields that Sovrn passes through:
-
plcmt(Video object) — the recommended replacement forplacement, using updated placement type definitions from AdCOM 1.0. Sovrn supports bothplacementandplcmt; sendingplcmtis recommended. -
sua(Device object) — structured user agent data; useful for improved device targeting. -
ssai(Imp object) — indicates server-side ad insertion; recommended for CTV/streaming integrations. -
schain(Source object) — supply chain transparency. Sovrn supports bothschainandpchain, butschainis preferred.
What about fields beyond the spec?
Any field you pass that Sovrn doesn't recognize natively will still be forwarded to demand in the ext object or as-received, as long as it doesn't conflict with required fields. When in doubt, send more context rather than less — demand partners generally reward richer signals with higher bids.
For the full list of supported objects, required fields, and recommended attributes, see the Sovrn oRTB Specs article.
Questions? Concerns? Our team would be more than happy to help. Reach out to our Support Team here.