Being place a quote that contain an SDK rendered advertising, the bid response must are the SDK’s ID recovered from the quote consult, also the information that will be rendered by that SDK. The Bing protocol reveals this through the [].sdk_rendered_ad area, plus the OpenRTB method via Bidreaction.seatbid[].bid[].ext.sdk_rendered_ad . You can study more and more the SdkRenderedAd content in the yahoo and OpenRTB process guides.
Google requirements difference resolution (Beta)
This particular aspect aims to guarantee that the number of thoughts which is why an exchange is actually billed aligns using quantity of impressions being settled by yahoo screen & video clip 360 (DV360).
By accurately identifying DV360 impressions that were served by Open putting in a bid, Google may then modify for post junk e-mail and billable celebration discrepancies to ensure that you are not billed for impressions for which you commonly paid.
Propagate google_query_id in bid desires
Being ensure that the quantity of appropriate thoughts matches across Google need, the google_query_id need to be propagated as well as from Open Bidding needs to Google requirements networks. This might be a prerequisite to Open Bidding discrepancy quality. Current expected amount of the google_query_id is about 64 bytes.
Propagate third_party_buyer_token in bid responses
When the Google need system victories an exchange’s internal public auction, third_party_buyer_token industry need to be propagated as is click the link now inside quote feedback straight back through the Open Bidding impression. This enables Google writer platforms to determine that the winning quote from an unbarred Bidding spouse are a bid with respect to Bing demand for the exact same impression chance. The existing greatest amount of this industry is anticipated getting 150 bytes.
To make certain that the difference solution pertains to bids from Google requirements, a change must propagate Bing imaginative parece, or SIGNIFICANT wrappers). Due to the difference quality, Bing may invalidate rather than charge pertaining to anyone Open putting in a bid thoughts which weren’t counted by Google demand programs. Bing will occasionally test imaginative markup to verify that estimates with third_party_buyer_token comprise submitted on the part of Yahoo requirements, and never any purchaser.
HTML5 creatives
a trade must upload Google HTML markup as it is, with exchange-specific macro expansions that generally incorporate, and, optionally, further tracker pixels or programs a change normally includes.
Google cannot implement difference resolution if a change wraps Bing HTML artistic into a tag ( software , iframe , or any other method) that consequently load or render Google HTML code.
Meets technical requirements
Inside example, Bing (DV360) imaginative html page through the quote impulse are passed verbatim, prepended and appended with an exchange-specific code.
Does not meet technical requirements
Within instance, imaginative code returned by Google was obfuscated inside quote responses offered by an exchange and will not appear verbatim inside bid impulse. Google-provided code could get made by an exchange-provided wrapper for the internet browser.
MASSIVE video clip creatives
Becoming qualified to receive the difference solution, a trade is required to incorporate among the after approaches to populate VASTTagURI in MASSIVE XML reactions:
- a trade can conserve the worth of VASTTagURI element as part of MASSIVE XML document came back by Bing in adm industry as is, with exchange-specific macro expansions that ordinarily apply.
- DV360 can populate the nurl industry with a massive document Address in quote replies to a trade. an exchange can then go the worth of nurl that Google (DV360) responds within VASTTagURI label, with exchange-specific macros widened generally as required.
Satisfies technical criteria
In this example, Google (DV360) creative MASSIVE URI through the bid reaction was passed away verbatim, with a trade incorporating the particular VAST occasion and mistake trackers.
