The integration of Prebid Mobile with AppLovin MAX assumes that publisher has a MAX account and has integrated the AppLovin MAX SDK into the app.
See the AppLovin MAX Documentation for the MAX integration details.
Steps 1-2 Prebid SDK makes a bid request. Prebid Server runs an auction and returns the winning bid.
Step 3 MAX SDK makes an ad request. MAX returns the waterfall with respective placements.
Step 4 For each Prebid placement, the MAX SDK sequentially instantiates an adapter.
Step 5 The adapter verifies the targeting keywords of the winning bid and the custom properties of the given placement. If they match the adapter will render the winning bid. Otherwise, the adpater will immediately fail with a “no ad” error and the next placement will instantiate the same adapter but for another custom properties.
Prebid SDK is integrated into AppLovin MAX setup thru custom adapters. To integrate Prebid adapters into your app add the following line to your Podfile:
pod 'PrebidMobileMAXAdapters'
Integration example:
// 1. Create MAAdView
adBannerView = MAAdView(adUnitIdentifier: maxAdUnitId)
adBannerView?.delegate = self
// 2. Create MAXMediationBannerUtils
mediationDelegate = MAXMediationBannerUtils(adView: adBannerView!)
// 3. Create MediationBannerAdUnit
adUnit = MediationBannerAdUnit(configID: prebidConfigId,
size: adUnitSize,
mediationDelegate: mediationDelegate!)
// 4. Make a bid request
adUnit?.fetchDemand { [weak self] result in
// 5. Make an ad request to MAX
self?.adBannerView.loadAd()
}
This step is the same as for the original MAX integration. You don’t have to make any modifications here.
The MAXMediationBannerUtils
is a helper class, which performs certain utilty work for the MediationBannerAdUnit
, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
The MediationBannerAdUnit
is a part of the Prebid Mediation API. This class is responsible for making bid request and providing the winning bid and targeting keywords to mediating SDKs.
The fetchDemand
method makes a bid request to Prebid Server and provides a result in a completion handler.
Make a regular MAX’s ad request. Everything else will be handled by prebid adapters.
Integration example:
// 1. Create MAInterstitialAd
interstitial = MAInterstitialAd(adUnitIdentifier: maxAdUnitId)
interstitial.delegate = self
// 2. Create MAXMediationInterstitialUtils
mediationDelegate = MAXMediationInterstitialUtils(interstitialAd: interstitial!)
// 3. Create MediationInterstitialAdUnit
adUnit = MediationInterstitialAdUnit(configId: prebidConfigId,
minSizePercentage: CGSize(width: 30, height: 30),
mediationDelegate: mediationDelegate!)
// 4. Make a bid request
adUnit?.fetchDemand { [weak self] result in
guard let self = self else { return }
guard result == .prebidDemandFetchSuccess else {
self.fetchDemandFailedButton.isEnabled = true
return
}
// 5. Make an ad request to MAX
self.interstitial?.load()
})
The default ad format for interstitial is .banner. In order to make a multiformat bid request
set the respective values in the adFormats
property.
// Make bid request for video ad
adUnit?.adFormats = [.video]
// Make bid request for both video amd banner ads
adUnit?.adFormats = [.video, .banner]
// Make bid request for banner ad (default behaviour)
adUnit?.adFormats = [.banner]
This step is the same as for the original MAX integration. You don’t have to make any modifications here.
The MAXMediationInterstitialUtils
is a helper class, which performs certain utilty work for the MediationInterstitialAdUnit
, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
The MediationInterstitialAdUnit
is a part of the Prebid Mediation API. This class is responsible for making a bid request and providing a winning bid to the mediating SDKs.
The fetchDemand
method makes a bid request to Prebid Server and provides a result in a completion handler.
Now you should make a regular MAX’s ad request. Everything else will be handled by GMA SDK and prebid adapters.
Once you receive the ad it will be ready for display. Follow the MAX instructions for displaying an ad.
Integration example:
// 1. Get an instance of MARewardedAd
rewarded = MARewardedAd.shared(withAdUnitIdentifier: maxAdUnitId)
rewarded.delegate = self
// 2. Create MAXMediationRewardedUtils
mediationDelegate = MAXMediationRewardedUtils(rewardedAd: rewarded!)
// 3. Create MediationRewardedAdUnit
adUnit = MediationRewardedAdUnit(configId: prebidConfigId, mediationDelegate: mediationDelegate!)
// 4. Make a bid request
adUnit?.fetchDemand { [weak self] result in
guard let self = self else { return }
// 5. Make an ad request to MAX
self.rewarded?.load()
}
The process for displaying the rewarded ad is the same as for displaying the Interstitial Ad.
To be notified when a user earns a reward follow the MAX intructions.
This step is the same as for the original MAX integration. You don’t have to make any modifications here.
The MAXMediationRewardedUtils
is a helper class, which performs certain utilty work for the MediationRewardedAdUnit
, like passing the targeting keywords to the adapters.
The MediationRewardedAdUnit
is a part of the Prebid Mediation API. This class is responsible for making a bid request and providing a winning bid and targeting keywords to the adapters.
The fetchDemand
method makes a bid request to the Prebid Server and provides a result in a completion handler.
Make a regular MAX’s ad request. Everything else will be handled by GMA SDK and prebid adapters.
Once the rewarded ad is received you can display it. Follow the MAX instructions for the details.
Integration example:
// 1. Create MANativeAdLoader
nativeAdLoader = MANativeAdLoader(adUnitIdentifier: maxAdUnitId)
nativeAdLoader?.nativeAdDelegate = self
// 2. Create MAXMediationNativeUtils
mediationDelegate = MAXMediationNativeUtils(nativeAdLoader: nativeAdLoader!)
// 3. Create and configure MediationNativeAdUnit
nativeAdUnit = MediationNativeAdUnit(configId: prebidConfigId,
mediationDelegate: mediationDelegate!)
nativeAdUnit.setContextType(ContextType.Social)
nativeAdUnit.setPlacementType(PlacementType.FeedContent)
nativeAdUnit.setContextSubType(ContextSubType.Social)
// 4. Set up assets for bid request
nativeAdUnit.addNativeAssets(nativeAssets)
// 5. Set up event tracker for bid request
nativeAdUnit.addEventTracker(eventTrackers)
// 6. Make a bid request
nativeAdUnit.fetchDemand { [weak self] result in
// 7. Make an ad request to MAX
self?.nativeAdLoader?.loadAd(into: self?.createNativeAdView())
}
Prepare the MANativeAdLoader
object before you make a bid request. It will be needed for prebid mediation utils.
The MAXMediationNativeUtils
is a helper class, which performs certain utilty work for MediationNativeAdUnit
, like passing the targeting keywords to adapters and checking the visibility of the ad view.
The MediationNativeAdUnit
is a part of the Prebid Mediation API. This class is responsible for making a bid request and providing a winning bid and targeting keywords to the adapters. Fot the better targetting you should provide additional properties like conteaxtType
and placemantType
.
The bid request for native ads should have the description of expected assets. The full spec for the native template can be found in the Native Ad Specification from IAB.
The example of creating the assets array:
let image = NativeAssetImage(minimumWidth: 200, minimumHeight: 50, required: true)
image.type = ImageAsset.Main
let icon = NativeAssetImage(minimumWidth: 20, minimumHeight: 20, required: true)
icon.type = ImageAsset.Icon
let title = NativeAssetTitle(length: 90, required: true)
let body = NativeAssetData(type: DataAsset.description, required: true)
let cta = NativeAssetData(type: DataAsset.ctatext, required: true)
let sponsored = NativeAssetData(type: DataAsset.sponsored, required: true)
return [icon, title, image, body, cta, sponsored]
The bid request for mative ads may have a descrition of expected event trackers. The full spec for the Native template can be found in the Native Ad Specification from IAB.
The example of creating the event trackers array:
let eventTrackers = [
NativeEventTracker(event: EventType.Impression,
methods: [EventTracking.Image,EventTracking.js])
]
The fetchDemand
method makes a bid request to Prebid Server and provides a result in a completion handler.
Load a native ad from MAX according to the MAX instructions.