MoPub Mediation Integration Checklist for Publishers

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

SDK Integration and Initialisation

• If you are integrating an earlier version of the SDK (i.e: v:2.3.0 or earlier), make sure the necessary Run Script is added properly to the project.
• Add MoPub adapter dependencies for HyBid SDK.
• Check in the release notes that the MoPub adapter version is compatible with your app's MoPub SDK version.
• Initialise the SDK and make sure it finishes before making any ad requests.
• Use the app token provided for the iOS integration. Note that an iOS app token won't work on Android.
• Disable test mode once the app is ready to go to production.
• Add SKAdNetwork support for apps that use iOS 14 and above.
• 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 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 Xcode debug console.
• Check on Charles Proxy that the MoPub SDK responses for the ad unit contain the custom event names for HyBid adapters.
• Check in Xcode debug console that there are no error messages indicating that HyBid custom event classes can't be found.
• Check on Charles Proxy that the SDK requests are going out without errors. The URL looks like api.pubnative.net.