Mediation Network Support
The FeedAd SDK is built to work together with ad mediation networks. If you are planning to integrate FeedAd alongside other ad networks, we recommend the following:
Choose your Integration
If you don’t have any ads, yet, or are planning to replace your ads with FeedAds:
We recommend integrating the FeedAd SDK without any mediation network This removes the overhead of the mediation request and results in faster loading times of your ad placements. Continue reading the documentation for your targeted platform on how to integrate the FeedAd SDK into your app.
If you are using AdMob, Google Ad Manager or MoPub:
We have tested the integration for these networks through custom events. You can find a detailed integration example for each network inside the example app for your targeted platform. For most cases, the example code can be copied and pasted into your app with only minimal changes to the configuration.
If you are using Prebid.JS:
We have implemented an official Prebid.JS header bidding adapter for our FeedAd Web SDK. If you have an already working Prebid.JS integration, all you have to do is to add and configure the FeedAd bidder adapter. For more information, please head over to our guide for the Prebid.JS integration.
If you are using any other mediation network or have built the ad mediation yourself:
FeedAd provides the necessary methods and callbacks to be integrated into any ad mediation. Learn more about these callbacks in the general mediation guide.
If you want to use the Web SDK through a mediation network:
Read about how to integrate the SDK through iFrames.
Mediation Best Practices
Make sure your mediation only displays one visible ad per screen:
Since multiple FeedAd UI elements play the same creative and a video can only be played on one UI element at a time, your mediation should not show more than one ad at a time. Otherwise, the FeedAd element to have become visible last will take over the video while the other elements display a still frame. For example, this can happen if you display ads at too small an interval within lists on large screen devices.
Put FeedAd as the topmost priority on your mediation waterfall:
The main feature of FeedAd is that video creatives are continued across different placements to maximize View-Through-Rate (VTR). Placements of apps with a high VTR are more likely to be booked by advertisers, which in turn increases your fill rate. If you put FeedAds behind other ads inside a waterfall mediation, it prevents FeedAd to continue the creative if one of the other networks receives fill. This will have a negative impact on your VTR.
We have implemented and tested FeedAd mediation in the following major ad networks:
AdMob mediation is tested via AdMob Native Custom Events (Android, iOS). Our example app shows in detail how to integrate FeedAds alongside other native ads. You should be able to copy & paste most of the AdMob related classes of the example and only adjust the parts of the classes that are related to your UI. Check the example code comments and README for detailed explanations.
Google Ad Manager (GAM)
For Android and iOS, our example app shows how to integrate FeedAds alongside other Google Ad Manager banner placements. Since the GAM and AdMob share the same SDK, this example can also be used if you want to add FeedAds to an AdMob banner mediation instead of AdMob native ads. Check the example code comments and README for detailed explanations.
For Web, our Web SDK works well alongside Google Ad Manager.
MoPub mediation is tested via MoPub Native Custom Events (Android, iOS). Our example app shows a full example of how to integrate FeedAd into a MoPub mediation, including the MoPub helper adapter that automatically inserts ad placements into lists. To give you a quick start, you can copy & paste most of the MoPub example classes into your code. Only some small adjustments to the classes that render the ad into your layout have to be made. Check the example code documentation and README for detailed information about the MoPub integration.
FeedAd is integrated into the Prebid.JS header bidding SDK of Prebid.org.
If you are only just starting with header bidding on your website, please follow the instructions in the general developer guide until you have a working integration running. Once Prebid.JS is working, you can add the FeedAd bidder adapter to the list of your bidder adapters.
Also, our FeedAd Web SDK demo project includes the simple Prebid.JS integration tailored to the FeedAd bidder adapter.
Before going live, please remember to check the following tasks:
- Replace the
clientTokenwith your FeedAd account's web token.
- Replace the
placementIdwith a sensible value.
- When downloading your production Prebid.JS script, check
FeedAdas a selected bidder adapter.
You can choose placement IDs yourself. A placement ID should be named after the ad position inside your product.
For example, if you want to display an ad inside a list of news articles, you could name it "ad-news-overview".
A placement ID may consist of lowercase
_. You do not have to manually create the placement IDs before using them.
Just specify them within the code, and they will appear in the FeedAd admin panel after the first request.
Learn more about Placement IDs and how they are grouped to play the same Creative
We have developed FeedAd with mediation networks in mind. If you are using a custom mediation or ad mediation network not mentioned above, you can still integrate FeedAd.
The following activity diagram illustrates the typical ad network mediation flow.
You will have to implement the
FeedAdAdapter actions to communicate between the mediation and the FeedAd SDK.
This adapter will forward the ad request and handle all FeedAd event callbacks.
For detailed explanations regarding the SDK events, please check the respective Android and iOS integration guides. Since most mediation networks are implemented similarly, we also recommend to look at the examples of the other mediation networks inside the demo app.