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 in device.ip or device.ipv6, and imp.tagid. Each address must match its IP family.
  • at, when sent, must be 1 (first price).
  • tmax must be at least 100 milliseconds.
  • badv may 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 mimes may be omitted, which means any type is acceptable.

Documented extensions

PathMeaning
device.ext.ifviOS identifier for vendors.
device.ext.attsApp Tracking Transparency status, 0 to 3.
source.ext.omidpnOpen Measurement partner name; source.ext.omidpv carries the version.
regs.ext.gppGPP string in its legacy location, with section IDs in regs.ext.gpp_sid.
regs.ext.us_privacyUS Privacy string in its legacy location.
user.ext.consentTCF consent string in its legacy location.
user.ext.hemsHashed email objects with hem and hem_type.
bid.ext.mfMobileFuse event strings for render, cache, and SDK click tracking.

What the validator checks for this profile

Validate against this contract

Open the tester with the MobileFuse in-app bidding profile, or run:

rtblint validate --profile mobilefuse request.json

Similar integrations