Nexus extension

Popunder Ads (2.6)

OpenRTB does not define a dedicated popunder object. Nexus identifies the opportunity through the preconfigured account and tagid; do not invent a popunder field in the bid request. The response uses the standard Bid object and Nexus popunder XML in adm.

• Nexus-specific format
• Preconfigured tagid
• instl 1
• One bid per request

Request · imp object

{
  "id": "1",
  "instl": 1,
  "secure": 1,
  "bidfloor": 0.5,
  "bidfloorcur": "USD",
  "tagid": "popunder-zone-778899"
}

Response · bid object

{
  "id": "bid-popunder-1",
  "impid": "1",
  "price": 0.62,
  "adomain": ["advertiser.example"],
  "cid": "campaign-43",
  "crid": "creative-33",
  "mtype": 1,
  "iurl": "https://cdn.advertiser.example/preview.jpg",
  "nurl": "https://bidder.example/win?price=${AUCTION_PRICE}",
  "burl": "https://bidder.example/bill?price=${AUCTION_PRICE}",
  "lurl": "https://bidder.example/loss?code=${AUCTION_LOSS}",
  "adm": "[NEXUS_POPUNDER_XML]"
}

Nexus popunder markup

<?xml version="1.0" encoding="UTF-8"?>
<ad>
  <popunderAd>
    <clickUrl><![CDATA[https://advertiser.example/landing]]></clickUrl>
  </popunderAd>
</ad>

Integration contract: A tag is treated as popunder only after Nexus enables that format for the partner. A generic interstitial request is not automatically a popunder request.