Publisher MoPub Header Bidding Integration Checklist - pubnative/pubnative-hybid-android-sdk GitHub Wiki

All the following points must have been checked out to confirm a successful MoPub Header Bidding integration:

SDK integration and initialisation

  • Add gradle dependencies for HyBid SDK.
  • Include the MoPub Adapters.
  • Check in the release notes that the MoPub adapter version is compatible with your app's MoPub version. There are breaking changes for MoPub 5.10 and older.
  • Add mandatory manifest permissions.
  • Add Proguard configuration. Documentation.
  • Initialise the SDK and make sure it finishes before making any ad requests.
  • Use the app token provided for the Android integration. Note that an Android token won't work on iOS.
  • Disable test mode once the app will go to production.
  • Setup the line items in MoPub's waterfall according to the documentation.
  • Check that the custom event names and params match the ones in the header bidding documentation.
  • Create the targeting keywords starting on the floor price (base eCPM) set for each line item.
  • Make sure that the line items for HyBid adapter custom events are enabled.

Targeting (has an impact on fill rate and bid prices)

  • Enable the COPPA flag only if the app is intended for children.
  • Check the state of the GDPR or CCPA consent on your app. If you have any 3rd party IAB compliant Consent Management Platform (CMP), our SDK will pick up on the state of the consent string, therefore some data could be anonymised.

Integration troubleshooting

  • No ad requests are made before the HyBid SDK has finished initialising.
  • Use different log levels on the app to see any error messages in the Android Studio Logcat.
  • Check on Android Studio Profiler or Charles Proxy that the MoPub SDK requests for the ad unit contain the bid price in the targeting keywords. the keywords follow the format pn_bid:PRICE.
  • Check on Android Studio Profiler or Charles Proxy that the MoPub SDK responses for the ad unit contain the custom event names for HyBid adapters.
  • Check in Android Studio Logcat that there are no error messages indicating that HyBid custom event classes can't be found.
  • Check on Android Studio Profiler or Charles Proxy that the SDK requests are going out without errors. The url looks like api.pubnative.net.
  • Check in Android Studio Logcat that there are requests going out to the HyBid API before the MoPub requests go out.
  • Make sure that you are making ad requests to HyBid using the RequestManager and passing the keywords right after in the request to MoPub.
  • The targeting keywords for HyBid set in MoPub should cover all the possible price ranges. Using the 2 decimal precision will reduce the amount of keywords needed.
  • If you need to build your own keyword format you can follow this guide.