OpenRTB 2.6 Specifications
Overview
This document outlines Verve Brand+ support for the OpenRTB 2.6 specifications. It highlights the key changes introduced in OpenRTB 2.6 and details which new features are supported.
OpenRTB 2.6: A New Versioning Approach
OpenRTB 2.6 introduces a significant change in versioning. Version numbers are now incremented only for breaking changes. This means that OpenRTB 2.6 will continue to evolve with new objects, attributes, and features without changing the version number, as long as these additions are non-breaking. Verve Brand+ encourages publishers and demand partners to actively communicate about newly supported features and align on their integration plans.
Major Changes in OpenRTB 2.6 and Verve Brand+ Support
Supported Objects
The table below provides a list of objects supported in OpenRTB 2.6 and Verve Brand+.
| Object | Description | Detail |
|---|---|---|
Qty | Verve Brand+ supports this object for describing the source of the multiplier value in Digital Out of Home (DOOH). | For more detail on Qty, see Qty Object section. |
DOOH | Verve Brand+ supports programmatic buys of DOOH inventory using this object | For more detail on DOOH, see DOOH Object section. |
UserAgent | Verve Brand+ supports the structured UserAgent object for detailed user agent information. | For more detail on UserAgent, see UserAgent Object section. |
BrandVersion | Verve Brand+ supports the BrandVersion object to identify name and version of a device's browser or similar software component. | For more detail on BrandVersion, see BrandVersion Object section. |
Refresh | Verve Brand+ supports the Refresh object for providing minimum exposure time details before ad refresh | For more detail on Refresh, see Refresh Object section. |
RefSettings | Verve Brand+ supports the RefSettings object for ad slot refresh information | For more detail on RefSettings, see RefSettings Object section. |
Unsupported Objects
The Open RTB 2.6 and Verve Brand+ do not support the following object.
DurFloors
Supported Attributes
The table below provides a list of attributes supported in OpenRTB 2.6 and Verve Brand+.
| Attribute | Type | Description |
|---|---|---|
BidRequest.gpp | string | Verve Brand+ supports the Global Privacy Protection string in the BidRequest object's Regs section. |
BidRequest.gpp_sid | integer array | Verve Brand+ supports the use of gpp_sid to indicate the applicable sections of the Global Privacy Protection string |
Site.inventorypartnerdomain | string | Verve Brand+ supports these attributes in the Site and App objects for inventory authorization purposes. |
App.inventorypartnerdomain | string | |
Imp.rwdd | integer | Verve Brand+ supports the rwdd attribute to signal rewarded ad formats. |
Device.mccmnc | string | Verve Brand+ supports the mccmnc attribute for capturing mobile country code and network information. |
BidRequest.acat | string array | Verve Brand+ supports the acat attribute to allow specific advertiser categories based on the defined taxonomy. |
Deal.guar | integer | Verve Brand+ supports the guaranteed attribute to indicate guaranteed deals. |
Deal.mincpmpersec | float | Verve Brand+ supports the use of mincpmpersec to specify the minimum CPM per second for video or audio impressions |
Video.plcmt | integer | Verve Brand+ supports the plcmt attribute in the Video object to align with updated digital video definitions. |
Back to → Supported Attributes ↑
Unsupported Attributes
The Open RTB 2.6 and Verve Brand+ do not support the following attribute.
Deal.durfloorsEID.inserterEID.matcherEID.mm
Deprecated Attributes
The table below lists the deprecated attributes in OpenRTB 2.6 that Verve Brand+ continues to support, as well as those that are no longer supported
Note:
The Supported Deprecated attributes are indicated with √, while non-supported attributes are marked with x.
| Deprecated Attribute | Object | Verve Support+ | |
|---|---|---|---|
api | bidrequest | video | √ |
| banner | √ | ||
| native | √ | ||
bidresponse | audio | √ | |
| bid | √ | ||
placement | video | √ | |
didsha1 | device | √ | |
didmd5 | device | √ | |
dpidsha1 | device | √ | |
dpidmd5 | device | √ | |
macsha1 | device | x | |
macmd5 | device | x | |
yob | user | √ | |
gender | user | √ |
Back to → Deprecated Attributes ↑
Unsupported Objects and Attributes: Handling and Future Support
Currently, Verve Brand+ does not support the following objects and attributes:
Object
DurFloorsAudio
Attribute
Deal.durfloors
Verve Brand+ is continuously evaluating new OpenRTB features and will assess the feasibility of supporting these and other currently unsupported elements in future releases.
When Verve Brand+ encounters an unsupported object or attribute in a bid request, it will either:
- Ignore it or
- Pass it through without processing, depending on the specific element and its context.
Verve Brand+ will communicate any changes in its handling of unsupported OpenRTB 2.6 elements through updated documentation.
2.6 Technical Specifications
Object: BidRequest
The table below shows the Verve Brand+ support for BidRequest Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the BidRequest object, see Section 3.2.1 Object: Bid Request (Page 18 of the Open RTB 2.6 PDF).
Note:
Field1 are newly added in the oRTB 2.6 and supported by Verve Brand+.
Table: Verve Brand+ Supports for BidRequest Attributes
| Field | Scope | Type | Default |
|---|---|---|---|
id | required | string | - |
imp | required | object array | - |
site | recommended | object | - |
app | recommended | object | - |
dooh | optional | object | - |
device | recommended | object | - |
user | recommended | object | - |
test | optional | integer | 0 |
at | optional | integer | 2 |
tmax | optional | integer | - |
wseat | optional | string array | - |
bseat | optional | string array | - |
allimps | optional | integer | 0 |
cur | optional | string array | - |
wlang | optional | string array | - |
wlangb | optional | string array | - |
acat1 | optional | string array | - |
bcat | optional | string array | - |
cattax1 | optional | integer | 1 |
badv | optional | string array | - |
bapp | optional | string array | - |
source | optional | object | - |
regs | optional | object | - |
ext | optional | object | - |
Back to → Object: BidRequest ↑
Object: Source
The table below shows the Verve Brand+ support for Source Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Source object, see Section 3.2.2 Object: Source (Page 19 of the Open RTB 2.6 PDF).
Table: Verve Brand+ Supports for Source Attributes
| Field | Scope | Type | Default |
|---|---|---|---|
fd | recommended | integer | - |
tid | recommended | string | - |
pchain | recommended | string | - |
schain | recommended | object | - |
ext | optional | object | - |
Object: Regs
The table below shows the Verve Brand+ support for Regs Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Reg object, see Section 3.2.3 Object: Reg (Page 19 of the Open RTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+.
Table: Verve Brand + supports for Regs Attributes
| Field | Scope | Type | Default |
|---|---|---|---|
coppa | optional | integer | - |
gdpr1 | optional | integer | - |
us_privacy | optional | string | - |
gpp1 | optional | string | - |
gpp_sid1 | optional | integer array | - |
ext | optional | object | - |
Object: Imp
The table below shows the Verve Brand+ support for Imp Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Imp object, see Section 3.2.4 Object: Imp (Page 20 of the Open RTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+.
Table: Verve Brand+ support for Imp Attributes
| Field | Scope | Type | Default |
|---|---|---|---|
id | required | string | - |
metric | optional | object array | - |
banner | optional | object | - |
video | optional | object | - |
native | optional | object | - |
pmp | optional | object | - |
displaymanager | optional | string | - |
displaymanagerver | optional | string | - |
instl | optional | integer | 0 |
tagid | optional | string | - |
bidfloor | optional | float | 0 |
bidfloorcur | optional | string | USD |
clickbrowser | optional | integer | - |
secure | optional | integer | - |
iframebuster | optional | string array | - |
rwdd1 | optional | integer | 0 |
ssai | optional | integer | 0 |
exp | optional | integer | - |
qty | optional | object | - |
dt | optional | float | - |
refresh | optional | object | - |
ext | optional | object | - |
Object: Metric
The table below shows the Verve Brand+ support for Metric Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Metric object, see Section 3.2.5 Object: Metric (Page 21 of the OpenRTB 2.6 PDF).
Table: Verve Brand + supports for Metric Attributes
| Field | Scope | Type | Default |
|---|---|---|---|
type | required | string | - |
value | required | float | - |
vendor | recommended | string | - |
ext | optional | object | - |
Object: Banner
The table below shows the Verve Brand+ support for Banner Attributes in the OpenRTB 2.6 specification. For the latest updates on the Banner object description, see Section 3.2.6 Object: Banner (Page 21 of the OpenRTB 2.6 PDF).
Table: Verve Brand + supports for Banner Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
format | recommended | object array | Array of format objects (Section 3.2.10) representing the banner sizes permitted. If none are specified, then use of the h and w attributes is highly recommended. | - |
w | optional | integer | Exact width in device-independent pixels (DIPS); recommended if no Format objects are specified. | - |
h | optional | integer | Exact height in device-independent pixels (DIPS); recommended if no Format objects are specified. | - |
btype | optional | integer array | Blocked banner ad types. Values: 1 = XHTML Text Ad, 2 = XHTML Banner Ad, 3 = JavaScript Ad, 4 = iframe. | - |
battr | optional | integer array | Blocked creative attributes. Refer to List: Creative Attributes in AdCOM 1.0. | - |
pos | optional | integer | Ad position on screen. Refer to List: Placement Positions in AdCOM 1.0. | - |
mimes | optional | string array | Content MIME types supported. Popular MIME types may include, “image/jpeg” and “image/gif”. | - |
topframe | optional | integer | Indicates if the banner is in the top frame as opposed to an iframe, where 0 = no, 1 = yes. | - |
expdir | optional | integer | Directions in which the banner may expand. Refer to List: Expandable Directions in AdCOM 1.0. | - |
api | optional | integer array | List of supported API frameworks for this impression. Refer to List: API Frameworks in AdCOM 1.0. If an API is not explicitly listed, it is assumed not to be supported. | - |
id | optional | string | Unique identifier for this banner object. Recommended when Banner objects are used with a Video object (Section 3.2.7) to represent an array of companion ads. Values usually start at 1 and increase with each object; should be unique within an impression. | - |
vcm | optional | integer | Relevant only for Banner objects used with a Video object (Section 3.2.7) in an array of companion ads. Indicates the companion banner rendering mode relative to the associated video, where 0 = concurrent, 1 = end-card. | |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. |
Object: Video
The table below shows the Verve Brand+ support for Video Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Video object, see Section 3.2.7 Object: Video (Page 23 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+.Field2 are deprecated from the OpenRTB 2.6 specification but continue to support by Verve Brand+.
Table: Verve Brand + supports for Video Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
mimes | required | string array | Content MIME types supported (e.g., “video/mp4”). | - |
minduration | recommended | integer | Minimum video ad duration in seconds. This field is mutually exclusive with rqddurs; only one of minduration and rqddurs may be in a bid request. | 0 |
maxduration | recommended | integer | Maximum video ad duration in seconds. This field is mutually exclusive with rqddurs; only one of maxduration and rqddurs may be in a bid request. | - |
startdelay | recommended | integer | Indicates the start delay in seconds for pre-roll, mid-roll, or post-roll ad placements. Refer to List: Start Delay Modes in AdCOM 1.0. | - |
maxseq1 | recommended | integer | Indicates the maximum number of ads that may be served into a “dynamic” video ad pod (where the precise number of ads is not predetermined by the seller). See Section 7.6 for more details. | - |
poddur1 | recommended | integer | Indicates the total amount of time in seconds that advertisers may fill for a “dynamic” video ad pod (See Section 7.6 for more details), or the dynamic portion of a “hybrid” ad pod. This field is required only for the dynamic portion(s) of video ad pods. | - |
protocols | recommended | integer array | Array of supported video protocols. Refer to List: Creative Subtypes - Audio/Video in AdCOM 1.0. | - |
w | recommended | integer | Width of the video player in device independent pixels (DIPS). | - |
h | recommended | integer | Height of the video player in device independent pixels (DIPS). | - |
podid1 | optional | string | Unique identifier indicating that an impression opportunity belongs to a video ad pod. If multiple impression opportunities within a bid request share the same podid, this indicates that those impression opportunities belong to the same video ad pod. | - |
podseq1 | optional | integer | The sequence (position) of the video ad pod within a content stream. Refer to in AdCOM 1.0 for guidance on the use of this field. | 0 |
rqddurs1 | optional | integer array | Precise acceptable durations for video creatives in seconds. This field is mutually exclusive with minduration and maxduration; if rqddurs is specified, minduration and maxduration must not be specified and vice versa. | - |
placement2 | optional | integer | Video placement type for the impression. Refer to List: Placement Subtypes - Video in AdCOM 1.0. | - |
plcmt1 | optional | integer | Video placement type for the impression. Refer to List: Plcmt Subtypes - Video in AdCOM 1.0. | - |
linearity | optional | integer | Indicates if the impression must be linear, nonlinear, etc. If none specified, assume all are allowed. Refer to List: Linearity Modes in AdCOM 1.0. | - |
skip | optional | integer | Indicates if the player will allow the video to be skipped, where 0 = no, 1 = yes. Refer to List: Creative Attributes in AdCOM 1.0. | - |
skipmin | optional | integer | Videos of total duration greater than this number of seconds can be skippable; only applicable if the ad is skippable. | 0 |
skipafter | optional | integer | Number of seconds a video must play before skipping is enabled; only applicable if the ad is skippable. | 0 |
sequence2 | optional | integer | If multiple ad impressions are offered in the same bid request, the sequence number will allow for the coordinated delivery of multiple creatives. | 0 |
slotinpod1 | optional | integer | For video ad pods, this value indicates that the seller can guarantee delivery against the indicated slot position in the pod. Refer to List: Slot Position in Pod in AdCOM 1.0. | 0 |
mincpmpersec1 | optional | float | Minimum CPM per second. This is a price floor for the "dynamic" portion of a video ad pod, relative to the duration of bids an advertiser may submit. | - |
battr | optional | integer array | Blocked creative attributes. Refer to List: Creative Attributes in AdCOM 1.0. | - |
maxextended | optional | integer | Maximum extended ad duration if extension is allowed. If blank or 0, extension is not allowed. If -1, extension is allowed, and there is no time limit imposed. If greater than 0, then the value represents the number of seconds of extended play supported beyond the maxduration value. | - |
minbitrate | optional | integer | Minimum bit rate in Kbps (kilobits per second). | - |
maxbitrate | optional | integer | Maximum bit rate in Kbps (kilobits per second). | - |
boxingallowed | optional | integer | Indicates if letter-boxing of 4:3 content into a 16:9 window is allowed, where 0=no, 1=yes. | 1 |
playbackmethod | optional | integer array | Playback methods that may be in use. If none are specified, any method may be used. Refer to List: Playback Methods in AdCOM 1.0. | - |
playbackend | optional | integer | The event that causes playback to end. Refer to List: Playback Cessation Modes in AdCOM 1.0. | - |
delivery | optional | integer array | Supported delivery methods (e.g., streaming, progressive). If none specified, assume all are supported. Refer to List: Delivery Methods in AdCOM 1.0. | - |
pos | optional | integer | Ad position on screen. Refer to List: Placement Positions in AdCOM 1.0. | - |
companionad | optional | object array | Array of Banner objects Section 3.2.6 if companion ads are available. | - |
api | optional | integer array | List of supported API frameworks for this impression. Refer to List: API Frameworks in AdCOM 1.0. | - |
companiontype | optional | integer array | Supported VAST companion ad types. Refer to List: Companion Types in AdCOM 1.0. | - |
poddedupe | optional | enum array PROVISIONAL | Indicates pod deduplication settings that will be applied to bid responses. Refer to List: Pod Deduplication in AdCOM 1.0. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Native
The table below shows the Verve Brand+ support for Native Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Native object, see Section 3.2.9 Object: Native (Page 28 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+
Table: Verve Brand + supports for Native Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
request | required | string | Request payload complying with the Native Ad Specification. The root node of the payload, "native", was dropped in the Native Ads Specification 1.1. For Native 1.0, this is a JSON-encoded string consisting of an unnamed root object, with a single subordinate object named 'native', which is the Native Markup Request object, section 4.1 of OpenRTB Native 1.0 specification. For Native 1.1 and higher, this is a JSON-encoded string consisting of an unnamed root object which is itself the Native Markup Request Object, section 4.1 of OpenRTB Native 1.1+. | - |
ver | optional | string | Version of the Dynamic Native Ads API to which request complies; highly recommended for efficient parsing. | - |
api | optional | integer array | List of supported API frameworks for this impression. Refer to List: API Frameworks in AdCOM. If an API is not explicitly listed, it is assumed not to be supported. | - |
battr | optional | integer array | Blocked creative attributes. Refer to List: Creative Attributes in AdCOM. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Format
The table below shows the Verve Brand+ support for Format Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Format object, see Section 3.2.10 Object: Format (Page 28 of the OpenRTB 2.6 PDF).
Table: Verve Brand + supports for Format Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
w | optional | integer | Width in device independent pixels (DIPS). | - |
h | optional | integer | Height in device independent pixels (DIPS). | - |
wratio | optional | integer | Relative width when expressing size as a ratio. | - |
hratio | optional | integer | Relative height when expressing size as a ratio. | - |
wmin | optional | integer | The minimum width in device independent pixels (DIPS) at which the ad will be displayed the size is expressed as a ratio. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Pmp
The table below shows the Verve Brand+ support for Pmp Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Pmpobject, see Section 3.2.11 Object: Pmp (Page 29 of the OpenRTB 2.6 PDF).
Table: Verve Brand + supports for Pmp Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
private_auction | optional | integer | Indicator of auction eligibility to seats named in the Direct Deals object, where 0=all bids are accepted, 1=bids are restricted to the deals specified and the terms thereof. | 0 |
deals | optional | object array | Array of Deal (Section Object:Deal) objects that convey the specific deals applicable to this impression. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Deal
The table below shows the Verve Brand+ support for Deal Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Deal object, see Section 3.2.12 Deal: Format (Page 29 of the OpenRTB 2.6 PDF).
Note:
Field1are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+.
Table: Verve Brand + supports for Deal Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | required | string | A unique identifier for the direct deal. | - |
bidfloor | optional | float | Minimum bid for this impression expressed in CPM. | 0 |
bidfloorcur | optional | string | 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. | USD |
at | optional | integer | Optional override of the overall auction type of the bid request, where 1 = First Price, 2 = Second Price Plus, 3 = the value passed in bidfloor is the agreed upon deal price. Additional auction types can be defined by the exchange. | - |
wseat | optional | string array | 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 a priori. Omission implies no seat restrictions. | - |
wadomain | optional | string array | Array of advertiser domains (for example,  Advertiser.com domain name is for sale ) allowed to bid on this deal. Omission implies no advertiser restrictions. | - |
guar1 | optional | integer | 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. | 0 |
mincpmpersec1 | optional | float | 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. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Site
The table below shows the Verve Brand+ support for Site Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Site object, see Section 3.2.13 Object: Site (Page 30 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+
Table: Verve Brand + supports for Site Attributes
| Field | Scope | Type | Description | Default |
id | recommended | string | Exchange-specific site ID. | - |
name | optional | string | Site name (may be aliased at the publisher's request). | - |
domain | optional | string | Domain of the site (e.g., "Foo.com "). | - |
cattax1 | optional | integer | The taxonomy in use. Refer to the AdCOM List: Category Taxonomies for values. If no cattax field is supplied, IAB Content Category Taxonomy 1.0 is assumed. | 1 |
cat | optional | string array | Array of IAB Tech Lab content categories of the site. The taxonomy to be used is defined by the cattax field. | - |
sectioncat | optional | string array | Array of IAB Tech Lab content categories that describe the current section of the site. The taxonomy to be used is defined by the cattax field. | - |
pagecat | optional | string array | Array of IAB Tech Lab content categories that describe the current page or view of the site. The taxonomy to be used is definied by the cattax field. | - |
page | optional | string | URL of the page where the impression will be shown. | - |
ref | optional | string | Referrer URL that caused navigation to the current page. | - |
search | optional | string | Search string that caused navigation to the current page. | - |
mobile | optional | integer | Indicates if the site has been programmed to optimize layout when viewed on mobile devices, where 0=no, 1=yes. | - |
privacypolicy | optional | integer | Indicates if the site has a privacy policy, where 0 = no, 1 = yes. | - |
publisher | optional | object | Details about the see Publisher (Section 3.2.15) of the site. | - |
content | optional | object | Details about the [Content (Section 3.2.16)](https://iabtechlab.com/wp-content/uploads/2022/04/OpenRTB-2-6_FINAL.pdf#page=32 target= _blank) within the site. | - |
keywords | optional | string | Comma separated list of keywords about the site. Only one of keywords or kwarray may be present. | - |
kwarray | optional | string array | Array of keywords about the site. Only one of keywords or kwarray may be present. | - |
inventorypartnerdomain1 | optional | string | The taxonomy in use. Refer to the AdCOM List: Category Taxonomies for values. If no cattax field is supplied, IAB Content Category Taxonomy 1.0 is assumed. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: App
The table below shows the Verve Brand+ support for App Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the App object, see Section 3.2.14 Object: App (Page 31 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+
Table: Verve Brand + supports for App Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | Exchange-specific seller ID. Every ID must map to only a single entity that is paid for inventory transacted via that ID. Corresponds to a seller_id of a seller in the exchange’s sellers.json file. | |
name | optional | string | Seller name (may be aliased at the seller's request). | |
cattax1 | optional | integer | The taxonomy in use. Refer to the AdCOM List: Category Taxonomies for values. | |
cat | optional | string array | Array of IAB Tech Lab content categories of the publisher. The taxonomy to be used is defined by the cattax field. If no cattax field is supplied Content Category Taxonomy 1.0 is assumed. | |
domain | optional | string | Highest level domain of the seller (e.g., "Seller.com data-annotation-inline-node="true" data-annotation-mark="true" data-renderer-start-pos="32474">Seller.com "). | |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. |
Back to → Object: Site Back to → Object: Site ↑
Object: Publisher
The table below shows the Verve Brand+ support for Publisher Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Publisher object, see Section 3.2.15 Object: Publisher (Page 32 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+
Table: Verve Brand + supports for Publisher Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | Exchange-specific seller ID. Every ID must map to only a single entity that is paid for inventory transacted via that ID. Corresponds to a seller_id of a seller in the exchange’s sellers.json file. | |
name | optional | string | Seller name (may be aliased at the seller's request). | |
cattax1 | optional | integer | The taxonomy in use. Refer to the AdCOM List: Category Taxonomies for values. | |
cat | optional | string array | Array of IAB Tech Lab content categories of the publisher. The taxonomy to be used is defined by the cattax field. If no cattax field is supplied Content Category Taxonomy 1.0 is assumed. | |
domain | optional | string | Highest level domain of the seller (e.g., "Seller.com data-annotation-inline-node="true" data-annotation-mark="true" data-renderer-start-pos="32474">Seller.com "). | |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. |
Object: Content
The table below shows the Verve Brand+ support for Content Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Content object, see Section 3.2.16 Object: Content (Page 32 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+
Table: Verve Brand + supports for Content Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | ID uniquely identifying the content. | - |
episode | optional | integer | Episode number. | - |
title | optional | string | Content title. *Video Examples:* “Search Committee” (television), “A New Hope” (movie), or “Endgame” (made for web). *Non-Video Example:* “Why an Antarctic Glacier Is Melting So Quickly” (Time magazine article). | - |
series | optional | string | Content series. *Video Examples:* “The Office” (television), “Star Wars” (movie), or “Arby ‘N’ The Chief” (made for web). *Non-Video Example:* “Ecocentric” (Time Magazine blog). | - |
season | optional | string | Content season (e.g., “Season 3”). | - |
artist | optional | string | Artist credited with the content. | - |
genre | optional | string | Genre that best describes the content (e.g., rock, pop, etc). | - |
album | optional | string | Album to which the content belongs; typically for audio. | - |
isrc | optional | string | International Standard Recording Code conforming to ISO- 3901. | - |
producer | optional | object | Details about the content Producer (Section 3.2.17). | - |
url | optional | string | URL of the content, for buy-side contextualization or review. | - |
cattax1 | optional | integer | The taxonomy in use. Refer to list List: Category Taxonomies in AdCOM 1.0 for values. | 1 |
cat | optional | string array | Array of IAB Tech Lab content categories that describe the content. The taxonomy to be used is defined by the cattax field. If no cattax field is supplied Content Category Taxonomy 1.0 is assumed. | - |
prodq | optional | integer | Production quality. Refer to List: Production Qualities in AdCOM 1.0. | - |
context | optional | integer | Type of content (game, video, text, etc.). Refer to List: Content Contexts in AdCOM 1.0. | - |
contentrating | optional | string | Content rating (e.g., MPAA). | - |
userrating | optional | string | User rating of the content (e.g., number of stars, likes, etc.). | - |
qagmediarating | optional | integer | Media rating per IQG guidelines. Refer to List: Media Ratings in AdCOM 1.0. | - |
keywords | optional | string | Comma separated list of keywords describing the content. Only one of keywords or kwarray may be present. | - |
kwarray | optional | string array | Array of keywords about the site. Only one of keywords or kwarray may be present. | - |
livestream | optional | integer | 0 = not live, 1 = content is live (e.g., stream, live blog). | - |
sourcerelationship | optional | integer | 0 = indirect, 1 = direct. | - |
len | optional | integer | Length of content in seconds; appropriate for video or audio. | - |
language1 | optional | string | Content language using ISO-639-1-alpha-2. Only one of language or langb should be present. | - |
langb | optional | string | Content language using IETF BCP 47. Only one of language or langb should be present. | - |
embeddable | optional | integer | Indicator of whether the content is embeddable (e.g., an embeddable video player), where 0 = no, 1 = yes. | - |
data | optional | object array | Additional content data. Each Data object (Section 3.2.21) represents a different data source. | - |
network | optional | object | Details about the network (Section 3.2.23) the content is on. | - |
channel | optional | object | Details about the channel (Section 3.2.24) the content is on. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Producer
The table below shows the Verve Brand+ support for Producer Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Producer object, see Section 3.2.17 Object: Producer (Page 34 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+
Table: Verve Brand + supports for ProducerAttributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | Content producer or originator ID. Useful if content is syndicated and may be posted on a site using embed tags. | - |
name | optional | string | Content producer or originator name (e.g., “Warner Bros”). | - |
cattax1 | optional | integer | The taxonomy in use. Refer to the AdCOM 1.0 list List: Category Taxonomies for values. | 1 |
cat | optional | string array | Array of IAB Tech Lab content categories that describe the content producer. The taxonomy to be used is defined by the cattax field. If no cattax field is supplied Content Category Taxonomy 1.0 is assumed. | - |
domain | optional | string | Highest level domain of the content producer (e.g., "producer.com"). | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Device
The table below shows the Verve Brand+ support for Device Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the **Device** object, see Section 3.2.18 Object: Device (Page 34 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+Field2 are deprecated from OpenRTB2.6, but continue to support by Verve Brand+.
Table: Verve Brand + supports for DeviceAttributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
geo | recommended | object | Location of the device assumed to be the user’s current location defined by a Geo object (Section 3.2.19). | - |
dnt | recommended | integer | Standard “Do Not Track” flag as set in the header by the browser, where 0 = tracking is unrestricted, 1 = do not track. | - |
lmt | recommended | integer | “Limit Ad Tracking” signal commercially endorsed (e.g., iOS, Android), where 0 = tracking is unrestricted, 1 = tracking must be limited per commercial guidelines. | - |
ua | optional | string | Browser user agent string. This field represents a raw user agent string from the browser. For backwards compatibility, exchanges are recommended to always populate ua with the User-Agent string, when available from the end user’s device, even if an alternative representation, such as the User-Agent Client-Hints, is available and is used to populate sua. No inferred or approximated user agents are expected in this field. If a client supports User-Agent Client Hints, and sua field is present, bidders are recommended to rely on sua for detecting device type, browser type and version and other purposes that rely on the user agent information, and ignore ua field. This is because the ua may contain a frozen or reduced user agent string. | - |
sua | optional | object | Structured user agent information defined by a UserAgent object (see Section 3.2.29). If both ua and sua are present in the bid request, sua should be considered the more accurate representation of the device attributes. This is because the ua may contain a frozen or reduced user agent string. | - |
ip | optional | string | IPv4 address closest to device. | - |
ipv6 | optional | string | IP address closest to device as IPv6. | - |
devicetype | optional | integer | The general type of device. Refer to List: Device Types in AdCOM 1.0. | - |
make | optional | string | Device make (e.g., “Apple”). | - |
model | optional | string | Device model (e.g., “iPhone”). | - |
os | optional | string | Device operating system (e.g., “iOS”). | - |
osv | optional | string | Device operating system version (e.g., “3.1.2”). | - |
hwv | optional | string | Hardware version of the device (e.g., “5S” for iPhone 5S). | - |
h | optional | integer | Physical height of the screen in pixels. | - |
w | optional | integer | Physical width of the screen in pixels. | - |
ppi | optional | integer | Screen size as pixels per linear inch. | - |
pxratio | optional | float | The ratio of physical pixels to device independent pixels. | - |
js | optional | integer | Support for JavaScript, where 0 = no, 1 = yes. | - |
geofetch | optional | integer | Indicates if the geolocation API will be available to JavaScript code running in the banner, where 0 = no, 1 = yes. | - |
flashver | optional | string | Version of Flash supported by the browser. | - |
language | optional | string | Browser language using ISO-639-1-alpha-2. Only one of language or langb should be present. | - |
langb | optional | string | Browser language using IETF BCP 47. Only one of language or langb should be present. | - |
carrier | optional | string | Carrier or ISP (e.g., “VERIZON”) using exchange curated string names which should be published to bidders *a priori*. | - |
mccmnc1 | optional | string | Mobile carrier as the concatenated MCC-MNC code (e.g., “310-005” identifies Verizon Wireless CDMA in the USA). Refer to | - |
connectiontype | optional | integer | Network connection type. Refer to List: Connection Types in AdCOM 1.0. | - |
ifa | optional | string | ID sanctioned for advertiser use in the clear (i.e., not hashed) Unless prior arrangements have been made between the buyer and the seller directly, the value in this field is expected to be an ID derived from a call to an advertising API provided by the device’s Operating System. | - |
didsha12 | optional | string | Hardware device ID (e.g., IMEI); hashed via SHA1. | - |
didmd52 | optional | string | Hardware device ID (e.g., IMEI); hashed via MD5. | - |
dpidsha12 | optional | string | Platform device ID (e.g., Android ID); hashed via SHA1. | - |
dpidmd52 | optional | string | Platform device ID (e.g., Android ID); hashed via MD5. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Geo
The table below shows the Verve Brand+ support for Geo Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the Geo object, see Section 3.2.19 Object: Geo (Page 36 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+
Table: Verve Brand + supports for Geo Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
lat | optional | float | Latitude from -90.0 to +90.0, where negative is south. | - |
lon | optional | float | Longitude from -180.0 to +180.0, where negative is west. | - |
type | optional | integer | Source of location data; recommended when passing lat/lon. Refer to List: Location Types in AdCOM 1.0. | - |
accuracy | optional | integer | Estimated location accuracy in meters; recommended when lat/lon are specified and derived from a device’s location services (i.e., type = 1). Note that this is the accuracy as reported from the device. Consult OS specific documentation (e.g., Android, iOS) for exact interpretation. | - |
lastfix | optional | integer | Number of seconds since this geolocation fix was established. Note that devices may cache location data across multiple fetches. Ideally, this value should be from the time the actual fix was taken. | - |
ipservice | optional | integer | Service or provider used to determine geolocation from IP address if applicable (i.e., type = 2). Refer to List: IP Location Services in AdCOM 1.0. | - |
country | optional | string | Country code using ISO-3166-1-alpha-3. | - |
region | optional | string | Region code using ISO-3166-2; 2-letter state code if USA. | - |
regionfips104 | optional | string | Region of a country using FIPS 10-4 notation. While OpenRTB supports this attribute, it was withdrawn by NIST in 2008. | - |
metro | optional | string | Google metro code; similar to but not exactly Nielsen DMAs. See Appendix A for a link to the codes. | - |
city | optional | string | City using United Nations Code for Trade & Transport Locations. See Appendix A for a link to the codes. | - |
zip | optional | string | ZIP or postal code. | - |
utcoffset | optional | integer | Local time as the number +/- of minutes from UTC. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: User
The table below shows the Verve Brand+ support for User Attributes in the OpenRTB 2.6 specification. For the most up-to-date details on all available attributes in the User object, see Section 3.2.20 Object: User(Page 37 of the OpenRTB 2.6 PDF).
Note:
Field1 are newly added to the OpenRTB 2.6 specification and supported by Verve Brand+.Field2 are deprecated from OpenRTB 2.6, but continue to support by Verve Brand+.
Table: Verve Brand + supports for User Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | Exchange-specific ID for the user. Unless prior arrangements have been made between the buyer and the seller directly, the value in this field is expected to be derived from an ID sync. (see Appendix: Cookie Based ID Syncing) | - |
buyeruid | optional | string | Buyer-specific ID for the user as mapped by the exchange for the buyer.Unless prior arrangements have been made between the buyer and the seller directly, the value in this field is expected to be derived from an ID sync. (see Appendix: Cookie Based ID Syncing) | - |
yob2 | optional | integer | Year of birth as a 4-digit integer. | |
gender2 | optional | string | Gender, where “M” = male, “F” = female, “O” = known to be other (i.e., omitted is unknown). | - |
keywords | optional | string | Comma separated list of keywords, interests, or intent. Only one of keywords or kwarray may be present. | - |
kwarray | optional | string array | Array of keywords about the user. Only one of keywords or kwarray may be present. | - |
customdata | optional | string | Optional feature to pass bidder data that was set in the exchange’s cookie. The string must be in base85 cookie safe characters and be in any format. Proper JSON encoding must be used to include “escaped” quotation marks. | - |
geo | optional | object | Location of the user’s home base defined by a Geo object (Section 3.2.19). This is not necessarily their current location. | - |
data | optional | object array | Additional user data. Each Data object (Section 3.2.21) represents a different data source. | - |
consent1 | optional | string | When GDPR regulations are in effect this attribute contains the Transparency and Consent Framework’s Consent String data structure. | - |
eids | optional | object array | Details for support of a standard protocol for multiple third party identity providers (see Section Object: EID). | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Data
The table below shows Verve Brand+ support for the Data Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand + supports for Data Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | Exchange-specific ID for the data provider. | - |
name | optional | string | Exchange-specific name for the data provider. | - |
segment | optional | object array | Array of Segment (Section 3.2.22) objects that contain the actual data values. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Segment
The table below shows Verve Brand+ support for the Segment Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for Segment Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | ID of the data segment specific to the data provider. | - |
name | optional | string | Name of the data segment specific to the data provider. | - |
value | optional | string | String representation of the data segment value. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Network
The table below shows Verve Brand+ support for the Network Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ support for Network Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | A unique identifier assigned by the publisher. This may not be a unique identifier across all supply sources. | - |
name | optional | string | Channel the content is on (e.g., a TV channel like “WABC-TV") | - |
domain | optional | string | The primary domain of the channel (e.g. “ ABC7 Eyewitness News - WABC-TV New York ” in the case of the local channel WABC-TV). It is recommended to include the top private domain (PSL+1) for DSP targeting normalization purposes. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Channel
The table below shows Verve Brand+ support for the Channel Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for Channel Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | A unique identifier assigned by the publisher. This may not be a unique identifier across all supply sources. | - |
name | optional | string | Channel the content is on (e.g., a TV channel like “WABC-TV") | - |
domain | optional | string | The primary domain of the channel (e.g. “ABC7 Eyewitness News - WABC-TV New York ” in the case of the local channel WABC-TV). It is recommended to include the top private domain (PSL+1) for DSP targeting normalization purposes. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: SupplyChain
The table below shows Verve Brand+ support for the SupplyChain Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for SupplyChain Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
complete | required | integer | Flag indicating whether the chain contains all nodes involved in the transaction leading back to the owner of the site, app or other medium of the inventory, where 0 = no, 1 = yes. | - |
nodes | required | object array | Array of SupplyChainNode objects in the order of the chain. In a complete supply chain, the first node represents the initial advertising system and seller ID involved in the transaction, i.e. the owner of the site, app, or other medium. In an incomplete supply 1chain, it represents the first known node. The last node represents the entity sending this bid request. | - |
ver | required | string | Version of the supply chain specification in use, in the format of “major.minor”. For example, for version 1.0 of the spec, use the string “1.0”. | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Back to → Object: SupplyChain ↑
Object: SupplyChainNode
The table below shows Verve Brand+ support for the SupplyChainNodeAttributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for SupplyChainNode Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
asi | required | string | The canonical domain name of the SSP, Exchange, Header Wrapper, etc system that bidders connect to. This may be the operational domain of the system, if that is different than the parent corporate domain, to facilitate WHOIS and reverse IP lookups to establish clear ownership of the delegate system. This should be the same value as used to identify sellers in an ads.txt file if one exists. | - |
sid | required | string | The identifier associated with the seller or reseller account within the advertising system. This must contain the same value used in transactions (i.e. OpenRTB bid requests) in the field specified by the SSP/exchange. Typically, in OpenRTB, this is publisher.id. For OpenDirect it is typically the publisher’s organization ID. Should be limited to 64 characters in length. | - |
rid | optional | string | The OpenRTB RequestId of the request as issued by this seller. | - |
name | optional | string | The name of the company (the legal entity) that is paid for inventory transacted under the given seller_ID. This value is optional and should NOT be included if it exists in the advertising system’s sellers.json file. | - |
domain | optional | string | The business domain name of the entity represented by this node. This value is optional and should NOT be included if it exists in the advertising system’s sellers.json file. | |
hp | optional | integer | Indicates whether this node will be involved in the flow of payment for the inventory. When set to 1, the advertising system in the asi field pays the seller in the sid field, who is responsible for paying the previous node in the chain. When set to 0, this node is not involved in the flow of payment for the inventory. For version 1.0 of SupplyChain, this property should always be 1. Implementers should ensure that they propagate this field onwards when constructing SupplyChain objects in bid requests sent to a downstream advertising system. | |
ext | optional | object | Placeholder for advertising-system specific extensions to this object. |
Back to → Object: SupplyChainNode ↑
Object: EID
The table below shows Verve Brand+ support for the EID Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for EID Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
inserter2 | optional | string | The canonical domain name of the entity (publisher, publisher monetization company, SSP, Exchange, Header Wrapper, etc.) that caused the ID array element to be added. This may be the operational domain of the system, if that is different from the parent corporate domain, to facilitate WHOIS and reverse IP lookups to establish clear ownership of the delegate system. This should be the same value as used to identify sellers in an ads.txt file if one exists. For ad tech intermediaries, this would be the domain as used in ads.txt. For publishers, this would match the domain in the site or app object. | - |
source | optional | string | Canonical domain of the ID. | - |
matcher2 | optional | string | Technology providing the match method as defined in mm.In some cases, this may be the same value as inserter. When blank, it is assumed that the matcher is equal to the sourceMay be omitted when mm=0, 1, or 2. | -. |
mm2 | optional | int | Match method used by the matcher. Refer to List: ID Match Methods in AdCOM 1.0 | -. |
uids | optional | object array | Array of extended ID UID objects from the given source. Refer to the Extended Identifier UIDs object (Section Object: UID) | - |
ext | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: UID
The table below shows Verve Brand+ support for the UID Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for UID Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | optional | string | The identifier for the user. | - |
atype | optional | integer | Type of user agent the ID is from. It is highly recommended to set this, as many DSPs separate app-native IDs from browser-based IDs and require a type value for ID resolution. Refer to List: Agent Types in AdCOM 1.0 | - |
ext | optional | object | Placeholder for vendor specific extensions to this object. | -. |
Object: UserAgent
The table below shows Verve Brand+ support for the UserAgent Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for UserAgent Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
browser | recommended | array of BrandVersion objects | BrandVersion object (see Section 3.2.30) identifies a browser or similar software component. Implementers should send brands and versions derived from the Sec-CH-UA-Full-Version-List header*. | - |
platform | recommended | BrandVersion object | A BrandVersion object (see Section BrandVersion) that identifies the user agent’s execution platform / OS. Implementers should send a brand derived from the Sec-CH-UA-Platform header, and version derived from the Sec-CH-UA-Platform-Version header*. | - |
mobile | optional | integer | 1 if the agent prefers a mobile version of the content, if available, i.e. optimized for small screens or touch input. 0 if the agent prefers the desktop or full content. Implementers should derive this value from the Sec-CH-UA-Mobile header *. | - |
architecture | optional | string | Device’s major binary architecture, for example, “x86” or “arm”. Implementers should retrieve this value from the Sec-CH-UA-Arch header*. | - |
bitness | optional | string | Device’s bitness, for example. 64 for 64-bit architecture. Implementers should retrieve this value from the Sec-CH-UA-Bitness header*. | - |
model | optional | string | Device model. Implementers should retrieve this value from the Sec-CH-UA-Model header*. | - |
source | optional | integer | Device model. Implementers should retrieve this value from the Sec-CH-UA-Model header*. | 0 |
ext | optional | object | Placeholder for vendor-specific extensions to this object. | - |
Back to → Object: UserAgent Back to Top ↑
Object: BrandVersion
The table below shows Verve Brand+ support for the BrandVersion Attributes as per the OpenRTB 2.6 specification.
Table: Verve Brand+ supports for BrandVersion Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
brand | required | string | A brand identifier, for example, “Chrome” or “Windows”. The value may be sourced from the User-Agent Client Hints headers, representing either the user agent brand (from the Sec-CH-UA-Full-Version header) or the platform brand (from the Sec-CH-UA-Platform header). | - |
version | required | array of string | A sequence of version components, in descending hierarchical order (major, minor, micro) | - |
ext | optional | object | Placeholder for vendor specific extensions to this object. | - |
Back to → Object: BrandVersion ↑
Object: Qty
The table below shows Verve Brand+ support for the Qty Attributes, which have been added as a new object in the OpenRTB 2.6 specification.
Note: `
Field`1 are newly added in the oRTB 2.6 and supported by Verve Brand+.
Table: Verve Brand+ supports for Qty Attribute
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
multiplier1 | required | float | The quantity of billable events which will be deemed to have occurred if this item is purchased. For example, a DOOH opportunity may be considered to be 14.2 impressions. Equivalent to qtyflt in OpenRTB 3.0. | - |
sourcetype1 | recommended | integer | The source type of the quantity measurement, i.e. publisher. Refer to the List: DOOH Multiplier Measurement Source Types | - |
vendor1 | required | string | The top-level business domain name of the measurement vendor providing the quantity measurement. | If sourcetype is present and type = 1 |
ext1 | optional | object | Placeholder for vendor-specific extensions to this object. | - |
Object: DOOH
The table below shows Verve Brand+ support for the DOOH Attributes, which have been added as a new object in the OpenRTB 2.6 specification.
Note:
Field1 are newly added in the oRTB 2.6 and supported by Verve Brand+.
Table: Verve Brand+ supports for DOOH object
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id1 | recommended | string | Exchange provided id for a placement or logical grouping of placements. | - |
name1 | optional | string | Name of the DOOH placement. | - |
venuetype1 | optional | string array | The type of out-of-home venue. The taxonomy to be used is defined by the venuetax field. If no venuetax field is supplied, The OpenDOOH Venue Taxonomy is assumed. See Digital Out-of-Home Screen Venue Types | - |
venuetypetax1 | optional | integer | The venue taxonomy in use. Refer to list: See ADCOM Specification 1.0. | 1 |
publisher1 | optional | object | Details about the publisher of the placement. | - |
domain1 | optional | string | Domain of the inventory owner (for example, http://mysite.foo.com) | - |
keywords1 | optional | string | Comma separated list of keywords about the DOOH placement. | - |
content1 | optional | object | Details about the Content within the DOOH placement. | - |
ext1 | optional | object | Placeholder for exchange-specific extensions to OpenRTB. | - |
Object: Refresh
The table below shows Verve Brand + support for the Refresh Attributes as per the Open RTB 2.6 specification.
Table: Verve Brand+ supports for Refresh object
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
refsettings | recommended | object array | A RefSettings object (see Section 3.2.34) describing the mechanics of how an ad placement automatically refreshes. | - |
count | recommended | integer | The number of times this ad slot had been refreshed since last page load. | - |
ext | optional | object | Placeholder for vendor specific extensions to this object. | - |
Object: RefSettings
The table below shows Verve Brand+ support for the RefSettings Attributes as per the Open RTB 2.6 specification.
Table: Verve Brand+ supports for RefSettings Attributes
| Field | Scope | Type | Description | Default |
reftype | recommended | integer | The type of the declared auto refresh. Refer to List: Auto Refresh Triggers in AdCOM 1.0 | 0 |
minint | recommended | integer | The minimum refresh interval in seconds. This applies to all refresh types. This is the (uninterrupted) time the ad creative will be rendered before refreshing to the next creative. If the field is absent, the exposure time is unknown. This field does not account for viewability or external factors such as a user leaving a page. | - |
ext | optional | object | Placeholder for vendor specific extensions to this object. | - |
Back to → Object: RefSetting ↑
Object: BidResponse
The table below shows Verve Brand+ support for the BidResponse Attributes. For the most up-to-date details on all available attributes in the BidResponse object, see Section 4.3.1 Object: BidResponse (Page 44 of the OpenRTB 2.6 PDF).
Table: Verve Brand+ supports for BidResponse Attribute
| Field | Scope | Type | Description | Default |
id | required | string | ID of the bid request to which this is a response. | - |
seatbid | optional | object array | Array of seatbid objects; 1+ required if a bid is to be made. | - |
bidid | optional | string | Bidder generated response ID to assist with logging/tracking. | - |
cur | optional | string | Bid currency using ISO-4217 alpha codes. | USD |
customdata | optional | string | Optional feature to allow a bidder to set data in the exchange’s cookie. The string must be in base85 cookie safe characters and be in any format. Proper JSON encoding must be used to include “escaped” quotation marks. | - |
nbr | optional | integer | Reason for not bidding. Refer to List: No-Bid Reason Codes in OpenRTB 3.0. | - |
ext | optional | object | Placeholder for bidder-specific extensions to OpenRTB. | - |
Back to → Object: BidResponse ↑
Object: Seat Bid
The table below shows Verve Brand+ support for the SeatBid Attributes. For the most up-to-date details on all available attributes in the SeatBid object, see Section 4.3.2 Object: Seat Bid (Page 44 of the OpenRTB 2.6 PDF).
Table: Verve Brand+ supports for SeatBid Attribute
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
bid | required | object array | Array of 1+ Bid objects (Section 4.2.3) each related to an impression. Multiple bids can relate to the same impression. | - |
seat | optional | string | ID of the buyer seat (for example, advertiser, agency) on whose behalf this bid is made. | - |
group | optional | integer | 0 = impressions can be won individually; 1 = impressions must be won or lost as a group. | 0 |
ext | optional | object | Placeholder for bidder-specific extensions to OpenRTB. | - |
Object: Bid
The table below shows Verve Brand+ support for the Bid Attributes. For the most up-to-date details on all available attributes in the Bid object, see Section 4.3.3 Object: Bid (Page 45 of the OpenRTB 2.6 PDF).
Note:
Field1are newly added in the oRTB 2.6 and supported by Verve Brand+.Field2are deprecated in the oRTB 2.6 but continue to support by Verve Brand+.
Table: Verve Brand+ supports for Bid Attributes
| Field | Scope | Type | Description | Default |
|---|---|---|---|---|
id | required | string | Bidder generated bid ID to assist with logging/tracking. | - |
impid | required | string | ID of the Imp object in the related bid request. | - |
price | required | float | Bid price expressed as CPM although the actual transaction is for a unit impression only. Note that while the type indicates float, integer math is highly recommended when handling currencies (for example, BigDecimal in Java). | - |
nurl | optional | string | - | - |
burl | optional | string | Billing notice URL called by the exchange when a winning bid becomes billable based on exchange-specific business policy (e.g., typically delivered, viewed, etc.). Substitution macros (Section 4.4) may be included. | - |
lurl | optional | string | Loss notice URL called by the exchange when a bid is known to have been lost. Substitution macros (Section 4.4) may be included. Exchange-specific policy may preclude support for loss notices or the disclosure of winning clearing prices resulting in ${AUCTION_PRICE} macros being removed (i.e., replaced with a zero-length string). | - |
adm | optional | string | Optional means of conveying ad markup in case the bid wins; supersedes the win notice if markup is included in both. Substitution macros (Section 4.4) may be included. | - |
adid | optional | string | ID of a preloaded ad to be served if the bid wins. | - |
adomain | optional | string array | Advertiser domain for block list checking (e.g., “http://ford.com”). This can be an array for the case of rotating creatives. Exchanges can mandate that only one domain is allowed. | - |
bundle | optional | string | The store ID of the app in an app store (e.g., Apple App Store, Google Play). See OTT/CTV Store Assigned App Identification Guidelines for more details about expected strings for CTV app stores. For mobile apps in Google Play Store, these should be bundle or package names (e.g. com.foo.mygame). For apps in Apple App Store, these should be a numeric ID. | - |
iurl | optional | string | URL without cache-busting to an image that is representative of the content of the campaign for ad quality/safety checking. | - |
cid | optional | string | Campaign ID to assist with ad quality checking; the collection of creatives for which iurl should be representative. | - |
crid | optional | string | Creative ID to assist with ad quality checking. | - |
tactic | optional | string | Tactic ID to enable buyers to label bids for reporting to the exchange the tactic through which their bid was submitted. The specific usage and meaning of the tactic ID should be communicated between buyer and exchanges a priori. | - |
cattax | optional | integer | The taxonomy in use. Refer to List: Category Taxonomies for values. | 1 |
cat | optional | string array | IAB Tech Lab content categories of the creative. The taxonomy to be used is defined by the cattax field. If no cattax field is supplied Content Taxonomy 1.0 is assumed. | - |
attr | optional | integer array | Set of attributes describing the creative. Refer to List: Creative Attributes in AdCOM 1.0. | - |
apis1 | optional | integer array | List of supported APIs for the markup. If an API is not explicitly listed, it is assumed to be unsupported. Refer to List: API Frameworks in AdCOM 1.0. | - |
api2 | optional | integer | Deprecated in favor of the apisinteger array. API required by the markup if applicable. Refer to List: API Frameworks in AdCOM 1.0. | - |
protocol | optional | integer | Video response protocol of the markup if applicable. Refer to List: Creative Subtypes - Audio/Video in AdCOM 1.0. | - |
qagmediarating | optional | integer | Creative media rating per IQG guidelines. Refer to List: Media Ratings in AdCOM 1.0. | - |
language | optional | string | Language of the creative using ISO-639-1-alpha-2. The non-standard code “xx” may also be used if the creative has no linguistic content (e.g., a banner with just a company logo). Only one of language or langb | - |
langb | optional | string | Language of the creative using IETF BCP 47. Only one of language or langb should be present. | - |
dealid | optional | string | Reference to the deal.id from the bid request if this bid pertains to a private marketplace direct de | - |
w | optional | integer | Width of the creative in device independent pixels (DIPS). | - |
h | optional | integer | Height of the creative in device independent pixels (DIPS). | - |
wratio | optional | integer | Relative width of the creative when expressing size as a ratio. Required for Flex Ads. | - |
hratio | optional | integer | Relative height of the creative when expressing size as a ratio. Required for Flex Ads. | - |
exp | optional | integer | Advisory as to the number of seconds the bidder is willing to wait between the auction and the actual impression. | - |
dur | optional | integer | Duration of the video or audio creative in seconds. | - |
mtype | optional | integer | Type of the creative markup so that it can properly be associated with the right sub-object of the BidRequest.Imp. Values: 1 = Banner 2 = Video, 3 = Audio 4 = Native | 0 |
slotinpod | optional | integer | Indicates that the bid response is only eligible for a specific position within a video or audio ad pod (e.g. first position, last position, or any). Refer to List: Slot Position in Pod in AdCOM 1.0 for guidance on the use of this field. | 0 |
ext | optional | object | Placeholder for bidder-specific extensions to OpenRTB. |
Updated 4 days ago