Banner Best Practices


Singleton Approach

Singleton ad view creates a seamless in-app experience by allowing you to show the same ad impression as users navigate through the various screens of your application.  This means that if you show an ad on your main menu and the user navigates to a new screen the user will see the same ad on both screens, increasing the chances the user will click on the ad.

What is the “singleton approach”? How does it affect my CTR performance?

  • The singleton approach involves creating an object with the MoPub ad view, allocating the object to the active view, and then de-allocating it and reallocating it to each view as the user navigates within the application.
  • Publishers often want to know how they can improve their overall click-through rate (CTR) performance. CTR performance is particularly important because some ad networks pay by click and DSPs in the MoPub Marketplace tend to bid higher on placements with high CTR.

  • Altering the refresh rate between 30-60 seconds and employing the singleton approach optimizes CTR, thus increasing eCPMs from ad networks and DSPs.

Why would a developer use the singleton approach in their app? What are the benefits?

  • The singleton approach has been proven to increase CTR, and subsequently revenue, as the app doesn’t need to load up a new ad each time the user moves through the app.
  • Since some mobile ad networks pay by click, this approach gives users more time to engage with the ad.

How does a developer set up the singleton ad unit?

  • The singleton design pattern ensures that only one instance exists for a given class and that there’s a global access point to that instance. There are various tutorials and articles on the implementation for both iOS and Android across the web.

  • The MoPub SDK does not come with the singleton implementation. It’s a recommended approach depending on the app’s user flow and should be implemented by the developer.

Updated: November 2016