Array of Imp objects representing the impressions offered. At least 1 Imp object is required.

Details via a Site object about the publisher’s website. Only applicable and recommended for websites

This object should be included if the ad supported content is a non-browser application (typically in mobile) as opposed to a website. A bid request must not contain both an App and a Site object. At a minimum, it is useful to provide an App ID or bundle, but this is not strictly required.

This object provides information pertaining to the device through which the user is interacting. Device information includes its hardware, platform, location, and carrier data. The device can refer to a mobile handset, a desktop computer, set top box, or other digital device.

This object contains information known or derived about the human user of the device (i.e., the audience for advertising). The user id is an exchange artifact and may be subject to rotation or other privacy policies. However, this user ID must be stable long enough to serve reasonably as the basis for frequency capping and retargeting.

White list of buyer seats (e.g., advertisers, agencies) allowed
to bid on this impression. IDs of seats and knowledge of the
buyer’s customers to which they refer must be coordinated
between bidders and the exchange a priori.
At most, only one of wseat and bseat should be used in the same request.
Omission of both implies no seat restrictions.

Block list of buyer seats (e.g., advertisers, agencies) restricted
from bidding on this impression. IDs of seats and knowledge
of the buyer’s customers to which they refer must be
coordinated between bidders and the exchange a priori. At
most, only one of wseat and bseat should be used in the
same request. Omission of both implies no seat restrictions.

Array of allowed currencies for bids on this bid request using
ISO-4217 alpha codes. Recommended only if the exchange
accepts multiple currencies.

White list of languages for creatives using ISO-639-1-alpha-2.
Omission implies no specific restrictions, but buyers would be
advised to consider language attribute in the Device and/or
Content objects if available.

Blocked advertiser categories using the IAB content
categories. See https://iabtechlab.com/standards/content-taxonomy/

Block list of advertisers by their domains (e.g., “bol.com”).

Block list of applications by their platform-specific exchange-
independent application identifiers. On Android, these should
be bundle or package names (e.g., com.foo.mygame). On iOS,
these are numeric IDs.

This object describes the nature and behavior of the entity that is the source of the bid request upstream from the exchange. The primary purpose of this object is to define post-auction or upstream decisioning when the exchange itself does not control the final decision. A common example of this is header bidding, but it can also apply to upstream server entities such as another RTB exchange, a mediation platform, or an ad server combines direct campaigns with 3rd party demand in decisioning.

This object contains any legal, governmental, or industry regulations that apply to the request. The coppa flag signals whether or not the request falls under the United States Federal Trade Commission’s regulations for the United States Children’s Online Privacy Protection Act (“COPPA”).

Placeholder for exchange-specific extensions to OpenRTB.