This page gives an overview of steps you need to take, either as an ad ops user or as a developer, to start using Prebid Mobile.
Before you begin using Prebid Mobile in your apps, you need to prepare your end-to-end system. The first step is to set up your Prebid Server host. Prebid Mobile works in conjunction with Prebid Server to request and receive bids. Here are the options:
Prebid Server is an open source project. This allows you to host your own implementation of Prebid Server, though it’s not as easy as downloading Prebid.js, because it needs to be hosted. The source code is available for Prebid Server Go and Prebid Server Java.
See the Prebid Server documentation for more information on setting up your own server host.
Several pages and examples in the mobile documentation refer to entering your “Prebid Server Account ID”.
In actuality, an account ID is just the name of the “top-level” stored request as described on the Prebid Server Stored Request page.
By convention, most Prebid Server host companies define the top level stored request ID as the account ID they assign to the publisher. This is a convenient convention since publishers generally set the same timeout and price granularity across all apps. But it may not be the case for your Prebid Server host company, so please check with them. If you’re hosting your own Prebid Server, this value can be whatever value you wish, not necessarily an account ID.
After you’ve registered with your chosen Prebid Server host, you need to create at least one Prebid Server bidder configuration in a stored request. Each stored request configuration contains a list of bidders and their parameters. The configuration will be in the form of a JSON structure, similar to this:
[
{
"bidder": "appnexus",
"params": {
"placementId": 13144370
}
}
]
The preceding is an example “impression-level stored request” using AppNexus as the bidder. The parameters you need to set differ for each bidder. See Bidder Parameters for a full list of parameters for available Prebid Server bidders.
Each block of JSON like this is called a “stored request” and gets an ID called a “stored request ID”. This ID is then programmed into an adslot using the iOS or Android SDKs. Doing it this way allows the publisher to change bidders and parameters without having to change the app.
Ad ops users configure the primary ad server with Prebid Mobile line items targeted to key/values.
To begin using Prebid Mobile follow the instructions for the respective platforms and integration approach:
The following resources are available for further information on working with Prebid Mobile:
Learn about the parameters available in the Prebid SDK
Prebid Mobile provides APIs for app publishers in support of the IAB Europe Transparency & Consent Framework.
For general information on these APIs see Prebid Mobile Guide to Privacy Regulation.