To be able to put a quote containing an SDK rendered advertisement, the bid reaction must range from the SDK’s ID retrieved from the bid demand, along with the data which is rendered by that SDK. The Bing method exposes this through the .sdk_rendered_ad field, and also the OpenRTB method via Bidreaction.seatbid.bid.ext.sdk_rendered_ad . You can study more info on the SdkRenderedAd content in yahoo and OpenRTB protocol books.
This feature is designed to ensure that the quantity of impressions which is why a trade is actually charged aligns with the few thoughts which happen to be settled by Bing Display & Video 360 (DV360).
By precisely pinpointing DV360 impressions which were offered by start putting in a bid, Google are able to modify for post junk e-mail and billable show discrepancies to make sure you commonly billed for thoughts that you aren’t paid.
In order to guarantee that the number of legitimate impressions fits across yahoo need, the google_query_id need to be propagated as it is from Open putting in a bid needs to Google need systems. This is certainly a prerequisite to Open Bidding discrepancy solution. The present forecasted length of the google_query_id is approximately 64 bytes.
In the event that the Google need system wins a trade’s interior public auction, third_party_buyer_token area need to be propagated as well as inside the quote responses right back through the Open Bidding perception. This permits Google author systems to determine the winning bid from an Open putting in a bid partner is a bid on the behalf of yahoo interest in similar impression chance. The current optimum length of this area is expected to-be 150 bytes.
To be able to make sure the difference resolution pertains to estimates from Google requirements, an exchange is needed to propagate yahoo innovative parece, or SIGNIFICANT wrappers). Because of the difference resolution, Bing may invalidate rather than invoice for those start putting in a bid impressions that have beenn’t mentioned by Google demand programs. Google will periodically scan creative markup to ensure that offers with third_party_buyer_token had been submitted for Yahoo demand, rather than other consumer.
a trade must submit Google HTML markup as it is, with exchange-specific macro expansions that generally implement, and, optionally, higher tracker pixels or scripts a trade typically contributes.
Google cannot implement difference resolution if a change wraps Google HTML artistic into a label ( program , iframe , or any other practices) that consequently load or make Google HTML code.
Inside example, yahoo (DV360) creative HTML code from the bid responses try passed away verbatim, prepended and appended with an exchange-specific code.
Inside instance, imaginative html page returned by Bing are obfuscated in quote responses supplied by a trade and does not look verbatim in the bid response. Google-provided html page might get made by an exchange-provided wrapper inside web browser.
To-be entitled to the difference solution, a trade is needed to use one of several appropriate methods to populate VASTTagURI in VAST XML replies:
Within instance, Google (DV360) imaginative VAST URI from the bid feedback are passed verbatim, with a trade incorporating its certain MASSIVE event and mistake trackers.