SDK mediation
Mobile SDK mediation allows you to send impressions from mobile apps to ad networks via an ad network's' own SDK.
The SDK mediation creative type in DFP allows publishers to specify an ordered list of ad networks to call. For each impression, the ad request goes to the ad networks in the specified order. If the current network times out or doesn't return an impression because of an error or an impression cannot be found, then the request moves on to the next network. This continues until the impression is filled, or the last network in the mediation chain is reached.
Here’s the list of support Ad Network partners : Link
For supported ad networks:
The developer team should integrate the following into the app:
- Include the ad network SDK and adapter - Link
- Include the Google Mobile Ads SDK - Link - Link
- Setup the network configurations:
For unsupported ad networks:
If you don’t find the ad network you want to mediate with in the list of certified networks, you can use custom events.
The Google Mobile Ads SDK includes a handler for custom events, so you can integrate non-certified ad networks by entering the Adapter Class Name in the DFP SDK Mediation Creative. You can also introduce callouts to other services, or trigger other behavior in your app as part of the mediation chain. Learn more in the developer documentation on custom events for Android and iOS.
Custom Events - Link
This guide is intended for publishers looking to use DFP Mediation to:
- show ads from a network that is not directly supported in the DFP user interface
- show a custom view instead of an ad
Custom events allow you to write a custom mediation adapter to place any view into your ad space. You can find the full source for this project on GitHub. There are 2 types of Custom Events that you can use:
Comments
Post a Comment