Get Started

Setting Up Ad Network IDs

MoPub strongly recommends setting up separate Network IDs for each MoPub Ad Unit
  • Network ID is the placement ID provided by an ad network and is often the granularity at which a the network provides reporting. This is the ID you enter into the MoPub UI at the time of network setup. See setup instructions below
  • Publishers should ensure that no two ad units on MoPub share the same Network ID.
  • IDs should be unique to the MoPub integration. Publishers should not use the same network IDs across multiple demand partners.
  • Benefits:
    • Access to granular network revenue and performance data on unique ad units
    • Helps publishers to confidently set up waterfall based on individual ad units performance
    • Helps isolate performance issues
Leverage Network Segments
  • Network segments make it easier for customers to visualize and manage the network waterfall for different regions

Ad Network Setup

  • AdColony
  • Facebook
  • Millennial Media
  • Unity
  • MobFox
  • mNectar
  • mobileCore
  • Conversant
  • Lifestreet
AdColony

You will need your app id and zone id from the AdColony UI

  • Remember:
    • Zone IDs must be unique per MoPub ad unit
    • App and Zone ID are required for ad serving
    • Client Options are optional and only apply to Android

Migrating Your AdColony IDs from a Custom Native Network

  1. Add the AdColony Account to your UI
  2. Replicate setup and transfer only the App and Zone IDs from the old custom native connection to the new AdColony account
    • MoPub will initiate ‘allZoneIds’ and the following AdColony custom event class names for you:
      • iOS
        • AdColonyInterstitialCustomEvent
        • AdColonyRewardedVideoCustomEvent
      • Android
        • com.mopub.mobileads.AdColonyInterstitial
        • com.mopub.mobileads.AdColonyRewardedVideo
    • Note: If you are using the above mentioned class names, migrate to the new network setup and pause the “custom native network”. If you are not using the above naming convention and instead using your own custom event class names, you should have both the old custom native network setup & New Adcolony network UI setup for backward compatibility.
    • Note: During migration, please make sure the custom native network and AdColony network are not live at the same time as this may cause revenue impacting issues

 

Facebook

Setup:

  1. Click into the Networks section of the MoPub UI
  2. Click “Add a Network” and select Facebook
  3. You’ll see all of your applications and ad units listed
  4. Enter in the Facebook Placement IDs to the corresponding MoPub ad units
  5. Ensure to click the “ENABLE NATIVE VIDEO” if you would like to get video ad inventory from FAN
  6. Make note of the “Enable this Network” section

Note:  MoPub will automatically initiate the following Facebook custom event class names, make sure the naming convention and location in the app match exactly what is listed above.  Find further details on GitHub (Android, iOS).

  • iOS
    • FacebookBannerCustomEvent
    • FacebookInterstitialCustomEvent
    • FacebookNativeCustomEvent
  • Android
    • com.mopub.mobileads.FacebookBanner
    • com.mopub.mobileads.FacebookInterstitial
    • com.mopub.nativeads.FacebookNative

Migrating Your Facebook IDs from a Custom Native Network

  1. Click into the Networks section of the MoPub UI
  2. Click “Add a Network” button and select Facebook
  3. Set the status to Paused
  4. Transfer the Placement IDs from the old custom native network to the new Facebook network
    • Ensure to click the “ENABLE NATIVE VIDEO” if your FAN native placement is setup for video demand
  5. Update your segments so that they include the new Facebook network with the correct desired eCPMs
  6. Create new instances (don’t use copy feature) of any Network Line Items running the old custom native network using the new Facebook network
    • Note: don’t use the copy feature as the old custom native network will be carried over and can’t be changed.
  7.  Important: MoPub will initiate the Facebook custom event class names (mentioned above) automatically.
    • If you are using (within your app) the above mentioned class names exactly then after the above migration steps are complete you should,
      • activate the newly created Facebook network
      • pause the “custom native network”
    • If you are not using the above mentioned naming convention exactly and instead using your own custom event class names, you should have both the old custom native network setup & New Facebook network UI setup for backward compatibility.
      • Note: Use the above naming convention for all future app versions and pause the “custom native network” once users have fully transitioned off of older app versions using a custom naming convention.

 

Millennial Media

Revenue Reporting

  • You need your Millennial App Name and APID

 

  1. Login to the Millennial UI
  2. Select Apps and Sites
  3. Click on the App on the left hand side
  4. Scroll to the bottom of the page to find your APID. Traffic these in the MoPub UI
    • Note: APIDs should be unique per MoPub ad unit
  5. In the MoPub UI, input the App name into ‘Millennial App Name Override’

 

Unity

Setup:

  1. Click into the Networks section of the MoPub UI
  2. Click “Add a Network” and select “Custom Native Network” from the options below “Additional Networks”
  3. You’ll see all of your applications and ad units listed with entry boxes (“CUSTOM EVENT METHOD”, “CUSTOM EVENT CLASS”, “CUSTOM EVENT CLASS DATA”)
  4. You’ll need to enter in values for “CUSTOM EVENT CLASS” and “CUSTOM EVENT CLASS DATA”
    • Interstitials
      • iOS: Update CUSTOM EVENT CLASS entry box with UnityAdsInterstitialCustomEvent
      • Android: Update CUSTOM EVENT CLASS entry box with com.mopub.mobileads.UnityInterstitial
      • Update CUSTOM EVENT CLASS DATA entry box with,
        • Unity Ads SDK 1.x: {“gameId”: “1235890”, “zoneId”: “xxxxxx”}
        • Unity Ads SDK 2.x: {“gameId”: “1235890”, “placementId”: “xxxxxx”}
          • note if zoneId is passed the adapter will still work
    • Rewarded Video
      • iOS: Update CUSTOM EVENT CLASS entry box with UnityAdsRewardedVideoCustomEvent
      • Android: Update CUSTOM EVENT CLASS entry box with com.mopub.mobileads.UnityRewardedVideo
      • Update CUSTOM EVENT CLASS DATA entry box with,
        • Unity Ads SDK 1.x: {“gameId”: “1235890”, “zoneId”: “xxxxxx”}
        • Unity Ads SDK 2.x: {“gameId”: “1235890”, “placementId”: “xxxxxx”}
          • note if zoneId is passed the adapter will still work
MobFox
  • You will need your MobFox Publisher ID from the MobFox UI
    • Note: MobFox Publisher ID is now called ‘Inventory Hash’ in the MobFox UI
  • Instructions for Migrating MobFox from the Old Connection can be found here

 

mNectar
    • You will need your mNectar Ad Unit IDs for each size.
    • Follow the instructions below:
      • Log into the mNectar UI
      • In the Applications widget, click on the orange disclosure arrow to the left of your Application title
      • Select the Ad Unit title that appears below your application
      • Your Ad Unit ID will appear in the widget below the Applications widget

 

mobileCore
  1. Both new and existing mobileCore customers must have the MoPub server-to-server connection enabled in the mobileCore UI. To have this activated, reach out to the mobileCore team at following alias: [email protected]
  2. Once enabled, you will need your mobileCore App and Ad Unit IDs.
  3. mobileCore Ad Unit IDs must be unique per MoPub Ad Unit

Locating your mobileCore App and Ad Unit IDs in the mobileCore UI:

    • Click on the Apps tab
    • Select the application you want to configure
    • Click on the settings button on the top right corner

      • If you have not already done so, create an ad unit by selecting ‘Create New Ad Unit’
        • Select integration type: “Mopub”
        • Choose your preferred configuration and click ‘Create’

 

    • You can find your mobileCore ‘App ID’ at the top of the page
    • You can find your mobileCore ‘Ad Unit ID’ next to the Ad Unit Name

 

 

Conversant
  • You will need to obtain your site ids from the Conversant Publisher Portal.
  • Existing publishers: Reach out to publishersupport@conversantmedia.com with the subject line ‘S2S Placement IDs’ to obtain placement IDs. The site id is used in place of the app id used within your MoPub account setup. Please follow instructions here

Lifestreet

  • Please follow instructions here.