Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

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, if not using size

Width in pixels

h

Yes, if not using size

Height in pixels

size

Yes, if not using w & h

Width in height in the form of wxh, eg. 320x50

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?

  • 1 = GPS/Location Services

  • 2 = IP Address

  • 3 = User provided (eg. registration data)

pos

No

Position of ad in the viewport

  • 0 = Unknown

  • 1 = Above Fold

  • 3 = Below Fold

  • 7 = Fullscreen

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

  • 0 = No

  • 1 = Yes

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

  • M = Male

  • F = Female

  • O = Other

dnt

No

Do not track (or limit ad tracking, since we treat both the same way)

  • 0 = No

  • 1 = Yes

us_privacy

No

US privacy string, required jurisdictions where legally enforced
https://github.com/InteractiveAdvertisingBureau/USPrivacy/blob/master/CCPA/US%20Privacy%20String.md

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

coppa

No

Boolean to specify if the transaction is subject to COPPA or not

  • 0 = No

  • 1 = Yes

title

No

Content title (e.g. Search Committee)

series

No

Content series (e.g. The Office)

genre

No

Genre that best describes the content

len

No

Length of content in seconds

ctx

No

Type of content (game, video, text, etc.).

  • 1 = Video

  • 2 = Game

  • 3 = Music

  • 4 = Application

  • 5 = Text

  • 6 = Other

  • 7 = Unknown

test

No

Indicator of test mode in which auctions are not billable

  • 0 = Live

  • 1 = Test

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

  • 1 = VAST 1.0

  • 2 = VAST 2.0

  • 3 = VAST 3.0

  • 4 = VAST 1.0 Wrapper

  • 5 = VAST 2.0 Wrapper

  • 6 = VAST 3.0 Wrapper

  • 7 = VAST 4.0

  • 8 = VAST 4.0 Wrapper

  • 9 = DAAST 1.0

  • 10 = DAAST 1.0 Wrapper

apis

No*

Comma separated list of supported video API IDs

  • 1 = VPAID 1.0

  • 2 = VPAID 2.0

  • 3 = MRAID-1

  • 4 = ORMMA

  • 5 = MRAID-2

  • 6 = MRAID-3

  • 7 = OMID-1

playbackmethod

No

Playback method that is used, if none is specified, any may be used:

  • 1 = Initiates on Page Load with Sound On

  • 2 = Initiates on Page Load with Sound Off by Default

  • 3 = Initiates on Click with Sound On

  • 4 = Initiates on Mouse-Over with Sound On

  • 5 = Initiates on Entering Viewport with Sound On

  • 6 = Initiates on Entering Viewport with Sound Off by Default

startdelay

No

Indicates the start delay in seconds for pre-roll, mid-roll, or post-roll:

  • Value > 0 = Mid-Roll (value indicates start delay in second)

  • 0 = Pre-Roll

  • -1 = Generic Mid-Roll

  • -2 = Generic Post-Roll

placement

No

Placement type for the impression:

  • 1 = In-Stream

  • 2 = In-Banner

  • 3 = In-Article

  • 4 = In-Feed

  • 5 = Interstitial

cb

No

Recommended to ensure requests are not cached by client

  • No labels