Imp.ssai

How server-side ad insertion affects asset and tracker retrieval: 0 unknown, 1 all client-side, 2 assets stitched server-side with tracking fired from the client, 3 all server-side. Defaults to 0. Added in OpenRTB 2.6.

CurrentintegerOptionalSince 2.6-202204

Field facts

Path: imp.ssai
Object: Imp
Type: integer
Default: 0
Requirement: Optional
Added: OpenRTB 2.6-202204
Spec section: 3.2.4

How it is used

Most CTV ads are stitched into the stream on a server. The value tells buyers whether impression pixels and verification will fire from the viewer's device or from the stitching server, which changes how they measure and how they screen for fraud. With 2 or 3, the device IP and user agent should still be the viewer's, forwarded by the server.

Allowed values

0, 1, 2, 3.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "imp": [
    {
      "ssai": 2
    }
  ]
}

Common mistakes

Putting ssai inside the video object; it is defined on the Imp.
Sending 3 while Device.ip holds the stitching server's address, which makes real viewers look like data center traffic.

Version history

Added in OpenRTB 2.6-202204, 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.6-202204	Added in the first 2.6 release, published without a structured text archive; the 2.6-202210 republication is the first tagged text.
2.6-202210 to 2.6-202606	integer, default 0	No	No

Versioned rules that name this field

openrtb.2.6.imp.rwdd_ssai OpenRTB 2.6 added rewarded-inventory and SSAI signaling on impressions.

Related fields

Other Imp fields

For a walkthrough of the whole object, read Bid request anatomy.