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 app with bundle, device with ua and ip, user, tmax, and a non-empty cur.
  • The SDK bidder token goes in user.data[].segment[].signal and must be non-empty.
  • The first impression needs imp.tagid and imp.ext.ad_type.
  • Yandex considers only the first impression, and the response must reference it.
  • A response has exactly one seatbid with exactly one bid. Its bid.ext.signaldata stays opaque, because the client SDK consumes it.
  • ${AUCTION_LOSS} is substituted only in lurl, and ${AUCTION_MIN_TO_WIN} only in nurl or lurl.
  • Fullscreen and native examples omit ordinary media objects, so an impression may carry only the SDK envelope.
  • Requests with test set to 1 are not charged.

Documented extensions

PathMeaning
imp.ext.ad_typeSDK ad format: banner, interstitial, rewarded, appopenad, or native.
regs.ext.consentUser consent, 0 or 1.
regs.ext.tcf_consent_stringTCF consent string in URL-safe base64.
bid.ext.signaldataJSON string the client passes back to the SDK for rendering.

What the validator checks for this profile

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