Dec 17, 2019
What's New in RTB Proto version 170
- Added
BidRequest.AdSlot.MatchingAdData.DirectDeal.must_bid
. - This new field will be set to true for PG deals when the buyer is required to bid. Bidders are only allowed to skip bidding on the PG deal for this impression if this value is set to false. See this help center article for information on bidding on Programmatic Guaranteed deals.
- Deprecated
BidRequest.AdSlot.MatchingAdData.DirectDeal.must_bid_level
. - This field is marked as deprecated in favor of the must_bid field added in this release. We will continue to populate this until the end of Q1 2020, at which point this field will be removed from the protocol entirely.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.44
- Added
DealExt.must_bid
. - Added
- This new field will be set to true for PG deals when the buyer is required to bid. Bidders are only allowed to skip bidding on the PG deal for this impression if this value is set to false. See this help center article for information on bidding on Programmatic Guaranteed deals.
Dec 5, 2019
What's New in RTB Proto version 169
- Added
BidRequest.AdSlot.OpenBidding.is_open_bidding
. - This new field will be set to true on bid requests where the publisher set up a yield group or a mediation group that targets the adslot on the request and bidder receiving the request. See this help center article for information on Open Bidding and its effects on the bidding process.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.43
- Added
ImpExt.OpenBidding.is_open_bidding
. - Added
- This new field will be set to true on bid requests where the publisher set up a yield group or a mediation group that targets the adslot on the request and bidder receiving the request. See this help center article for information on Open Bidding and its effects on the bidding process.
- Added
DealExt.publisher_blocks_overridden
. - This field indicates whether the publisher has exempted the corresponding deal from configured blocks. This setting does not override AdX policies or Ad Review Center decisions. See this help center article for more information.
November 21, 2019
What's New in RTB dictionaries
- The
providers.csv
dictionary file has changed.
Nov 14, 2019
What's New in RTB Proto version 168
- Added
BidRequest.bid_response_feedback.sampled_mediation_cpm_ahead_of_auction_winner
. - If there are other networks in the mediation chain, the value of this field is a price representing a sample bid from one of the eligible mediation networks that were higher than the auction winner, weighted by expected fill rate. This will be set to 0 if none of the networks in the mediation chain fill, or if the publisher does not use SDK mediation. See Build a bidding model for first-price auctions for information.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.42
- Added
BidRequestExt.bid_feedback.sampled_mediation_cpm_ahead_of_auction_winner
. - Added
- If there are other networks in the mediation chain, the value of this field is a price representing a sample bid from one of the eligible mediation networks that were higher than the auction winner, weighted by expected fill rate. This will be set to 0 if none of the networks in the mediation chain fill, or if the publisher does not use SDK mediation. See Build a bidding model for first-price auctions for information.
November 13, 2019
What's New in RTB dictionaries
- The
providers.csv
dictionary file has changed.
November 12, 2019
What's New in RTB dictionaries
- The
callout-status-codes.txt
dictionary file has changed. - Deleted
22 Dropped due to pretargeting sampling
.
November 05, 2019
What's New in RTB dictionaries
- The
cookie-matcher-status-codes.txt
dictionary file has changed. - Added
13 COOKIE_MATCHER_UIS_RPC_ERROR
.
Oct 17, 2019
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.41
- Added
BidExt.buyer_reporting_id
. - Added
- Buyer declared ID which will be used to break down spend and invalid traffic metrics in IVT
transparency reporting in Query Tool. We currently also break down metrics in IVT transparency
reporting based on the value declared in the
Seatbid.seat
field (only ifBidExt.buyer_reporting_id
is not populated), but we will stop doing so at the end of Q1, 2020, allowing sufficient time for bidders to migrate to this new field.
Oct 1, 2019
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.40
- Added
DealExt.deal_type
. - Added
- We now send a Google-specific deal type in the OpenRTB Deal extension.
Sep 23, 2019
What's New in RTB Proto version 167
- Added clarification comments about currency to all cpm fields.
Sep 16, 2019
What's New in RTB Proto version 166
- The
OMID
value of theBidResponse.Ad.ImpressionTrackingResource.Context
enum is not currently supported. - We do not currently process OMID scripts submitted through the
impression_tracking_resource
field.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.39
- The
OMID
value of theEventTrackerExt.Context
enum is not currently supported. - The
- We do not currently process OMID scripts submitted through the native
eventtrackers
field.
Sep 13, 2019
What's New in RTB Proto version 165
- Added
BidResponse.ad.adslot.third_party_buyer_token
. - This token used to identify end third party buyer information if an exchange as an open bidder is an intermediary. This is obtained from the third party buyer and must be passed to Google unaltered in the bid response.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.38
- Added
BidExt.third_party_buyer_token
. - Added
- This token used to identify end third party buyer information if an exchange as an open bidder is an intermediary. This is obtained from the third party buyer and must be passed to Google unaltered in the bid response.
Aug 21, 2019
What's New in Cookie Bulk Upload Proto version 8
- Added new enum value
RIDA
,AFAI
andMSAI
toUserIdType
.
Jul 29, 2019
What's New in RTB Proto version 164
- Added
BidRequest.AdSlot.flexible_adslot_settings
. - This submessage is used to indicate settings related to how the size of the adslot can change.
For example, if a range of sizes is allowed to be returned from the bidder, the max and min
height and width will be specified here.
For OpenRTB, flexible height and width are also specified through the
BidRequest.Imp.Banner
message'swmax
,hmax
,wmin
, andhmin
attributes.
Jul 10, 2019
What's New in RTB Proto version 163
- Deprecated and removed
BidRequest.AdSlot.is_intersitial_slot
. - This field is obsolete and no longer populated. Use
BidRequest.Mobile.is_interstitial_request
and theBidRequest.Video.Placement
INTERSTITIAL
enum value to determine whether the adslot is interstitial.
Jul 9, 2019
What's New in Snippet Status Report Proto version 29
- Removed the deprecated
SSL_REQUEST
value from theContextType
enum.
Mar 13, 2019
What's New in Google RTB Proto version 162 and the OpenRTB protos
- We've recently announced an upcoming change to our pricing model. The following new fields are related to this change:
-
- Added
BidRequest.bid_response_feedback.minimum_bid_to_win
to realtime-bidding.proto, andBidRequestExt.bid_feedback.minimum_bid_to_win
to openrtb-adx.proto. - This field is only populated for first-price auctions, and indicates the
minimum bid needed to clear floors and outbid all competitors. This is
excluded for all bidders in auctions won through a deal, where a new
LOST_TO_PMP_DEAL
creative status will indicate if you lost for this reason. - Added
BidResponse.ad.adslot.use_bid_translation_service
to realtime-bidding.proto andBidExt.use_bid_translation_service
to openrtb-adx.proto. - An optional boolean allowing first-price auction bids to opt-in for the bid translation service. If true, the provided second-price bid will be converted to a first-price bid. In practice, enabling this will never raise your bid. This service is being temporarily offered to assist with migration, and is planned to be removed in 2020.
- Added
- Bidders are encouraged to update their bidding implementation in preparation for this change.
- Added support for the following macros in
adm
,impression_tracking_url
, andburl
: -
${AUCTION_ID}
- ID of the bid request; fromBidRequest.id
attribute.${AUCTION_BID_ID}
- ID of the bid; fromBidResponse.bidid
attribute.${AUCTION_IMP_ID}
- ID of the impression just won; fromBidRequest.imp[].id
attribute.${AUCTION_SEAT_ID}
- ID of the bidder seat for whom the bid was made; fromBidResponse.seatbid[].seat
attribute.${AUCTION_AD_ID}
- ID of the ad markup the bidder wants to serve; fromBidResponse.seatbid[].bid[].adid
attribute.${AUCTION_PRICE}
- Clearing price using the same currency and units as the bid.
- Removed
gdn-vendors.txt
dictionary file. - Use
vendors.txt
instead. Download file.
Dec 10, 2018
What's New in Cookie Bulk UPload Proto version 8
- Removed enum value
BUYER_PROVIDED_ID
toUserIdType
.
Dec 10, 2018
What's New in RTB Proto version 161
- Updated comments for the
BidRequest.Adslot.width
andBidRequest.Adslot.height
. - Updated comments to reflect that the first interstitial width/height slot is no longer necessarily the same as the screen size, as some interstitial ads may be slightly smaller than screen size.
- Deprecated
NativeAdTemplate.Fields.STORE
andNativeAdTemplate.store_max_safe_length
.
Nov 16, 2018
What's New in RTB Proto version 160
- Added
BidResponse.Ad.AdSlot.buyer_reporting_id
. - Bidders can use this field to specify an ID of their choosing, which will be used to breakdown spend and invalid traffic metrics in IVT transparency reporting. IDs longer than 64 bytes will be ignored.
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- Bidders can now use
SeatBid.seat
to specify an ID of their choosing, which will be used to breakdown spend and invalid traffic metrics in IVT transparency reporting. IDs longer than 64 bytes will be ignored.
Oct 29, 2018
What's New in RTB Proto version 159
- Added
BidRequest.auction_type
. - This field is analogous to BidRequest.at, already sent in OpenRTB.
Oct 22, 2018
What's New in RTB Proto version 158
- Added
BidRequest.AdSlot.excluded_creatives
. - The field contains a list of creatives that are disallowed to serve on this impression. Contact your account manager if you would like to enable this feature.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.36
- Added
ImpExt.excluded_creatives
. - Added
- The field contains a list of creatives that are disallowed to serve on this impression. Contact your account manager if you would like to enable this feature.
Oct 17, 2018
What's New in RTB Proto version 157
- Added support for set top box in
BidRequest.Device.device_type
. BidRequest.Device.device_type
can contain a new set top box type.
Oct 19, 2018
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.35
- Added
BidExt.billing_id
. - Added
- We are migrating away from the use of
Bid.cid
for specifying in a bid response which billing ID an impression should be attributed to, and migrating to this newBidExt.billing_id
field. We will continue to fall back on consumingBid.cid
for backward compatibility until bidders have migrated.
Oct 17, 2018
What's New in RTB Proto version 157
- Added support for set top box in
BidRequest.Device.device_type
. BidRequest.Device.device_type
can contain a new set top box type.
Oct 8, 2018
What's New in RTB Proto version 155
- Added support for Samsung device id in
BidRequest.Mobile.advertising_id
. - Samsung id can be sent out through
BidRequest.Mobile.advertising_id
.
Oct 1, 2018
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.33
- Added
BidExt.restricted_categories
. - Added
- This field should be used to specify the restricted categories for the ads that may be shown from the corresponding snippet. See ad-restricted-categories.txt for a list of restricted category IDs. In particular, declaration of attribute 33 is required for ads for alcohol to avoid creative disapproval.
- Google OpenRTB protocol 2.5.0
App.storeurl
is now populated on applicable requests.
What's New in Reporting
- Deprecated CSV Performance Report.
- The hourly CSV download of performance report data has been deprecated. Performance report data is still available through the Performance Report API.
Sep 20, 2018
What's New in RTB Proto version 153
- Added
BidRequest.google_query_id
. - This represents a unique ID for the overall query. In the event that there are multiple
callouts for a query, all callout requests for that query will contain the same
google_query_id
.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.32
- Added
BidRequestExt.google_query_id
. - Added
- This represents a unique ID for the overall query. In the event that there are multiple
callouts for a query, all callout requests for that query will contain the same
google_query_id
.
Sep 18, 2018
What's New in Snippet Status Report Proto version 28
- Added new disapproval reason.
- 100 Promotes services related to bail bonds.
Aug 27, 2018
What's New in Snippet Status Report Proto version 27
- Added new disapproval reason.
- 99 Temporary pausing of creative.
Aug 23, 2018
What's New in RTB Proto version 153
- Added
BidRequest.adslot.native_placement_type
. - This message describes placement of native ad slot with respect to surrounding context.
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
NativeRequest.plcmttype
is now populated with the same data as theBidRequest.adslot.native_placement_type
field in the AdX protocol.
Aug 1, 2018
What's New in RTB Proto version 152
- Added
BidRequest.Mobile.installed_sdk
. - This message allows a bidder to know about the SDK installed on the app that they are allowed to bid into.
Jul 30, 2018
What's New in Snippet Status Report Proto version 26
- Added new field
creative_status_identity_type
for the migration to sizeless creative verification.
July 23, 2018
What's New in RTB dictionaries
- The
providers.csv
dictionary file has changed. - Updated the entries for "Integral Ad Science", "Google", "EMX Digital",
"KeyCDN", "Better Banners", "zeotap", and "Tramplin Media".
- Removed the entry for "Clearstream.TV, Inc."
July 19, 2018
What's New in RTB Proto version 150
- Added a new exchange deal type to
BidResponse.Ad.AdSlot.exchange_deal_type
. - The new
EXCHANGE_AUCTION_PACKAGE
deal type for exchange bidders represents a bundle of inventory with no special treatment in the auction.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.31
- Added a new exchange deal type to
BidExt.exchange_deal_type
. - Added a new exchange deal type to
- The new
EXCHANGE_AUCTION_PACKAGE
deal type for exchange bidders represents a bundle of inventory with no special treatment in the auction.
July 17, 2018
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Added 3 cities in Argentina.
- Added 3 cities in Canada.
- Added 2 cities in Colombia.
- Added 2 cities in Greece.
- Added 26 cities in Italy.
- Added 333 cities in Japan.
- Added 78 cities in Switzerland.
- Added 3 cities in Canada.
July 16, 2018
What's New in RTB dictionaries
- The
providers.csv
dictionary file has changed. - Updated information for existing providers: Adriver, MediaMath, The Reach Group,
GetIntent, DYNADMIC, AdClear, Sharethrough Inc., media.ventive GmbH, Ingenious
Technologies, StreamRail, Adways SAS, BDSK Handels GmbH & Co. KG, Advertserve,
INFINIA, Dochase.
- Added new providers: AT Internet, Media.net, Vidazoo, Madington, IgnitionAI, All In Views LTD, Captify, Seedtag, Affiliate Future, Grabit Interactive, FXCM.com, Rambla, Tramplin Media.
- See the list of certified vendors for more details.
- Added new providers: AT Internet, Media.net, Vidazoo, Madington, IgnitionAI, All In Views LTD, Captify, Seedtag, Affiliate Future, Grabit Interactive, FXCM.com, Rambla, Tramplin Media.
July 02, 2018
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
4513 Rippll
.- See the list of certified vendors for more details.
- The
gdn-vendors.txt
dictionary file has changed. - Added
4513 Rippll
.- See the list of certified vendors for more details.
June 27, 2018
What's New in RTB Proto version 149
- Marked
BidRequest.adslot.matching_ad_data.direct_deal.remaining_impressions_to_buy
as deprecated. - We will no longer be providing this information in an effort to simplify our API.
June 26, 2018
What's New in RTB Proto version 148
- Added
BidRequest.AdSlot.buyer_generated_request_data
. - This will be set on mobile app requests for buyers that have their SDK installed in the app to pass additional information.
- Added
BidResponse.Ad.AdSlot.sdk_rendered_ad
. - This field allows a bidder to return an ad to be rendered by an SDK known to them. This can only be used when the BidRequest includes a mobile.installed_sdk submessage.
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.30
- Added
AppExt.InstalledSdk
. - Added
- This message allows a bidder to know about the SDK installed on the app that they are allowed to bid into.
- Added
ImpExt.BuyerGeneratedRequestData
. - This will be set on mobile app requests for buyers that have their SDK installed in the app to pass additional information.
- Added
BidExt.SdkRenderedAd
. - This field allows a bidder to return an ad to be rendered by an SDK known to them. This can
only be used when the BidRequest includes a
AppExt.InstalledSdk
submessage.
- Added support for
NativeRequest.eventtrackers
. - Specifies what type of event tracking is supported. Maps to the Authorized
Buyers Protocol's
BidRequest.adslot[].excluded_attribute
field submessage.
- Added support for
NativeResponse.eventtrackers
. - Array of response event trackers to run with the ad, in response to the declared supported
methods in the NativeRequest. Replaces imptrackers and jstrackers. Maps to
the Authorized Buyers Protocol's
BidResponse.ad[].impression_tracking_resource
.
June 26, 2018
What's New in RTB dictionaries
- The
publisher-excludable-creative-attributes.txt
dictionary file has changed. - Added
114 OmsdkType: OMSDK 1.0
, which is used to indicate whether the Open Measurement SDK is supported.
June 13, 2018
What's New in RTB Proto version 147
- Added the enum value
AUCTION_PACKAGE
toBidRequest.adslot.matching_ad_data.direct_deal.deal_type
. - We now use the
AUCTION_PACKAGE
enum value (as opposed to the previously usedPRIVATE_AUCTION
) to indicate that an Auction Packagedirect_deal_id
is present in thedirect_deal
.
June 11, 2018
What's New in RTB Proto version 146
- Added
BidRequest.AdSlot.ImpressionTrackingResource.verification_parameters
andBidRequest.AdSlot.ImpressionTrackingResource.vendor_key
. verification_parameters
can be populated with additional parameters to be passed to the OMID verification script set inImpressionTrackingResource.script_url
.vendor_key
should be populated with the unique identifier of the OMID script vendor. The contents of these new fields will be passed to the Open Measurement SDK whenImpressionTrackingResource.context
is set toOMID
.
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.29
- Added
EventTrackerExt.verification_parameters
andEventTrackerExt.vendor_key
.verification_parameters
can be populated with additional parameters to be passed to the OMID verification script set inEventTracker.url
.vendor_key
should be populated with the unique identifier of the OMID script vendor. The contents of these new fields will be passed to the Open Measurement SDK whenEventTrackerExt.context
is set toOMID
. - Google OpenRTB protocol 2.5.0
User.buyeruid
is now populated with the same contents asUser.customdata
. We will eventually deprecate populatingUser.customdata
altogether.
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
263 AddThis, Inc
.- See the list of certified vendors for more details.
June 07, 2018
What's New in RTB dictionaries
- The
gdn-vendors.txt
dictionary file has changed. - Deleted
10 Tumri
.- Deleted
56 Adobe Media Optimizer
.- Deleted
132 Adobe Media Optimizer
.- Deleted
225 ZANOX AG
.- Deleted
233 Xaxis, Inc
.- Deleted
260 Alenty S.A.S
.- Deleted
432 Hi-Media
.- Deleted
497 Exactag
.- Deleted
815 Resonate Networks, Inc
.- Deleted
874 Cint AB
.- Deleted
886 Research and Analysis of Media in Sweden AB
.- Deleted
888 ViewersLogic LTD
.- Deleted
4362 Adnami ApS
.- See the list of certified vendors for more details.
- Deleted
- The
vendors.txt
dictionary file has changed. - Deleted
10 Tumri
.- Deleted
56 Adobe Media Optimizer
.- Deleted
132 Adobe Media Optimizer
.- Deleted
225 ZANOX AG
.- Deleted
233 Xaxis, Inc
.- Deleted
260 Alenty S.A.S
.- Deleted
432 Hi-Media
.- Deleted
497 Exactag
.- Deleted
616 Tealium, Inc
.- Deleted
814 Media Detect GmbH
.- Deleted
815 Resonate Networks, Inc
.- Deleted
864 INCUBIQ Solutions Ltd
.- Deleted
874 Cint AB
.- Deleted
886 Research and Analysis of Media in Sweden AB
.- Deleted
888 ViewersLogic LTD
.- Deleted
4362 Adnami ApS
.- See the list of certified vendors for more details.
- Deleted
June 04, 2018
What's New in RTB dictionaries
- The
publisher-verticals.txt
dictionary file has changed. - Changed line
5227 /World Localities/Latin America/South America/Brazil/Southeast Brazil/São Paulo (State)
. - The
creative-status-codes.txt
dictionary file has changed. - Added
193 Filtered due to missing SDK identifier
.- Added
194 Filtered due to missing SDK rendering data
. - Added
May 31, 2018
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
4483 ComScore vCE (YouTube)
.- Added
4484 Campaign Monitor (YouTube)
.- See the list of certified vendors for more details.
- Added
- The
gdn-vendors.txt
dictionary file has changed. - Added
4483 ComScore vCE (YouTube)
.- Added
4484 Campaign Monitor (YouTube)
.- See the list of certified vendors for more details.
- Added
May 21, 2018
What's New in RTB dictionaries
- The
providers.csv
dictionary file has changed. - Updated to include the latest domain information for all providers.
May 18, 2018
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Deleted
284 Research Now Limited
.- See the list of certified vendors for more details.
- The
gdn-vendors.txt
dictionary file has changed. - Deleted
284 Research Now Limited
.- See the list of certified vendors for more details.
May 17, 2018
What's New in Snippet Status Report Proto version 25
- Added new disapproval reasons.
- 97 Unsupported language.
- 98 Non-SSL compliant.
What's New in RTB dictionaries
- The
gdn-vendors.txt
dictionary file has changed. - Added
4374 TailTarget
.- See the list of certified vendors for more details.
- The
vendors.txt
dictionary file has changed. - Added
4374 TailTarget
.- Added
4458 Yieldlab
.- Added
4461 Sharethrough
.- See the list of certified vendors for more details.
- Added
May 16, 2018
What's New in RTB dictionaries
- The
gdn-vendors.txt
dictionary file has changed. - Deleted
4452 Research Now (YouTube)
.- See the list of certified vendors for more details.
- The
vendors.txt
dictionary file has changed. - Deleted
4452 Research Now (YouTube)
.- See the list of certified vendors for more details.
May 15, 2018
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
4452 Research Now (YouTube)
.- See the list of certified vendors for more details.
- The
gdn-vendors.txt
dictionary file has changed. - Added
4452 Research Now (YouTube)
.- See the list of certified vendors for more details.
May 11, 2018
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Deleted
43 BrightRoll Inc.
.- Deleted
94 Nielsen OBE (Vizu)
.- Deleted
145 DoubleVerify Inc.
.- Deleted
204 Pulpo Media Inc
.- Deleted
303 Dynamic Logic / Safecount (AdIndex)
.- Deleted
316 Flashtalking
.- Deleted
334 Adloox Research Verification
.- Deleted
395 Adnologies GmbH
.- Deleted
441 Hubrus LLC
.- Deleted
472 Neustar AdAdvisor
.- Deleted
476 ComScore Validated Campaign Essentials:Ad Swapping
.- Deleted
539 Adform DSP
.- Deleted
551 Nielsen Digital Ad Ratings
.- Deleted
553 Kpsule
.- Deleted
554 Content Directions, Inc. dba Linkstorm
.- Deleted
569 Contobox
.- Deleted
606 Gruvi Ltd.
.- Deleted
608 Rockabox Media Ltd
.- Deleted
615 Nielsen Digital Ad Ratings (JS)
.- Deleted
618 Demand Side Science, Inc.
.- Deleted
633 Knorex Pte. Ltd.
.- Deleted
713 MezzoMedia
.- Deleted
724 Extreme Reach, Inc.
.- Deleted
791 VideoHub DSP
.- Deleted
813 Protected Media LTD
.- Deleted
820 Beijing PinYou Interactive Information Technology
.- Deleted
834 Jivox Corporation
.- Deleted
838 RevJet LLC.
.- Deleted
863 Bonzai Digital Pvt. Ltd
.- Deleted
876 Exponential Interactive, Inc
.- See the list of certified vendors for more details.
- Deleted
- The
gdn-vendors.txt
dictionary file has changed. - Deleted
43 BrightRoll Inc.
.- Deleted
94 Nielsen OBE (Vizu)
.- Deleted
145 DoubleVerify Inc.
.- Deleted
204 Pulpo Media Inc
.- Deleted
303 Dynamic Logic / Safecount (AdIndex)
.- Deleted
334 Adloox Research Verification
.- Deleted
395 Adnologies GmbH
.- Deleted
441 Hubrus LLC
.- Deleted
551 Nielsen Digital Ad Ratings
.- Deleted
553 Kpsule
.- Deleted
554 Content Directions, Inc. dba Linkstorm
.- Deleted
569 Contobox
.- Deleted
606 Gruvi Ltd.
.- Deleted
618 Demand Side Science, Inc.
.- Deleted
713 MezzoMedia
.- Deleted
724 Extreme Reach, Inc.
.- Deleted
813 Protected Media LTD
.- See the list of certified vendors for more details.
- Deleted
May 9, 2018
What's New in RTB dictionaries
- The
providers.csv
dictionary file has changed. - Deleted line
184,"eBay","https://www.ebay.com/help/policies/member-behaviour-policies/user-privacy-notice-privacy-policy?id=4260#section12","rover.ebay.com ebay.cachetastic.com *.ebaystatic.com dap.ebay.gslb.com *.ebay.de *.ebay.co.uk *.ebay.fr *.ebay.it *.ebay.es *.ebayrtm.com *.ebay.at *.ebay.ch *.ebay.be *.ebay.dk *.ebay.gr *.ebay.ie *.ebay.nl *.ebay.no *.ebay.pl *.ebay.cz *.ebay.ru *.ebayimg.com anywhere.ebay.com i.ebayimg.com *.edpn.ebay.com mstconsole.ebay.com rpsx.ebay.com *.ebay.com ads.ebay.com sc.dealtime.com mktg.kijiji.ca *.fetchback.com"
.
May 7, 2018
What's New in Snippet Status Report Proto version 24
- Added new disapproval reasons.
- 96 Unacceptable destination experience.
May 3, 2018
What's New in RTB dictionaries
- The
providers.csv
file has been added. - This file conveys information about providers that are passed in the bid request. See RTB dictionaries for a full description.
- The
gdn-vendors.txt
dictionary file has changed. - Added
303 Insight Express (Mobile)
.- Deleted
303 Dynamic Logic / Safecount (AdIndex)
.- Deleted
523 Spongecell - Expandable
.- See the list of certified vendors for more details.
- Deleted
- The
vendors.txt
dictionary file has changed. - Added
303 Insight Express (Mobile)
.- Deleted
303 Dynamic Logic / Safecount (AdIndex)
.- Deleted
486 Adloox: Ad Swapping
.- Deleted
523 Spongecell - Expandable
.- Deleted
537 Public Eye
.- Deleted
623 Human Demand
.- Deleted
798 Nielsen Catalina Solutions
.- Deleted
806 Sociomantic Expandable
.- See the list of certified vendors for more details.
- Deleted
May 1, 2018
What's New in RTB dictionaries
- The
gdn-vendors.txt
dictionary file has changed. - Changed
43 BrightRoll
to43 BrightRoll Inc.
.- Changed
56 Efficient Frontier
to56 Adobe Media Optimizer
.- Changed
79 Revenue Science
to79 revenue cloud
.- Changed
94 Nielsen OBE (Vizu) - Survey
to94 Nielsen OBE (Vizu)
.- Changed
132 Adlens
to132 Adobe Media Optimizer
.- Changed
144 Campaign Monitor (Integral Ad Science)
to144 Campaign Monitor
.- Changed
145 DoubleVerify
to145 DoubleVerify Inc.
.- Changed
204 Pulpo Media
to204 Pulpo Media Inc
.- Changed
225 Zanox
to225 ZANOX AG
.- Changed
233 Media Innovation Group (Xaxis)
to233 Xaxis, Inc
.- Changed
238 Aggregate Knowledge
to238 Media Intelligence Platform (Aggregate Knowledge)
.- Changed
260 Alenty
to260 Alenty S.A.S
.- Changed
284 Research Now
to284 Research Now Limited
.- Changed
303 Millward Brown Digital - Survey
to303 Dynamic Logic / Safecount (AdIndex)
.- Changed
334 Adloox
to334 Adloox Research Verification
.- Changed
395 Adnologies
to395 Adnologies GmbH
.- Changed
414 Batch Media
to414 Batch Media Gmbh
.- Changed
441 Hubrus
to441 Hubrus LLC
.- Changed
474 Integral Ad Science Firewall - Ad Swapping
to474 Integral Ad Science Firewall
.- Changed
485 comScore - VoiceFive
to485 VoiceFive (ComScore)
.- Changed
489 Revenue Cloud
to489 revenue cloud
.- Changed
550 AdYapper
to550 AdYapper, Inc.
.- Changed
551 Nielsen Digital Ad Ratings (formerly OCR)
to551 Nielsen Digital Ad Ratings
.- Changed
553 Kpsule - Expandable
to553 Kpsule
.- Changed
554 Linkstorm - Expandable
to554 Content Directions, Inc. dba Linkstorm
.- Changed
566 Spark Flow Expandable
to566 Spark Flow S.A.
.- Changed
569 Contobox Expandable
to569 Contobox
.- Changed
606 Gruvi TV
to606 Gruvi Ltd.
.- Changed
618 Demand Side Science
to618 Demand Side Science, Inc.
.- Changed
698 GET IT Mobile
to698 GET IT Mobile, Inc
.- Changed
724 Extreme Reach ad server
to724 Extreme Reach, Inc.
.- Changed
743 White Ops
to743 White Ops, Inc.
.- Changed
767 SFR
to767 SOCIETE FRANCAISE DU RADIOTELEPHONE
.- Changed
776 Spark Flow
to776 Spark Flow S.A.
.- Changed
780 Where 2 Get It
to780 Where 2 Get It, Inc.
.- Changed
785 Scrutineer Survey
to785 Scrutineer
.- Changed
797 ADmantX
to797 ADmantX, SPA
.- Changed
813 Protected Media
to813 Protected Media LTD
.- Changed
815 Resonate Networks
to815 Resonate Networks, Inc
.- Changed
828 Crutchfield New Media
to828 Crutchfield New Media, LLC
.- Changed
874 Cint
to874 Cint AB
.- Changed
886 Research and Analysis of Media
to886 Research and Analysis of Media in Sweden AB
.- Changed
888 ViewersLogic
to888 ViewersLogic LTD
.- See the list of certified vendors for more details.
- Changed
- The
vendors.txt
dictionary file has changed. - Changed
43 BrightRoll
to43 BrightRoll Inc.
.- Changed
56 Efficient Frontier
to56 Adobe Media Optimizer
.- Changed
79 Revenue Science
to79 revenue cloud
.- Changed
94 Nielsen OBE (Vizu) - Survey
to94 Nielsen OBE (Vizu)
.- Changed
132 Adlens
to132 Adobe Media Optimizer
.- Changed
144 Campaign Monitor (Integral Ad Science)
to144 Campaign Monitor
.- Changed
145 DoubleVerify
to145 DoubleVerify Inc.
.- Changed
204 Pulpo Media
to204 Pulpo Media Inc
.- Changed
225 Zanox
to225 ZANOX AG
.- Changed
233 Media Innovation Group (Xaxis)
to233 Xaxis, Inc
.- Changed
238 Aggregate Knowledge
to238 Media Intelligence Platform (Aggregate Knowledge)
.- Changed
242 Lotame
to242 Lotame Solutions Inc.
.- Changed
260 Alenty
to260 Alenty S.A.S
.- Changed
267 DataLogix
to267 DataLogix, Inc.
.- Changed
284 Research Now
to284 Research Now Limited
.- Changed
303 Millward Brown Digital - Survey
to303 Dynamic Logic / Safecount (AdIndex)
.- Changed
316 Flashtalking Expandable
to316 Flashtalking
.- Changed
332 Audience Manager(DemDex)
to332 Audience Manager
.- Changed
334 Adloox
to334 Adloox Research Verification
.- Changed
395 Adnologies
to395 Adnologies GmbH
.- Changed
414 Batch Media
to414 Batch Media Gmbh
.- Changed
441 Hubrus
to441 Hubrus LLC
.- Changed
474 Integral Ad Science Firewall - Ad Swapping
to474 Integral Ad Science Firewall
.- Changed
475 zzzz [ARCHIVED] comScore AdXpose - Ad Blocking
to475 ComScore (AdXpose): Ad Swapping
.- Changed
476 comScore vCE - Ad Swapping
to476 ComScore Validated Campaign Essentials:Ad Swapping
.- Changed
477 DoubleVerify BrandShield - Ad Swapping
to477 ComScore (AdXpose): Ad Swapping
.- Changed
481 eXelate
to481 eXelate Inc.
.- Changed
485 comScore - VoiceFive
to485 VoiceFive (ComScore)
.- Changed
486 AdLoox - Ad Swapping
to486 Adloox: Ad Swapping
.- Changed
489 Revenue Cloud
to489 revenue cloud
.- Changed
490 AdLedge - Ad Blocking
to490 Adledge: Ad Swapping
.- Changed
501 Rutarget
to501 Rutarget / Segmento
.- Changed
529 Eyeota
to529 Eyeota Limited
.- Changed
539 Adform - Expandable
to539 Adform DSP
.- Changed
542 Bizo
to542 Bizo Inc
.- Changed
543 VisualDNA
to543 VisualDNA (Imagini)
.- Changed
550 AdYapper
to550 AdYapper, Inc.
.- Changed
551 Nielsen Digital Ad Ratings (formerly OCR)
to551 Nielsen Digital Ad Ratings
.- Changed
553 Kpsule - Expandable
to553 Kpsule
.- Changed
554 Linkstorm - Expandable
to554 Content Directions, Inc. dba Linkstorm
.- Changed
564 Noddington Technologies Limited (Aidata)
to564 NODDINGTON TECHNOLOGIES LIMITED
.- Changed
566 Spark Flow Expandable
to566 Spark Flow S.A.
.- Changed
569 Contobox Expandable
to569 Contobox
.- Changed
572 Webtrekk
to572 Webtrekk GmbH
.- Changed
573 Fabric Worldwide
to573 Fabric Worldwide Inc
.- Changed
574 Liveramp
to574 LiveRamp, Inc.
.- Changed
575 Krux
to575 Krux Digital, Inc.
.- Changed
577 Ru Target LLC
to577 Rutarget / Segmento
.- Changed
606 Gruvi TV
to606 Gruvi Ltd.
.- Changed
608 Rockabox Media - Expandable
to608 Rockabox Media Ltd
.- Changed
615 Nielsen Digital Ad Ratings (formerly OCR) JS
to615 Nielsen Digital Ad Ratings (JS)
.- Changed
616 Tealium
to616 Tealium, Inc
.- Changed
618 Demand Side Science
to618 Demand Side Science, Inc.
.- Changed
633 Knorex - Expandable
to633 Knorex Pte. Ltd.
.- Changed
698 GET IT Mobile
to698 GET IT Mobile, Inc
.- Changed
724 Extreme Reach ad server
to724 Extreme Reach, Inc.
.- Changed
743 White Ops
to743 White Ops, Inc.
.- Changed
767 SFR
to767 SOCIETE FRANCAISE DU RADIOTELEPHONE
.- Changed
776 Spark Flow
to776 Spark Flow S.A.
.- Changed
780 Where 2 Get It
to780 Where 2 Get It, Inc.
.- Changed
785 Scrutineer Survey
to785 Scrutineer
.- Changed
793 Semasio
to793 Semasio GmbH
.- Changed
797 ADmantX
to797 ADmantX, SPA
.- Changed
808 Hatena
to808 Hatena Co., Ltd
.- Changed
813 Protected Media
to813 Protected Media LTD
.- Changed
814 Media Detect
to814 Media Detect GmbH
.- Changed
815 Resonate Networks
to815 Resonate Networks, Inc
.- Changed
818 Redbranch
to818 Redbranch, Inc. (dba Fraudlogix)
.- Changed
820 iPinyou - Expandable
to820 Beijing PinYou Interactive Information Technology
.- Changed
826 AmberData
to826 AmberData LLC
.- Changed
828 Crutchfield New Media
to828 Crutchfield New Media, LLC
.- Changed
834 Jivox - Expandable
to834 Jivox Corporation
.- Changed
838 Revjet Expandable
to838 RevJet LLC.
.- Changed
863 Bonzai Expandable
to863 Bonzai Digital Pvt. Ltd
.- Changed
864 INCUBIQ Solutions
to864 INCUBIQ Solutions Ltd
.- Changed
874 Cint
to874 Cint AB
.- Changed
876 Exponential Expandable
to876 Exponential Interactive, Inc
.- Changed
884 Nugg.ad
to884 nugg.ad AG
.- Changed
885 Cloud Technologies
to885 OnAudience.com
.- Changed
886 Research and Analysis of Media
to886 Research and Analysis of Media in Sweden AB
.- Changed
888 ViewersLogic
to888 ViewersLogic LTD
.- See the list of certified vendors for more details.
- Changed
April 30, 2018
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
79 Revenue Science
.- Added
138 Reddion
.- Added
475 zzzz [ARCHIVED] comScore AdXpose - Ad Blocking
.- Added
501 Rutarget
.- Added
566 Spark Flow Expandable
.- Deleted
130 Broadband Enterprises
.- Deleted
182 comScore - vCE
.- Deleted
226 DoubleClick Rich Media Expandable
.- Deleted
228 Sizmek Expandable
.- Deleted
229 PointRoll Expandable
.- Deleted
428 Conversant (Mediaplex) Expandable
.- Deleted
520 Flite - Expandable
.- Deleted
538 Weborama Expandable
.- Deleted
549 Predicta - Expandable
.- Deleted
568 Admotion - Expandable
.- Deleted
617 Mixpo - Expandable
.- See the list of certified vendors for more details.
- Added
- The
gdn-vendors.txt
dictionary file has changed. - Added
79 Revenue Science
.- Added
138 Reddion
.- Added
566 Spark Flow Expandable
.- Deleted
130 Broadband Enterprises
.- Deleted
182 comScore - vCE
.- Deleted
226 DoubleClick Rich Media Expandable
.- Deleted
617 Mixpo - Expandable
.- See the list of certified vendors for more details.
- Added
April 26, 2018
What's New in RTB Proto version 145
- Added
BidRequest.AdSlot.session_depth
- This field represents the total number of impressions served to this user (within this specific site or app) in this browsing session, plus 1. A session ends after 30 minutes inactivity. The default value of -1 indicates that the session depth cannot be estimated.
April 25, 2018
What's New in Snippet Status Report Proto version 23
- Added new disapproval reasons.
- 94 Misuse by OMID script
- 95 Non-whitelisted OMID vendor
April 18, 2018
What's New in RTB Proto version 144
BidRequest.AdSlot.ConsentedProvidersSettings.consented_providers
is nowpacked
.- This will ensure the field is more compact on the wire. Be sure to update to this
version, as adding
packed
is not backwards compatible.
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.28
UserExt.ConsentedProvidersSettings.consented_providers
is nowpacked
. This will ensure the field is more compact on the wire. Be sure to update to this version, as addingpacked
is not backwards compatible.
April 17, 2018
What's New in RTB dictionaries
- The
mobile-os.csv
dictionary file has changed. - Added line
630359,"iOS",11,4,-1
. - The
hosted-match-status-codes.txt
dictionary file has changed. - Added
10 HOSTED_MATCH_INTERNAL_ERROR
.
April 16, 2018
What's New in RTB Proto version 143
- Adding
BidRequest.AdSlot.consented_providers_settings
andBidRequest.AdSlot.regs_gdpr
- Adding new fields to indicate user consent for ads personalization providers as passed by publishers for users in the countries within the European Economic Area. providers.csv will be posted at a later date.
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.27
- Adding
UserExt.consented_providers_settings
andRegsExt.gdpr
to indicate user consent for ads personalization providers as passed by publishers for users in the countries within the European Economic Area. providers.csv will be posted at a later date.
April 9, 2018
What's New in RTB Proto version 142
- Added
BidResponse.Ad.impression_tracking_resource
- This field can be used to specify Javascript resources that will be invoked when the impression is rendered. Currently, its only use case is to specify resources that are intended to be invoked by the Open Measurement SDK.
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.26
- Added
EventTrackerExt.context
, which can be used to specify that a Javascript resource included in the EventTracker message is intended to be invoked by the Open Measurement SDK.
March 28, 2018
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Rolled out a new geo targets version.
- Added over 5000 locations.
March 9, 2018
What's New in RTB Proto version 141
- Added a new field under
BidRequest.adslot.matching_ad_data.direct_deal
:must_bid_level
- See Additional Real Time Bidding fields for Programmatic Guaranteed for more details.
March 8, 2018
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Changed
15 Creative filtered because one or more detected product categories were excluded in the bid request
.
March 7, 2018
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.25
- Added
BidExt.amp_ad_url
- This field allows a bidder to respond with a URL for an AMPHTML ad.
What's New in RTB Proto version 140
- Added
BidResponse.Ad.amp_ad_url
- This field allows a bidder to respond with a URL for an AMPHTML ad.
March 1, 2018
What's New in RTB Proto version 139
- Added new enum values
INITIATE_ON_ENTERING_VIEWPORT_SOUND_ON
andINITIATE_ON_ENTERING_VIEWPORT_SOUND_OFF
toVideoPlaybackMethod
.
February 27, 2018
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- Added the new enum value
OMID_1
toAPIFramework
. This value indicates that the Open Measurement SDK is enabled for the request. While the value does not yet exist in the IAB OpenRTB spec, it is documented in the current IAB AdCom spec.
February 22, 2018
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
192 Rejected due to Coppa/KFA being filtered for demand syndication
.
February 14, 2018
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
191 Creative filtered because it contains an invalid OMSDK script URL
.
February 13, 2018
What's New in RTB Proto version 138
- Marked
BidRequest.adslot.matching_ad_data.pricing_rule
as deprecated. - We will no longer be providing this information in an effort to simplify our API.
February 6, 2018
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.24
- Added
BidRequestExt.bid_feedback
. Real-time feedback is now supported in OpenRTB through this extension.- Added
BidExt.event_notification_token
. This field can be set to an arbitrary token chosen by the bidder, and will be present in the real-time feedback for the bid it is sent in. - Added
February 5, 2018
What's New in RTB Proto version 137
- Added
BidRequest.BidResponseFeedback.buyer_creative_id
. - The RTB real-time feedback now includes the buyer creative ID from the corresponding bid response.
Archived Release Notes from 2017 and earlier
December 19, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- Switched encoding of
BidRequest.id
andBidRequest.[constrained_usage_]hosted_match_data
from base64 to websafe base64. There will still be no padding.
November 1, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- Fixed fields
NativeRequest.EventTrackers.methods
andNativeResponse.EventTracker.method
; the cardinality was mixed up, the request field is repeated not the response field.- Fixed pluralization of some new message and enum names to better conform to the OpenRTB standard and avoid confusion.
October 26, 2017
What's New in RTB Proto version 136
- Added
BidResponse.Ad.NativeAd.click_tracking_urls
. - Adx now supports multiple native click tracking urls.
- The click_tracking_url field is planned for deprecation.
October 25, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- The Native protocol was updated for version 1.2 of the specification.
- Mapping comments in the form "[AdX: ...]" were removed; refer now to the OpenRTB guide for all information about mapping and Authorized Buyers specific behavior.
- Google OpenRTB extensions protocol v.22
- Added extensions
ImpExt.ampad
andSiteExt.amp
to support Accelerated Mobile Pages.
October 18, 2017
What's New in RTB dictionaries
- The
mobile-os.csv
dictionary file has changed. - Added line
630343,"iOS",11,1,-1
.- Added line
630345,"Android",8,1,-1
. - Added line
- The
creative-status-codes.txt
dictionary file has changed. - Added
184 Creative filtered because the field amp_ad_url is too short, must be at least 11 characters
.- Added
185 Creative filtered because the field amp_ad_url could not be parsed
.- Added
186 Creative filtered because the field amp_ad_url has a domain consisting of all digits
. - Added
- The
callout-status-codes.txt
dictionary file has changed. - Added
22 Dropped due to pretargeting sampling
.
October 16, 2017
What's New in RTB Proto version 135
- Added
BidResponse.Ad.event_notification_token
.- Added
BidRequest.BidResponseFeedback.event_notification_token
. - Added
- The event_notification_token is sent to AdX by bidders in bid responses for troubleshooting. AdX will include the event_notification_token in real-time BidResponseFeedback for the bid. The content of the token will not be logged by AdX. AdX will ignore any token longer than 64 bytes.
- Updated comments for the
BidRequest.Adslot.allowed_vendor_type
.- Added 2 bid request signals:
AmpPage
andAmpAdRequirementType
. - Added 2 bid request signals:
- AmpPage indicates whether the request is coming from a webpage built using AMP (Accelerated Mobile Pages) HTML. AmpAdRequirementType provides more information about whether Ads built in AMP are allowed and/or required, and how AMP Ads will be rendered. These signals replace enum AmpAdRequestType for clarity.
What's New in Cookie Bulk Upload Proto version 7
- Added a new enum value
BUYER_PROVIDED_ID
toUserIdType
. - BUYER_PROVIDED_ID is the cookie in buyer's domain. When buyer uploads IDs in buyer's domain, we will use our mapping table to map the ID to Google's domain.
October 6, 2017
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Lines were added and deleted for locations in Canada, UK, Italy, Norway, South Africa, Columbia, Nigeria, Ukraine, and the United States. See the differences list for details.
September 22, 2017
What's New in RTB dictionaries
- The
ad-sensitive-categories.txt
dictionary file has changed. - Deleted
28 Free Gifts, Quizzes, & Surveys
.- Deleted
29 Misleading Claims
. - Deleted
- The
hosted-match-status-codes.txt
dictionary file has changed. - Added
1 DEPRECATED_HOSTED_MATCH_FORBIDDEN
.- Deleted
1 HOSTED_MATCH_FORBIDDEN
. - Deleted
September 19, 2017
What's New in RTB Proto version 134
- Added
BidRequest.response_deadline_ms
- This field states how long Google will wait for a response to this particular bid request. Bidders who have deadline-dependent logic should prefer to read this field from each bid request instead of hardcoding the deadline to 100 ms, for instance. If the field is unset, bidders should assume the default deadline as they currently do. Unit is milliseconds.
September 18, 2017
What's New in RTB protos
- RTB Proto version 133 and Cookie Bulk Upload Proto version 6.
- Updated comments for the
BidRequest.Video.Placement.IN_FEED
enum.- Introduced
BidRequest.Video.Placement.IN_ARTICLE
enum for video creatives that load and play between paragraphs of editorial content as a standalone video player.- Added
ErrorCode.BAD_DATA_SOURCE_ID
enum to the Cookie Bulk Upload proto to indicate that a data_source_id was outside the valid range of [1, 1000]. This id is not interpreted by Google and is used purely for reporting purposes. - Introduced
September 15, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- We now fill in the
Imp
object'sdisplaymanager
field withBidRequest.AdSlot.renderer
. See theImp
object in the OpenRTB guide for more information.- We now use
BidRequest.StickySettings
, in addition toBidRequest.AdSlot.slot_visibility
, to determine theBanner.pos
field. See theBanner
object in the OpenRTB guide for details. - We now use
September 14, 2017
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Added new locations and postal codes in Canada, India, Italy, Japan, Korea, Lebanon, Netherlands, Panama, and the US. See the differences list for details.
September 11, 2017
What's New in RTB Proto version 132
- Updated comments for
BidRequest.Mobile.is_app
andBidRequest.Mobile.app_id
to reflect the behavior of requests from mobile web pages contained inside mobile apps.
August 24, 2017
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Added locations in Canada, Germany, Spain, UK, India, Japan, Lebanon, Netherlands, and the US. See the differences list for details.
August 10, 2017
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
181 Creative filtered because the VAST XML document is larger than the set maximum size
.- Added
182 Creative filtered because the publisher disallowed the deal ID it targeted
.- Added
183 Creative filtered beacuse the publisher enabled the deal ID it targeted for a different deal type
. - Added
August 9, 2017
What's New in RTB Proto version 131
- Added new supported for audio mimetype values to
BidRequest.Video.VideoFormat
: - Added AUDIO_MP3
- Added AUDIO_OGG
- Added AUDIO_MP4A
- Added AUDIO_MP3_OGG for when both mp3 and ogg are required.
- Added AUDIO_OGG
- Added ALLOWED_AD_TYPE_AUDIO to
BidRequest.AdSlot.AllowedAdType
- Will be present when any of the audio mime types are present
- Added AUDIO to
BidRequest.Video.Placement
to represent when request is from an audio stream. - IMPORTANT: some audio players will request video ads when the user is interacting with the screen. This field does not mead audio ads are accepted or that video ads are not accepted!
August 7, 2017
What's New in RTB Proto version 130
- Added new supported mimetype values to
BidRequest.Video.VideoFormat
: - Added VIDEO_WEBM for "video/webm"
- Added VIDEO_MOV for "video/quicktime"
- Added VIDEO_3GPP for "video/3gpp"
- Added VIDEO_HLS for "application/x-mpegURL"
- Added VIDEO_DASH for "application/dash+xml"
- Added VIDEO_MOV for "video/quicktime"
August 2, 2017
What's New in RTB Proto version 129
- Added
BidRequest.AdSlot.exchange_bidding.key_value
. - This will be set when a publisher participating in Open Bidding decides to forward keys and values in the request to the third-party exchange.
- Added
BidResponse.Ad.AdSlot.video_vast_xml
. - This field allows a bidder to respond to a video ad request by returning a full VAST 2.0 or 3.0 XML document.
July 28, 2017
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
181 Creative filtered because the VAST XML document is larger than the set maximum size
.- Added
182 Creative filtered because the publisher disallowed the deal ID it targeted
.- Added
183 Creative filtered because the publisher enabled the deal ID it targeted for a different deal type
. - Added
July 20, 2017
What's New in RTB dictionaries
- The
publisher-verticals.txt
dictionary file has changed. - New verticals and world localities were added. See the differences list for details.
- The
creative-status-codes.txt
dictionary file has changed. - Added
179 Creative filtered because the required field amp_ad_url was missing or empty
.- Added
180 Video ad VAST version is not one of the supported versions in the video ad request
. - Added
July 13, 2017
What's New in RTB dictionaries
- The
publisher-verticals.txt
dictionary file has changed. - Added line
1347 /Business & Industrial/Transportation & Logistics/Self Storage
.- Deleted line
1347 /Business & Industrial/Transportation & Logistics/Public Storage
. - Deleted line
- The
buyer-declarable-creative-attributes.txt
dictionary file has changed. - Added
30 InstreamVastVideoType: Vpaid
.- Deleted
30 InstreamVastVideoType: Vpaid Flash
. - Deleted
- The
publisher-excludable-creative-attributes.txt
dictionary file has changed. - Added
30 InstreamVastVideoType: Vpaid
.- Deleted
30 InstreamVastVideoType: Vpaid Flash
. - Deleted
- The
pretargetable-creative-attributes.txt
dictionary file has changed. - Added
30 InstreamVastVideoType: Vpaid
.- Deleted
30 InstreamVastVideoType: Vpaid Flash
. - Deleted
- The
geo-table.csv
file has changed. - New locations have been added. See the differences list for details.
June 30, 2017
What's New in RTB protos
- RTB Proto version 128 and Cookie Bulk Upload Proto version 5
- Added
BidRequest.publisher_id
field to the RTB proto to indicate the publisher from which the impression originated.- Added
data_source_id
to the Cookie Bulk Upload proto to indicate the data source which contributed to a membership. - Added
June 28, 2017
What's New in RTB dictionaries
- The
pretargetable-creative-attributes.txt
dictionary file has changed. - Added
71 InstreamVastVideoType: Non Vpaid
.- Deleted
71 InstreamVastVideoType: Non Vpaid Flash
. - Deleted
June 16, 2017
What's New in RTB dictionaries
- The
mobile-os.csv
dictionary file has changed. - Added line
630335,"iOS",10,4,-1
.- Added line
630337,"iOS",11,0,-1
.- Added line
630339,"Android",8,0,-1
.- Added line
630341,"WindowsPhone",10,0,-1
. - Added line
- The
creative-status-codes.txt
dictionary file has changed. - Added
175 Creative filtered because it has an empty VAST XML document
.- Added
176 Creative filtered because the VAST document can't be parsed
. - Added
June 15, 2017
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.21
- Added the
is_rewarded_inventory
field. This field is populated with the same data as theBidRequest.AdSlot.is_rewarded
field of the in the AdX protocol.
June 8, 2017
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
174 Creative filtered because it lacks an MP4A file in the VAST
.
June 7, 2017
What's New in RTB Proto version 127
- Unspecified values were added to enums that lacked a default value.
- This guards against a pitfall where new enum values are included in the
BidRequest
but the bidder is still using an older version of the RTB proto which lacks those enum value definitions. In such a case, the proto library will make the getter return the first-declared value (if no default). Making the first value unspecified ensures clients know to ignore such values.
June 6, 2017
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
170 Creative filtered because it lacks a MOV file in the VAST
.- Added
171 Creative filtered because it lacks a 3GPP file in the VAST
.- Added
172 Creative filtered because it lacks a DASH file in the VAST
.- Added
173 Creative filtered because it lacks an HLS file in the VAST
. - Added
June 5, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- Added support for
vcm
for video end cards. OpenRTB 2.5 allows the exchange to setvcm=1
when an end card is supported after the video. See theBanner
object documentation in the OpenRTB guide for more information.- We now fill in
cat
in theApp
object for mobile apps, mapping mobile app categories to corresponding IAB values. See theApp
object documentation in the OpenRTB guide for more information.- We now fill in three metrics for the
metric
field in theimp
object:click_through_rate
,viewability
, andcompletion_rate
. See the Imp object in the OpenRTB guide for more information. - We now fill in
June 4, 2017
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.20
- Added the
attribute
field. This field is populated with the same data as theattribute
field of the Ad object in the AdX protocol, including thesizeless
AdX attribute.- Added
PublisherExt
object to support sending the publisher country from the AdX proto. - Added
May 25, 2017
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
166 Creative filtered beacuse the publisher didn't whitelist the deal ID it targeted, and didn't enable unknown deal IDs from the exchange
.- Added
167 Publisher requires premium (high-quality) snippets only, but this snippet does not match
.- Added
168 Creative filtered because it lacks a MP3 (audio) file in the VAST
.- Added
169 Creative filtered because it lacks a AUDIO (audio) file in the VAST
. - Added
May 11, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- We now honor the
BidResponse.burl
field.
May 10, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- We now set the
BidRequest.wlang
field.- For video ads, we now set the
BidRequest.imp.video.placement
field. - For video ads, we now set the
May 4, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- For video ads, we now set the
BidRequest.{site|app}.content.producer.domain
field.
May 2, 2017
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - New locations have been added, mainly in the United States. See the full diff for details.
April 21, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.5.0
- Updated to the OpenRTB 2.5 specification. Actual support for new fields in OpenRTB 2.5 will follow in future releases.
April 12, 2017
What's New in RTB dictionaries
- The
publisher-verticals.txt
dictionary file has changed. - Lines were added and deleted to update the file.
- The
mobile-carriers.csv
dictionary file has changed. - Lines were added and deleted to update the file.
March 27, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- Added comment to indicate that the
${AUCTION_PRICE}
macro is now supported forimpression_tracking_url
.
March 22, 2017
What's New in RTB Proto version 126
- The comments for the
click_through_url
field were changed to clarify its use. - Comments were added to indicate the field is functional as a destination URL declaration that won't be used in a live environment.
March 17, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- Updated the comment above the
protocols
field to reflect that the field is now set dynamically for each request, and is no longer hardcoded to a specific set of values.
March 10, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- Added comments to clarify that strings exceeding
max_safe_length
may be truncated by Authorized Buyers or the publisher upon rendering.
March 9, 2016
What's New in RTB Proto version 125
- Updated description for
max_safe_length
fields. - Added comments to clarify that strings exceeding
max_safe_length
may be truncated by Authorized Buyers or the publisher upon rendering.
March 3, 2017
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
889 Netscore
.- See the list of certified vendors for more details.
March 1, 2017
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.9
- Removed
dfp_network_code
. The value of this field is always the same as the first part ofdfp_ad_unit_code
sodfp_network_code
field is no longer needed.
February 28, 2017
What's New in RTB Proto version 124
- Added a new field under
BidRequest.adslot.matching_ad_data.direct_deal
:remaining_impressions_to_buy
- See the RTB documentation for programmatic guaranteed deals for more details.
February 24, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- Comments were added to clarify use of the
adm
andadm_native
fields.
February 23, 2017
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Creative status codes
147
,148
,149
,150
,151
are deprecated and no longer used.
February 22, 2017
What's New in RTB Proto version 123
- The comments for the
EndCapSupport
enum were changed to make it clear that some values are unused. - Values
END_CAP_FORBIDDEN
andEND_CAP_REQUIRED
have never been set in the BidRequest. - The comments for
click_through_url
field were changed to clarify its use. - Comments were added to indicate the field is functional as a destination URL declaration that won't be used in a live environment.
February 17, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- Comments were removed to clarify that demographic fields are no longer mapped to AdX
UserDemographic fields, which were deprecated.
- A comment was added to describe the mapping back to the AdX proto for the
BidRequest.Imp.secure
field. - A comment was added to describe the mapping back to the AdX proto for the
February 16, 2017
What's New in RTB dictionaries
- The
gdn-vendors.txt
dictionary file has changed. - Added
888 ViewersLogic
.- See the list of certified vendors for more details.
- The
vendors.txt
dictionary file has changed. - Added
888 ViewersLogic
.- See the list of certified vendors for more details.
February 9, 2017
What's New in RTB Proto version 122
- The
realtime-bidding.proto.txt
dictionary file has changed. - Modified the description for
IN_FEED
.
February 8, 2017
What's New in RTB Proto version 121
- Added new value for
BidRequest.adslot.matching_ad_data.direct_deal.deal_type
:PROGRAMMATIC_GUARANTEED
. - See the RTB documentation for programmatic guaranteed deals for more details.
February 3, 2017
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Minor corrections to administrative hierarchies, mainly in France. See the full diff for details.
January 26, 2017
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Added
165 Creative filtered by publisher's restrictions on which brands can be shown together
. This code is used if the creative was filtered by competitive advertiser exclusions set up by the publisher.
January 25, 2017
What's New in RTB Proto version 120
- Added
BidRequest.AdSlot.is_rewarded
. - This field indicates whether the user receives a reward for viewing the ad.
January 18, 2017
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Minor hierarchy fixes in
geo-table.csv
. See the differences list for details. - The
publisher-verticals.txt
dictionary file has changed. - Minor naming fixes added in
publisher-verticals.txt
. See the differences list for details. - The
creative-status-codes.txt
dictionary file has changed. - Added new status codes
163 Native ad image asset width not in permitted range
and164 Native ad image asset aspect ratio not in permitted range
tocreative-status-codes.txt
.
January 13, 2017
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
885 Cloud Technologies
.- Added
886 Research and Analysis of Media
.- See the list of certified vendors for more details.
- Added
- The
gdn-vendors.txt
dictionary file has changed. - Added
886 Research and Analysis of Media
.- See the list of certified vendors for more details.
January 12, 2016
What's New in RTB Proto version 119
- Updated the
app_id
description. - In the RTB proto,
updated the comment for
app_id
to include a sample for Windows devices.
January 9, 2017
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- Comments were added to describe a new behavior: for the browser user agent string, certain data may be redacted or replaced.
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
884 Nugg.ad
.- See the list of certified vendors for more details.
January 6, 2017
What's New in RTB Proto version 118
- Add IN_FEED Video Placement.
- Add a new IN_FEED video placement in BidRequest's Video message. IN_FEED placement corresponds to an in-feed video format, for which the video creative shows when the user is scrolling through a feed of content, typically a social app feed, a news article, etc. The video renders in the main feed and in the user's vision and reading flow, not to the side as for example, for in-banner video.
January 5, 2017
What's New in RTB protos
- RTB Proto version 117 and Cookie Bulk Upload proto version 4
- Minor comment fix in
cookie-bulk-upload.proto
- Incremented the copyright notice year to 2017
January 4, 2017
What's New in Snippet Status Report Proto version 22
- Added new disapproval reason
93 Unsupported Flash Content
December 16, 2016
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- Comments were updated to clarify that the native ad implementation may reject an image with an aspect ratio that's too far from the preferred ratio, and that it will truncate strings that are too long.
What's New in RTB Proto version 116
- Added comments.
- Comments were updated to clarify that the native ad implementation may reject an image with an aspect ratio that's too far from the preferred ratio, and that it will truncate strings that are too long.
December 14, 2016
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - The description for status code
99
was changed to99 Creative filtered because it lacks a required video MIME type in the VAST file (the specific missing type is not available)
.- Minor typo fixes in descriptions of status codes
115
,120
,131
,147
,148
. - Minor typo fixes in descriptions of status codes
December 13, 2016
What's New in RTB Proto version 115
- Added
publisher_country
- The billing address country of the publisher. This may be different from the detected country of the user in geo_criteria_id or the hosting country of the website.
- Clarify comments of
geo_criteria_id
andpostal_code
December 5, 2016
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- This release simply updates the comment for the OpenRTB
BidRequest.imp.video.protocols
field to reflect a change in the way the field is being filled. Instead of always containing the protocol numbers corresponding to VAST 3, this field will properly contain the protocol numbers for VAST 2, VAST 3, or VAST 4, depending on what is supported (see the RTB proto version 114 release notes).
December 2, 2016
What's New in RTB Proto version 114
- Added
BidRequest.Video.protocols
- This field contains an array of supported video ad protocols, matching the OpenRTB 2.4
behavior. Currently, only
VAST_2_0
,VAST_3_0
,VAST_2_0_WRAPPER
,VAST_3_0_WRAPPER
,VAST_4_0
, andVAST_4_0_WRAPPER
are possible.
November 29, 2016
What's New in RTB Proto version 113
- Added support for new video playback method
- Added a new enum value
MOUSE_OVER
toBidRequest.Video.VideoPlaybackMethod
to comply with OpenRTB 2.0.
November 18, 2016
What's New in RTB Proto version 112
- Removed old deprecated fields.
- Fields that were previously deprecated and are no longer being set are now completely removed to remove clutter.
November 14, 2016
What's New in RTB Proto version 111
- Deprecated
BidRequest.AdSlot.ExchangeBidding.dfp_network_code
. - The value of this field is always the same as the first part of
BidRequest.AdSlot.dfp_ad_unit_code
, sodfp_network_code
field is no longer needed.
November 9, 2016
What's New in RTB Proto version 110
- Added
BidResponse.Ad.NativeAd.click_link_url
- The URL that the browser/SDK loads when the user clicks the ad. Can
change between bids.
For backward compatibility, when not set, the browser/SDK loads the first
click_through_url
. However, theclick_through_url
is expected to stay identical between bids for the same buyer_creative_id, whileclick_link_url
may change.
November 4, 2016
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.7
- Added
BidResponse.SeatBid.Bid.exchange_deal_type
- Added
- This is only used for exchanges participating in Open Bidding (third party exchanges using real-time bidding on DFP). It represents information about the type of a deal that applies to an exchange bid.
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.8
- Added signals to the Native Extension in the OpenRTB Native 1.1 request.
- Added the following fields:
style_id
,style_width
,style_height
, andstyle_layout_type
. - Added the following fields:
What's New in RTB Proto version 109
- Added
BidResponse.Ad.AdSlot.exchange_deal_id
andBidResponse.Ad.AdSlot.exchange_deal_type
. - These are only used for exchanges participating in Open Bidding (third party exchanges using real-time bidding on DFP). They represent information about deals that apply to an exchange bid.
November 3, 2016
What's New in RTB Proto version 108
- Added
BidRequest.AdSlot.allowed_ad_types
. - This contains a repeated enum representing the ad types that are allowed in the bid response. Possible values are ALLOWED_AD_TYPE_BANNER, ALLOWED_AD_TYPE_NATIVE, and ALLOWED_AD_TYPE_VIDEO. This field should make it easier for bidders to identify what types of ads they can return.
November 2, 2016
What's New in RTB Dictionaries - new version of the geo-table.csv file
- Highlights of the new geo targets:
- About 100 USA/Canada National Parks. National Parks are available for targeting for the first time.
- About 1200 Australia/Germany/Netherlands/France cities and postal codes.
- 78 Municipalities in Puerto Rico.
- 71 Provinces/Districts in Bangladesh.
- 21 Provinces/Cities in Costa Rica.
- 2 new country-level targets: Guernsey (GG) and Jersey (JE).
- A few hundred province-level targets in South America, Africa and Middle East.
- About 1200 Australia/Germany/Netherlands/France cities and postal codes.
October 31, 2016
What's New in RTB Proto version 107
- Update to the
BidRequest.AdSlot.NativeAdTemplate
. - Added the following fields:
style_id
,style_width
,style_height
, andstyle_layout_type
.
What's New in RTB dictionaries
- The
ad-product-categories.txt
dictionary file has changed. -
Added over 200 new general categories which publishers can use to block ads.
These categories are generally more fine-grained, allowing publishers to
block narrower categories, for example,
Used Motor Vehicle
creatives instead of allAutomotive
creatives. As before, this dictionary file is useful in mapping the category IDs found in theexcluded_product_category
field in bid requests to human-readable categories.- For more detail, see the full list of differences.
October 27, 2016
What's New in RTB Proto version 106
- Added
BidRequest.AdSlot.sticky_settings
. - This contains the different types of stickiness settings that a publisher can declare on their inventory. Three types of stickiness settings are supported - vertical stickiness, bottom horizontal stickiness, and top horizontal stickiness.
BidRequest.AdSlot.stickiness
is now deprecated.- This field is deprecated in favor of
BidRequest.AdSlot.sticky_settings.vertical_stickiness
.
What's New in RTB dictionaries
- The
publisher-verticals.txt
dictionary file has changed. - Fixed typos in some category names; download the list of differences for details.
October 24, 2016
What's New in RTB Proto version 105
- Deprecated field
BidRequest.user_demographics
. - The
BidRequest.user_demographics
field has been deprecated.
October 21, 2016
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.6
- Added
BidRequest.imp.dfp_ad_unit_code
. - Added
- This is only used for Open Bidding.
What's New in RTB Proto version 104
- Added
BidRequest.AdSlot.non_browser_slot_source
. - This will be set when a publisher declares that the ad slot is served on a non-browser inventory, and will specify the kind of non-browser inventory.
- Added
BidRequest.AdSlot.is_interstitial_slot
. - This will be set when a publisher declares that the ad slot is an interstitial, covering the content for a period of time.
October 20, 2016
What's New in RTB Proto version 103
- Added
BidRequest.AdSlot.dfp_ad_unit_code
. - This is only used for Open Bidding.
October 14, 2016
What's New in RTB dictionaries
- The
geo-table.csv
dictionary file has changed. - Corrected minor spelling and geo hierarchy errors. See the differences list for details.
What's New in OpenRTB
-
Google OpenRTB protocol 2.4.1
- This release doesn't make any change to the protos, but updates mapping with initial support for OpenRTB 2.4:
- Banner impression sizes are now mapped to
Banner.format
. Thewmin
,wmax
,hmin
andhmax
fields are deprecated and won't be populated for 2.4+. Thew
andh
fields are still populated (with the first dimension like before).Video.skip
is now populated.Bid.api
is now supported.- HTTP header
x-openrtb-version
is "2.4". - Bidders using OpenRTB/JSON can opt into the new version 2.4 through RTB API; bidders using OpenRTB/Protobuf can only use version 2.3 and future upgrade will be announced separately.
October 13, 2016
What's New in RTB Proto version 102
- Updated the "Connected_TV = 4" description.
- In the RTB proto, updated the comment for "Connected_TV = 4" to more completely describe the devices included.
October 11, 2016
What's New in Snippet Status Report Proto version 21
- Added new disapproval reason
92 Personal Loans
October 6, 2016
What's New in RTB Proto version 101
- Updated the native ads template comment.
- In the RTB proto,
modified the native ads template comment to note that under some
circumstances the
html_snippet
orvideo_url
field can be set instead of thenative_ad
field.
October 5, 2016
What's New in RTB Proto version 100
- Updated the comment for mobile advertising identifier.
- In the RTB proto, updated
the comment on the
BidRequest.Mobile.encrypted_advertising_id
field to clarify on which platforms it is available (in addition to iOS and Android devices).
September 30, 2016
What's New in RTB Proto version 99
- Added video completion rate signal to Real Time Bidding.
- In the RTB proto, added
a new field
video_completion_rate
toBidRequest.AdSlot
. This field indicates an estimate of the likelihood that a video ad served in this slot will be viewed to completion.
September 29, 2016
What's New in RTB dictionaries
- The
vendors.txt
dictionary file has changed. - Added
880 Navegg
.- See the list of certified vendors for more details.
September 20, 2016
What's New in Snippet Status Report Proto version 20
- Added new disapproval reasons.
90 Maximum number of HTTP calls exceeded
91 Maximum number of cookies exceeded
- Renamed disapproval reason 36 from
Invalid ad download size
toMaximum download size exceeded
September 19, 2016
What's New in RTB dictionaries
- The
buyer-declarable-creative-attributes.txt
dictionary file has changed. - Added
105 Rendering: Sizeless AdX
. Used to declare whether an HTML creative can dynamically resize to fill a variety of slot sizes. Refer to the interstitial ads documentation for further information.
September 15, 2016
What's New in RTB Proto version 98
- Added support for native video in Real Time Bidding.
- In the RTB proto, added
a new enum value
VIDEO
toBidRequest.NativeAdTemplate
and a new fieldvideo_url
toBidResponse.NativeAd
. This allows bidders to send back a video response innative_ad
field whenVIDEO
is present inBidRequest.native_ad_template.required_fields
orBidRequest.native_ad_template.recommended_fields
.
September 13, 2016
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.1
- This releases contains minor fixes for OpenRTB 2.4, specifically:
deprecation status of several fields;
extension support for
Audio
andFormat
; correct enum type of the new fieldBid.qagmediarating
.
September 8, 2016
What's New in RTB dictionaries
- The
creative-status-codes.txt
dictionary file has changed. - Changed description of status
107
toRequired elements specified in bid_request.adslot.native_ad_template.required_fields are missing or empty
, to reflect the logic change that adds filtering on required native ad elements with explicit empty values.
September 7, 2016
What's New in RTB Proto version 97
- Updated comments to clarify that for iOS apps, the
app_name
is provided by AppAnnie.
September 6, 2016
What's New in Snippet Status Report Proto version 19
- Added new disapproval reasons.
- 81 Video too long
- 82 Violates Japanese pharmacy law
- 83 Unaccredited pet pharmacy
- 84 Unacceptable content: abortion
- 85 Unacceptable content: birth control
- 86 Violates Chinese serving requirements
- 87 Creative promotes a Korean pharmacy without proper certification
- 88 Non-family safe or adult content
- 89 Unacceptable content: clinical trial recruitment
- 82 Violates Japanese pharmacy law
September 2, 2016
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.4.0
- This is a major new release that updates the protocol schema for
the latest specification versions: OpenRTB 2.4 and OpenRTB Native 1.1.
The change is backward-compatible at the wire level, but incorporating the
new schema into the bidder may require trivial code changes.
Specifically, there are two changes:
- New fields are added according to the latest spec. They are not set yet, and support for them will be announced separately.
- All enums are now top-level instead of nested. This does not change the wire representation, but requires fixing imports or using differently qualified enum names in some languages.
- New fields are added according to the latest spec. They are not set yet, and support for them will be announced separately.
August 31, 2016
What's New in RTB dictionaries
- The
gdn-vendors.txt
dictionary file has changed. - Added
284 Research Now
.- See the list of certified vendors for more details.
- The
vendors.txt
dictionary file has changed. - Added
284 Research Now
.- Added
876 Exponential Expandable
.- See the list of certified vendors for more details.
- Added
August 22, 2016
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.5
- Added
BidRequest.imp.dfp_network_code
. - Added
- This is only used for Open Bidding.
What's New in RTB Proto version 96
- Added
dfp_network_code
toBidRequest.AdSlot
. - This is only used for Open Bidding.
August 18, 2016
What's New in RTB Proto version 95
- Changed the semantics of
mediation_status
field. - The field is set to DIRECT_REQUEST or UNKNOWN based on whether the ad request has been determined to come directly from the publisher or not.
August 8, 2016
What's New in RTB Proto version 94
- Added
amp_ad_request_type
toBidRequest.AdSlot
. - This field indicates whether the page is an Accelerated Mobile Page (AMP).
August 1, 2016
What's New in RTB Proto version 92
- Noted that responses to bid requests are filtered out of the auction whether the
is_test
field of the bid request is set to true or false during initial testing with Google traffic.
July 26, 2016
What's New in RTB dictionaries
- The
gdn-vendors.txt
dictionary file has changed. - Added
874 Cint
.- See the list of certified vendors for more details.
- The
vendors.txt
dictionary file has changed. - Changed
332 Audience Manger (DemDex/Omniture)
to332 Audience Manger (DemDex)
.- Changed
832 The AdExchange
to832 The ADEX
.- Added
874 Cint
.- See the list of certified vendors for more details.
- Changed
July 18, 2016
What's New in RTB Proto version 92
- Updated comments to clarify that for native ads the
click_through_url
provides the URL of the landing page to which the user is delivered while theclick_tracking_url
specifies a URL on which a background thread can ping for tracking purposes.
July 14, 2016
What's New in RTB dictionaries
- The vendors.txt dictionary file has changed.
- Added
838 Revjet Expandable
.- Added
863 Bonzai Expandable
.- Added
864 INCUBIQ Solutions
. - Added
- The vendors.txt and gdn-vendors.txt dictionary files have changed.
- Cleaned up all VAST video vendors, which have been deprecated since
April 2016: they are always allowed (no
declaration needed) and do not appear in the
allowed_vendors
field in bid requests. - See the list of certified vendors for more details.
July 13, 2016
What's New in Snippet Status Report Proto version 18
- Added a new
detected_domain
field that exposes the domains detected during verification scans.
July 11, 2016
What's New in RTB Proto version 91
- Updated comments to indicate that parts of the user agent string might be redacted or replaced.
July 8, 2016
What's New in RTB Proto version 90
- Updated comments to clarify that only the first value of
click_through_url
is used as the click URL for native ads.
June 29, 2016
What's New in RTB Proto version 89
- Updated comments to clarify that
url
always contains a protocol.
June 22, 2016
What's New in RTB Proto version 88
- Updated comments to clarify that
click_through_rate
does not include data aggregated from AdWords.
What's New in RTB Proto version 87
- Clarified in the
BidResponse
comment that theBidRequest
can have only oneAdSlot
.- Made some minor wording changes in other comments.
June 3, 2016
What's New in RTB Dictionaries - new version of the geo-table.csv file
- It adds almost 6000 new geo targets. These targets are already live and present in bid requests (with the exception of Myanmar, which is not live yet). Notable additions:
- 2214 sub-localities and postal codes in the Netherlands.
- 1423 cities, neighborhoods and postal codes in Malaysia.
- 722 cities, neighborhoods and postal codes in major eastern European countries (Poland, Hungary, Czech Republic) and in Greece.
- 639 provinces, cities and neighborhoods in the Philippines.
- 155 cities and sub-localities in Sweden.
- 104 cities and postal codes in Germany.
- 1423 cities, neighborhoods and postal codes in Malaysia.
- Some highlights from the long tail:
- 2 important sub-localities in New York City - Manhattan and Queens.
- 44 targets in Myanmar, include the country itself (note: not live yet).
- Capitals / large cities in many countries, for example Nairobi in Kenya and Guatemala City in Guatemala.
- 44 targets in Myanmar, include the country itself (note: not live yet).
June 2, 2016
What's New in OpenRTB Protos
- Google OpenRTB extensions protocol v.4
- Added
BidRequest.processing_time_ms
.
May 30, 2016
What's New in Snippet Status Report Proto version 17
- Added the
VIDEO_IN_SNIPPET_ATTRIBUTE_ADDED
declaration correction. - This correction is applied when an HTML snippet is playing video content, and therefore should be blocked on inventory that forbids video.
- Added the
detected_language
field. - This field reports the languages that AdX detected for the creative.
- These languages are used for applying publisher language blocks. See also the
allowed_languages
field in the RTB proto. - These languages are used for applying publisher language blocks. See also the
- Added the
context
field to theCorrection
message. - This field describes the context(s) in which the correction is applied.
- Correction and serving contexts now separate mobile web from mobile app.
- Added new values to the
Platform
enum:ANDROID_IN_APP
andIOS_IN_APP
. PreexistingANDROID
andIOS
values have been renamed toANDROID_WEB
andIOS_WEB
.
May 26, 2016
What's New in OpenRTB Protos
-
Google OpenRTB extensions protocol v.3
- Added
BidRequest.imp.publisher_parameter
andBidResponse.SeatBid.Bid.bidder_name
. - Added
- Both fields are only used for exchanges participating in Open Bidding (third party exchanges using real-time bidding on DFP).
What's New in RTB Proto version 86
- Added
allowed_languages
toBidResponse.AdSlot
. - This field contains the creative languages allowed by the publisher.
- When not set, all languages are allowed.
May 25, 2016
What's New in RTB Proto version 85
- Added
exchange_bidding
toBidRequest.AdSlot
andbidder_name
toBidResponse.Ad
. - Both fields are only used for exchanges participating in Open Bidding (third party exchanges using real-time bidding on DFP).
May 19, 2016
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.3.3
- Fixed Native response's
Video.vasttag
to be a scalar, not array.- Updated comments to reflect changes in the encoding of fields:
BidRequest.id
,User.customdata
,Device.ifa
.- Google OpenRTB extensions protocol v.2
- Added
BidRequest.imp.allowed_vendor_type
andBidResponse.SeatBid.Bid.ad_choices_destination_url
. - Fixed Native response's
May 13, 2016
What's New in RTB Proto version 84
- Added
ad_choices_destination_url
toBidResponse.Ad
. - This field can be used to provide a link to your ad preferences page.
- This is only supported for native ads.
- If provided, a standard AdChoices icon is added to the native creative and linked to this URL.
- This is only supported for native ads.
April 29, 2016
What's New in RTB dictionaries
- Removed VAST (in-stream video) vendors from the declarable lists.
- These vendors are now allowed without declaration. Since publishers do
not have the ability to opt into or block them, we also no longer send them
in the
allowed_vendors
field in bid requests.- See the list of certified vendors for more details.
April 28, 2016
What's New in RTB Proto version 83
- Updated comments to clarify that
viewability
may be estimated based on historical or environment data.
April 27, 2016
What's New in RTB dictionaries
- Removed vendor
113 "Image & Flash"
from the declarable lists. - This vendor is deprecated. It should not be declared in bid responses, since it
does not stand for any 3PAS technology (but if it is declared, the bid will not be
filtered because of it). Bidders should ignore the presence or absence of this vendor
in the
allowed_vendors
field in bid requests, since it is not a meaningful signal.
April 12, 2016
What's New in BidResponse
- Updated comments to clarify that XML responses
fetched through
video_url
can conform to either VAST 2.0 or 3.0.
April 11, 2016
What's New in RTB dictionaries
- Removed the obsolete
site-lists.txt
dictionary file - AdX stopped populating the
site_list_id
field in bid requests in October 2015, eliminating the need for thesite-lists.txt
dictionary. Removed it to reduce confusion.
April 1, 2016
What's New in RTB Proto version 81
- Updated comments
- Updated comment on the
creative_index
field ofBidResponseFeedback
to say that it always refers to the index of the ad in the response.
March 30, 2016
What's New in the Snippet Status Report - Deals Policy Update
- Fine-grained status is provided for both Open Auction and Deals.
- In general,
open_auction_status
anddeals_status
are a replacement forstatus
, which is now deprecated. - The new
serving_restriction
field provides detailed, contextual status. - This replaces the now deprecated
disapproval_reason
. It allows us to communicate the status of an ad in a specific context. for example, the ad is disapproved on mobile because it contains Flash or the ad cannot serve in Russia because it has not yet been reviewed there. - Added a new Status enum value:
CONDITIONALLY_APPROVED
- It is used when the ad is approved in general, but with restrictions in some contexts. Most ads will be CONDITIONALLY_APPROVED for the open auction.
March 29, 2016
What's New in OpenRTB Proto version 2.3.2
- Improved documentation for several fields:
-
id
in theBidRequest
andBidResponse
;ip
,ipv6
,carrier
,dpidm5
andadvertising_id
inDevice
;Geo
message;customdata
inUser
;clicktrackers
inLink
.
March 4, 2016
What's New in OpenRTB Protos
- Google OpenRTB protocol 2.3.1 (available now)
- Contains the latest version of Authorized Buyers's OpenRTB protocol. Field mappings to Authorized Buyers's RTB protocol can be found in the comments.
- Google OpenRTB extensions protocol v.1 (available now)
- Contains Authorized Buyers's extensions used in the OpenRTB protocol.
February 26, 2016
What's New in RTB Proto version 80
- Updated comments on the
fixed_cpm_micros
field of direct deals.- Renamed enum values of the
VideoFormat
field to better match functionality: VIDEO_FLASH to VIDEO_FLV and VIDEO_HTML5 to VIDEO_MP4.- Added new supported values to the
VideoFormat
field: VPAID_FLASH (SWF) and VPAID_JS (Javascript). - Renamed enum values of the
February 19, 2016
What's New in RTB Proto version 79
- Updated comments on the
placement
field.
February 8, 2016
What's New in RTB Proto version 78
- Added a new video placement field to replace
inventory_type
field. - The video sub-message in the
RTB Proto now has a
placement
field to differentiate between INSTREAM and INTERSTITIAL. Theinventory_type
field is deprecated, this field duplicates information found elsewhere in the RTB proto. - Added a new
renderer
field to the ad slot submessage. - The
renderer
field defines who controls the environment (either Google or the publisher) that made the ad request and will render the ad. This field is only set for requests that allow VAST video ads.
January 29, 2016
What's New
- Updated snippet-status-report-proto.txt to v.15
- Added two CorrectionType enum values: IN_BANNER_VIDEO_ATTRIBUTE_ADDED and MRAID_ATTRIBUTE_ADDED. Refer to the comments on the new values for more details.
May 18, 2015
What's New
- Authorized Buyers starts enforcing an upper sanity limit on bids
- To protect itself and its partners from bugs and misconfigurations, Authorized Buyers starts enforcing an upper sanity limit of $5000 CPM on bids. See Bid Response Filtering for details.
July 11, 2014
What's New
- Flash-Less Declaration in Bid Response is No Longer Necessary
- Buyers no longer need to declare use of flash-less creative when bidding on flash-less inventory as Authorized Buyers will automatically detect the presence of flash-less creative. Buyers still need to include flash-less creative when bidding on flash-less inventory. If a buyer responds to a flash-less bid request with a flash creative, Authorized Buyers will detect the presence of flash creative and filter out the Bid Response. Note that Authorized Buyers will not detect if a flash-less backup creative is included with a flash creative in a Bid Response and Authorized Buyers will filter out that Bid Response for including a flash creative.
- The Name of the "encrypted_idfa" Field Has Been Changed to "encrypted_advertising_id"
- Authorized Buyers has changed the name of the "encrypted_idfa" field to "encrypted_advertising_id" so that the field name reflects that we are able to pass buyers either the IDFA or advertising ID in the BidRequest based on which is available. Buyers can continue referring to the original "encrypted_idfa" field name until they download and start using the latest version of the RTB proto. Once a buyer starts using the latest version of the RTB proto, they need to update their bidder to refer to "encrypted_advertising_id" as the new name for that field. See Targeting mobile app inventory with IDFA for details.
- New Field to Identify if Video Player is Embedded
- Authorized Buyers has added a new field to the RTB proto to specify if the video player is embedded or not embedded. The new field is called "is_embedded_offsite" and if true, the video is embedded on pages out of the publisher's domain. See Authorized Buyers Video Integration Guide for details.
July 16, 2013
What's New
- [IMPORTANT]
BidResponses
must include ad size for multi-size requests For all bid requests that specify multiple ad sizes, your
BidResponse
must include theBidResponse.Ad.width
andBidResponse.Ad.height
fields. Bid responses to multi-size requests that do not include these fields will be dropped from the auction. We expect that about 5% of ad requests will contain multiple ad sizes starting September 24, 2013 as we turn on multi-size dynamic allocation in DFP. We expect this percentage to grow over time.Although bid responses to single-size bid requests are not required to include the
Ad.width
andAd.height
fields, we suggest always including them, as a best practice.- [REMINDER] Per-region CSV reports to be deprecated on July 9, 2013
- After July 9, the per-region CSV performance reports will no longer be available for download.
- [REMINDER] Download size increased to 150 kilobytes
- We have increased the maximum allowable download size from 50 kb to 150 kb. In addition we are activating automated enforcement for this policy so that ads that exceed 150 kb will be disapproved. See our Help Center documentation for details.
- [REMINDER] Flashless Creative Declaration for Mobile In-App Inventory
- All mobile in-app RTB certified buyers MUST indicate that an ad is flash-less in their bid response if they are responding to a mobile app callout. If the correct creative declarations are not present, the ad can be disapproved. See the Help Center documentation for more details.
- [REMINDER] carrier_name and carrier_country to be removed from bid requests
- On June 4, 2013, we have ended official support of the carrier_name and carrier_country fields in the BidRequest. Buyers should adopt the new carrier_id field. Find out more by referring to the March newsletter.
May 20, 2013
What's New
- Google Hosted Match Tables (available now)
Google is now able to host a buyer's match table between the buyer's IDs and Google's cookie IDs. This reduces the infrastructure requirements for our buyers and lays the groundwork for further cookie matching enhancements. Buyers are now able to, in one call, add the user to one or more user lists and set the Ad Manager cookie if it's missing.
We strongly recommend that you embrace Google hosted cookie match tables. In addition to efficiency and cost savings from switching, you will also be eligible to join our pixel matching beta which on average improves cookie match rates by 20-30%. To be eligible, you must be using Google hosted match tables, so we encourage all AdX RTB buyers to do so as soon as possible.
April 15, 2013
What's New
- [IMPORTANT]
seller_network
field has been deprecated. - The
seller_network
field has been replaced with the newseller_network_id
field, which contains an integer corresponding to a network found in the seller-network-ids.txt dictionary file. We stopped setting theseller_network
field as of April 2, 2013. Update your bidder to use the new field, particularly to identify inventory from the Google Display Network, which now has aseller_network_id
value of 1. - [IMPORTANT] Change to Pixel Match requirements
- Starting in mid-April, we will begin assigning a URL-safe string value
to the
google_push
parameter in our pixel match requests and we will expect that same URL-safe string to be returned in thegoogle_push
parameter you set. This change will help us with our latency troubleshooting efforts and improve our pixel match efficiency. - RTB Protocol update - New Agency Field in
BidResponse
To enable buyers and sellers to create Preferred Deals and Private Auctions for a specific agency, a new field,
agency_id
, has been added to theBidResponse
. To implement this new field we have created a new dictionary file, agencies.txt, with accepted agencies.Supporting this field will give buyers more flexibility in their programmatic offerings and help you negotiate more Preferred Deals with publishers looking for buyers with this capability. To find out more, see our Help Center documentation or reach out to your Technical Account Manager.
- Google-hosted creatives can no longer be used for RTB
- In the past, buyers were able to use Google-hosted creative files for
both RTB and UI campaigns. Now RTB buyers can no longer respond with
Google-hosted creatives and all Google-hosted creatives sent in the
creative_id
field through RTB will be discarded. Hosted creatives are still available to UI buyers. - RTB Real-time Feedback BETA
- To facilitate more dynamic bidder strategies, we can provide near real-time auction feedback on why your bid did not win, for example: publisher blocks, creative not approved, or a higher bid. The actual reason will be passed in the BidResponseFeedback sub-message in a subsequent BidRequest and there is a complete list of possible reasons on the downloads page in creative-status-codes.txt. For losing bids that exceeded the specified price floor and used creatives that were not filtered pre-auction, we will pass back the price needed to win the auction. Only buyers that opt-in to disclosing their winning bid data may participate in this limited beta. If you are interested in participating, contact your Technical Account Manager.
March 11, 2013
What's New
- [IMPORTANT] Cookie Matching v1 to be deprecated
- Starting June 4, 2013, we will no longer support Cookie Matching V1. To better serve our buyers, we built more advanced features, such as Hosted Match Tables, into our Cookie Matching v2 API. If you have not done so already, we strongly recommend that all buyers upgrade to the new version of Cookie Matching as soon as possible.
- [IMPORTANT] Update seller_network_id change
- If you buy inventory by targeting using the seller_network_id field, note that we have made changes to some of the IDs in the seller-network-ids.txt file. These changes were the result of a one time re-indexing of the IDs and the existing mappings will be persistent and subsequent publisher additions will be appended to the end of the file. Note that the Google Display Network (GDN) seller_network_id has changed from 0 to 1.
- Download the most recent dictionary file of seller network IDs to ensure that you are properly targeting GDN and other publisher networks on AdX. If you have any questions, contact your Account Manager.
- [IMPORTANT] Impressions eligible for multiple ad sizes must include Ad Width and Height in the BidResponse
- Publishers are increasingly accepting multiple ad sizes for individual ad slots. These impressions include multiple sizes in the BidRequest.AdSlot field and require the BidResponse.Ad.width and BidResponse.Ad.height fields to be returned in corresponding BidResponses. Bid Responses made in response to requests containing multiple Ad sizes must include these fields or else they will be automatically filtered from the auction.
- Currently multiple ad size bid requests are only available to buyers passing the BidResponse.Ad.width and BidResponse.Ad.height fields in their BidResponse. This accounts for 3% of available impressions and will increase in Q2 as more inventory becomes available from our Ad Manager clients. We will soon be creating an allowlist to make this inventory available only to buyers who set the ad size in response to multiple ad size bid requests. If your bidder is not currently returning BidResponse.Ad.width and BidResponse.Ad.height fields in your BidResponses, you are encouraged to start doing so to be eligible for such inventory. Contact your Account Manager for more details on how to join the allowlist.
- [IMPORTANT REMINDER] SSL - Upcoming Change for 3rd Party Ad Serving
- We are excited to start support for Secure Socket Layer (SSL) encrypted traffic, which will allow Authorized Buyers to start offering additional inventory types to our clients, including webmail and other inventory from logged-in users. SSL inventory is unique in that all subsequent calls to 3rd parties after the initial ad request must also be SSL-based or the browser will display a warning to the user. In order to ensure a seamless consumer experience across AdX, we are introducing a new SSL certification to confirm all buyer technologies are SSL compliant.
- As we mentioned at the end of October last year, the first source of SSL inventory on AdX will come from signed-in users of Google owned and operated properties such as YouTube. Currently, only a small percentage of YouTube inventory is SSL-enabled, but in May 2013 this volume will ramp up to all signed-in YouTube users, totalling about 40% of YouTube traffic. The supply of SSL inventory on AdX will continue to grow this year as we add new inventory from webmail and other secure environments.
- SSL inventory will only be available to buyers certified as SSL compliant by the Google certification team. Don't miss out on this opportunity--start implementing SSL on your RTB and 3rd party ad serving platform as soon as possible.
- RTB buyers do not need to use separate buyer_creative_id for the SSL and non-SSL snippets. See our help center documentation for additional details.
- As we mentioned at the end of October last year, the first source of SSL inventory on AdX will come from signed-in users of Google owned and operated properties such as YouTube. Currently, only a small percentage of YouTube inventory is SSL-enabled, but in May 2013 this volume will ramp up to all signed-in YouTube users, totalling about 40% of YouTube traffic. The supply of SSL inventory on AdX will continue to grow this year as we add new inventory from webmail and other secure environments.
- [REMINDER] New Formatting for Publisher Settings Files
- We recently made a change to the format of our Publisher Settings Files (PSFs) to make processing them easier. The new format splits the PSF into two 9MB files and reduces the overall file size by 60%.
- In addition, we will be transitioning from an id field of type bytes to an id field of type fixed64. Currently both fields are being provided but as of April 2, 2013 only the fixed64 id field will be filled.
- PSFs provide buyers with information about individual publisher inventory requirements to help their bidders make better decisions. The PSFs include data such as: allowed ad technologies, excluded categories, and blocked landing pages. Contact your Technical Account Manager with questions or refer to the Real-time Bidding documentation.
- In addition, we will be transitioning from an id field of type bytes to an id field of type fixed64. Currently both fields are being provided but as of April 2, 2013 only the fixed64 id field will be filled.
- [RTB Protocol] ROADMAP PLANNING - New Agency Field in BidResponse coming in March
- With the growth of programmatic buying, publishers are increasingly looking to sign programmatic deals directly with agencies. To enable buyers and sellers to create Preferred Deals segmented by specific buyer/agency/advertiser, a new Agency field will be added to the BidResponse. The ability to create Agency specific deals gives buyers more flexibility with programmatic buying on AdX by reducing spending conflicts with other advertisers and agencies on their account.
- We believe that this is an important change and one that requires some development work so we're making this announcement to give you sufficient time to plan for the necessary modifications to your bidders. We will begin accepting this field at the end of March and it will be available in Preferred Deals later in Q2. Supporting this field will give buyers more flexibility in their programmatic offerings and help you negotiate more Preferred Deals with publishers looking for buyers with this capability.
- Once available, you'll be able to fill in the Agency field at the time of creative submission or in the BidResponse. Stay tuned for more details on how to implement the new Agency field and reach out to your Account Manager if you have any questions.
- We believe that this is an important change and one that requires some development work so we're making this announcement to give you sufficient time to plan for the necessary modifications to your bidders. We will begin accepting this field at the end of March and it will be available in Preferred Deals later in Q2. Supporting this field will give buyers more flexibility in their programmatic offerings and help you negotiate more Preferred Deals with publishers looking for buyers with this capability.
- Cookie matching macros now available
- Now you have the option to configure your cookie matching URLs with one or more macros to determine the order and location in which cookie matching parameters are added to the URL. By using these macros you have more flexibility and control for cookie matching. Read our Cookie Matching Guide to learn more about the new macros and how to use them.
October 15, 2012 Release
What's New
- New
geo_criteria_id
- Starting on April 2, 2013, the
{country, region, city, metro}
fields in the RTB Protocol will no longer be passed in BidRequests. These fields will replaced with the newgeo_criteria_id
field, which is an ID representing geographic locations that can be found in the Targets Table at our developers site here. If you have any questions, contact your Technical Account Manager. - [ACTION REQUIRED] Migration from
seller_network
toseller_network_id
- The
seller_network
field will be replaced with the newseller_network_id
field, which contains an integer corresponding to a network found in the seller-network-id.txt dictionary file on the Downloads page. We will stop setting theseller_network
field on April 2, 2013.- Update your bidder to use the new field, particularly to identify inventory from the Google Display Network.
- [IMPORTANT] Ad Width and Height must be included for multiple ad size bid requests
- For all bid requests that contain multiple ad sizes, your
BidResponse
must include theBidResponse.Ad.width
andBidResponse.Ad.height
fields. Bid responses to requests with multiple Ad sizes that do not include these fields will be dropped from the auction.- Although bid requests with a single ad size in the BidRequest.AdSlot need not include the Ad.width and Ad.height fields, we suggest always declaring the Ad Size as a best practice.
July 2, 2012 Release
What's New
- New RTB Protocol Field
- The
BidRequest.AdSlot.ad_block_key
field in the RTB protocol contains a 64-bit integer that provides a stable identifier for the (web_property, slot, page) combinations. This new field lets you track the performance of specific adslot-ad combinations to make better bidding decisions.- If you have any questions about the new
BidRequest.AdSlot.ad_block_key
field, contact your Technical Account Manager or refer to the RTB protocol developer documentation. - If you have any questions about the new
- AdGroup ID required when a
BidRequest
has multiple ad groups - The
BidResponse
must include thebilling_id
field when responding to any bid request that has multiple ad groups. A bid request that has multiplematching_ad_data
fields (sub-messages) has multiple ad groups, because eachmatching_ad_data
field contains exactly one ad group.
Prior to July 2, 2012, the bid response needed to include thebilling_id
field only when the bidder used hosted creatives or merged streams. This requirement is now obsolete. - Bulk location targeting in the UI
- The bulk upload tool for locations, which can make location targeting strategies more powerful, is now part of the Authorized Buyers UI.
June 5, 2012 Release
What's New
GDN
has replacedGCN
as the permitted value in theseller_network
field- The
BidRequest
now sends a value ofGDN
in theseller_network
field, replacing the value ofGCN
that was sent prior to June 1, 2012. Wherever your bidder uses theseller_network
field, be sure that you have reviewed and if necessary adapted your code so that the value change does not cause problems. - Interactive in-stream video ads beta based on VPAID v1.0 standard
- VPAID stands for "Video Player-Ad Interface Definition" and is an IAB-published industry standard for interactive in-stream video ads. Authorized Buyers has begun limited beta support for VPAID ads through the RTB Protocol and the UI. To learn more, contact your account representative.
- New
mobile_device_type
field inBidRequest
- Bid requests for mobile inventory now include the
mobile_device_type
field. The field's value specifies the type of mobile device on which the ad is to be shown: eitherTABLET
orHIGHEND_PHONE
. - New nomenclature: Preferred Deals, formerly known as Direct Deals
- The term "Direct Deal" has been replaced by "Preferred Deal" in the UI and Help. Look for the new nomenclature in the relevant section of the Buyer REST API documentation in the near future.
- New
UserList
message inBidRequest
- Bid requests may include one or more
UserList
messages. EachUserList
message specifies an audience-targeting list to which the user has been added, along with the time elapsed since the user was added. See the Buyer UI Help topics on remarketing, where the audience-targeting list is called a remarketing list. To arrange for your bidder to use this feature, contact your account representative. - Transition of the
excluded_sensitive_category
field from string to int32 - Your bidder may use
excluded_sensitive_category
field in thepublisher-settings
protobuf to see what content categories are disallowed by publishers. If so, be aware that this field is now being sent in two forms: the repeated int32excluded_sensitive_category
, and the repeated stringDEPRECATED_excluded_sensitive_category
. We recommend that when it is convenient, you modify your bidder to handle the int32 form of this field to prepare for the eventual sunset of the string. - When sending bid requests that lack URL and anonymous ID, Authorized Buyers can skip your bidder
- If you prefer that bid requests which contain neither a page URL nor an anonymous ID are never sent to your bidder, contact your account representative about this new option.
Coming Soon
- Bulk location targeting in the UI
- The bulk upload tool for locations, which can make location targeting strategies more powerful, continues its gradual rollout as part of the Authorized Buyers UI.
- AdGroup ID to be required when a
BidRequest
has multiple ad groups - Beginning July 2, 2012, the
BidResponse
must include thebilling_id
field when responding to any bid request that has multiple ad groups. Here's how you can tell when a bid request has multiple ad groups: look for multiplematching_ad_data
fields (sub-messages). Because eachmatching_ad_data
field contains exactly one ad group, the presence of multiplematching_ad_data
fields always means that there are multiple ad groups.
When this change takes effect, the current requirement (which is that the bid response must include thebilling_id
field whenever the bidder uses hosted creatives or merged streams) will be obsolete.
Resolved Issues
- Snippet Status Report now shows expected categories
- The content categories that the Snippet Status Report is intended to show are those in the
ad-product-categories.txt
dictionary file. In some cases, a Snippet Status Report was showing categories not documented in the dictionary file. This problem has been fixed.
May 11, 2012 Release
What's New
- Ads now appear only on sites that match both topic and placement targeting
- Previously, ads appeared on sites that matched either topic or placement targeting. Now, ads only appear on sites that match both topic and placement targeting.
- Multi-directional expandable creatives beta
- Authorized Buyers offers support for multi-directional expandable creatives as a beta feature. Multi-directional expandable creatives can expand up to the maximum expanded size as specified in the updated Program Guidelines.
- In-game video inventory is now available in Authorized Buyers
- The video ad inventory that campaigns buy on Authorized Buyers now includes in-game video inventory offered by Google In-Game Advertising publishers.
Any campaign that buys video ads now automatically buys these in-game placements unless the "in-game" category exclusion is added to the campaign. You can add this exclusion through the Buyer SOAP API, by using the CampaignCriterionService to add aNegativeCampaignCriterion
of typeContentLabel
, withcontentLabelType
set toGAMES
. This update to the Authorized Buyers Video beta took effect on May 1, 2012. - Program Guidelines updated
- The Program Guidelines have been updated to clarify the scope of the prohibition on passing personally identifiable information, improve consistency in terminology used, remove topics covered by the Authorized Buyers APIs and Protocol Terms of Service, explain beta support for multi-directional expandable creatives, and, to clarify the process of third-party ad serving, including by providing links to the list of approved technology vendors and to the requirements for declaring technology vendors.
- Targeting video impressions by player size
- For video inventory, the width and height fields in the
BidRequest.AdSlot
now describe the video player. This update to Authorized Buyers Video beta enables you to target video impressions by player size.
Coming Soon
- Bulk location targeting in the UI
- A new bulk upload tool for locations, which can make location targeting strategies more powerful, is gradually being rolled out as part of the Authorized Buyers UI.
GDN
to replaceGCN
as the permitted value in theseller_network
field- Beginning June 1, 2012, the
BidRequest
will send a value ofGDN
in theseller_network
field, replacing the value ofGCN
that is sent today. Wherever your bidder uses theseller_network
field, review and if necessary adapt your code to ensure that the value change does not cause problems. - AdGroup ID to be required when a
BidRequest
has multiple ad groups - Beginning July 2, 2012, the
BidResponse
must include thebilling_id
field when responding to any bid request that has multiple ad groups. Here's how you can tell when a bid request has multiple ad groups: look for multiplematching_ad_data
fields (sub-messages). Because eachmatching_ad_data
field contains exactly one ad group, the presence of multiplematching_ad_data
fields always means that there are multiple ad groups.
When this change takes effect, the current requirement (which is that the bid response must include thebilling_id
field whenever the bidder uses hosted creatives or merged streams) will be obsolete.
November 30, 2010 Release
- There is a new field in the
BidRequest
calledcookie_age_seconds
. When set, this indicates how long ago the cookie used in thegoogle_user_id
was created. - There is a new field in the
BidRequest.AdSlot.MatchingAdData
calledper_buyer_minimum_cpm
. When set to true, this field indicates that the publisher has set a minimum CPM specific to the pretargeting adgroup's account. - You can now optionally serve hosted creatives rather than returning an ad in the form of an HTML snippet. Refer to Building the Response for more details.
- New support for separate and consolidated streams facilitates buying through one or more DSPs from a separate Authorized Buyers account. Refer to the Bidding on Behalf of Multiple Accounts for more details.
September 14, 2010 Release
- There is now a campaign setting in the UI that is used instead of the
adxrtb.com
URL to mark a campaign and all of its adgroups for pretargeting. Theadxrtb.com
URL will continue to work for now until we have migrated all existing campaigns to use the new setting. Placeholder ads are still required in pretargeting adgroups that use the new setting, and these still require that a destination URL be specified. However, you can now optionally use a real URL that corresponds to the placeholder ad in the HTML snippet. The other option is to continue to use theadxrtb.com
URL for the placeholder ad, but realize that the campaign setting is also needed. Note that pretargeting and non-pretargeting adgroups cannot exist in the same campaign when using the campaign setting. - Automated reports are now available that contain information to help you understand the performance of your bidder. These reports are emailed to an address that you provide approximately every hour on the hour. Talk to your technical account manager if you want to enable these reports.
June 17, 2010 Release
- HTTPS support has been added to the cookie matching service. You can now make a request to cm.g.doubleclick.net using HTTPS rather than HTTP. In this case, the redirect will go to the same configured URL, but also use HTTPS rather than HTTP.
- There is a new field
timezone_offset
in theBidRequest
that indicates detected timezone of the user's browser when available. Download the newest version ofrealtime-bidding.proto
from the Downloads page, read the comments on the new field, and make any required updates to your application. - We are adding more review and verification steps for ads served through RTB. To ensure that your ads get approved for serving in a timely manner, make sure that they are able to render properly for an extended time after the original impression. Anomalies or inconsistencies may sometimes lead to long delays or disapprovals.
April 14, 2010 Release
- Above the fold information is now available in the new
slot_visibility
field. The new protocol buffer definition is available on the Downloads page. - We will be transitioning gradually to a new vertical taxonomy over the coming months. The new taxonomy file is available on the Downloads page and a new field,
vertical_dictionary_version
, has been added to theBidRequest
that will indicate when the new taxonomy is used. - There is now support for inserting the value of the
google_user_id
field from theBidRequest
into the bid URL. This can be done using theGOOGLE_USER_ID
macro, see Bid URL Macros for information. - As a reminder, you should always return a valid
BidResponse
with atprotocol_version
andprocessing_time_ms
set for requests that have theis_ping
field set in theBidRequest
. This will help us track locations that can reach your bidder and make ongoing configuration adjustments.
March 10, 2010 Release
Authorized Buyers is pleased to announce a new enhancement that will significantly increase the amount of inventory available to Real-time bidder buyers. Publisher inventory which restricts ads belonging to one or more “sensitive categories” (for example, politics, dating, religion, weight loss) is now available through RTB. In order to comply with publisher restrictions, Google will classify buyer’s ads based on the content of the landing page. This classification will be done every time a new ad landing page is detected, at 10 minute intervals. As a result, new ads may not be eligible for delivery for a short duration while the ad is classified.
In conjunction with the Google Content Network, Authorized Buyers is announcing a new feature that allows buyers to now filter out "below the fold" inventory on GCN sites. The new filter gives you the ability to show ads only in places that appear on the user's screen when the page loads, without requiring them to scroll down. Google has implemented a statistically driven solution to determine which ads are above and below the fold. The statistically driven model only considers ads "above the fold" if they are completely on-screen when the browser window loads. Our goal with this release is to give advertisers greater control over where their ads appear, and make the Google Content Network an even more powerful, controlled environment for running high performing brand campaigns.
Buyers using the RTB solution can exclude below the fold inventory in the user interface. In addition to this filtering functionality, each bid request will include an indication of the ad unit location – above the fold, below the fold, or unknown. You may use this data to assist calculating your bid. The information is in the new slot_visibility
field in the BidRequest
. You can find the updated protocol buffer definition on the Downloads page.
In addition, we've made the following changes:
- Frequency capping settings on pretargeting campaigns are now respected in deciding whether to send bid requests. Previously, any such settings made in the UI were ignored.
- We are now able to send requests to bidders located in Europe. This is available to new customers with the usual testing process. No further testing is needed if you are already doing bidding from other locations and also have servers in Europe. In that case, ask your technical account manager about configuring quota.
- Inventory from publishers that use category exclusions is now eligible for real-time bidding. You need to declare categories in a BidResponse when you bid on this inventory. Otherwise the bids will be dropped.
- The system now sends a small number of
BidRequests
with theis_ping
field set to true - The requester script has been updated in several ways to:
- Keep HTTP connections open
- Populate all new fields introduced over the last few releases
- Optionally allow you to specify the set of
google_user_ids
to send inBidRequests
- Send 1% of requests with
is_ping
true
- There is an updated version of
vendors.txt
available on the Downloads page. - At this time, you still need to ask your technical account manager to make quota adjustments. If you want to increase traffic, contact your technical account manager to request an increase.
February 24, 2010 Release
There are two publisher_settings_list_id
fields added
to the BidRequest
. One is at the page level and one is at
the slot level. Both pass values that can be used as keys to look up
entries in publisher restrictions lists. For more information, contact
your Technical Account Manager.
There is a new seller_network
field in the BidRequest
. For non-anonymous inventory (for example, inventory for which the url field is set), this is filled in with the name of the network selling the impression. For example, all inventory from the Google Content Network will have this field filled in with the value "GCN".
The account-level setting mentioned in the January 27, 2010 release notes is now active. Review the description in the previous notes and contact your account manager if you want to change the setting.
A new vendor.txt file is available on the Downloads page. It lists more vendors than the previous version. All IDs from the previous version are still valid.
There is a new category field in the BidResponse
. Read the comments on that field and the excluded_category
field in the BidResponse
for instructions on how to use this new feature. There is also a new ad-categories.txt
file on the Downloads page with updated category codes.
Make sure to use the latest version of the requester tool from the Downloads page for testing before releasing any changes to your bidder.
As a reminder, make sure you declare all URLs for ads correctly in the click_through_url
field of the BidResponse
, as described in the Declare click-through URLs in ads help center article. Note that you must include the full protocol of the URL (for example, http://www.example.com rather than www.example.com).
January 27, 2010 Release
The realtime-bidding.proto
has several new fields, and some fields have been deprecated. Download the newest version, read the comments on any fields that have changed, and make any required updates to your application.
We encourage you to obtain the latest version of the requester.tar.gz program and use it for testing every time you make a change to your bidding program.
Per-region bid URLs are now supported. Contact us if you want to configure a different URL in each region (for example, one on the West coast and one on the East coast).
In the next release, we'll be adding an account-level setting to specify a preference for impressions to be sent either anonymous or branded in cases where there is a choice. Anonymous impressions will often have lower minimum CPM thresholds set by the seller, but will have an anonymous ID rather than a site URL; branded impressions will have a site URL, but may have a higher minimum CPM threshold. The default setting for the preference will be branded. Contact us if you want this setting to differ from the default.