So that you can spot a bid that contain an SDK rendered advertising, the quote feedback must include the SDK’s ID recovered from bid request, in addition to the data which will be made by that SDK. The yahoo protocol reveals this through the .sdk_rendered_ad industry, plus the OpenRTB method via Bidresponses.seatbid.bid.ext.sdk_rendered_ad . You can study more info on the SdkRenderedAd information in the Bing and OpenRTB process instructions.
Google requirements discrepancy resolution (Beta)
This particular feature will make certain the quantity of impressions that a change was charged aligns with the few thoughts which can be compensated by yahoo screen & Video 360 (DV360).
By truthfully identifying DV360 impressions that have been supported by Open putting in a bid, Google can then modify for offer spam and billable occasion discrepancies to ensure that you aren’t charged for impressions for which you commonly compensated.
Propagate google_query_id in quote requests
In order to make sure that the number of valid thoughts suits across yahoo demand, the google_query_id need to be propagated as well as from start putting in a bid needs to Google demand systems. This is certainly a prerequisite to Open Bidding discrepancy solution. The current forecasted period of the google_query_id is just about 64 bytes.
Propagate third_party_buyer_token in quote replies
When the Bing need program victories a trade’s inner auction, third_party_buyer_token field must be propagated as it is in bid reaction back once again through the start putting in a bid impact. This permits Bing publisher platforms to determine that winning bid from an unbarred Bidding companion try a bid for yahoo interest in similar perception chance. The present greatest duration of this area is expected are 150 bytes.
To make sure the difference quality relates to offers from Google demand, a trade must propagate yahoo innovative parece, or SIGNIFICANT wrappers). As a result of discrepancy quality, yahoo may invalidate and never invoice for people start putting in a bid impressions that have beenn’t counted by Google requirements systems. Yahoo will occasionally scan innovative markup to ensure that offers with third_party_buyer_token happened to be presented on the behalf of Yahoo need, and not any other consumer.
a trade is needed to upload Google HTML markup as well as, with exchange-specific macro expansions that typically use, and, optionally, additional tracker pixels or programs an exchange usually brings.
Bing is unable to implement difference quality if a trade wraps Yahoo HTML creative into a tag ( program , iframe , or other practices) that consequently load or give Google code.
Matches technical requirement
Within this example, Google (DV360) innovative code from the quote responses try passed verbatim, prepended and appended with an exchange-specific code.
Will not satisfy technical requisite
Inside example, creative code returned by Google was obfuscated into the bid responses supplied by a trade and will not appear verbatim within the quote responses. Google-provided html page might get made by an exchange-provided wrapper in browser.
MASSIVE videos creatives
Becoming entitled to the discrepancy resolution, a change is needed to make use of the soon after ways to populate VASTTagURI in VAST XML answers:
- a trade can preserve the worth of VASTTagURI element as an element of MASSIVE XML data returned by Bing in adm field as it is, with exchange-specific macro expansions that typically pertain.
- DV360 can populate the nurl area with a massive document Address in quote responses to a change. a change may then go the worth of nurl that yahoo (DV360) reacts with in VASTTagURI tag, with exchange-specific macros expanded generally as needed.
Matches technical requirement
Within this sample, Bing (DV360) innovative SIGNIFICANT URI from bid responses is passed verbatim, with an exchange adding their particular SIGNIFICANT celebration and error trackers.
Leave A Comment