Publisher Admob Mediation Integration Checklist - pubnative/pubnative-hybid-android-sdk GitHub Wiki

All the following points must have been checked out to confirm a successful Admob Mediation integration:

SDK integration and initialisation

  • Add gradle dependencies for HyBid SDK.
  • Add Admob adapter dependencies for HyBid SDK.
  • Check in the release notes that the Admob adapter version is compatible with your app's Admob/GAM version.
  • 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 Admob's waterfall according to the documentation.
  • Check that the custom event names and params match the ones in the mediation documentation.
  • 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 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.