You are here: Developers > OpenX Bidder for Apps Android > Data enrichment

Data enrichment

Last updated on May 31, 2017

Whether you are using QueuedBidderManager or BidderManager, you need to create and configure an AdCallParams instance to set additional data for the ad requestCommunication from a web browser or app to an ad server to display an ad.. Setting this data provides more information to buyers, which can help increase revenue by increasing the value of impressions to buyers.

Details on the AdCallParams object:

Property

Type

Description

isInterstitial

Boolean

Whether or not this ad will be presented as an interstitialA full-screen ad displayed in content transitions. For example, a video ad that loads between levels of a mobile game.. 'true' for interstitial, 'false' for bannerThis is an ad that appears on a web page which is typically hyperlinked to an advertiser’s website. Banners can be images (GIF, JPEG, PNG), JavaScript programs or multimedia objects (For example, Java)..

setAppKeywords

String

Comma-delimited list of keywords describing the app.

Example: Social,Friends,Chat

setFlexAdSize

String

Comma-delimited string of desired ad sizes. For details, see Flexible ad size support.

setUserBirthYear

int

Year of birth of the user as a 4-digit integer.

Example: 1990

setUserGender

Gender

Gender of the user.

Can be one of:

  • MALE
  • FEMALE
  • OTHER

(OTHER means known to be other. It does not mean unknown. For unknown, do not set this property.)

supportsMRAIDVersion1

Boolean

Whether or not your app supports MRAIDMobile Rich Ad Interface Definitions, a type of API framework for interfacing between an ad creative and native mobile capabilities. version 1.0.

supportsMRAIDVersion2

Boolean

Whether or not your app supports MRAID version 2.0.

Next steps

After you have completed your adapter integration, complete the self-test before submitting a build to OpenX for final testing.

See also:

Data enrichment

Bidder for Apps self-testing

Setup checklist

Feedback form