Skip to content

OpenRTB bidding

Elo bids on native ad inventory over OpenRTB. A supply partner sends Elo a bid request for one native ad, and Elo answers with a bid for one of its campaigns, or with no bid. These pages describe one contract that is the same for every partner.

  • One native ad per request. Elo reads the first impression (imp[0]) of an OpenRTB 2.6 bid request, and that impression must carry a Native 1.2 request. Banner, video and audio impressions are not supported.
  • Chat inventory. Elo matches campaigns to the context of the request: keywords, intent, categories and content titles. Inventory with clear context, such as a conversation in an AI chat app, gets the best matches. Send it in the standard fields or in imp[0].ext.elo. See Context.
  • First-price auction. Elo bids the price it is willing to pay. A clearing price above the bid counts as the bid.
  • USD. Bids, floors and clearing prices are CPMs in US dollars.
User's device your publisher's app or site Your platform SSP or exchange Elo api.elo.ad 1 POST /v1/rtb/bid bid request, publisher API key Elo matches the context and prices its bid 2 200 bid or 204 no bid price, adm, nurl, burl, lurl Your auction Elo wins 3 GET nurl ${AUCTION_PRICE} 4 Show the ad from adm 5 GET impression pixel 6 GET burl viewable impression, billed 7 GET click link the user taps the ad 8 307 to the advertiser Elo loses 9 GET lurl ${AUCTION_LOSS}
  1. Your server sends a bid request with your publisher API key.
  2. Elo answers with a bid response, or 204 for no bid.
  3. When Elo’s bid wins your auction, your server calls nurl.
  4. You show the ad, built from the Native 1.2 response in adm.
  5. The user’s device loads the impression pixel from adm.eventtrackers.
  6. Your server calls burl when the impression is viewable. This is the impression Elo pays for. See Notices and billing.
  7. When the user taps the ad, the device opens the click link in adm.link.url.
  8. Elo redirects the device to the advertiser.
  9. When Elo’s bid loses, your server calls lurl with the loss reason.

Elo answers within your tmax less 200 ms, and in at most about 800 ms when tmax is longer or not set. A request Elo cannot price in that time gets 204.

  1. Sign up as a publisher in the Elo dashboard and create a publisher API key in its settings. You send it as Authorization: Bearer on every request.
  2. Send test requests with test: 1. Each one gets a bid for the test ad, which is never billed. They work as soon as you have a key.
  3. Contact Elo at contact@elo.ad. Send your publisher ID, the requests per second you expect, and a sample bid request. If you keep context in an imp.ext object of your own instead of imp.ext.elo, tell us its name.
  4. Elo turns bidding on for your publisher and gives you your request rate limit. Until then, only test requests get a bid.
  5. Once your test requests and notices work, switch to live traffic.
SettingWho sets itDefault
EndpointEloPOST https://api.elo.ad/v1/rtb/bid for every partner
AuthenticationYou, in the dashboardYour publisher API key, elo_pub_...
Request rate limitEloAgreed at onboarding
Context objectEloimp[0].ext.elo, plus your own object if you have one