Skip to content

Commit

Permalink
2.6-202309
Browse files Browse the repository at this point in the history
2.6-202309
Updated attribute description of bidrequest.id
New acat attribute in Object: Bid Request
New Object: DurFloor that allows sellers to specify price floors for video and audio creatives, whose price varies based on time and associated attributes in Object: Audio, Object: Video and Object: Deal
New attributes in Object: Deal (guaranteed, mincpmpersec, durfloors)
Implementation guidance on the use of Bid Floors
  • Loading branch information
hillslatt authored Sep 28, 2023
2 parents 556bc13 + 96916a5 commit 7e8693a
Show file tree
Hide file tree
Showing 6 changed files with 172 additions and 75 deletions.
147 changes: 112 additions & 35 deletions 2.6.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,9 +133,13 @@ THE STANDARDS, THE SPECIFICATIONS, THE MEASUREMENT GUIDELINES, AND ANY OTHER MAT
- [3.2.31 - Object: Qty](#objectqty)

- [3.2.32 - Object: DOOH](#objectdooh)

- [3.2.33 - Object: Refresh](#objectrefresh)

- [3.2.34 - Object: RefSettings](#objectrefsettings)

- [3.2.35 - Object: DurFloors](#objectdurfloors)

## [4. Bid Response Specification](#bidresponsespec)

- [4.1 - Object Model](#4.2objectmodel)
Expand Down Expand Up @@ -190,26 +194,29 @@ THE STANDARDS, THE SPECIFICATIONS, THE MEASUREMENT GUIDELINES, AND ANY OTHER MAT

- [6.3.4 - Example 4 – Native Markup Returned Inline](#nativemarkupreturnedinline)

## [7. Implementation Notes](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#7-implementation-notes-)
## [7. Implementation Notes](implementation.md#implementationnotes)

- [7.1 - No-Bid Signaling](implementation.md#nobidsignaling)

- [7.1 - No-Bid Signaling](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#71-no-bid-signaling-)
- [7.2 - Impression Expiration](implementation.md#impressionexpiration)

- [7.2 - Impression Expiration](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#72-impression-expiration-)
- [7.3 - PMP & Direct Deals](implementation.md#pmpanddirectdeals)

- [7.3 - PMP & Direct Deals](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#73-pmp--direct-deals-)
- [7.4 - Skippability](implementation.md#skippability)

- [7.4 - Skippability](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#74-skippability-)
- [7.5 - Regs Resources](implementation.md#regsresources)

- [7.5 - Regs Resources](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#75-regs-resources-)
- [7.6 - Pod Bidding for Video and Audio](implementation.md#podbidding)

- [7.6 - Pod Bidding for Video and Audio](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#76-pod-bidding-for-video-and-audio-)
- [7.7 - Network vs Channel Example Cases](implementation.md#networkandchannel)

- [7.7 - Network vs Channel Example Cases](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#77-network-vs-channel-example-cases-)
- [7.8 - Counting Billable Events and Tracked Ads](implementation.md#counting)

- [7.8 - Counting Billable Events and Tracked Ads](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#78-counting-billable-events-and-tracked-ads-)
- [7.9 - Digital Out-Of-Home](implementation.md#dooh)

- [7.9 - Digital Out-Of-Home](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#79---digital-out-of-home-)
- [7.10 - Updated Video Signals](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#710---updated-video-signals)
- [7.10 - Updated Video Signals](implementation.md#videosignals)

- [7.11 - Guidance on the Use of Floors](implementation.md#floors)


## [Appendix A. Additional Information](#appendixa)
Expand Down Expand Up @@ -680,7 +687,7 @@ The following table summarizes the objects in the Bid Request model and serves a

### 3.2.1 - Object: BidRequest <a name="objectbidrequest"></a>

The top-level bid request object contains a globally unique bid request or auction ID. This `id` attribute is required as is at least one impression object (Section 3.2.4). Other attributes in this top-level object establish rules and restrictions that apply to all impressions being offered.
The top-level bid request object contains an exchange unique bid request or auction ID. This `id` attribute is required as is at least one impression object (Section 3.2.4). Other attributes in this top-level object establish rules and restrictions that apply to all impressions being offered.

There are also several subordinate objects that provide detailed data to potential buyers. Among these are the `Site`, `App` and `DOOH`objects, which describe the type of published media in which the impression(s) appear. These objects are highly recommended, but only one applies to a given bid request depending on whether the media is browser-based web content, a non-browser application, or Digital Out of Home inventory respectively.

Expand All @@ -695,7 +702,7 @@ There are also several subordinate objects that provide detailed data to potenti
<tr>
<td><code>id</code></td>
<td>string; required</td>
<td>Unique ID of the bid request, provided by the exchange.</td>
<td>ID of the bid request, assigned by the exchange, and unique for the exchange’s subsequent tracking of the responses. The exchange may use different values for different recipients.</td>
</tr>
<tr>
<td><code>imp</code></td>
Expand Down Expand Up @@ -772,10 +779,15 @@ There are also several subordinate objects that provide detailed data to potenti
<td>string array</td>
<td>Allowed list of languages for creatives using IETF BCP 47I. Omission implies no specific restrictions, but buyers would be advised to consider language attribute in the <code>Device</code> and/or <code>Content</code> objects if available. Only one of <code>wlang</code> or <code>wlangb</code> should be present.</td>
</tr>
<tr>
<td><code>acat</code></td>
<td>string array</td>
<td>Allowed advertiser categories using the specified category taxonomy. <br>The taxonomy to be used is defined by the <code>cattax</code> field. If no <code>cattax</code> field is supplied IAB Content Taxonomy 1.0 is assumed. Only one of <code>acat</code> or <code>bcat</code> should be present.</td>
</tr>
<tr>
<td><code>bcat</code></td>
<td>string array</td>
<td>Blocked advertiser categories using the specified category taxonomy. <br>The taxonomy to be used is defined by the <code>cattax</code> field. If no <code>cattax</code> field is supplied IAB Content Taxonomy 1.0 is assumed.</td>
<td>Blocked advertiser categories using the specified category taxonomy. <br>The taxonomy to be used is defined by the <code>cattax</code> field. If no <code>cattax</code> field is supplied IAB Content Taxonomy 1.0 is assumed. Only one of <code>acat</code> or <code>bcat</code> should be present.</td>
</tr>
<tr>
<td><code>cattax</code></td>
Expand Down Expand Up @@ -972,7 +984,7 @@ The presence of `Banner` (Section 3.2.6), `Video` (Section 3.2.7), and/or `Nativ
<tr>
<td><code>bidfloorcur</code></td>
<td>string; default "USD"</td>
<td>Currency specified using ISO-4217 alpha codes. This may be different from bid currency returned by bidder if this is allowed by the exchange.</td>
<td>Currency specified using ISO-4217 alpha codes. This may be different from bid currency returned by bidder if this is allowed by the exchange. This currency sets the default for all floors specified in the `Imp` object.</td>
</tr>
<tr>
<td><code>clickbrowser</code></td>
Expand Down Expand Up @@ -1327,12 +1339,17 @@ The presence of a `Video` as a subordinate of the `Imp` object indicates that th
<td><code>api</code></td>
<td>integer array</td>
<td>List of supported API frameworks for this impression. Refer to <a href="https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list--api-frameworks-">List: API Frameworks</a> in AdCOM 1.0. If an API is not explicitly listed, it is assumed not to be supported.</td>
</tr>
</tr>
<tr>
<td><code>companiontype</code></td>
<td>integer array</td>
<td>Supported VAST companion ad types. Refer to <a href="https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list--companion-types-">List: Companion Types</a> in AdCOM 1.0. Recommended if companion <code>Banner</code> objects are included via the <code>companionad</code> array. If one of these banners will be rendered as an end-card, this can be specified using the <code>vcm</code> attribute with the particular banner (Section 3.2.6).</td>
</tr>
<tr>
<td><code>durfloors</code></td>
<td>object array</td>
<td>An array of `DurFloors` objects (Section 3.2.35) indicating the floor prices for video creatives of various durations that the buyer may bid with.</td>
</tr>
<tr>
<td><code>ext</code></td>
<td>object</td>
Expand Down Expand Up @@ -1460,7 +1477,7 @@ The presence of a `Audio` as a subordinate of the `Imp` object indicates that th
<td><code>maxseq</code></td>
<td>integer</td>
<td>The maximum number of ads that can be played in an ad pod.</td>
</tr>
</tr>
<tr>
<td><code>feed</code></td>
<td>integer</td>
Expand All @@ -1476,6 +1493,11 @@ The presence of a `Audio` as a subordinate of the `Imp` object indicates that th
<td>integer</td>
<td>Volume normalization mode. Refer to <a href="https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list--volume-normalization-modes-">List: Volume Normalization Modes</a> in AdCOM 1.0.</td>
</tr>
<tr>
<td><code>durfloors</code></td>
<td>object array</td>
<td>An array of `DurFloors` objects (Section 3.2.35) indicating the floor prices for audio creatives of various durations that the buyer may bid with.</td>
</tr>
<tr>
<td><code>ext</code></td>
<td>object</td>
Expand Down Expand Up @@ -1629,29 +1651,42 @@ This object constitutes a specific deal that was struck between a buyer and a se
<tr>
<td><code>bidfloorcur</code></td>
<td>string; default "USD"</td>
<td>Currency specified using ISO-4217 alpha codes. This may be different from bid currency returned by bidder if this is allowed by the exchange.</td>
<td>Currency specified using ISO-4217 alpha codes. This may be different from bid currency returned by bidder if this is allowed by the exchange. This field does not inherit from `Imp.bidfloorcur`; it is either explicitly specified or defaults to USD.</td>
</tr>
<tr>
<td><code>at</code></td>
<td>integer</td>
<td>Optional override of the overall auction type of the bid request, where 1 = First Price, 2 = Second Price Plus, 3 = the value passed in <code>bidfloor</code> is the agreed upon deal price. Additional auction types can be defined by the exchange.</td>
<tr>
</tr>
<tr>
<td><code>wseat</code></td>
<td>string array</td>
<td>Allowed list of buyer seats (e.g., advertisers, agencies) allowed to bid on this deal. IDs of seats and the buyer’s customers to which they refer must be coordinated between bidders and the exchange <i>a priori</i>. Omission implies no seat restrictions.</td>
</tr>
<tr>
</tr>
<tr>
<td><code>wadomain</code></td>
<td>string array</td>
<td>Array of advertiser domains (e.g., advertiser.com) allowed to bid on this deal. Omission implies no advertiser restrictions.</td>
</tr>
<tr>
<td><code>guar</code></td>
<td>integer, default 0</td>
<td>Indicates that the deal is of type `guaranteed` and the bidder must bid on the deal, where 0 = not a guaranteed deal, 1 = guaranteed deal.</td>
</tr>
<tr>
<td><code>mincpmpersec</code></td>
<td>float</td>
<td>Minimum CPM per second. This is a price floor for video or audio impression opportunities, relative to the duration of bids an advertiser may submit.</td>
</tr>
<tr>
<td><code>durfloors</code></td>
<td>object array</td>
<td>Container for floor price by duration information, to be used if a given deal is eligible for video or audio demand. An array of DurFloors objects (see Section 3.2.35).</td>
</tr>
<tr>
<td><code>ext</code></td>
<td>object</td>
<td>Placeholder for exchange-specific extensions to OpenRTB.</td>
</td>
</td>
</tr>
</table>

Expand Down Expand Up @@ -1683,7 +1718,7 @@ This object should be included if the ad supported content is a website as oppos
</tr>
<tr>
<td><code>cattax</code></td>
<td>integer</td>
<td>integer; default 1</td>
<td>The taxonomy in use. Refer to the AdCOM <a href="https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list_categorytaxonomies">List: Category Taxonomies</a> for values. If no cattax field is supplied IAB Cotent Category Taxonomy 1.0 is assumed.</td>
<tr>
</tr>
Expand Down Expand Up @@ -2963,6 +2998,40 @@ Information on how often and what triggers an ad slot being refreshed.
</tr>
</table>

### 3.2.35 - Object: DurFloors <a name="objectdurfloors"></a>

This object allows sellers to specify price floors for video and audio creatives, whose price varies based on time. For example: 1-15 seconds at a floor of $5; 16-30 seconds at a floor of $10, > 31 seconds at a floor of $20. There are no explicit constraints on the defined ranges, nor guarantees that they don't overlap. In cases where multiple ranges may apply, it is up to the buyer and seller to coordinate on which floor is applicable.

<table>
<tr>
<td><strong>Attribute&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</strong></td>
<td><strong>Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</strong></td>
<td><strong>Description</strong></td>
</tr>
<tr>
<td><code>mindur</code></td>
<td>integer</td>
<td>An integer indicating the low end of a duration range. If this value is missing, the low end is unbounded. Either mindur or maxdur is required, but not both.</td>
</tr>
<tr>
<td><code>maxdur</code></td>
<td>integer</td>
<td>An integer indicating the high end of a duration range. If this value is missing, the high end is unbounded. Either mindur or maxdur is required, but not both.</td>
</tr>
<tr>
<td><code>bidfloor</code></td>
<td>float; default 0</td>
<td>Minimum bid for a given impression opportunity, if bidding with a creative in this duration range, expressed in CPM. For any creatives whose durations are outside of the defined min/max, the `bidfloor` at the `Imp` level will serve as the default floor.</td>
</tr>
<tr>
<td><code>ext</code></td>
<td>object</td>
<td>Placeholder for vendor specific extensions to this object.</td>
</td>
</td>
</tr>
</table>


# 4. Bid Response Specification <a name="bidresponsespec"></a>

Expand Down Expand Up @@ -4067,27 +4136,29 @@ Following is an example of a bid response that returns a native ad inline to be
```


# [7. Implementation Notes](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#7-implementation-notes-)
## [7. Implementation Notes](implementation.md#implementationnotes)

- [7.1 - No-Bid Signaling](implementation.md#nobidsignaling)

- [7.1 - No-Bid Signaling](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#71-no-bid-signaling-)
- [7.2 - Impression Expiration](implementation.md#impressionexpiration)

- [7.2 - Impression Expiration](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#72-impression-expiration-)
- [7.3 - PMP & Direct Deals](implementation.md#pmpanddirectdeals)

- [7.3 - PMP & Direct Deals](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#73-pmp--direct-deals-)
- [7.4 - Skippability](implementation.md#skippability)

- [7.4 - Skippability](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#74-skippability-)
- [7.5 - Regs Resources](implementation.md#regsresources)

- [7.5 - Regs Resources](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#75-regs-resources-)
- [7.6 - Pod Bidding for Video and Audio](implementation.md#podbidding)

- [7.6 - Pod Bidding for Video and Audio](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#76-pod-bidding-for-video-and-audio-)
- [7.7 - Network vs Channel Example Cases](implementation.md#networkandchannel)

- [7.7 - Network vs Channel Example Cases](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#77-network-vs-channel-example-cases-)
- [7.8 - Counting Billable Events and Tracked Ads](implementation.md#counting)

- [7.8 - Counting Billable Events and Tracked Ads](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#78-counting-billable-events-and-tracked-ads-)
- [7.9 - Digital Out-Of-Home](implementation.md#dooh)

- [7.9 - Best Practices for server-side billing notifications](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/implementation.md#best-practices-for-server-side-billing-notifications-)
- [7.10 - Updated Video Signals](implementation.md#videosignals)

- [7.10 - Digital Out-Of-Home](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/OOH-Ammends/implementation.md#79---digital-out-of-home-)
- [7.11 - Guidance on the Use of Floors](implementation.md#floors)


# Appendix A. Additional Information <a name="appendixa"></a>
Expand Down Expand Up @@ -4184,6 +4255,12 @@ This appendix serves as an index of specification changes across 2.x versions. T
<td><code><b>3.2.1, 3.2.16, 4.2.3, 3.2.18</b></code></td>
<td>Added new language field to support IETF BCP 47, IETF BCP 47 offers additional layers of granularity, for example, differentiating written language versions of the same spoken language (e.g. Traditional and Simplified Chinese), https://en.wikipedia.org/wiki/IETF_language_tag</td>
</tr>
<td><code><b>3.2.3</b></code></td>
<td><b>Object: Regs</b> added `gdpr` attribute (previously ext)</td>
</tr><tr>
<td><code><b>3.2.20</b></code></td>
<td><b>Object: User</b> added `consent` attribute (previously ext)</td>
</tr><tr>
<tr>
<td><code><b>5</b></code></td>
<td>Removed section (Enumerated Lists) All references now point to AdCOM 1.0 / OpenRTB 3.0 Lists</td>
Expand Down
File renamed without changes
File renamed without changes
Binary file added assets/interstitial.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes
Loading

0 comments on commit 7e8693a

Please sign in to comment.