Yandex SDK bidding
Yandex SDK bidding is the Open Bidding integration for apps that use the Yandex Mobile Ads SDK on Android and iOS. Ad unit IDs come from the Yandex Advertising Network, and the bid is tied to a bidder token the SDK produces. It is not Yandex's general DSP protocol.
Direction and version
A mediation or auction server sends a request carrying the Yandex SDK bidder token to Yandex's server-to-server endpoint, and Yandex returns one bid whose signal data goes back to the client SDK.
OpenRTB 2.5 JSON with integer flags. Native requests are JSON strings, and the response cur is a single string.
The RTBlint profile yandex-sdk-bidding checks requests and responses against the published contract.
Rules beyond the OpenRTB spec
- Requests need
appwithbundle,devicewithuaandip,user,tmax, and a non-emptycur. - The SDK bidder token goes in
user.data[].segment[].signaland must be non-empty. - The first impression needs
imp.tagidandimp.ext.ad_type. - Yandex considers only the first impression, and the response must reference it.
- A response has exactly one
seatbidwith exactly one bid. Itsbid.ext.signaldatastays opaque, because the client SDK consumes it. ${AUCTION_LOSS}is substituted only inlurl, and${AUCTION_MIN_TO_WIN}only innurlorlurl.- Fullscreen and native examples omit ordinary media objects, so an impression may carry only the SDK envelope.
- Requests with
testset to 1 are not charged.
Documented extensions
| Path | Meaning |
|---|---|
imp.ext.ad_type | SDK ad format: banner, interstitial, rewarded, appopenad, or native. |
regs.ext.consent | User consent, 0 or 1. |
regs.ext.tcf_consent_string | TCF consent string in URL-safe base64. |
bid.ext.signaldata | JSON string the client passes back to the SDK for rendering. |
What the validator checks for this profile
openrtb.profile.yandex.ad_typeYandex SDK ad type must be banner, interstitial, rewarded, appopenad, or native.openrtb.profile.yandex.bidder_tokenYandex SDK Open Bidding requires the SDK bidder token in user.data[].segment[].signal.openrtb.profile.yandex.currency_offerYandex SDK Open Bidding needs a supported request currency.openrtb.profile.yandex.ignored_impressionsYandex SDK Open Bidding considers only the first impression.openrtb.profile.yandex.impression_mismatchYandex SDK Open Bidding responses must reference the first offered impression.openrtb.profile.yandex.macro_contextYandex substitutes AUCTION_LOSS only in lurl and AUCTION_MIN_TO_WIN only in nurl or lurl.openrtb.profile.yandex.response_countA Yandex SDK Open Bidding response contains one SeatBid and one bid.
Validate against this contract
Open the tester with the Yandex SDK bidding profile, or run:
rtblint validate --profile yandex-sdk-bidding request.json
Similar integrations
- Adform OpenRTB handler
- AppLovin ALX DSP response
- BidSwitch buyer 5.7
- Digital Turbine Exchange
- Display & Video 360
- Equativ bidder contract
- Google Authorized Buyers
- Index Exchange DSP
- InMobi DSP
- Magnite DV+ xAPI
- Microsoft Monetize bidder
- MobileFuse in-app bidding
- MobileFuse SDK bidding
- Sovrn request
- Unity Exchange
- Vungle Exchange