Mediate from MoPub

The following instructions apply to publishers looking to mediate their MoPub inventory to Oath Ad Platforms SSP.

Integrating with the Oath SDK may require a "Custom Network" within MoPub using the adapters listed below.

Notice to Unity Engine developers: The Oath SDK can still deliver ads on an app developed through the Unity Engine if you are mediating through MoPub. Please follow the instructions that correspond to the MillennialSupport.unitypackage integration found on MoPub's documentation page to get started.

Download and Add the MoPub Adapters

The most current MoPub adapter files have been released via pull requests to the MoPub git repository.

Configure MoPub to use Oath SSP

Using MoPub with SSP (formerly ONE by AOL: Mobile or Nexage), however, requires adding Exchange compatibility to SDK integration. Network setup in MoPub is similar to previous SDK versions. Publishers will integrate MoPub with Ad Network Support, and use the dashboard to enter their placement ID.

Click the Add a Network button. If you formerly had a Nexage integration, skip this.

Click the Custom Native Network link. This gives the SDK the power to invoke adapter classes and pass data to them.

Name the network and use the Edit Network screen to enter the Custom Network Information. Be sure to fill in all the required fields as they are integral to making mediation work within the app.

Each of the Ad Units targeted by this custom network will require some additional information (Custom Event Class and Custom Event Class Data) which varies between iOS and Android. See the second and third columns of the table below; they represent what will be shown on the Networks tab. (The first column was deprecated by MoPub and should not be used.)