To be able to setting a quote containing an SDK rendered ad, your own quote impulse must are the SDK’s ID recovered from the bid consult, also the data which will be made by that SDK. The Google method reveals this via the [].sdk_rendered_ad field, and also the OpenRTB method via Bidresponses.seatbid[].bid[].ext.sdk_rendered_ad . You can discover more and more the SdkRenderedAd information during the Bing and OpenRTB process courses.
Google demand difference resolution (Beta)
This particular aspect aims to make certain that the number of thoughts that a trade are billed aligns making use of the wide range of impressions being paid by Google show & Video 360 (DV360).
By correctly identifying DV360 thoughts which were offered by Open Bidding, yahoo are able to modify for advertisement spam and billable show discrepancies to ensure that you are not charged for thoughts that you aren’t settled.
Propagate google_query_id in quote desires
To make sure that the quantity of legitimate impressions fits across Google need, the google_query_id need to be propagated as is from Open Bidding needs to Google demand programs. This can be a prerequisite to open up Bidding discrepancy solution. The current forecasted amount of the google_query_id is just about 64 bytes.
Propagate third_party_buyer_token in quote replies
In case the Google requirements platform gains a trade’s internal public auction, third_party_buyer_token industry needs to be propagated as is from inside the quote reaction back once again through Open Bidding impression. This enables yahoo manager platforms to determine that winning quote from an Open putting in a bid mate was a bid on the behalf of yahoo demand for equivalent feeling opportunity. The current optimum period of this field is expected getting 150 bytes.
To be able to make certain that the discrepancy solution relates to offers from Google demand, a change is needed to propagate Bing imaginative es, or MASSIVE wrappers). As a result of the discrepancy solution, yahoo may invalidate and not charge for everyone Open Bidding thoughts which weren’t mentioned by Google demand platforms. Google will regularly scan innovative markup to ensure that bids with third_party_buyer_token are published for Google demand, rather than another purchaser.
HTML5 creatives
an exchange is needed to send Google HTML markup as well as, with exchange-specific macro expansions that usually use, and, optionally, extra tracker pixels or programs a change normally brings.
Yahoo is not able to apply discrepancy quality if a change wraps Yahoo HTML artistic into a tag ( program , iframe , or any other practices) that 
afterwards weight or render Google html page.
Suits technical demands
Inside instance, Google (DV360) creative code from bid reaction was passed away verbatim, prepended and appended with an exchange-specific code.
Cannot meet technical needs
Within example, imaginative HTML code returned by Bing is actually obfuscated during the bid responses supplied by an exchange and will not come verbatim in bid response. Google-provided code could get made by an exchange-provided wrapper when you look at the internet browser.
MASSIVE videos creatives
Getting eligible for the difference solution, a trade must use one of the appropriate ways to populate VASTTagURI in VAST XML replies:
- a change can protect the worth of VASTTagURI component included in VAST XML document returned by Bing in adm area as is, with exchange-specific macro expansions that generally implement.
- DV360 can populate the nurl area with a massive document URL in bid reactions to a trade. a change are able to move the value of nurl that Bing (DV360) reacts within VASTTagURI tag, with exchange-specific macros extended usually as required.
Satisfies technical demands
In this instance, Google (DV360) innovative VAST URI from quote impulse is passed away verbatim, with a trade incorporating its certain SIGNIFICANT show and error trackers.