Before publishing your app with MoPub and mediated networks, it is highly recommended to test the integrations to ensure they are operating properly.

Integration Review

  1. Review our Supported Networks Page to ensure you are using the certified network SDK versions

  2. Review our Supported Networks Page to ensure that the ad unit type you are testing is supported by your ad networks

  3. Enable the ad network on an ad unit

  4. Ensure that you have entered your ad networks properly. This includes entering network IDs and custom event class data correctly where applicable.

How To Test

Before you begin testing your ad network integrations, you will want to make sure there aren’t any issues with your MoPub SDK integration. In order to confirm that the MoPub SDK has been correctly integrated, please follow these steps:

  1. Create a guaranteed or backfill line item for testing purposes. Here are instructions on how to create a line item if needed.

  2. Add test creative to your line item.

  3. Follow the instructions under the “Testing Ad Network Integrations” section of this page to test your line item. You can confirm it has been done correctly if you see the test creative associated with your line item.

  4. Reading Device Logs can help you troubleshoot your integration.

Testing Ad Network Integrations

We recommend testing each network separately to ensure that each network in your waterfall is integrated correctly.

  1. Ensure that the ad network or line item you are testing is active. Active networks and line items will show a green circle in your ad source breakdown on the ad unit page, while paused line items will show a yellow or grey circle.

  2. Pause all other ad networks and line items targeted to your ad network in the MoPub UI

  3. Begin testing on device. Make sure you can see the device logs while you are testing, as you’ll need to review the logs to troubleshoot any problems you are having.

Tip: Checkout “Waterfall Latency and Best Practices” for specifics on network timeout thresholds.

Not seeing any ads?

Check out our FAQ below for solutions to common problems.

Testing Impression and Click Trackers

Make sure that ad requests, impressions and clicks are firing correctly in your app.  In addition to observing what happens on screen when you show and click on an ad, check the device logs for the following logs.


  • Loading url: http://ads.mopub.com/m/ad?…: This log indicates that an ad request has been made.
  • Banner / Mrect / Interstitial /  loaded: You will  see this log after the ad request is made and before the ad is shown to indicate that the creative has been loaded and is ready to show.
  • Interstitial shown: This log indicates that the interstitial has been shown on screen.   Please note that this log only applies to interstitial ad units.  Banner and MRECT ad units will show the ad immediately upon load.
  • Successfully hit tracking endpoint: http://ads.mopub.com/m/imp?…: This log indicates that the impression tracker has fired.
  • Banner / Interstitial /  clicked: This log indicates that MoPub has recorded a click.
  • Successfully hit tracking endpoint: http://ads.mopub.com/m/aclk?…: This log indicates that the click tracker has fired.

Reading Device Logs

Reading your test device logs can be a helpful way to troubleshoot your integration. Device logs can be pulled by using Android Studio.

Enable Verbose Logging

Android Verbose logging can be set here:

    static {
        LOG_HANDLER.setLevel(Level.ALL);  /* Change from FINE to ALL */

        addHandler(LOGGER, LOG_HANDLER);

Log Messages

Failed to load Custom Event class

The adapter/Custom Event is missing or in the wrong location (see Network Integration documentation) or there is a mismatch between the actual custom event name and what is entered in the Networks tab of the MoPub UI.

Adunit is currently warming up

This is an old message, check to make sure that the MoPub AdUnit ID is the same as the ID from the UI. Using a wrong value will result in this error.

No ads found for ad unit

This log indicates that there was no fill for your ad unit. It does not indicate that there is a problem with your integration, but you may see it in combination with another error log, such as “Could not find custom event class named” so be sure to review the logs thoroughly.

Make sure to review the ad source breakdown associated with your ad unit to ensure your ad sources are active.

Third-party network failed due to invalid internal state.

Double check that the App ID and network provided Adunit IDs entered in the UI are correct and entered in the right place. If not, Mopub SDK will be able to initiate the network, but you will not get fill.

Third-party network timed out.

For banners, mopub time-out limit is 10 seconds and for interstitial it’s 30 seconds. After we pinged the network, if the network does not respond within that timeout period, you will see the error below. This is a network driven issue – please reach out to your network partner.


I’m testing but I’m not seeing any ads. Why?

  • There could be multiple reasons why you aren’t seeing any ads in your testing.  You’ll want to consult the device logs to learn why.

What are device logs?  How do I pull them?

  • Device logs, also known as the logcat, record what is happening in your app, including actions and processes that are not visible on screen.  They can be pulled by a developer tool like Android Studio or Xcode.  If you are unsure of how to pull device logs, a developer on your team should be able to help you.

Where can I see definitions of the errors in the device logs?

Please reference our Reading Device Logs documentation for more information.

I am seeing “no ads for ad unit” or “no ads found” in my device logs?  What does this mean?

  • These errors indicate that there was no fill for your ad unit.
  • No ad network will have fill 100% of the time, so seeing this log is normal.  New apps and apps with very low volume tend to experience lower fill rates.  We recommend connecting with your ad network rep if you have any concerns related to a particular networks fill.
  • If you are consistently seeing no fill, we recommend reviewing your ad network placement details in the Networks tab of the MoPub UI, as well as your settings in the Network’s UI
  • You won’t be able to show ads from Certified Ad Networks if you forgot to include the network SDK or adapter files.  The “Couldn’t locate or instantiate custom event” and “Unable to find Native Network or Custom Event adapter” logs are indicators that the network SDK or adapter file is missing, renamed or in the wrong location.  You’ll want to review our Integrating Third Party Ad Networks documentation to resolve this.

Why aren’t I getting any fill from MoPub Marketplace?

  • You’ll need to be approved for MoPub Marketplace before you can begin showing Marketplace ads.  In order to determine if your account has been approved, navigate to the Marketplace tab of the MoPub UI.
    • If you haven’t started the Marketplace approval process yet, you’ll be prompted to enter your company and payment information.  This is the first step towards approval.
    • After you have entered your company and payment details, you will see an indication in yellow at the top of the page indicating that your account is under review.  We recommend emailing policy@mopub.com with up to date payment information and the corresponding Android package name/iTunes App Store URL/Website URL linked to your MoPub App in the MoPub UI to complete the approval process. For faster approval, please include screenshots of the app in your Admin page/your website’s admin page to show that you are the owner of the account in your email to policy.

Last updated February 19, 2018

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2018 MoPub Inc.