To be able to setting a bid containing an SDK rendered advertisement, their bid impulse must are the SDK’s ID recovered from the quote demand, along with the data that will be made by that SDK. The yahoo method exposes this via the .sdk_rendered_ad field, in addition to OpenRTB method via Bidreaction.seatbid.bid.ext.sdk_rendered_ad . You can study a lot more about the SdkRenderedAd information from inside the Google and OpenRTB process guides.
Google need discrepancy solution (Beta)
This particular aspect aims to make certain that the sheer number of thoughts which is why a trade is billed aligns with all the many thoughts being paid by Google show & movie 360 (DV360).
By correctly identifying DV360 thoughts that were served by start putting in a bid, Bing may then change for offer junk e-mail and billable show differences to ensure that you are not charged for impressions that you can are not settled.
Propagate google_query_id in quote demands
To be able to guarantee that how many valid impressions suits across yahoo need, the google_query_id should be propagated as well as from start putting in a bid requests to Google need systems. It is a prerequisite to Open Bidding difference solution. The present expected duration of the google_query_id is about 64 bytes.
Propagate third_party_buyer_token in quote answers
In the event that the Bing demand system victories an exchange’s internal public auction, third_party_buyer_token area need to be propagated as it is into the quote impulse right back through Open Bidding impression. This allows yahoo writer systems to determine your winning quote from an unbarred Bidding spouse is a bid for Bing need for similar feeling opportunity. The present greatest length of this industry is expected are 150 bytes.
To be able to make sure that the difference solution applies to bids from Google demand, a trade is required to propagate yahoo imaginative es, or SIGNIFICANT wrappers). As a result of difference quality, yahoo may invalidate rather than charge pertaining to anyone start putting in a bid thoughts that weren’t mentioned by Google need platforms. Bing will periodically examine creative markup to verify that offers with third_party_buyer_token were provided with respect to Bing demand, and never every other buyer.
a change must distribute Google HTML markup as well as, with exchange-specific macro expansions that generally pertain, and, optionally, additional tracker pixels or programs a trade normally includes.
Bing is unable to incorporate difference quality if a trade wraps Bing HTML artistic into a label ( software , iframe , or other tips) that consequently load or make Google code.
Joins technical specifications
Inside example, Google (DV360) innovative HTML code from quote response is passed away verbatim, prepended and appended with an exchange-specific html page.
Does not fulfill technical needs
In this instance, imaginative HTML code returned by Bing was obfuscated during the bid impulse supplied by an exchange and will not look verbatim within the bid response. Google-provided code gets rendered by an exchange-provided wrapper inside internet browser.
MASSIVE videos creatives
To be qualified to receive the difference solution, a change is needed to utilize among the many appropriate solutions to populate VASTTagURI in MASSIVE XML reactions:
- a trade can maintain the worth of VASTTagURI element included in VAST XML document came back by Google in adm field as is, with exchange-specific macro expansions that generally incorporate.
- DV360 can populate the nurl area with a massive data URL in bid feedback to an exchange. an exchange are able to move the value of nurl that yahoo (DV360) responds within VASTTagURI tag, with exchange-specific macros expanded generally as needed.
Touches technical criteria
Contained in this instance, Bing (DV360) innovative MASSIVE URI from bid responses was passed verbatim, with an exchange incorporating the certain SIGNIFICANT show and error trackers.