Skip to main content
Version: v1.0.0

Choosing an integration

Prebid can run on its own or next to the ad server you already use. All models share the same configuration, privacy and targeting setup.

Prebid renderingOriginal APIGAM renderingAdMob / MAX mediation
Packageprebid_mobile_sdkprebid_mobile_sdk + google_mobile_adsprebid_mobile_sdk_gamprebid_mobile_sdk_admob / _max
AuctionPrebidPrebid, then GAMPrebid, then GAMPrebid inside the mediation waterfall
RendersPrebid SDKGAM, via the Prebid Universal CreativeGAM or Prebid, through Prebid's event handlersAdMob / MAX, or the Prebid creative through the adapter
Ad server setupNonePrebid line items targeting hb_* keysPrebid line items targeting hb_* keysPrebid as a custom network / custom event
FormatsBanner, interstitial, rewarded, native, videoBanner, interstitial, native, in-stream videoBanner, interstitial, rewarded, nativeBanner, interstitial, rewarded, native
Bundles an ad SDKNoYour app adds google_mobile_adsGoogle Mobile AdsGoogle Mobile Ads / AppLovin MAX

Which one?​

  • No ad server yet, or Prebid-only demand: Prebid rendering. Nothing to configure outside Prebid Server.
  • Already on Google Ad Manager with google_mobile_ads widgets: the Original API. You keep your GAM ad objects and add Prebid's keywords to their requests.
  • On Google Ad Manager, and fine with Prebid's widgets: GAM rendering. The banner, interstitial, rewarded and native widgets handle the GAM request for you.
  • Monetizing through AdMob or AppLovin MAX mediation: the AdMob or MAX companion.

Packages can be combined: an app can render some placements with Prebid and send others through GAM.

Companion packages​

Every companion requires a compatible core package (prebid_mobile_sdk: ^1.0.0 for the 1.x companions: the core package keeps the building blocks they use stable within a major version); the native SDK versions each one bundles are on the Compatibility page.