MobileFuse in-app bidding
MobileFuse is a mobile advertising company that buys in-app supply over OpenRTB. This profile covers app supply sent to MobileFuse and MobileFuse's bid responses. SDK bidding with a MobileFuse token is the separate mobilefuse-sdk profile.
Direction and version
App publishers and supply partners send bid requests to MobileFuse, and MobileFuse returns bid responses.
OpenRTB 2.x JSON, checked against the 2.6 field catalog. Native requests may arrive as an object or as an encoded JSON string, and MobileFuse expects Native 1.2.
The RTBlint profile mobilefuse checks requests and responses against the published contract.
Rules beyond the OpenRTB spec
- Requests need
app.bundle,device.ua, a device address indevice.ipordevice.ipv6, andimp.tagid. Each address must match its IP family. at, when sent, must be 1 (first price).tmaxmust be at least 100 milliseconds.badvmay list at most 50 blocked advertiser domains.- MobileFuse processes only the first impression and ignores the rest, so a bid that references a later impression does not count. One impression may still offer several media formats.
- Bid responses are in USD.
- Video
mimesmay be omitted, which means any type is acceptable.
Documented extensions
| Path | Meaning |
|---|---|
device.ext.ifv | iOS identifier for vendors. |
device.ext.atts | App Tracking Transparency status, 0 to 3. |
source.ext.omidpn | Open Measurement partner name; source.ext.omidpv carries the version. |
regs.ext.gpp | GPP string in its legacy location, with section IDs in regs.ext.gpp_sid. |
regs.ext.us_privacy | US Privacy string in its legacy location. |
user.ext.consent | TCF consent string in its legacy location. |
user.ext.hems | Hashed email objects with hem and hem_type. |
bid.ext.mf | MobileFuse event strings for render, cache, and SDK click tracking. |
What the validator checks for this profile
openrtb.profile.mobilefuse.badv_limitMobileFuse supports at most 50 blocked advertiser domains.openrtb.profile.mobilefuse.bid_for_ignored_impMobileFuse documents processing only the first impression; this bid references a later impression.openrtb.profile.mobilefuse.currencyMobileFuse auctions use USD.openrtb.profile.mobilefuse.device_address_invalidThe address must use the documented IP family.openrtb.profile.mobilefuse.device_address_requiredMobileFuse requires ip or ipv6.openrtb.profile.mobilefuse.native_versionMobileFuse expects Native Ads 1.2.openrtb.profile.mobilefuse.tmax_minimumMobileFuse tmax must be at least 100 milliseconds.
Validate against this contract
Open the tester with the MobileFuse in-app bidding profile, or run:
rtblint validate --profile mobilefuse 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 SDK bidding
- Sovrn request
- Unity Exchange
- Vungle Exchange
- Yandex SDK bidding