In Google AdMob SDK v6.0 and above, you can request ads from multiple ad networks, including AdMob, while controlling how the requests are allocated among those networks. With this new feature, called mediation, you configure a mediation placement at mediation.admob.com by assigning each network either an eCPM or a percentage value.
Some of you have asked how AdMob uses these values to determine the network order, so we'd like to take this opportunity to explain. We’d also like to discuss what happens when you add an ad network to an existing mediation placement.
There are two ways in which traffic is allocated across ad networks.
Unlike AdWhirl, which refreshes its configuration on each ad refresh, AdMob Mediation refreshes its configuration once every 300 seconds. This means that the SDK uses the same network order until a new mediation configuration is fetched.
It's important to know how your application will behave when you add a new ad network to it. Remember that anytime you add a new ad network, you need to include the corresponding ad network adapter in your app. If the adapter cannot be found, the AdMob SDK skips that network and moves on to the next one.
Don't worry if your application doesn’t include the ad network adapter. For placements with eCPM values, the added network doesn't affect existing versions of the application. Similarly, for placements using percentage configurations, percentages are effectively normalized across existing valid ad networks, as invalid networks are automatically thrown out.
Let us know on our forum if you have any questions about mediation placements or general questions about the Google AdMob SDK. You can also ask us questions at our next hangout session.
- Eric Leichtenschlag, AdMob Team
