Let’s Get Technical: How Mediation Really Works

So often we interact with complex technology and don’t stop to think about how it actually works. We just care about results. When we ask what time it is for example, we don’t really want to know how a clock or watch works — we just want to know the time. Very few people know the intricacies of how a car works, yet it must function efficiently, powerfully, and safely every day.

Much is the same for an ad monetization platform. These tools have significant impact on how much revenue an app can generate, but how many developers or monetization managers actually know how SDKs, APIs and ad mediation platforms actually work?

Millions of users open an app, interact with an ad, and magically get a relevant, engaging and functional creative unit to view. Do you know what technical innovations are happening every millisecond to ensure that the ad they see works — and that you get the highest revenue for that click, view or download?

Knowledge is power, so join us as we will lift the hood to give you a step-by-step view of one of the most common processes when it comes to mobile monetization: mediation.

Start the engine

Imagine you’re on a road trip with your college buddies. You lost at Rock, Paper, Scissors, so you’re the one who must drive while the others play mobile games and eat Cheetos. Now imagine that you’re starting the car and getting ready to go. When you start your car, it initializes many complex systems that all must work together, such as the power steering and brakes, lights, air conditioning, sick road trip tunes, and more.

The same goes for when your buddy starts his mobile app to play a game. This starts the ad mediation process, where the mediation platform will send requests to multiple ad networks to find the highest paying ad. The app sends a signal to the Fyber SDK that it must get the app’s credentials from the Fyber server, and initialize all mediation partner SDKs. This process is essential to allow the app, Fyber SDK, Fyber Server, and partner SDKs to communicate and work together. Video ad precaching can also happen at this moment.


Running at full speed to deliver the highest paying ad

We’ve all put our car to the test, floored it, and saw just how fast we can go. Monetization platforms need to perform at top speed at all times. We expect them to always deliver the highest paying ad as fast as possible. So when your friend clicks “view video ad” in his mobile game to speed up his crops or advance to the next level, the Fyber SDK receives an ad request and goes to the Fyber server to get a list of the highest paying campaigns in order.


Streamlined tech for experience and efficiency

Nothing is worse than a car that guzzles gas and wastes energy. For mobile gamers, there’s nothing worse than slow loading ads that waste time. Once the Fyber SDK receives the list of high-paying ad campaigns, it calls to the highest paying network first. If this network does not have an ad, the Fyber SDK goes down the list of networks to find the network that can deliver a the next-highest paying ad, and fast.



Optimal ad delivery for experience and reliability

Now it’s time to show the rewarded video ad. Again, the process is designed to give the best user experience possible. Think of this as the heated seats, air conditioning, and music that make your road trip as comfortable as possible. At this time, a video ad may have already been pre-cached on the device. So when the ad is ready to show, there is almost no loading time and it can be viewed instantly. The Fyber SDK also signals when the video is complete to the app so that the reward can be delivered immediately to the user.


Want to learn more?

This is just scratching the surface of the complex technology that helps app developers monetize their apps. Expect to see even more “under the hood” posts from Fyber soon! And contact [email protected] to find out about Fyber Mediation.

Read these next

Contact Us

    By sharing your information you are agreeing to receive communications in regards to any questions or requests submitted on this form. Fyber will keep your information solely for internal tracking purposes and will not use this information for any other purpose. You may request to delete the information provided at any time.

    If you send us a message by clicking the "Send" button, we use a recaptcha service provided by Google LLC to check whether the message was sent by a natural person or a computer program ("bot") in order to ensure that only valid user requests are forwarded to us. Google LLC processes personal information from your browser, such as your browser settings and your click behavior on this screen. Please refer to the Privacy Policy for further information on data processing procedures of our third-party services.

    Error: SSL certificate problem: certificate has expired