AI Search
New
InMobi Now
提交支持工单
后退

Auction Lifecycle and Supported Macros

Chinese
English
Chinese

Notification URLs (NURL and LURL) let InMobi Exchange inform DSPs of auction outcomes for each bid. They include a win notice with pricing details, or a loss notice with the reason code. 

Auction Lifecycle 

The following flowchart illustrates the lifecycle of a bid submitted to InMobi, from the initial InMobi auction through the downstream mediation auction. It shows the decision points that determine whether a bid progresses to mediation or is eliminated and indicates when Win Notification (NURL) and Loss Notification (LURL) callbacks are triggered. The flowchart also summarizes the values populated in each callback based on the auction outcome. 

Supported Auction Macros

InMobi Exchange supports macro substitution aligned with the OpenRTB API Specification. These macros can be applied within the NURL and LURL during auctions. The table below outlines all macros currently supported by InMobi Exchange.

Macro Description Supported URL (NURL/LURL)
${AUCTION_ID} ID of the bid request from the BidRequest.id attribute. Both NURL and LURL
${AUCTION_BID_ID} ID of the bid; from the BidResponse.bidid attribute.
${AUCTION_IMP_ID} ID of the impression just won, from the imp.id attribute.
${AUCTION_SEAT_ID} ID of the bidder seat for whom the bid was made.
${AUCTION_AD_ID} ID of the ad markup the bidder wishes to serve; from the bid.adid attribute.
${AUCTION_PRICE} Clearing price of the mediation auction, using the same currency and units as the bid.
${AUCTION_CURRENCY} The currency used in the bid (explicit or implied); for confirmation only.
${AUCTION_MIN_TO_WIN}
  • NURL – Minimum bid price required to win the mediation auction for the impression, in the same currency and units as the submitted bid.
  • LURL – Clearing price of the mediation auction, in the same currency and units as the bid.
${AUCTION_LOSS} Loss reason code indicating why a bid did NOT win the auction. See Loss Reason Codes for possible values. LURL only

Note

These macros will be populated at 100% coverage when included in either the NURL or LURL.

IP Address Handling for NURL and LURL

  • Source: Both NURL and LURL are triggered via server-to-server calls from InMobi.
  • IP version: Only IPv4 addresses are supported.
  • Header: The IP address is retrieved from the X-Forwarded-For header (case-insensitive). This value is typically derived from the source address at the network layer and sent as headers.
  • No truncation: Since the IP originates from network-level headers rather than a request field, it is not truncated when firing NURL or LURL.

For IP address handling of BURL, see InMobi BURL: IP and User-Agent Signals.

本页内容

最后更新于 : 19 Aug, 2026
✕

You are almost there...

By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.

I AGREE