Release Notes

Nov 19, 2024

What's New in OpenRTB Proto

Added support for BidRequest.imp.video.minbitrate and BidRequest.imp.video.maxbitrate.

Indicates the minimum and maximum bitrates for the video ad. Ads that do not meet the minimum or maximum bitrate requirements will not be accepted.

Nov 6, 2024

What's New in OpenRTB Extensions

Added BidRequest.imp.banner.ext.clpadslot

This field represents a collapsible banner ad slot. It specifies the maximum width and height a collapsible ad can be shown. The slot can appear on both mobile apps and web. For format information, see Help Center article for details on mobile apps and Help Center article for details on mobile web.

Added BidResponse.seatbid.bid.ext.clpad

This field represent a collapsible banner ad information. It specifies the width and height of a collapsible ad at the expanded state. The width and height of a collapsible ad at the collapsed state are repsented by the existing BidResponse.seatbid.bid.wandBidResponse.seatbid.bid.h, respectively. For format information, see Help Center article for details on mobile apps and Help Center article for details on mobile web.

Nov 1, 2024

What's New in RTB Proto version 331

Added BidRequest.experiment_ids.

Contains labels indicating the experiments or control groups that are active for this request.

What's New in OpenRTB Extensions Proto version 180

Added BidRequestExt.expids.

Contains labels indicating the experiments or control groups that are active for this request.

Oct 31, 2024

What's New in OpenRTB Proto

Added BidRequest.user.EID.inserter, BidRequest.user.EID.matcher, and BidRequest.user.EID.mm.

These fields are not supported by Google.

Sep 25, 2024

What's New in OpenRTB Proto

Added support for BidRequest.app.ver.

This field contains the version of the mobile application specified in the BidRequest.app.bundle.

Sep 12, 2024

What's New in OpenRTB Proto

Added support for BidRequest.source.schain.nodes.name.

This field contains the name of the company (the legal entity) that has paid for the transacted inventory. If available for SupplyChain nodes upstream of Google, it will be included.

Added support for BidRequest.source.schain.nodes.domain.

This field contains the business domain name of the entity represented by the SupplyChain node. If available for SupplyChain nodes upstream of Google, it will be included.

What's New in OpenRTB Proto Extensions Proto

Added support for BidRequest.source.ext.schain.nodes.name.

This field contains the name of the company (the legal entity) that has paid for the transacted inventory. If available for SupplyChain nodes upstream of Google, it will be included.

Added support for BidRequest.source.ext.schain.nodes.domain.

This field contains the business domain name of the entity represented by the SupplyChain node. If available for SupplyChain nodes upstream of Google, it will be included.

Sep 11, 2024

What's New in OpenRTB Extensions Proto version 178

Added BidRequest.imp.banner.ext.flexslot.

Indicates the acceptable ad width and height ranges for impressions which support flexible ad sizes.

Sep 06, 2024

What's New in OpenRTB Extensions Proto version 178

Added BidRequest.imp.pmp.deal.ext.billing_id.

Indicates the eligible billing IDs for the deal.

Aug 07, 2024

What's New in RTB Proto version 330

Changed enum BidRequest.PrivacyTreatments.UserAgentGeneralization.

Renamed the value USER_AGENT_COARSENED to USER_AGENT_COARSE.

What's New in OpenRTB Extensions Proto version 177

Changed enum BidRequestExt.PrivacyTreatments.UserAgentGeneralization.

Renamed the value USER_AGENT_COARSENED to USER_AGENT_COARSE.

Aug 01, 2024

What's New in RTB Proto version 329

Added BidRequest.refresh.

This new field contains details about ad slots being refreshed automatically.

Jul 26, 2024

What's New in OpenRTB Extensions Proto version 175

Added BidRequest.imp.video.ext.embeddedoffsite.

This new field contains whether or not the video is embedded on a page outside the publisher's domain.

Jul 15, 2024

What's New in OpenRTB Extensions Proto version 174

Added BidResponse.seatbid.bid.ext.clickurl.

This new field contains The URLs that the user could be directed to when clicking on this ad.

May 21, 2024

What's New in RTB Proto version 328

Added BidRequest.session_duration_seconds.

This new field contains the time in seconds since the first ad request in a given app or site session. The session is reset after a sufficiently long break in user activity. Currently, the field is only populated for mobile app requests.

What's New in OpenRTB Extensions Proto version 173

Added BidRequest.user.ext.session.duration.

This new field contains the time in seconds since the first ad request in a given app or site session. The session is reset after a sufficiently long break in user activity. Currently, the field is only populated for mobile app requests.

May 15, 2024

What's New in OpenRTB Extensions Proto version 172

Added field BidRequest.user.ext.idage.

Indicates the amount of time, in seconds, since the ID in `BidRequest.user.id` was created.

Added extension BidRequest.device.geo.ext.geo_criteria_id.

The device's approximate geographic location. This field is provisional, intended only to help with migration from the Google Authorized Buyers protocol to OpenRTB; it will be removed in the future. The standard fields in BidRequest.device.geo should be used instead; they contain the same location as the geo_criteria_id and both are subject to the same privacy treatments.

May 7, 2024

What's New in RTB Proto version 324

Added BidRequest.segment_data.id.

This new field holds the data provider associated with the Publisher Provided Signal. For the list of possible data providers, see data_providers.txt.

What's New in OpenRTB Extensions Proto version 171

Updated value for BidRequest.user.data.id.

Updated value for BidRequest.site.content.data.id.

Updated value for BidRequest.app.content.data.id.

This field now holds the data provider associated with the Publisher Provided Signal. For the list of possible data providers, see data_providers.txt.

May 6, 2024

What's New in RTB Proto version 326

Added field BidRequest.adslot.blocked_seat_ids.

Contains a list of media planner seat IDs in the bidder's namespace that are blocked by the publisher.

Added field BidRequest.adslot.allowed_seat_ids.

Contains the list of media planner seat IDs in the bidder's namespace that are allowed by the publisher.

Added field BidRequest.adslot.matching_ad_data.direct_deal.allowed_seat_ids.

Contains the list of media planner seat IDs in the bidder's namespace that are allowed by the publisher to bid on this deal.

April 25, 2024

What's New in RTB Proto version 325

Deprecated BidRequest.seller_network_id.

This field is no longer supported and will be removed in Q2 2024.

Aptril 17, 2024

What's New in RTB Proto version 324

Added BidRequest.video.inferred_plcmt.

Google inferred video placement type for the impression. This field is always filled and can be different from BidRequest.video.plcmt (the publisher-declared placement type).

What's New in OpenRTB Extensions Proto version 171

Added BidRequest.imp.video.ext.inferredplcmt.

Google inferred video placement type for the impression. This field is always filled and can be different from BidRequest.imp.video.plcmt (the publisher-declared placement type).

Aptril 5, 2024

What's New in OpenRTB Extensions Proto version 170

Added new extension to the Data object.

This new extension has a single field segtax that identifies the taxonomy that the Data segment IDs belong to.

March 18, 2024

What's New in OpenRTB Extensions Proto version 168

Updated field BidRequest.regs.ext.dsa.

Get rid of all the *_UNKNOWN enum values in bid request DSA fields in BidRequest.regs.ext.dsa to align with OpenRTB DSA IAB spec. See Help Center article for details.

March 13, 2024

What's New in RTB Proto version 322

Added field BidRequest.device.connection_type.

This field contains the type of network to which the user's device is connected.

What's New in OpenRTB Proto version 168

Started supporting field BidRequest.device.connectiontype.

This field contains the type of network to which the user's device is connected.

February 26, 2024

What's New in RTB Proto version 321

Added field BidRequest.dsa.

This field contains the Digital Services Act (DSA) transparency requirements in the bid request. See Help Center article for details.

Added field BidResponse.ad.dsa_transparency.

This field contains the DSA Ad Transparency declarations in the bid response. See Help Center article for details.

What's New in OpenRTB Extensions Proto version 167

Added field BidRequest.regs.ext.dsa.

This field contains the Digital Services Act (DSA) transparency requirements in the bid request. See Help Center article for details.

Added field BidResponse.seatbid.bid.ext.dsa.

This field contains the DSA Ad Transparency declarations in the bid response. See Help Center article for details.

February 14, 2024

What's New in RTB Proto version 320

Removed deprecated field BidRequest.privacy_treatments.user_agent_data.

What's New in OpenRTB Extensions Proto version 166

Removed deprecated field BidRequest.ext.privacy_treatments.user_agent_data.

February 12, 2024

What's New in RTB Proto version 319

Added BidRequest.privacy_treatments.ip.

Indicates whether the field BidRequest.ip has been generalized to protect user privacy.

What's New in OpenRTB Extensions Proto version 165

Added BidRequest.ext.privacy_treatments.ip.

Indicates whether the field BidRequest.device.ip or BidRequest.device.ipv6 has been generalized to protect user privacy.

February 5, 2024

What's New in RTB Proto version 318

Added field BidRequest.bid_response_feedback.feedback_type.

This field indicates the type of feedback the bid response feedback message is intended for. The supported feedback types are for bids submitted on a bid response and for interest group buyers submitted on a bid response to enter an interest group bidding component of the auction run using the Protected Audience API.

Added field BidRequest.bid_response_feedback.buyer_origin.

This field is populated with the origin of an interest group buyer that was included in the bid response. This field is only populated for bid feedback for an interest group buyer.

Added field BidRequest.bid_response_feedback.interest_group_buyer_status_code.

This field is populated with the status code for the submitted interest group buyer. This field is only populated for bid feedback for an interest group buyer. See https://storage.googleapis.com/adx-rtb-dictionaries/interest-group-buyer-status-codes.txt for a list of interest group buyer status codes.

What's New in OpenRTB Extensions Proto version 164

Added field BidRequest.ext.bid_feedback.feedbacktype.

This field indicates the type of feedback the bid response feedback message is intended for. The supported feedback types are for bids submitted on a bid response and for interest group buyers submitted on a bid response to enter an interest group bidding component of the auction run using the Protected Audience API.

Added field BidRequest.ext.bid_feedback.buyerorigin.

This field is populated with the origin of an interest group buyer that was included in the bid response. This field is only populated for bid feedback for an interest group buyer.

Added field BidRequest.ext.bid_feedback.igbuyerstatus.

This field is populated with the status code for the submitted interest group buyer. This field is only populated for bid feedback for an interest group buyer. See https://storage.googleapis.com/adx-rtb-dictionaries/interest-group-buyer-status-codes.txt for a list of interest group buyer status codes.

January 30, 2024

What's New in RTB Proto version 316

Added field BidRequest.adslot.gpp_consent_string.

This field contains the Global Privacy Platform's consent string. See IAB-GPP spec for details.

Added repeated field BidRequest.adslot.gpp_section_ids.

Array of the section(s) of the GPP string which should be applied for this request.

January 26, 2024

What's New in RTB Proto version 316

Added field BidRequest.privacy_treatments.device_storage_restriction_reason.

This field indicates the reason why access to local device storage during winning ad rendering and measurement is restricted. See Limted ads requests for additional details.

What's New in OpenRTB Proto version 163

Added field BidRequest.ext.privacy_treatments.storagerestrict.

This field indicates the reason why access of local device storage during winning ad rendering and measurement is restricted. See Limted ads requests for additional details.

January 11, 2024

What's New in RTB Proto version 315

Deprecated field BidRequest.user_data_treatment.

This field is unused.

January 10, 2024

What's New in OpenRTB Proto version 162

Started populating BidRequest.imp.clickbrowser.

January 5, 2024

What's New in RTB Proto version 314

Removed deprecated field BidRequest.adslot.multi_ads_cell_info.

This field is obsolete and no longer supported.

What's New in OpenRTB Proto version 162

Removed deprecated field BidRequest.imp.ext.multi_ads_cell_info.

This field is obsolete and no longer supported.

December 21, 2023

What's New in RTB Proto version 313

Added field BidRequest.publisher_first_party_id.

This field is used to share first party identifiers that can be scoped to a single site, app or vendor.

December 11, 2023

What's New in RTB Proto version 312

Removed deprecated field BidResponse.ad.agency_id.

This field was obsolete and no longer needed.

December 8, 2023

What's New in RTB Proto

Expanded support to IMA SDK traffic for BidRequest.AdSlot.display_manager and BidRequest.AdSlot.display_manager_version.

Populate BidRequest.AdSlot.display_manager with “InteractiveMediaAds-Android” or “InteractiveMediaAds-iOS" and BidRequest.Imp.displaymanager with the SDK version for IMA SDK traffic.

What's New in OpenRTB Proto

Expanded support to IMA SDK traffic for BidRequest.Imp.displaymanager and BidRequest.Imp.displaymanagerver.

Populate BidRequest.Imp.displaymanager with “InteractiveMediaAds-Android” or “InteractiveMediaAds-iOS" and BidRequest.Imp.displaymanagerver with the SDK version for IMA SDK traffic.

November 21, 2023

What's New in RTB Proto version 311

Added field BidRequest.production_quality.

This field contains the quality of the content where an ad can be shown. The population of this field is subject to privacy controls.

Added field BidRequest.content_rating.

This field contains the rating of the content where an ad can be shown. The population of this field is subject to privacy controls.

Added field BidRequest.video.feed_type.

This field contains the type of feed for the audio content where an ad can be shown. The population of this field is subject to privacy controls.

Added field BidRequest.video.delivery_method.

This field contains the supported delivery methods for the video or audio content where an ad can be shown. The population of this field is subject to privacy controls.

November 14, 2023

What's New in RTB Proto version 310

Capitalize the first letter of BidRequest.Device.brand field.

For example, we now send "Apple" rather than "apple".

What's New in OpenRTB Proto

Capitalize the first letter of BidRequest.Device.make field.

For example, we now send "Apple" rather than "apple".

November 8, 2023

What's New in RTB Proto version 309

Deprecated field BidRequest.privacy_treatments.user_agent_data.

This field is redundant, BidRequest.privacy_treatments.user_agent provides the generalization level for both forms of user agent information.

This field is no longer supported and will be removed in January 2024.

What's New in OpenRTB Extensions Proto version 161

Deprecated field BidRequest.ext.privacy_treatments.user_agent_data.

This field is redundant, BidRequest.ext.privacy_treatments.user_agent provides the generalization level for both forms of user agent information.

This field is no longer supported and will be removed in January 2024.

November 2, 2023

What's New in RTB Proto version 307

Added fields BidRequest.AdSlot.display_manager and BidRequest.AdSlot.display_manager_version.

We populate BidRequest.AdSlot.display_manager with a value of “GoogleMobileAds-Android” or “GoogleMobileAds-iOS” and set BidRequest.AdSlot.display_manager_version to the SDK version for GMA SDK traffic.

Updated behavior of BidRequest.AdSlot.renderer

Previously, we populated BidRequest.AdSlot.renderer with the enum values corresponding to Google and Publisher for some video-eligible bid requests only. Now, we no longer populate BidRequest.AdSlot.renderer for any GMA SDK traffic regardless of video-eligibility.

What's New in OpenRTB Proto

Expanded support to GMA SDK traffic for BidRequest.Imp.displaymanager and BidRequest.Imp.displaymanagerver.

Previously, we populated BidRequest.Imp.displaymanager with “GOOGLE” or “PUBLISHER” for some video-eligible bid requests only. Now we populate BidRequest.Imp.displaymanager with “GoogleMobileAds-Android” or “GoogleMobileAds-iOS" for all GMA SDK traffic, which may overwrite “GOOGLE” or “PUBLISHER”. Additionally, BidRequest.Imp.displaymanager will be set to the SDK version for the same slice.

October 27, 2023

What's New in OpenRTB Proto

Added support for BidRequest.app.content.prodq and BidRequest.site.content.prodq.

These two fields contain the quality of the content where an ad can be shown.

Added support for BidRequest.app.content.contentrating and BidRequest.site.content.contentrating.

These two fields contain the rating of the content where an ad can be shown.

Added support for BidRequest.imp.audio.feed.

This field contains the type of feed for the audio content where an ad can be shown.

Added support for BidRequest.imp.audio.delivery and BidRequest.imp.video.delivery.

These two fields contain the supported delivery methods for the video or audio content where an ad can be shown.

October 24, 2023

What's New in RTB Proto version 305

Added BidRequest.video.plcmt.

Video placement field. INSTREAM and ACCOMPANYING values will be directly declared by the publisher in the ad request. INTERSTITIAL and NO_CONTENT_STANDALONE values will be inferred from other publisher declared signals available on the request.

Deprecated BidRequest.video.placement.

This field is no longer supported and will be removed in January 2025.

What's New in OpenRTB Protos

Added support for BidRequest.imp.video.plcmt.

Video placement field. INSTREAM and ACCOMPANYING values will be directly declared by the publisher in the ad request. INTERSTITIAL and NO_CONTENT_STANDALONE values will be inferred from other publisher declared signals available on the request.

Deprecated BidRequest.imp.video.placement.

This field is no longer supported and will be removed in January 2025.

October 11, 2023

What's New in RTB Proto version 304

Added field BidRequest.segment_data.

This field contains first-party data segments that describe the content or audience that may be shared with bidders by publishers. Segments are populated subject to privacy controls.

What's New in OpenRTB Proto

Added support for BidRequest.user.data.

This field will contain first-party data segments that describe the audience.

Added support for BidRequest.app.content.data and BidRequest.site.content.data.

These two fields will contain first-party data segments that describe the content.

October 9, 2023

What's New in RTB Proto version 303

Added field BidRequest.user_activation.

This field contains the status of whether the user is currently interacting with the page.

It originates from the [Mozilla Web API](https://html.spec.whatwg.org/multipage/interaction.html#the-useractivation-interface).

Added field BidRequest.navigation_type.

This field contains the type of navigation that led to a page load. It originates from the

[UserActivation HTML interface](https://w3c.github.io/navigation-timing/#dom-performancenavigationtiming-type).

What's New in OpenRTB Proto version 159

Added field BidRequest.site.ext.uact.

This field contains the status of whether the user is currently interacting with the page.

It originates from the [Mozilla Web API](https://html.spec.whatwg.org/multipage/interaction.html#the-useractivation-interface).

Added field BidRequest.site.ext.ntype.

This field contains the type of navigation that led to a page load. It originates from the

[PerformanceNavigationTiming HTML interface](https://w3c.github.io/navigation-timing/#dom-performancenavigationtiming-type).

October 4, 2023

What's New in RTB Proto version 303

Added field BidRequest.publisher_provided_id.

This field is a pseudonymized identifier created and controlled by the publisher for use in frequency capping, audience segmentation and targeting, and sequential ad rotation. See https://support.google.com/admanager/answer/2880055.

What's New in OpenRTB Proto version 158

Added support for BidRequest.user.eids.

Publisher-provided identifiers are shared using the BidRequest.user.eids field.

What's New in OpenRTB Extensions Proto version v.154

Added field BidRequest.user.eids.uids.ext.

This extension supports differentiating between types of extended data items using the BidRequest.user.eids.uids.ext.stype field. See details at https://developers.google.com/authorized-buyers/rtb/openrtb-guide#uid-stype

October 2, 2023

What's New in OpenRTB

Changed the semantics of values for BidRequest.device.hwv and BidRequest.device.model for iPhone/iPad.

For iPhone/iPad, these fields contain Apple's model identifier string (such as "iPhone12,1" and "iPad13,8") if available. Otherwise, hwv is empty, and model contains the generic model (either "iphone" or "ipad").

What's New in RTB Proto version 302

Changed the semantics of values for BidRequest.device.hardware_version and BidRequest.device.model for iPhone/iPad.

For iPhone/iPad, these fields contain Apple's model identifier string (such as "iPhone12,1" and "iPad13,8") if available. Otherwise, hardware_version is empty, and model contains the generic model (either "iphone" or "ipad").

September 13, 2023

What's New in RTB Proto version 301

Deprecated BidRequest.adslot.multi_ads_cell_info.

This field is no longer supported and will be removed in Q1 2024.

What's New in OpenRTB Proto version 157

Deprecated BidRequest.imp.ext.multi_ads_cell_info.

This field is no longer supported and will be removed in Q1 2024.

September 1, 2023

What's New in OpenRTB Proto version 155

Deleted deprecated field BidRequest.imp.ext.creative_enforcement_settings.is_default.

BidRequest.imp.ext.creative_enforcement_settings.is_default, was deprecated in June, 2022.

Deleted deprecated field BidResponse.seatbid.bid.ext.DEPRECATED_bidder_name.

BidResponse.seatbid.bid.ext.DEPRECATED_bidder_name, was deprecated in September, 2020.

August 21, 2023

What's New in RTB Proto version 299

Deprecated BidResponse.ad.agency_id.

This field is no longer needed and will be removed in November, 2023.

August 17, 2023

What's New in RTB Proto version 298

Added repeated field BidRequest.adslot.billable_event_rate_bid_adjustment of type BillableEventRateBidAdjustment message.

This field lists the billable event rate bid adjustments applicable to the request and the dependent features of the ad the adjustment applies to, such as the format or the SDK used to render the ad. Each feature combination may have a unique adjustment, each adjustment therefore specifies which SDK or creative format it applies to. This field replaces the deprecated field BidRequest.adslot.billable_event_rate_adjustment.

Added float field BidRequest.bid_response_feedback.billable_event_rate_bid_adjustment.

This field contains the billable event rate multiplier applied to this bid during ranking. The adjustment reflects the likelihood that your bid would generate a billable event (namely, the ad renders successfully) if it won the auction, relative to the probability that other bids generate a billable event if they won the auction.

Deprecated field BidRequest.adslot.billable_event_rate_adjustment.

This is replaced by the above BidRequest.adslot.billable_event_rate_bid_adjustment, and will be removed in Q1 2024.

What's New in OpenRTB Proto version 154

Added repeated field BidRequest.imp.ext.billable_event_rate_bid_adjustment of type BillableEventRateBidAdjustment object.

This field lists the billable event rate bid adjustments applicable to the request and the dependent features of the ad the adjustment applies to, such as the format or the SDK used to render the ad. Each feature combination may have a unique adjustment, each adjustment therefore specifies which SDK or creative format it applies to. This field replaces the deprecated field BidRequest.imp.ext.billable_event_rate_adjustment.

Added float field BidRequest.ext.bid_feedback.billable_event_rate_bid_adjustment.

This field contains the billable event rate multiplier applied to this bid during ranking. The adjustment reflects the likelihood that your bid would generate a billable event (namely, the ad renders successfully) if it won the auction, relative to the probability that other bids generate a billable event if they won the auction.

Deprecated field BidRequest.imp.ext.billable_event_rate_adjustment.

This is replaced by the above BidRequest.imp.ext.billable_event_rate_bid_adjustment, and will be removed in Q1 2024.

Auguest 16, 2023

What's New in RTB Proto version 297

Removed BidRequest.adslot.secure_signals.source_js.

BidRequest.adslot.secure_signals.source should be used instead of BidRequest.adslot.secure_signals.source_js.

August 16, 2023

What's New in RTB Proto version 296

Deprecated BidRequest.auction_environment.

Instead, use BidRequest.supported_auction_environment, which indicates the auction environment that is supported for the available impression.

Added field BidRequest.supported_auction_environment

Describes how the winning ad will be selected, either by the traditional server-side auction or the on-device interest group auction using the Protected Audience API.

What's New in OpenRTB Extensions Proto version v.153

Deprecated BidRequest.imp.ext.auction_environment.

Instead, use BidRequest.imp.ext.ae, which indicates the auction environment that is supported for the available impression.

Added field BidRequest.imp.ext.ae.

Describes how the winning ad will be selected, either by the traditional server-side auction or the on-device interest group auction using the Protected Audience API.

August 7, 2023

What's New in RTB Proto version 295

Added field BidRequest.bid_response_feedback.server_side_component_minimum_bid_to_win

This field contains the minimum bid to win of the server side auction if a bid partcipated in an auction with an interest group bidding component run using the Protected Audience API.

What's New in OpenRTB Extensions Proto version v.152

Added field BidRequest.ext.bid_feedback.sscminbidtowin.

This field contains the minimum bid to win of the server side auction if a bid partcipated in an auction with an interest group bidding component run using the Protected Audience API.

July 18, 2023

What's New in RTB Proto version 294

Added BidRequest.adslot.matching_ad_data.direct_deal.creative_constraints of the newly defined type CreativeConstraints

The BidRequest.adslot.matching_ad_data.direct_deal.creative_constraints contains the creative constraints for PROGRAMMATIC_GUARANTEED or PREFERRED_DEAL deals. The new type has 3 fields:

• allowed_ad_types: a list of allowed ad types for the deal.
• video_ad_skippable: the skippability type for the video/audio deal.
• max_ad_duration_ms: the maximum ad duration allowed by the video/audio deal in milliseconds.

What's New in OpenRTB Extensions Proto version v.151

Added BidRequest.imp.pmp.deals.ext.creative_constraints of the newly defined type CreativeConstraints

The BidRequest.imp.pmp.deals.ext.creative_constraints contains the creative constraints for PROGRAMMATIC_GUARANTEED or PREFERRED_DEAL deals. The new type has 3 fields:

• mtypes: a list of allowed ad types for the deal.
• skippability: the skippability type for the video/audio deal.
• maxduration: the maximum ad duration allowed by the video/audio deal in seconds.

July 5, 2023

What's New in RTB Proto version 293

Added field BidRequest.max_pod_duration_seconds.

BidRequest.max_pod_duration_seconds contains maximum number of seconds that advertisers may fill for a video ad pod. This field is populated only for rewarded pod requests.

Added field BidResponse.position_in_pod and enum PodPosition.

Use BidResponse.position_in_pod to indicate that the bid is only eligible for a specific position within the pod. By default, bid will be eligible for any position in the pod. This field should only be used for rewarded pod requests.

Added field BidResponse.bid_group_id.

Use BidResponse.bid_group_id to group bids together to form a pod. All bids sharing the same bid_group_id will be won or lost as a group. Bids must have a non-empty bid_group_id to allow an ad to be played as part of a pod. This field should only be used for rewarded pod requests.

What's New in OpenRTB Proto

Added support for BidRequest.imp.video.poddur.

Imp.video.poddur contains maximum seconds that advertisers may fill for a video ad pod. This field is populated only for rewarded pod requests.

Added support for BidRequest.imp.video.maxseq.

Imp.video.maxseq contains maximum number of ads that may be served into a video ad pod.

Added support for BidResponse.seatbid.bid.slotinpod.

Use Bid.slotinpod to indicate that the bid is only eligible for a specific position within the pod. By default, bid will be eligible for any position in the pod. This field should only be used for rewarded pod requests.

Added field Bid.ext.bid_group_id.

Use Bid.ext.bid_group_id to group bids together to form a pod. All bids sharing the same bid_group_id will be won or lost as a group. Bids must have a non-empty bid_group_id to allow an ad to be played as part of a pod. This field should only be used for rewarded pod requests.

June 13, 2023

What's New in RTB Proto version 288

Deprecated fields BidRequest.postal_code and BidRequest.postal_code_prefix.

Use BidRequest.geo.zip which contains the same information. To be precise, it contains the full postal code if that's available, otherwise it contains the postal code prefix if that's available.

Deprecated field BidRequest.timezone_offset.

Use BidRequest.geo.utcoffset which contains the same information.

Deprecated fields BidRequest.hyperlocal_set and BidRequest.encrypted_hyperlocal_set.

Use BidRequest.geo which contains similar information, only with a different representation: use geo.lat / geo.lon instead of the Hyperlocal object's center_point, and geo.accuracy instead of the Hyperlocal object's corners. See Geographical Targeting for more details.

Jun 8, 2023

What's New in RTB Proto version 287

Added BidRequest.user_agent_data.source.

This field specifies which headers were used as source of the Structured User Agent, similar to the OpenRTB protocol.

Jun 5, 2023

What's New in OpenRTB Proto

Added fields BidRequest.regs.gpp and BidRequest.regs.gpp_sid.

These two fields enable support for the Global Privacy Platform’s consent string.

June 1, 2023

What's New in RTB Proto version 276

Changed the default behavior for BidResponse.ad.app_promotion_type.

Setting BidResponse.ad.advertised_app_id field without BidResponse.ad.app_promotion_type field will be treated as if the app_promotion_type field were set to OTHER.

What's New in OpenRTB Extensions Proto version v.134

Changed the default behavior for Bid.ext.app_promotion_type.

Setting BidResponse.seatbid.bid.bundle field without Bid.ext.app_promotion_type field will be treated as if the app_promotion_type field were set to OTHER.

May 31, 2023

What's New in OpenRTB Proto

Added support for the standard BidRequest.source.schain field.

Use this instead of BidRequest.source.ext.schain, which is deprecated. For more information about this field, see this article.

What's New in OpenRTB Extensions Proto version v.133

Deprecated BidRequest.source.ext.schain.

For more information about this field, see this article.

May 3, 2023

What's New in RTB Proto version 275

Removed the enum value AuctionEnvironment.SERVER_SIDE_AUCTION_WITH_INTEREST_GROUP_SIMULATION.

The server-side FLEDGE simulation has been deprecated, so this value is no longer relevant.

What's New in OpenRTB Extension version 132

Removed the enum value AuctionEnvironment.SERVER_SIDE_AUCTION_WITH_INTEREST_GROUP_SIMULATION.

The server-side FLEDGE simulation has been deprecated, so this value is no longer relevant

May 1, 2023

What's New in RTB Proto version 274

Added the field BidRequest.adslot.excluded_app_ids.

This field is populated with the block list of applications by their platform-specific exchange independent application identifiers. On Android, these should be bundle or package names (for example, com.foo.mygame). On iOS, these are numeric IDs. Bids with ads that advertise any app from this list will be filtered out before the auction.

What's New in OpenRTB Proto

Added support for the field BidRequest.bapp.

This field is populated with the block list of applications by their platform-specific exchange independent application identifiers. On Android, these should be bundle or package names (for example, com.foo.mygame). On iOS, these are numeric IDs. Bids with ads that advertise any app from this list will be filtered out before the auction.

April 18, 2023

What's New in RTB Proto version 273

Added the field BidResponse.ad.adslot.seat_id.

This field indicates the seat to which the bid should be attributed. It is equivalent to the OpenRTB BidResponse.seatbid.seat field.

March 30, 2023

What's New in RTB Proto version 272

Added a bool field skoverlay to BidRequest.mobile.skan.

This field indicates if SKOverlay is supported for video ads.

Added an object field skoverlay to BidResponse.ad.skadn

This field indicates how to present SKOverlay for rewarded and interstitial video.

What's New in OpenRTB Extensions Proto version v.130

Added a bool field skoverlay to Imp.ext.skadn.

This field indicates if SKOverlay is supported for video ads.

Added an object field skoverlay to Bid.ext.skadn

This field indicates how to present SKOverlay for rewarded and interstitial video.

March 14, 2023

What's New in RTB Proto version 270

Added the enum value MARKETPLACE_PACKAGE to BidRequest.adslot.matching_ad_data.direct_deal.deal_type.

The MARKETPLACE_PACKAGE is a new deal type where publishers create packages of inventory and allow eligible buyers to bid on them.

What's New in OpenRTB Extensions Proto version v.129

Added the enum value MARKETPLACE_PACKAGE to BidRequest.imp.pmp.deals.adx_ext.deal_type.

The MARKETPLACE_PACKAGE is a new deal type where publishers create packages of inventory and allow eligible buyers to bid on them.

March 9, 2023

What's New in OpenRTB Proto

Added support for BidRequest.imp.rwdd.

This field indicates whether the user receives a reward for viewing the ad. Use this instead of BidRequest.imp.ext.is_rewarded_inventory, which is deprecated.

What's New in OpenRTB Extensions Proto version v.129

Deprecated BidRequest.imp.ext.is_rewarded_inventory.

This field will be removed in July 2023. Use the standard field BidRequest.imp.rwdd instead.

March 5, 2023

What's New in RTB Proto version 269

Removed field BidRequest.adslot.targetable_channel. This field was previously deprecated and it has no replacement.

March 4, 2023

What's New in RTB Proto version 268

Removed several fields and enumerated values that were previously deprecated, and have no replacement: BidRequest.adslot.creative_enforcement_settings.is_default, BidRequest.PublisherType.DEPRECATED_GOOGLE_REPRESENTED, BidResponse.ad.native_ad.DEPRECATED_bidder_name.

March 2, 2023

What's New in RTB Proto version 267

Removed BidRequest.mobile.skadn.version (singular).

This field has been deprecated and is replaced by BidRequest.mobile.skadn.versions (plural).

What's New in OpenRTB Extensions Proto version v.127

Removed BidRequest.imp.ext.skadn.version (singular).

This field has been deprecated and is replaced by BidRequest.imp.ext.skadn.versions (plural).

February 28, 2023

What's New in RTB Proto version 266

Added BidResponse.ad.app_promotion_type.

This field indicates the type of app promotion corresponding to the app specified in the BidResponse.ad.advertised_app_id field.

What's New in OpenRTB Extensions Proto version v.126

Added Bid.ext.app_promotion_type.

This field indicates the type of app promotion corresponding to the app specified in the BidResponse.seatbid.bid.bundle field.

February 27, 2023

What's New in OpenRTB Extensions Proto version v.125

Removed BidRequest.device.ext.use_agent_data.

Contained structed user agent information, which has now been migrated to the new standard OpenRTB 2.6 field BidRequest.device.sua.

February 24, 2023

What's New in RTB Proto version 265

Added BidRequest.video.playback_cessation_mode.

The event that causes playback to end. This will only be filled for non-instream video formats.

February 2, 2023

What's New in RTB Proto version 264

Added BidRequest.adslot.ad_unit_mapping.

Used to identify publisher inventory units in the bidder's namespace. Populated only when the bidder works directly with a publisher. For more information, see: https://support.google.com/admanager/answer/9601810. This is being migrated from BidRequest.adslot.open_bidding.ad_unit_mapping.

What's New in OpenRTB Extensions Proto version v.124

Added BidRequest.imp.ext.ad_unit_mapping.

Used to identify publisher inventory units in the bidder's namespace. Populated only when the bidder works directly with a publisher. For more information, see: https://support.google.com/admanager/answer/9601810. This is being migrated from BidRequest.imp.ext.open_bidding.ad_unit_mapping.

January 19, 2023

What's New in RTB Proto version 262

Added BidResponse.ad.skadn.product_page_id.

This field indicates the ID of a custom product page that will be displayed using Apple's SKStoreProductViewController.

Deprecated BidRequest.adslot.targetable_channel. This field will be removed in March 2023.

What's New in OpenRTB Extensions Proto version v.123

Added Bid.ext.skadn.productpageid.

This field indicates the ID of a custom product page that will be displayed using Apple's SKStoreProductViewController.

January 18, 2023

What's New in RTB Proto version 261

Increased the size limit for BidResponse.ad.event_notification_token to 128 bytes.

What's New in OpenRTB Extensions Proto version v.122

Increased the size limit for Bid.ext.event_notification_token.payload to 128 bytes.

December 23, 2022

What's New in OpenRTB Extensions Proto version v.121

Fixed field name typos in the documentation comments.

adx_ext is changed to ext.

Imp.ImpExtension is changed to imp.ext.

AppExt is changed to app.ext.

December 10, 2022

What's New in RTB Proto version 260

Added BidResponse.ad.skadn.source_identifier.

This is used to represent the ad campaign during SKAdNetwork 4.0+ attribution. This field replaces the BidResponse.ad.skadn.campaign field used by SKAdNetwork 3.0 and below.

What's New in OpenRTB Proto version v.120

Added Bid.ext.skadn.sourceidentifier.

This is used to represent the ad campaign during SKAdNetwork 4.0+ attribution. This field replaces the Bid.ext.skadn.campaign field used by SKAdNetwork 3.0 and below.

December 8, 2022

What's New in OpenRTB Extension Proto version v.119

The extension BidRequest.ext.user_agent_data is now deprecated and will be removed in January 2023. The standard field BidRequest.device.sua should be preferred.

What's New in OpenRTB Extension Proto version v.119

Removed deprecated field BidRequest.ext.user_agent_data.browser.

What's New in RTB Proto version 259

Removed deprecated field BidRequest.user_agent_data.DEPRECATED_browser.

November 29, 2022

What's New in OpenRTB Proto

Initial support for OpenRTB 2.6.

This release updates the proto to support the OpenRTB 2.6 specification. Actual support for the new fields will be an incremental process, announced in separate release notes as Google starts filling new fields and in some cases also deprecating extensions that will be replaced by standard fields. This release includes the first of those changes.

November 9, 2022

What's New in RTB Proto version 258

Removed BidRequest.adslot.buyer_generated_request_data.source_app.

BidRequest.adslot.secure_signals.source should be used instead of BidRequest.adslot.buyer_generated_request_data.source_app.

November 3, 2022

What's New in OpenRTB Proto

The behavior of BidResponse.cur has changed. If this field is populated, the specified currency will be used to interpret the bid rather than the account's default bidding currency. We also support BidResponse.seatbid.bid.bundle. If this field is provided, users will see the app store listing as an overlay after clicking the ad, without leaving the publisher app. This is currently enabled on rewarded and interstitial video ads only.

What's New in RTB Proto version 254

The behavior of BidResponse.ad.adslot.currency has changed. If this field is populated, the specified currency will be used to interpret the bid rather than the account's default bidding currency. We added BidResponse.ad[].advertised_app_id. If this field is provided, users will see the app store listing as an overlay after clicking the ad, without leaving the publisher app. This is currently enabled on rewarded and interstitial video ads only.

October 18, 2022

What's New in OpenRTB Extension Proto version v.118

Starting October 18, 2022, we will no longer populate BidRequest.imp.adx_ext.buyer_generated_request_data if the corresponding data is 0 bytes. We anticipate minimal impact to bidders.

What's New in RTB Proto version 253

Starting October 18, 2022, we will no longer populate BidRequest.slot.secure_signals if the corresponding data is 0 bytes. We anticipate minimal impact to bidders.

October 7, 2022

What's New in RTB Proto version 251

Renamed BidRequest.adslot.buyer_generated_request_data to BidRequest.adslot.secure_signals.

Added BidRequest.adslot.secure_signals.source.

Deprecated BidRequest.adslot.buyer_generated_request_data.source_js and BidRequest.adslot.buyer_generated_request_data.source_app.

BidRequest.adslot.secure_signals.source should be used instead of BidRequest.adslot.buyer_generated_request_data.source_js and BidRequest.adslot.buyer_generated_request_data.source_app.

October 3, 2022

What's New in RTB Proto version 252

Deprecated BidRequest.mobile.skadn.version (singular).

This field has been deprecated and is replaced by BidRequest.mobile.skadn.versions (plural), and will be removed in November 2022.

What's New in OpenRTB Proto version v.117

Deprecated BidRequest.imp.ext.skadn.version (singular).

This field has been deprecated and is replaced by BidRequest.imp.ext.skadn.versions (plural), and will be removed in November 2022.

September 8, 2022

What's New in RTB Proto version 250

Added BidRequest.inventory_partner_domain.

This field indicates the domain of the partner (of the site/app owner) with ownership of some portion of ad inventory on the site/app. The partner's ads.txt or app-ads.txt file will be hosted here. See the IAB Guidance for Inventory Sharing for more info.

What's New in OpenRTB Proto version v.115

Added BidRequest.site.ext.inventorypartnerdomain and BidRequest.app.ext.inventorypartnerdomain.

These fields indicate the domain of the partner (of the site/app owner) with ownership of some portion of ad inventory on the site/app. The partner's ads.txt or app-ads.txt file will be hosted here. See the IAB Guidance for Inventory Sharing for more info.

August 19, 2022

What's New in OpenRTB Proto

Removed BidRequest.video.companionad_21.

This field had been obsolete for several versions. It existed to support an incorrect interpretation of this field in the OpenRTB 2.1 specification, corrected in 2.2.

Removed BidRequest.(site|app).content.context_22.

This field had been obsolete for several versions. It existed to support an incorrect interpretation of this field in the OpenRTB 2.2 specification, corrected in 2.3.

Renamed enumerated value AdPosition.LIKELY_BELOW_THE_FOLD.

This value was deprecated in OpenRTB 2.1, and as part of that deprecation it gained a prefix DEPRECATED_ which is usual in the Google protocol, but not to be used in OpenRTB. This is only a source-level compatibility change since the on-wire protocol (either Protobuf or JSON) only uses the numerical value, not the identifier for enumerated values.

Removed obsolete comments for keywords fields in several objects.

What's New in OpenRTB Extension Proto version v.112

Added BidRequest.privacy_treatments.user_agent.

Indicates whether the field BidRequest.user_agent has been generalized to protect user privacy.

Added BidRequest.privacy_treatments.user_agent_data.

Indicates whether the field BidRequest.user_agent_data has been generalized to protect user privacy.

What's New in RTB Proto version 246

Added BidRequest.ext.privacy_treatments.user_agent.

Indicates whether the field BidRequest.ua has been generalized to protect user privacy.

Added BidRequest.ext.privacy_treatments.user_agent_data.

Indicates whether the field BidRequest.ext.user_agent_data has been generalized to protect user privacy.

August 17, 2022

What's New in RTB Proto version 246

Added BidRequest.adslot.impression_expiration_seconds to the bid request.

This field specifies the expected time period for an impression following a winning bid. See Impressions expiration for more details.

August 15, 2022

What's New in RTB Proto version 245

Added BidRequest.mobile.is_app_open_ad.

This field indicates the ad slot is for a mobile app open ad. See the App open ad guide for more info.

What's New in OpenRTB Proto version v.111

Added BidRequest.imp.ext.is_app_open_ad.

This field indicates the ad slot is for a mobile app open ad. See the App open ad guide for more info.

July 18, 2022

What's New in OpenRTB Proto version 244

Removed field BidRequest.device.ext.user_agent_data.browser. Use the field BidRequest.device.ext.user_agent_data.browsers instead.

General reviews to documentation (field comments), in particular deprecation/removal status.

Added field Content.data. This field was introduced in OpenRTB 2.4 but was missing from the proto.

June 29, 2022

What's New in RTB Proto version 243

Deprecated BidRequest.adslot.creative_enforcement_settings.is_default.

This field has been deprecated due to being unused and will be removed in August 2022.

What's New in OpenRTB Proto version v.109

Deprecated BidRequest.imp.ext.creative_enforcement_settings.is_default.

This field has been deprecated due to being unused and will be removed in August 2022.

What's changing with the deprecation process

Deprecated content such as fields and messages in Real-time Bidding Protocol Buffer files will no longer have their names appended with a DEPRECATED_ prefix. Instead, deprecated fields will be identified by the first line of their comments including a deprecation notice. Existing deprecated fields will remain unchanged until they are removed as planned.

June 23, 2022

What's New in RTB Proto version 242

Added BidResponse.Ad.AdSlot.currency field when specifying the bid response. Added comments to explain the behavior of this field.

June 8, 2022

What's New in OpenRTB Extension Proto version v.108

Documentation updates for field BidRequest.device.ext.user_agent_data for better alignment with the BidRequest.device.sua field in the recently-published OpenRTB 2.6 specification. (Support for the standard BidRequest.device.sua field will come in a future update.)

What's New in RTB Proto version 241

Documentation updates for field BidRequest.user_agent_data for better alignment with the BidRequest.device.sua field in the recently-published OpenRTB 2.6 specification. (Full compatibility with the OpenRTB 2.6 standard UserAgent object will come in a future update.)

May 23, 2022

What's New in RTB Proto version 240

Announced deprecation of field BidRequest.user_agent_data.browser. Use the field BidRequest.user_agent_data.browsers instead. This field will be removed on 2022-06-20.

What's New in OpenRTB Proto version v.107

Announced deprecation of field BidRequest.device.ext.user_agent_data.browser. Use the field BidRequest.device.ext.user_agent_data.browsers instead. This field will be removed on 2022-06-20.

May 17, 2022

What's New in RTB Proto version 239

Added field BidResponse.ad.sdk_rendered_ad.declared_ad.native_ad.

This field lets buyer sdk-rendered ad bidders declare a renderable native ad.

What's New in OpenRTB Proto version v.106

Added field BidResponse.seatbid.bid.ext.sdk_rendered_ad.declared_ad.native_response.

This field lets buyer sdk-rendered ad bidders declare a renderable native ad.

May 12, 2022

What's New in RTB Proto version 238

Added BidRequest.privacy_treatments.allow_user_data_collection.

Indicates if publisher grants the permission that allows the bidder to use user visitation information from their site to create interest categories that can be used to serve ads based on those categories. To use this data to create interest categories, a bidder must also win a given impression.

What's New in OpenRTB Proto version v.105

Added BidRequest.ext.privacy_treatments.allow_user_data_collection.

Indicates if publisher grants the permission that allows the bidder to use user visitation information from their site to create interest categories that can be used to serve ads based on those categories. To use this data to create interest categories, a bidder must also win a given impression.

April 25, 2022

What's New in RTB Proto version 237

Deleted deprecated BidRequest.floc.

What's New in OpenRTB Proto version v.104

Deleted deprecated User.ext.floc.

March 31, 2022

What's New in RTB Proto version 236

Added BidResponse.Ad.click_tracking_urls.

You can use this field to populate click tracking URLs for native ads and publisher managed creatives on Programmatic Guaranteed deals.

Deprecated BidResponse.Ad.NativeAd.click_tracking_url and BidResponse.Ad.NativeAd.click_tracking_urls.

The new BidResponse.Ad.click_tracking_urls replaces these fields at the NativeAd level. BidResponse.Ad.click_tracking_urls works the same way as these deprecated fields, with the addition that the new field also populates click trackers for publisher managed creatives. The deprecated fields will continue to work through June 2022, then they will be removed from the protocol. During the transition, we will render both sets of click trackers in the native creatives if both fields are specified in the bid response.

What's New in OpenRTB Proto version v.102

Added Bid.ext.click_tracking_urls.

You can use this field to populate click tracking URLs for native ads and publsher managed creatives on Programmatic Guaranteed deals. The fields in the NativeResponse and ResponseAsset will continue to work for native ads. If one or both of the native clicktrackers fields are specified in addition to this new field, we will render all click trackers from all three fields in the response.

November 29, 2021

What's New in RTB Proto version 235

Moved TURTLEDOVE and FLEDGE simulation fields to the early access testing version of the protocol.

Contact your account manager for access to the simulation.

November 18, 2021

What's New in RTB Proto version 233

Removed BidRequest.anonymous_id.

This field has been deprecated since version 218 and is now removed.

November 10, 2021

What's New in RTB Proto version 232

Added FREQUENCY_CAPPING_SCOPE_SITE and FREQUENCY_CAPPING_SCOPE_APP to BidRequest.AdSlot.FrequencyCappingScope, indicating that frequency capping is available within a single site or a single app.

What's New in OpenRTB Proto version v.98

Added FREQUENCY_CAPPING_SCOPE_SITE and FREQUENCY_CAPPING_SCOPE_APP to BidRequest.ext.fcap_scope, indicating that frequency capping is available within a single site or a single app.

November 9, 2021

What's New in RTB Proto version 231

Added BidRequest.user_agent_data.browsers, which should now be used in preference to BidRequest.user_agent_data.browser.

What's New in OpenRTB Proto version v.97

Added BidRequest.device.ext.user_agent_data.browsers, which should now be used in preference to BidRequest.device.ext.user_agent_data.browser.

October 27, 2021

Real-time Bidding updates

The following fields are now populated for native video bid requests to align with OpenRTB Dynamic Native Ads API Specification Version 1.2:

• BidRequest.video.max_ad_duration
• BidRequest.video.min_ad_duration
• BidRequest.video.protocols
• BidRequest.video.allowed_video_formats

• BidRequest.imp.native.request_native.assets.video.mimes
• BidRequest.imp.native.request_native.assets.video.minduration
• BidRequest.imp.native.request_native.assets.video.maxduration
• BidRequest.imp.native.request_native.assets.video.protocols

In the OpenRTB JSON protocol, video assets for native ads also have their mimes, minduration, maxduration, and protocols fields populated.

October 22, 2021

What's New in RTB Proto version 230

Added BidRequest.privacy_treatments.non_personalized_ads_reason. Specifies the reasons that ads returned in response to this request should not be personalized.

What's New in OpenRTB Proto version v.96

Added BidRequest.ext.privacy_treatments.non_personalized_ads_reason for the open RTB version of this field.

October 04, 2021

What's New in RTB Proto version 229

Added BidRequest.user_agent_data.bitness.

What's New in OpenRTB Proto version v.95

Added BidRequest.device.ext.user_agent_data.bitness.

September 2, 2021

What's New in RTB Proto version 227

Removed BidRequest.adslot.exchange_bidding.publisher_parameter.

This field has been deprecated since version 213 and is now removed.

What's New in OpenRTB Proto version v.93

Removed BidRequest.imp.ext.publisher_parameter.

This field has been deprecated since v.81 and is now removed.

July 19, 2021

What's New in RTB Proto version 225

Added field BidRequest.host_publisher_id.

The field is the ID of the host publisher. When populated, indicates that the host publisher participated in revenue sharing, and the ID can be used to authorize ads.txt.

What's New in RTB Proto version 224

Added BidRequest.mobile.skadn.supported_fidelity_types.

This field specifies which SKAdNetwork attribution fidelity types are supported by the ad request. For more information see the SKAdNetwork Attribution Initiation Guidelines.

Added BidResponse.ad.skadn.fidelities.

This message holds the parameters used to generate the signature for each of the fidelity types supported for SKAdNetwork v2.2 and up. For more information regarding SKAdNetwork v2.2 see Apple's release notes.
Note that this message is intended to replace the BidResponse.ad.skadn.nonce, BidResponse.ad.skadn.timestamp, and BidResponse.ad.skadn.signature fields, and so the older fields will be deprecated in the future.

What's New in OpenRTB Proto version v.91

Added field BidRequest.publisher.ext.host_publisher_id.

The field is the ID of the host publisher. When populated, indicates that the host publisher participated in revenue sharing, and the ID can be used to authorize ads.txt.

What's New in OpenRTB Proto version v.90

Added BidRequest.imp.ext.skadn.fidelities.

This field specifies which SKAdNetwork attribution fidelity types are supported by the ad request. For more information see the SKAdNetwork Attribution Initiation Guidelines.

Added Bid.ext.skadn.fidelities.

This message holds the parameters used to generate the signature for each of the fidelity types supported for SKAdNetwork v2.2 and up. For more information regarding SKAdNetwork v2.2 see Apple's release notes.
Note that this message is intended to replace the Bid.ext.skadn.nonce, Bid.ext.skadn.timestamp, and Bid.ext.skadn.signature fields, and so the older fields will be deprecated in the future.

July 14, 2021

What's New in RTB Proto version 222

Removed video.DEPRECATED_inventory_type field.

This field has been deprecated for several years.

July 13, 2021

What's New in RTB Proto version 221

Fixed typo in documentation for CreativeEnforcementSettings.PolicyEnforcement.

"Respected" was changed to "respective".

What's New in OpenRTB Proto version v.88

Fixed typo in documentation for CreativeEnforcementSettings.PolicyEnforcement.

"Respected" was changed to "respective".

July 08, 2021

What's New in RTB Proto version 220

Added field BidResponse.ad.skadn.skadn_options.always_open_appstore.

This option enables GMA SDK to always initiate SKAdNetwork attribution on-click regardless of the click-through URL's final destination. For more information, see the SKAdNetwork Attribution Initiation Guidelines.

What's New in OpenRTB Proto version v.87

Added field BidResponse.seat_bid.bid.adx_ext.skadn.skadn_opts.always_open_appstore.

This option enables GMA SDK to always initiate SKAdNetwork attribution on-click regardless of the click-through URL's final destination. For more information, see the SKAdNetwork Attribution Initiation Guidelines.

July 1, 2021

What's New in RTB Proto version 219

Added field BidResponse.ad.sdk_rendered_ad.declared_ad.

This field allows 3P sdk-rendered ad bidders to declare a renderable ad. Only html and video formats are supported for this release.

What's New in OpenRTB Proto version v.86

Added field BidResponse.seatbid.bid.ext.sdk_rendered_ad.declared_ad.

This field allows 3P sdk-rendered ad bidders to declare a renderable ad. Only html and video format are supported for this release.

What's New in RTB Proto version 218

Deprecated BidRequest.anonymous_id.

This field has been deprecated due to being unused and will be removed in September 2021.

June 30, 2021

What's New in RTB Proto version 217

Added BidRequest.slot.buyer_generated_request_data.source_js.

Specifies the JavaScript library that generated an encrypted signal that is sent to a buyer by the publisher.

What's New in OpenRTB Proto version v.85

Added BidRequest.user.ext.eids.

Indicates an encrypted signal that can be provided to a buyer by the publisher.

June 25, 2021

What's New in RTB Proto version 216

Added BidRequest.adslot.consented_providers_settings.additional_consent_string.

The raw Additional Consent string, which contains a list of consented Google Ad Tech Providers that are not registered with IAB.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.84

Added BidRequest.user.adx_ext.consented_providers_settings.additional_consent.

The raw Additional Consent string, which contains a list of consented Google Ad Tech Providers that are not registered with IAB.

June 21, 2021

What's New in RTB Proto version 215

Added enum field BidRequest.adslot.auction_environment.

This field describes the environment where the ad auction is run: either all on the server-side, server-side with sandboxed interest group bidding simulation, or with the contextual auction on the server-side and the interest group bidding and the final auction on the device.

What's New in OpenRTB Proto version v.83

Added enum field BidRequest.imp.ext.auction_environment.

This field describes the environment where the ad auction is run: either all on the server-side, server-side with sandboxed interest group bidding simulation, or with the contextual auction on the server-side and the interest group bidding and the final auction on the device.

June 17, 2021

What's New in RTB Proto version 214

Added BidRequest.device.app_tracking_authorization_status.

This field is only populated for iOS devices. Indicates the app tracking authorization status.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.82

Added Device.ext.atts.

This field is only populated for iOS devices. Indicates the app tracking authorization status.

June 15, 2021

What's New in RTB Proto version 213

Updated BidRequest.publisher_type.

This field's enums are now updated to align with sellers.json.

Deprecated BidRequest.adslot.exchange_bidding.publisher_parameter.

This field has been deprecated due to being unused and will be removed August 2021.

What's New in OpenRTB Proto version v.81

Deprecated BidRequest.imp.ext.publisher_parameter.

This field has been deprecated due to being unused and will be removed August 2021.

June 09, 2021

What's New in RTB Proto version 212

Added repeated field BidRequest.mobile.skadn.versions.

This field includes the list of SKAdNetwork versions supported, depending on the OS version and the SDK version. Note that this field is intended to replace the BidRequest.mobile.skadn.version (singular) field, and so the older field will be deprecated in the future.

What's New in OpenRTB Proto version v.80

Added repeated field BidRequest.imp.ext.skadn.versions.

This field includes the list of SKAdNetwork versions supported, depending on the OS version and the SDK version. Note that this field is intended to replace the BidRequest.imp.ext.skadn.version (singular) field, and so the older field will be deprecated in the future.

June 2, 2021

What's New in RTB Proto version 210

Added BidRequest.adslot.api.

The list of supported API frameworks for this impression.

June 1, 2021

What's New in RTB Proto version 209

Added BidRequest.bid_response_feedback.bidding_function_debug_string.

An optional debug string a bidding function can return to aid in remote debugging.

May 27, 2021

What's New in RTB Proto version 208

Introduced oneof field BidResponse.native_ad.video.

Allows either a video_url or a VAST document to be returned for Native video ads.

May 20, 2021

What's New in RTB Proto version 207

Added BidRequest.ext.bid_feedback.bidding_function_runtime.

The estimated time it took for a bidding function to run. This is an experimental feature for the TURTLEDOVE and FLEDGE server-side simulations.

May 06, 2021

What's New in RTB Proto version 206

Added BidRequest.Device.limit_ad_tracking.

Indicates whether the user has opted out of interest based advertising or ads personalization as determined by an OS-level setting in iOS or Android.

May 05, 2021

What's New in RTB Proto version 205

Added BidResponse.interest_group_map.

In FLEDGE simulation, bidder can use this to list out the interest groups on a response.

Added BidResponse.interest_group_bidding.

In FLEDGE simulation, bidder can use this to specify the Contextual signal.

Added BidResponse.adslot.interest_group_name.

In FLEDGE simulation, bidder can use this to specify the name of the interest group that an Ad belongs to.

Added BidResponse.adslot.ad_data.

In FLEDGE simulation, bidder can use this to specify the per ad data for each interest group ad.

What's New in OpenRTB Protos

Added BidResponse.ext.interest_group_map.

In FLEDGE simulation, bidder can use this to list out the interest groups on a response.

Added BidResponse.ext.interest_group_bidding.

In FLEDGE simulation, bidder can use this to specify the Contextual signal.

Added Bid.ext.interest_group_name.

In FLEDGE simulation, bidder can use this to specify the name of the interest group that an Ad belongs to.

Added Bid.ext.ad_data.

In FLEDGE simulation, bidder can use this to specify the per ad data for each interest group ad.

May 04, 2021

What's New in RTB Proto version 203

Added BidRequest.adslot.creative_enforcement_settings.

This describes the policy and publisher control enforcement level that a creative should adhere to.

March 24, 2021

What's New in RTB Proto version 202

Added BidRequest.bid_response_feedback.bidding_function_runtime.

The time it took for a bidder's TURTLEDOVE simulation bidding function to run.

March 22, 2021

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.73

Updated encoding alphabet for Device.ext.session_id.

Device.ext.session_id is now populated with web-safe base64 alphabet.

March 19, 2021

What's New in RTB Proto version 201

Added BidRequest.frequency_capping_scope.

Describes the scope of frequency cap enforcement available for the request.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.72

Added BidRequest.ext.fcap_scope.

Describes the scope of frequency cap enforcement available for the request.

March 18, 2021

What's New in RTB Proto version 199

Added BidRequest.adslot.multi_ads_cell_info.

New Beta feature subject to change, information about individual cells in multi ad grids.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.71

Added BidRequest.imp.ext.multi_ads_cell_info.

New Beta feature subject to change, information about individual cells in multi ad grids.

March 12, 2021

What's New in RTB Proto version 199

Added BidRequest.user_agent_data.

A structured representation of user agent information extracted from the User-Agent and/or Sec-CH-UA headers.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.70

Added BidRequest.device.ext.user_agent_data.

A structured representation of user agent information extracted from the User-Agent and/or Sec-CH-UA headers.

March 8, 2021

What's New in RTB Proto version 198

Added BidRequest.adslot.billable_event_rate_adjustment.

For ads rendered using a custom SDK only: multiplier applied to bid in the auction.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.69

Added Imp.ext.billable_event_rate_adjustment.

For ads rendered using a custom SDK only: multiplier applied to bid in the auction.

March 2, 2021

What's New in RTB dictionaries

The geo-table.csv dictionary file has changed.

Several new cities and postal codes were added.

February 24, 2021

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

The mobile-os.csv dictionary file has changed.

Added line 630432,"iOS",14,5,-1.

The creative-status-codes.txt dictionary file has changed.

Added 201 The TC string doesn't contain consent for one of the vendors included in this ad creative.

Added 219 The list of ad technology providers used by the publisher to collect consent doesn't contain one of the vendors included in this ad creative.

Added 220 Native ad filtered because it contains both video URL and VAST tag.

Added 221 Native ad filtered because the VAST XML document is empty.

Added 222 Native ad filtered because the VAST XML document is too large.

Deleted 201 Ad violates the vendor restrictions specified by the Transparency & Consent string.

February 18, 2021

What's New in RTB Proto version 190

Added BidRequest.supply_chain.

SupplyChain object. For more information, see https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/supplychainobject.md.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.59

Added BidRequest.source.adx_ext.schain.

SupplyChain object. For more information, see https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/supplychainobject.md.

January 28, 2021

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

January 11, 2021

What's New in RTB dictionaries

The publisher-verticals.txt dictionary file has changed.

Added line 1034 /Arts & Entertainment/Music & Audio/World Music/Middle Eastern & North African Music.

Deleted line 1034 /Arts & Entertainment/Music & Audio/World Music/Arab & Middle Eastern Music.

The mobile-os.csv dictionary file has changed.

Added line 630428,"iOS",14,4,-1.

The creative-status-codes.txt dictionary file has changed.

Added 94 Creative filtered because it is a non-skippable video ad for a skippable-only request. Creative filtered because it is a non-skippable video ad for a skippable-only request

Added 149 The click tracking URL is too short to be a valid URL. The click tracking URL is too short to be a valid URL

Added 150 The click tracking URL cannot be parsed as valid URL. The click tracking URL cannot be parsed as valid URL

Added 151 The click tracking URL has a domain that is all digits. The click tracking URL has a domain that is all digits

Added 218 Ad contains a vendor domain that could not be attributed to any known vendor.. Ad contains a vendor domain that could not be attributed to any known vendor.

Deleted 94 Creative filtered because it is a non-skippable video ad for a skippable request.

Deleted 149 Unknown error (deprecated).

Deleted 150 Unknown error (deprecated).

Deleted 151 Unknown error (deprecated).

December 22, 2020

What's New in RTB Proto version 189

Added BidRequest.geo.

The user's approximate geolocation expressed in a structured form.

December 14, 2020

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

Added line 2602,"TorchAD","https://app.torchad.com/advertiser/privacy","bidder.beambid.com".

Deleted line 2602,"Unmatched Solutions Ltd","","bidder.beambid.com".

Added line 528,"Weborama","https://weborama.com/en/weborama-privacy-commitment/","ade.weborama.nl adrcdn.com adrcntr.com adrime.com astatic.weborama.fr bigsea.weborama.com bsd.frontend-preprod.weborama.fr bsd.frontend.weborama.fr cntr.adrcntr.com cr.frontend-preprod.weborama.fr cr.frontend.weborama.fr cs.frontend-preprod.weborama.fr cs.frontend.weborama.fr cstatic.weborama.fr elstatic.weborama.fr esstatic.weborama.fr evt.adrcntr.com frontend.weborama.com frontend.weborama.fr idsync.frontend-preprod.weborama.fr idsync.frontend.weborama.fr istatic.weborama.fr l3static.weborama.fr media.adrcdn.com perf.weborama.fr pro.weborama.fr pub.weborama.fr rd.frontend-preprod.weborama.fr rd.frontend.weborama.fr redirect.frontend-preprod.weborama.fr redirect.frontend.weborama.fr script.weborama.fr scripts.adrcdn.com solution.weborama.fr static.weborama.fr wam-google.solution.weborama.fr wcm-na.frontend.weborama.com weborama.com weborama.fr wf.frontend-preprod.weborama.fr wf.frontend.weborama.fr".

Added line 1872,"Wizaly","https://www.wizaly.com/terms-of-use#privacy-policy","esearchvision.com t.wiz.meilleurtaux.com tk.abt.com tk.airfrance.fr tk.biovea.com tk.conforama.fr tk.engie.fr tk.healthwarehouse.com tk.lcl.fr tk.little-big-change.com tk.loreal-paris.fr tk.lulli-sur-la-toile.com tk.msccruises.com tk.ornikar.com tk.prismashop.fr tk.salomon.com tk.svsound.com tk.transavia.com tk.viapresse.com trackv.esearchvision.com tv.wizaly.com wiz.ghostbed.com wiz.mdhearingaid.com wiz.meilleurtaux.com wizaly.allianz.fr wizaly.com".

Added line 1892,"PERMODO","http://permodo.com/de/privacy.html","adsafety.net buyer.dspx.tv cdn-solution.net cdn.dspx.tv cdn.permodo.net cdn.recognified.net cm.adsafety.net concheck.adsafety.net d.permodo.net dspx.cdn-solution.net etrtbbs-adx.permodo.net mads.cdn-solution.net mads.permodo.net media.permodo.net permodo.net rads.recognified.net tags.adsafety.net tracking-mads.adsafety.net tracking.adsafety.net tracking.dspx.tv venc.dspx.tv venc.permodo.net xtag.cdn-solution.net".

Added line 3089,"Transmit.Live","https://transmit.live/privacy-policy/","clips.transmit.live gclips.transmit.live pix-us-east-1.transmit.live pix-us-west-1.transmit.live pix.transmit.live pixt.transmit.live stag2pix.transmit.live track.transmit.live vast-encodes.transmit.live vast.transmit.live".

Deleted line 528,"Weborama","https://weborama.com/en/weborama-privacy-commitment/","ade.weborama.nl adrcdn.com adrcntr.com adrime.com astatic.weborama.fr bigsea.weborama.com cntr.adrcntr.com cstatic.weborama.fr elstatic.weborama.fr esstatic.weborama.fr evt.adrcntr.com frontend.weborama.com frontend.weborama.fr istatic.weborama.fr l3static.weborama.fr media.adrcdn.com perf.weborama.fr pro.weborama.fr pub.weborama.fr script.weborama.fr scripts.adrcdn.com solution.weborama.fr static.weborama.fr wcm-na.frontend.weborama.com weborama.com weborama.fr".

Deleted line 1872,"Wizaly","https://www.wizaly.com/terms-of-use#privacy-policy","esearchvision.com t.wiz.meilleurtaux.com tk.abt.com tk.airfrance.fr tk.biovea.com tk.conforama.fr tk.engie.fr tk.healthwarehouse.com tk.lcl.fr tk.little-big-change.com tk.loreal-paris.fr tk.lulli-sur-la-toile.com tk.msccruises.com tk.prismashop.fr tk.salomon.com tk.svsound.com tk.transavia.com tk.viapresse.com trackv.esearchvision.com tv.wizaly.com wiz.ghostbed.com wiz.mdhearingaid.com wiz.meilleurtaux.com wizaly.allianz.fr wizaly.com".

Deleted line 1892,"PERMODO","http://permodo.com/de/privacy.html","adsafety.net buyer.dspx.tv cdn-solution.net cdn.dspx.tv cdn.permodo.net cdn.recognified.net cm.adsafety.net concheck.adsafety.net d.permodo.net dspx.cdn-solution.net etrtbbs-adx.permodo.net etrtbss.sspx.tech mads.cdn-solution.net mads.permodo.net media.permodo.net permodo.net rads.recognified.net tags.adsafety.net tracking-mads.adsafety.net tracking.adsafety.net tracking.dspx.tv venc.dspx.tv venc.permodo.net xtag.cdn-solution.net".

Deleted line 3089,"Transmit.Live","https://transmit.live/privacy-policy/","clips.transmit.live gclips.transmit.live pix-us-east-1.transmit.live pix-us-west-1.transmit.live pix.transmit.live pixt.transmit.live stag2pix.transmit.live".

Added line 1034,"Rutarget","https://segmento.ru/en/gdpr","cdn.rutarget.ru cdn2.rutarget.ru cdn3.rutarget.ru cdn4.rutarget.ru cdn5.rutarget.ru click.rutarget.ru creative-ibv.rutarget.ru creative.rutarget.ru google-sync.rutarget.ru rutarget.ru tag.rutarget.ru video.rutarget.ru".

Added line 1892,"PERMODO","http://permodo.com/de/privacy.html","adsafety.net buyer.dspx.tv cdn-solution.net cdn.dspx.tv cdn.permodo.net cdn.recognified.net cm.adsafety.net concheck.adsafety.net d.permodo.net dspx.cdn-solution.net etrtbbs-adx.permodo.net etrtbss.sspx.tech mads.cdn-solution.net mads.permodo.net media.permodo.net permodo.net rads.recognified.net tags.adsafety.net tracking-mads.adsafety.net tracking.adsafety.net tracking.dspx.tv venc.dspx.tv venc.permodo.net xtag.cdn-solution.net".

Added line 3002,"TrafficGuard","https://www.trafficguard.ai/gdpr/","api.trafficguard.ai pixel.trafficguard.ai px.tgtag.io".

Added line 3182,"LIDL SUPERMERCADOS, S.A.U.","https://www.lidl.es/es/politica-de-privacidad/s797","lidl.es".

Added line 3202,"ViralGains, Inc.","","events.viralgains.com odc-media.kube.viralgains.com odc-wsb.viralgains.com odc.kube.viralgains.com odc.vgview.com odyssey.viralgains.com player.kube.viralgains.com vpaid.kube.viralgains.com".

Added line 3214,"LINE","https://terms.line.me/line_rules","a.line.me bc2.fivecdm.com cdn.fivecdm.com google-hb.fivecdm.com lan-click.tr.line.me lap-click.tr.line.me vastbc.fivecdm.com".

Added line 3218,"42 Ads","https://www.42ads.io/42privacy.pdf","ai.trk42.net".

Deleted line 132,"Choicestream Inc.","","choicestream.com csstatic.choicestream.com".

Deleted line 1034,"Rutarget","https://segmento.ru/en/gdpr","cdn.rutarget.ru cdn2.rutarget.ru cdn3.rutarget.ru click.rutarget.ru creative-ibv.rutarget.ru creative.rutarget.ru google-sync.rutarget.ru rutarget.ru tag.rutarget.ru video.rutarget.ru".

Deleted line 1892,"PERMODO","http://permodo.com/de/privacy.html","adsafety.net cdn-solution.net cdn.permodo.net d.permodo.net etrtbbs-adx.permodo.net mads.cdn-solution.net mads.permodo.net media.permodo.net permodo.net tags.adsafety.net tracking-mads.adsafety.net tracking.adsafety.net venc.permodo.net".

Deleted line 3002,"TrafficGuard","https://www.trafficguard.ai/gdpr/","pixel.trafficguard.ai".

November 19, 2020

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

Several lines were added and deleted.

The mobile-os.csv dictionary file has changed.

Added line 630421,"iOS",14,1,-1.

The creative-status-codes.txt dictionary file has changed.

Added 213 A provided ad load notification URL is too short to be a valid URL.

Added 214 A provided ad load notification URL cannot be parsed as a valid URL.

Added 215 A provided ad load notification URL has a domain that is all digits.

Added 216 Ad load notification URLs are not supported for non mobile-app SDK rendered ads.

October 26, 2020

What's New in RTB dictionaries

The geo-table.csv dictionary file has changed.

Several new cities were added.

The providers.csv dictionary file has changed.

Added line 12,"LiveRamp","https://liveramp.com/service-privacy-policy/","id.rlcdn.com idsync.rlcdn.com p.tvpixel.com pippio.com rc.rlcdn.com rlcdn.com".

Added line 229,"Google","https://www.google.com/policies/technologies/partner-sites/","2mdn.net ad.ytsa.net adservice.google.ae adservice.google.co.ve adservice.google.com adservice.google.com.ae adservice.google.com.cy adservice.google.com.eg adservice.google.com.hk adservice.google.com.kw adservice.google.com.sg adservice.google.com.tr adservice.google.gr adservice.google.hr adservice.google.si ajax.googleapis.com ampproject.net apis.google.com appspot.com cdn.ampproject.org d3f7gw76qga2vf.cloudfront.net dartmotif.net dmtry.com doubleclick.net fonts.googleapis.com fonts.gstatic.com geo*.ggpht.com gexperiments1.com gexperiments2.com gexperiments3.com gexperiments4.com gmodules.com go.channelintelligence.com google.al google.am google.at google.az google.be google.bg google.ca google.ch google.cl google.co.id google.co.in google.co.jp google.co.nz google.co.th google.co.uk google.co.ve google.co.vi google.co.za google.com google.com.ar google.com.au google.com.bo google.com.br google.com.co google.com.ec google.com.gh google.com.lb google.com.mm google.com.mt google.com.mx google.com.ni google.com.om google.com.pe google.com.ph google.com.pk google.com.pr google.com.py google.com.sv google.com.tw google.com.ua google.com.vn google.cz google.de google.dk google.ee google.es google.fi google.fr google.ge google.hu google.ie google.iq google.it google.jo google.kz google.lk google.lt google.lv google.mn google.nl google.no google.pl google.pt google.ro google.rs google.ru google.se google.sk google.tn googleadservices.com googleapis.com googleapis.com.au googlecommerce.com googlesyndication.com googletagservices.com googleusercontent.com googlevideo.com gstatic.com gvt1.com lh*.ggpht.com links.channelintelligence.com livesportsresults-1273.appspot.com media.admob.com obrasilinteirojoga.com.br pcdn.tcgmsrv.net plusone.google.com rdr.tag.channelintelligence.com s0.2mdn.net static.googleadsserving.cn storage.googleapis.com studioapi.doubleclick.com teracent.net ttwbs.channelintelligence.com us-central1-amp-error-reporting.cloudfunctions.net wtb.channelintelligence.com www.googletagservices.com youknowbest.com youtu.be youtube-nocookie.com youtube.com yt3.ggpht.com ytimg.com".

Added line 2039,"Kadam","https://www.kadam.net/ru/privacy-policy","adx.kadam.net cdn.kadxin.net dsp.kadam.net go.kadxin.net h.kadxin.net hk-go.kadxin.net hk.kadam.net impr.kadxin.net media.kadxin.net s.kadxin.net us1impr.kadxin.net us2impr.kadxin.net".

Added line 2141,"Adways SAS","http://www.adways.com/privacy/","adways-v2-users-resources.s3.amazonaws.com analytics.adpaths.com analytics.adways.com assets.adpaths.com contents.adpaths.com hv-contents.adpaths.com play.adpaths.com publication.adpaths.com vast.adpaths.com videos.adpaths.com www.adways.com www.adwstats.com".

Added line 2467,"Phaistos Networks","http://adman.gr/gdpr","adman.gr bold.adman.gr ibv.adman.gr obj.adman.gr player.pstatic.gr sherlock.adman.gr static.adman.gr talos.adman.gr watson.adman.gr".

Added line 2649,"Seenthis","https://seenthis.co/privacy-notice-2018-04-18.pdf","seenthis.se t.seenthis.se video.seenthis.se".

Added line 2971,"Brand Metrics","https://collector.brandmetrics.com/brandmetrics_privacypolicy.pdf","cdn.brandmetrics.com collector.brandmetrics.com".

Added line 3057,"Lean Digital Media","https://www.contentignite.com/gdpr/","api.leandigitalmedia.com api.tagdeliver.com cdn.leandigitalmedia.com cdn.tagdeliver.com".

Added line 3178,"BLIINK","https://bliink.io/privacy-policy","bliink.io collector.bliink.io cookiesync.api.bliink.io creative-sdk.bliink.io creative.bliink.io creatives.bliink.io delivery.api.bliink.io e.api.bliink.io engine.bliink.io static.bliink.io tag.bliink.io video.bliink.io".

Added line 3206,"Pure Local Media GmbH","https://purelocalmedia.de/?page_id=593","ads.purelocalmedia.de".

Added line 3207,"Soundcast","https://soundcast.fm/en/data-privacy","soundcast.fm".

Added line 3208,"Czech Publisher Exchange z.s.p.o.","https://www.cpex.cz/en/for-users/","cdn.cpex.cz cpex.cz en.cpex.cz pixel.cpex.cz".

Added line 3209,"Lentainform","https://partner.lentainform.com/privacy-policy/","api.lentainform.com jsc.lentainform.com mg.lentainform.com".

Added line 3211,"AlikeAudience","https://alikeaudience.com/privacy-policy/","ad.alikeaudience.com".

Deleted line 12,"LiveRamp","https://liveramp.com/service-privacy-policy/","idsync.rlcdn.com p.tvpixel.com pippio.com rc.rlcdn.com rlcdn.com".

Deleted line 229,"Google","https://www.google.com/policies/technologies/partner-sites/","2mdn.net ad.ytsa.net adservice.google.ae adservice.google.co.ve adservice.google.com adservice.google.com.ae adservice.google.com.cy adservice.google.com.eg adservice.google.com.hk adservice.google.com.sg adservice.google.com.tr adservice.google.gr adservice.google.hr adservice.google.si ajax.googleapis.com ampproject.net apis.google.com appspot.com cdn.ampproject.org d3f7gw76qga2vf.cloudfront.net dartmotif.net dmtry.com doubleclick.net fonts.googleapis.com fonts.gstatic.com geo*.ggpht.com gexperiments1.com gexperiments2.com gexperiments3.com gexperiments4.com gmodules.com go.channelintelligence.com google.al google.am google.at google.az google.be google.bg google.ca google.ch google.cl google.co.id google.co.in google.co.jp google.co.nz google.co.th google.co.uk google.co.ve google.co.vi google.co.za google.com google.com.ar google.com.au google.com.bo google.com.br google.com.co google.com.ec google.com.gh google.com.lb google.com.mm google.com.mt google.com.mx google.com.ni google.com.om google.com.pe google.com.ph google.com.pk google.com.pr google.com.py google.com.sv google.com.tw google.com.ua google.com.vn google.cz google.de google.dk google.ee google.es google.fi google.fr google.ge google.hu google.ie google.iq google.it google.jo google.kz google.lk google.lt google.lv google.mn google.nl google.no google.pl google.pt google.ro google.rs google.ru google.se google.sk google.tn googleadservices.com googleapis.com googleapis.com.au googlecommerce.com googlesyndication.com googletagservices.com googleusercontent.com googlevideo.com gstatic.com gvt1.com lh*.ggpht.com links.channelintelligence.com livesportsresults-1273.appspot.com media.admob.com obrasilinteirojoga.com.br pcdn.tcgmsrv.net plusone.google.com rdr.tag.channelintelligence.com s0.2mdn.net static.googleadsserving.cn storage.googleapis.com studioapi.doubleclick.com teracent.net ttwbs.channelintelligence.com us-central1-amp-error-reporting.cloudfunctions.net wtb.channelintelligence.com www.googletagservices.com youknowbest.com youtu.be youtube-nocookie.com youtube.com yt3.ggpht.com ytimg.com".

Deleted line 2039,"Kadam","https://www.kadam.net/ru/privacy-policy","adx.kadam.net cdn.kadxin.net dsp.kadam.net go.kadxin.net hk-go.kadxin.net hk.kadam.net impr.kadxin.net media.kadxin.net us1impr.kadxin.net us2impr.kadxin.net".

Deleted line 2141,"Adways SAS","http://www.adways.com/privacy/","adways-v2-users-resources.s3.amazonaws.com analytics.adpaths.com analytics.adways.com assets.adpaths.com contents.adpaths.com hv-contents.adpaths.com play.adpaths.com publication.adpaths.com vast.adpaths.com videos.adpaths.com www.adwstats.com".

Deleted line 2467,"Phaistos Networks","http://adman.gr/gdpr","adman.gr bold.adman.gr ibv.adman.gr obj.adman.gr sherlock.adman.gr static.adman.gr talos.adman.gr watson.adman.gr".

Deleted line 2649,"Seenthis","https://seenthis.co/privacy-notice-2018-04-18.pdf","npv-cdn.seenthis.se seenthis.se t.seenthis.se video.seenthis.se".

Deleted line 2971,"Brand Metrics","https://collector.brandmetrics.com/brandmetrics_privacypolicy.pdf","collector.brandmetrics.com".

Deleted line 3057,"Lean Digital Media","https://www.contentignite.com/gdpr/","api.tagdeliver.com cdn.tagdeliver.com".

Oct 22, 2020

What's New in RTB Proto version 188

Added BidRequest.page_visibility.

The visibility state of the web page containing the ad slot. See Page Visibility W3C Recommendation.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.58

Added BidRequest.site.ext.page_visibility.

The visibility state of the web page containing the ad slot. Equivalent to BidRequest.page_visibility in the Google protocol. See Page Visibility W3C Recommendation.

Oct 09, 2020

What's New in RTB Proto version 187

Added BidRequest.is_semi_transparent_request.

Indicates that the request is using semi-transparent branding, which means only a truncated version of the request URL will be provided. This decision is made by the publisher, see the Help Center Article for context.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.57

Added BidRequest.site.ext.is_semi_transparent_request.

Indicates that the request is using semi-transparent branding. Equivalent to BidRequest.is_semi_transparent_request in the Google protocol, see the Help Center Article for context.

September 30, 2020

What's New in RTB Proto version 186

Removed BidResponse.ad.bidder_name.

This field has been deprecated due to being unused.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.56

Removed Bid.ext.bidder_name and OpenRtbAdx.bid_extension.bidder_name.

These fields have been deprecated due to being unused.

September 29, 2020

What's New in RTB dictionaries

The mobile-os.csv dictionary file has changed.

Added line 630419,"iOS",14,2,-1.

The creative-status-codes.txt dictionary file has changed.

Added 212 The ad is filtered because the bid is for a PG deal with publisher-managed creatives and contains bidder-provided creative information.

Sep 24, 2020

What's New in RTB Proto version 185

Added BidRequest.AdSlot.omidpn.

Identifier of the OM SDK integration. See the OpenRTB Advisory for Open Measurement SDK for more info.

Added BidRequest.AdSlot.omidpv.

Version of the OM SDK integration. See the OpenRTB Advisory for Open Measurement SDK for more info.

Removed the deprecated BidResponse.ad.adslot.use_bid_translation_service.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.55

Added Source.ext.omidpn.

Identifier of the OM SDK integration. Equivalent to BidRequest.AdSlot.omidpn in the Google protocol. See the OpenRTB Advisory for Open Measurement SDK for more info.

Added Source.ext.omidpv.

Version of the OM SDK integration. Equivalent to BidRequest.AdSlot.omidpv in the Google protocol. See the OpenRTB Advisory for Open Measurement SDK for more info.

Removed the deprecated Bid.ext.use_bid_translation_service.

What's New in RTB dictionaries

The geo-table.csv dictionary file has changed.

Several entries were added and several more deleted.

The providers.csv dictionary file has changed.

9 providers added; 9 deleted.

September 21, 2020

What's New in RTB Proto version 184

Removed BidRequest.matching_ad_data.direct_deal.must_bid_level

This field has been deprecated in favor BidRequest.matching_ad_data.direct_deal.must_bid for several months and is no longer filled. In this version we remove the deprecated field from the protocol buffer in order improve clarity of the API.

Added BidResponse.no_bid_reason.

This is an optional, bidder-specified reason for not submitting a bid. This field is equivalent to BidResponse.nbr in the OpenRTB protocol and uses the same namespace of no-bid reason codes. See https://developers.google.com/authorized-buyers/rtb/downloads/no-bid-reasons.txt for the full set of no-bid reason codes.

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

Added 19 new providers.

Deleted line 209,"Flashtalking","http://www.flashtalking.com/first-party-ad-serving/","3.base.de blau.de cdn.spongecell.com flashtalking.com ftadsrv.com in.ftadsrv.com o2-freikarte.de o2online.de portal.base.de portal.o2online.de poweredby.firstchoice.co.uk poweredby.thomson.co.uk poweredby.tui.co.uk servedby.o2.co.uk spongecdn.com spongecell.com vast.spongecell.com".

Deleted line 2770,"Thomann GmbH","https://www.thomann.de/de/compinfo_privacy.html","athumbs.thomann.de thomann.de".

Sep 9, 2020

What's New in RTB Proto version 183

Documentation fixes.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.54

Documentation fixes.

Aug 31, 2020

What's New in RTB Proto version 182

Added BidRequest.AdSlot.MatchingAdData.DirectDeal.creative_source.

This is experimental and subject to change. This field declares the host of the creative and will only be populated for Programmatic Guaranteed deals. Currently, this field should only ever be set to CREATIVE_SOURCE_ADVERTISER. See this help center article for information on bidding on Programmatic Guaranteed deals.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.53

Added Deal.ext.creative_source.

This is experimental and subject to change. This field declares the host of the creative and will only be populated for Programmatic Guaranteed deals. Currently, this field should only ever be set to CREATIVE_SOURCE_ADVERTISER. See this help center article for information on bidding on Programmatic Guaranteed deals.

August 26, 2020

What's New in RTB Proto version 181

Added BidRequest.mobile.skadn

BidRequest.mobile.skadn will contain the Publisher's SKAdNetwork information to support app installation attribution for iOS 14 and later. Apple's SKAdNetwork API helps advertisers measure ad-driven app installation by sending a postback to the ad network after a successful install. Publishers will need to configure supported ad networks in their app's property list (Info.plist) to allow an install to be attributed to the ad impression. See Apple's SKAdNetwork Developer Documentation for more info.

Added BidResponse.ad.skadn

BidResponse.ad.skadn can be used by the Advertiser to send their SKAdNetwork information to support app installation attribution for iOS 14 and later. Ad networks will need to send their network ID and signed advertiser information to allow an install to be attributed to the ad impression. See Apple's SKAdNetwork Developer Documentation for more info.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.52

Added Imp.ext.skadn.

Imp.ext.skadn will contain the Publisher's SKAdNetwork information to support app installation attribution for iOS 14 and later. Apple's SKAdNetwork API helps advertisers measure ad-driven app installation by sending a postback to the ad network after a successful install. Publishers will need to configure supported ad networks in their app's property list (Info.plist) to allow an install to be attributed to the ad impression. See Apple's SKAdNetwork Developer Documentation for more info.

Added Bid.ext.skadn

Bid.ext.skadn can be used by the Advertiser to send their SKAdNetwork information to support app installation attribution for iOS 14 and later. Ad networks will need to send their network ID and signed advertiser information to allow an install to be attributed to the ad impression. See Apple's SKAdNetwork Developer Documentation for more info.

What's New in RTB dictionaries

The publisher-verticals.txt dictionary file has changed.

Many Canadian and Indian postal codes were added.

August 18, 2020

What's New in RTB dictionaries

The ad-sensitive-categories.txt dictionary file has changed.

Added 31 References to Sex.

Deleted 31 References to Sex & Sexuality.

The callout-status-codes.txt dictionary file has changed.

Added 34 Filtered due to LGPD eligibility..

The providers.csv dictionary filke has changed.

Several lines were added and deleted.

August 10, 2020

What's New in RTB dictionaries

The geo-table.csv dictionary file has changed.

Several new Canadian and U.S. postal codes were added.

August 6, 2020

What's New in RTB Proto version 180

Added BidRequest.adslot.regs_lgpd

BidRequest.adslot.regs_lgpd is set to true when, based on information available to Google, this impression will serve to a user in Brazil. See the Help Center article for more information on LGPD.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.51

Added Regs.ext.lgpd.

Regs.ext.lgpd is set to true when, based on information available to Google, this impression will serve to a user in Brazil. See the Help Center article for more information on LGPD.

July 31, 2020

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

Added line 1178,"YOC","https://yoc.com/privacy/","ads.mo.yoc-adserver.com".

Added line 2945,"SunMedia","https://www.sunmedia.tv/en/legal","creatives.sunmedia.tv display.sunmedia.tv inline.sunmedia.tv services.sunmedia.tv static.sunmedia.tv track.sunmedia.tv vast.sunmedia.tv vod.sunmedia.tv vpaid.sunmedia.tv".

Added line 3036,"Discover-Tech LTD","http://discover-tech.io/dsp-privacy-policy/","mtrtb.com mydsp.io tracker.mtrtb.com".

Added line 3163,"Reset Digital","http://www.resetdigital.co/privacy-policy/","ads.resetdigital.co ads.resetsrv.com ads.vhsrv.com assets.resetdigital.co assets.resetsrv.com assets.vhsrv.com creatives.resetdigital.co creatives.resetsrv.com creatives.vhsrv.com data.resetdigital.co ds.resetdigital.co ibv.vhsrv.com meta.resetdigital.co resetdigital.co resetsrv.com vhsrv.com".

Deleted line 1178,"YOC Performance Network","","ads.mo.yoc-adserver.com".

Deleted line 3036,"MarketDSP","https://advertising.market.com/dsp-privacy-policy/","mtrtb.com mydsp.io tracker.mtrtb.com".

The geo-table.csv dictionary file has changed.

Several new entries were added.

July 24, 2020

What's New in RTB Proto version 179

Removed the fully deprecated BidRequest.adslot.matching_ad_data.pricing_rule, BidRequest.adslot.matching_ad_data.direct_deal.remaining_impressions_to_buy, BidRequest.adslot.native_ad_template.store_max_safe_length and BidResponse.ad.native_ad.store fields.

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

Added line 505,"Undertone","https://www.undertone.com/privacy/","ads.undertone.com c1.undertonevideo.com cdn.undertone.com creative-p.undertone.com evt.undertone.com prg.undertone.com rt.legolas-media.com sparkflow.net usr.undertone.com".

Added line 2059,"UnrulyX","https://www.rhythmone.com/landing/gdpr","1rx.io acp.1rx.io cdnacp.rhythmone.com cloud-video.unrulymedia.com cloud.video.unrulymedia.com emea.r1-cdn.net gwallet.com i.r1-cdn.net pixel.unruly.systems pre-usermatch.targeting.unrulymedia.com stats3.unrulymedia.com sync.1rx.io targaryen.unrulymedia.com targeting.unrulymedia.com unrulymedia.com usermatch.targeting.unrulymedia.com vast.unruly.systems video.unrulymedia.com vpaid.unruly.systems".

Added line 3005,"Dativa","https://www.dativa.com/privacy/","dev.pix.pub pix.pub pixels.dativa.com pixels1.dativa.com pixels10.dativa.com staging.pix.pub".

Added line 3031,"1plusX","https://www.1plusx.com/privacy-policy/","tagger.opecloud.com".

Added line 3162,"IronNet Cybersecurity","https://ironnet.com/privacy-statement/","detect-prod-ingest.highdegree.io detect-test-ingest.highdegree.io sensor-test.highdegree.io sensor.highdegree.io".

Added line 3169,"Adsolutions BV","https://www.adsolutions.com/privacy-policy/","cdnservices.net".

Added line 3171,"Audigent","https://audigent.com/privacypolicy/","a.ad.gt a.dev.ad.gt a.stage.ad.gt ids.ad.gt ids.dev.ad.gt ids.stage.ad.gt p.ad.gt p.dev.ad.gt p.stage.ad.gt pixels.ad.gt pixels.dev.ad.gt pixels.stage.ad.gt seg.ad.gt seg.dev.ad.gt seg.stage.ad.gt".

Deleted line 505,"Undertone","https://www.undertone.com/privacy/","ads.undertone.com c1.undertonevideo.com cdn.undertone.com prg.undertone.com rt.legolas-media.com sparkflow.net".

Deleted line 510,"UnrulyX","https://unruly.co/privacy","cloud-video.unrulymedia.com cloud.video.unrulymedia.com pixel.unruly.systems pre-usermatch.targeting.unrulymedia.com stats3.unrulymedia.com targaryen.unrulymedia.com targeting.unrulymedia.com unrulymedia.com usermatch.targeting.unrulymedia.com vast.unruly.systems video.unrulymedia.com vpaid.unruly.systems".

Deleted line 1031,"Twitter","","api-dev.tapcommerce.com api.tapcommerce.com cr.tellaparts.com cr0.tellaparts.com cr1.tellaparts.com cr2.tellaparts.com cr3.tellaparts.com cr4.tellaparts.com cr5.tellaparts.com cr6.tellaparts.com cr7.tellaparts.com cr8.tellaparts.com cr9.tellaparts.com media.snappytv.com static.tellaparts.com tellapart.com tellaparts.com".

Deleted line 1934,"Sodel Software Solutions Pvt. Ltd.","http://www.audience73.com/privacy.html","ad.audience73.com audience73.com cdn.audience73.com console.audience73.com pixel.audience73.com rtb-asia.audience73.com tg.audience73.com".

Deleted line 2059,"RhythmOne LLC","https://www.rhythmone.com/landing/gdpr","1rx.io acp.1rx.io cdnacp.rhythmone.com emea.r1-cdn.net gwallet.com i.r1-cdn.net sync.1rx.io".

Deleted line 2558,"Alphonso TV","","alphonso.tv".

Deleted line 2664,"Adclouds","https://adclouds.io/data-gdpr/","adclouds.io cdn-dispatch.adclouds.io cdn.adclouds.io dispatch.adclouds.io".

Deleted line 3005,"Dativa","https://www.dativa.com/privacy/","pixels.dativa.com pixels1.dativa.com pixels10.dativa.com".

Deleted line 3031,"1plusX","https://tagger.opecloud.com/goldbach/privacy-policy.html","tagger.opecloud.com".

July 23, 2020

What's New in RTB Proto version 178

Added BidRequest.session_id.

BidRequest.session_id is available as a beta feature for frequency capping on CTV/OTT platforms.

What's New in OpenRTB Protos

Google OpenRTB extensions protocol v.50

Added Device.ext.session_id.

Device.ext.session_id is available as a beta feature for frequency capping on CTV/OTT platforms.

July 18, 2020

What's New in RTB Proto version 177

Renamed BidRequest.adslot.matching_ad_data.direct_deal.must_bid_level as deprecated.

Renaming the field must_bid_level to be DEPRECATED_must_bid_level. This field has been tagged as deprecated in favor of must_bid and only been set to the default for several months.

July 16, 2020

What's New in RTB dictionaries

The providers.csv dictionary file has changed.

Added line 65,"Hybrid Theory","https://www.hybridtheory.com/privacy-policy","ad.go.affec.tv bid.go.affec.tv cdn.go.affec.tv go.affec.tv sad.go.affect.tv".

Added line 510,"UnrulyX","https://unruly.co/privacy","cloud-video.unrulymedia.com cloud.video.unrulymedia.com pixel.unruly.systems pre-usermatch.targeting.unrulymedia.com stats3.unrulymedia.com targaryen.unrulymedia.com targeting.unrulymedia.com unrulymedia.com usermatch.targeting.unrulymedia.com vast.unruly.systems video.unrulymedia.com vpaid.unruly.systems".

Added line 2467,"Phaistos Networks","http://adman.gr/gdpr","adman.gr bold.adman.gr ibv.adman.gr obj.adman.gr sherlock.adman.gr static.adman.gr talos.adman.gr watson.adman.gr".

Added line 2791,"Swaven","http://www.swaven.com/cookie-policy/","content.static-swaven.com eu-west-1-wtb-api-bt.swaven.com eu-west-1-wtb-api3-bt.swaven.com eu-west-1-wtb-tag-api.swaven.com img.static-swaven.com secure-content.static-swaven.com trk2-bt.swaven.com trk2-bt2.swaven.com trk2-vt.swaven.com trk2-vt2.swaven.com widgets.swaven.com".

Added line 2904,"Good-Loop","https://doc.good-loop.com/policy/privacy-policy.html","ads.good-loop.com as.good-loop.com lg.good-loop.com media.good-loop.com test.good-loop.com vid.good-loop.com".

Added line 3024,"Method Media Intelligence","https://www.methodmi.com/gdpr","bidsimulator.com files.bidsimulator.com go.bidsimulator.com ingeniouspics.com list.bidsimulator swap.bidsimulator view.bidsimulator.com".

Added line 3130,"Target RTB","http://new-programmatic.com/privacy.htm","ad.new-programmatic.com dsp.new-programmatic.com match.new-programmatic.com media.new-programmatic.com new-programmatic.com video.new-programmatic.com".

Added line 3166,"bam! Interactive marketing GmbH","https://bam-interactive.de/privacy-policy/","adtron.io cdn-2.wow-ads.de cdn-3.wow-ads.de cdn-4.wow-ads.de cdn-video.wow-ads.de cdn.wow-ads.de intrack.bam-interactive.de intrack.wow-ads.de intrackv2.bam-interactive.de intrackv2.wow-ads.de vpaid.wow-ads.de".

Deleted line 65,"Affec.tv","","ad.go.affec.tv bid.go.affec.tv cdn.go.affec.tv go.affec.tv sad.go.affect.tv".

Deleted line 510,"Unruly Group Limited","https://unruly.co/privacy","cloud-video.unrulymedia.com cloud.video.unrulymedia.com pixel.unruly.systems pre-usermatch.targeting.unrulymedia.com stats3.unrulymedia.com targaryen.unrulymedia.com targeting.unrulymedia.com unrulymedia.com usermatch.targeting.unrulymedia.com vast.unruly.systems video.unrulymedia.com vpaid.unruly.systems".

Deleted line 1075,"Reklamport","","ad.reklamport.com res.reklamport.com".

Deleted line 2467,"Phaistos Networks","http://adman.gr/gdpr","adman.gr bold.adman.gr ibv.adman.gr obj.adman.gr static.adman.gr talos.adman.gr".

Deleted line 2791,"Swaven","http://www.swaven.com/cookie-policy/","content.static-swaven.com eu-west-1-wtb-api-bt.swaven.com eu-west-1-wtb-api3-bt.swaven.com eu-west-1-wtb-tag-api.swaven.com secure-content.static-swaven.com trk2-bt.swaven.com trk2-bt2.swaven.com trk2-vt.swaven.com trk2-vt2.swaven.com widgets.swaven.com".

Deleted line 2904,"Good-Loop","https://doc.good-loop.com/policy/privacy-policy.html","as.good-loop.com lg.good-loop.com media.good-loop.com test.good-loop.com vid.good-loop.com".

Deleted line 3024,"Method Media Intelligence","https://www.methodmi.com/gdpr","bidsimulator.com files.bidsimulator.com go.bidsimulator.com ingeniouspics.com view.bidsimulator.com".

Deleted line 3166,"bam! Interactive marketing GmbH","https://bam-interactive.de/privacy-policy/","adtron.io cdn-2.wow-ads.de cdn-3.wow-ads.de cdn-4.wow-ads.de cdn-video.wow-ads.de cdn.wow-ads.de intrack.bam-interactive.de intrack.wow-ads.de intrackv2.bam-interactive.de intrackv2.wow-ads.de".