Overview
Although OpenRTB is the desired implementation method, it is possible to access MobileFuse demand using a client-side VAST tag. A video tag looks like the following. You should be sure to set up your ad server to replace the macros with relevant values.
https://mfx.mobilefuse.com/video?id=000000&w=320&h=480&bundle=${BUNDLE}&ifa=${IFA}&lat=${LATITUDE}&lon=${LONGITUDE}&lltype=${LAT_LON_TYPE}&pos=${POS}&apis=${APIS}&mimes=${MIME_TYPES}&protocols=${PROTOCOLS}&schain=${SUPPLY_CHAIN}&pchain=${PAY_ID}&age=${AGE}&gender=${GENDER}&us_privacy=${US_PRIVACY}&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_909}&cb=${CACHEBUSTER}
Parameters
All parameters should be URL encoded where necessary. If you are unable to provide a parameter, you should remove it from the tag. IP and User Agent macros are not needed as the information will be detected from the headers. Items marked with an asterisk are highly recommended to maximize earning potential.
Field | Required | Description |
---|---|---|
id | Yes | MobileFuse-provided ID for this ad unit |
w | Yes | Width in pixels |
h | Yes | Height in pixels |
bundle | Yes | On Android, this should be a bundle or package name (e.g., com.foo.mygame). On iOS, it should be a numeric ID. |
ifa | No* | Identifier For Advertisers (aka IDFA) |
ifv | No* | Identifier For Vendors (aka IDFV) |
lat | No* | Latitude expressed as a float |
lon | No* | Longitude expressed as a float |
lltype | No* | Lat/Lon type, ie. how was lat/lon collected?
|
pos | No | Position of ad in the viewport
|
schain | Yes, if not a direct publisher | The serialized form of the supply chain object. Only required if the publisher’s relationship with MobileFuse is not direct. |
pchain | string | Payment ID chain string containing embedded syntax described in the TAG Payment ID Protocol v1.0. |
instl | No | Whether this ad unit is within an interstitial or not
|
age | No* | Age or year of birth of user (eg. 51, 24, 1988, 1957) |
gender | No* | Gender of user. Lowercase values will work as well
|
dnt | No | Do not track (or limit ad tracking, since we treat both the same way)
|
us_privacy | No | US privacy string, required jurisdictions where legally enforced |
gdpr | No | GDPR applies (1 or 0), required in jurisdictions where legally enforced |
gdpr_consent | No | TCF2 GDPR consent string, required in jurisdictions where legally enforced |
ctx | No | Type of content (game, video, text, etc.).
|
test | No | Indicator of test mode in which auctions are not billable
|
mimes | No* | Comma separated list of the player’s supported mime types (eg. video/mp4) |
minduration | No | Minimum duration allowed in seconds |
maxduration | No | Maximum duration allowed in seconds |
minbitrate | No | Minimum bitrate allowed in Kbps |
maxbitrate | No | Maximum bitrate allowed in Kbps |
protocols | No* | Comma separated list of supported video protocol IDs
|
apis | No* | Comma separated list of supported video API IDs
|
playbackmethod | No | Playback method that is used, if none is specified, any may be used:
|
startdelay | No | Indicates the start delay in seconds for pre-roll, mid-roll, or post-roll:
|
placement | No | Placement type for the impression:
|
cb | No | Recommended to ensure requests are not cached by client |