Move Google imaginative markup as well as in quote reactions
To destination a quote containing an SDK rendered advertising, your own bid responses must through the SDK’s ID retrieved through the bid demand, also the facts which is made by that SDK. The Bing protocol reveals this via the [].sdk_rendered_ad area, therefore the OpenRTB protocol via quoteimpulse.seatbid[].bid[].ext.sdk_rendered_ad . You can study more info on the SdkRenderedAd content inside the Bing and OpenRTB process instructions.
Google requirements difference quality (Beta)
This particular aspect will make sure that the sheer number of thoughts which is why a change is billed aligns with all the range impressions being compensated by Bing show & videos 360 (DV360).
By precisely pinpointing DV360 thoughts that were supported by Open Bidding, yahoo are able to adjust for post junk e-mail and billable event differences to ensure that you are not billed for thoughts for which you are not paid.
Propagate google_query_id in bid needs
To make certain that the sheer number of good thoughts fits across Bing demand, the google_query_id ought to be
Propagate third_party_buyer_token in bid replies
In case the Google requirements program wins a change’s inner auction, third_party_buyer_token industry needs to be propagated as it is in the bid impulse back once again through start putting in a bid perception. This allows
To make certain that the discrepancy quality relates to estimates from Google need, a change is needed to propagate Google imaginative parece, or VAST wrappers). As a result of the discrepancy resolution, yahoo may invalidate and never charge for anyone Open Bidding impressions that weren’t counted by Google demand networks. Google will occasionally test creative markup to verify that offers with third_party_buyer_token had been presented for Google requirements, rather than any customer.
HTML5 creatives
a trade is needed to send yahoo HTML markup as is, with exchange-specific macro expansions that ordinarily incorporate, and, optionally, additional tracker pixels or programs a trade ordinarily includes.
Google cannot apply difference resolution if a trade wraps Bing HTML artistic into a tag ( software , iframe , or other practices) that consequently load or render Google HTML code.
Suits technical requirement
Inside instance, Bing (DV360) innovative html page from quote reaction is passed verbatim, prepended and appended with an exchange-specific code.
Cannot satisfy technical demands
Within this instance, imaginative html page came back by yahoo is actually obfuscated inside the bid reaction provided by an exchange and does not seem verbatim within the bid feedback. Google-provided code gets rendered by an exchange-provided wrapper within the web browser.
MASSIVE videos creatives
Getting eligible for the difference quality, a change is required to need one of many following methods to populate VASTTagURI in MASSIVE XML reactions:
- a change can maintain the value of VASTTagURI aspect within MASSIVE XML document came back by Bing in adm field as it is, with exchange-specific macro expansions that usually apply.
- DV360 can populate the nurl field with an enormous document URL in bid replies to a trade. an exchange are able to pass the value of nurl that yahoo (DV360) responds within VASTTagURI label, with exchange-specific macros broadened typically as needed.
Suits technical requirement
Contained in this instance, Google (DV360) imaginative SIGNIFICANT URI from quote feedback try passed away verbatim, with an exchange including their particular MASSIVE celebration and mistake trackers.