Imp.secure

Whether the impression requires HTTPS for all creative assets and markup: 1 for secure, 0 for not. When absent the state is unknown, and plain HTTP can be assumed to work. Added in OpenRTB 2.2.

CurrentintegerOptionalSince 2.2

Field facts

Path: imp.secure
Object: Imp
Type: integer
Requirement: Optional
Added: OpenRTB 2.2
Spec section: 3.2.4

How it is used

With 1, every URL the creative loads must be HTTPS, including trackers, VAST media files, and verification scripts, or the page blocks it as mixed content. Buyers that cannot guarantee HTTPS end to end should not bid on secure impressions.

Allowed values

0, 1.

Example

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

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

Common mistakes

Sending true instead of 1. The spec types it as an integer; the boolean form comes from protobuf JSON serializers, and the validator reports openrtb.dialect.bool_for_integer.
Omitting it on HTTPS pages, which lets buyers return HTTP assets the browser then refuses to load.

Version history

Added in OpenRTB 2.2, 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.2	int	No	No
2.3 to 2.4	integer	No	No
2.5 to 2.6-202606	integer	No	No

Versioned rules that name this field

openrtb.2.2.imp.secure OpenRTB 2.2 added secure versus non-secure inventory signaling.
openrtb.2.4.imp.secure.ssl OpenRTB 2.4 broadened SSL and secure-asset expectations for creatives.

Related fields

Other Imp fields

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