How to Set Up Ad Sources for Mediation



AerServ | InMobi Ad Mediation

Maximize your ad revenue with the industry's
first in-app header bidding solution for mobile apps.

Get AerServ + InMobi demand for Monetization, as well as 30+ Additional Demand Sources via a single platform. 

Once you've set up your app or site, and created an ad placement, you're ready to set up ad sources for Mediation to reap the full benefits of OpenAuction's simultaneous ad calls and dynamic bids.



Please note: You will need to create accounts for whichever new ad sources you wish to set up in the AerServ mediation platform. For a list of supported networks and their respective support links, please see Supported Ad Networks for Mediation.



How to Set Up a New Ad Source

While AerServ's aerMarket Ad Exchange is already included when you set up an ad placement, we suggest adding more Ad Sources to your stack to allow more networks to compete for your inventory in the unified auction.

There are two ways you can set up a new ad source for your app/site and placements.

  1. Step 3 of Onboarding Wizard after setting up your app and placements
  2. Ad Networks Index Page "New Ad Source" button


1. Onboarding Wizard - Step 3

You've just set up your app or site in Step 1 and created ad placements by choosing Ad Products in Step 2 of the onboarding wizard and are now on Step 3:


Step 1 - Set Up Your App or Website

Step 2 - Choose Your Ads

  Step 3 - Choose Your Networks for Mediation

Step 4 - Integrate


Here you can add as many ad networks for Mediation as you'd like to bind to the placements you set up in the previous step of the onboarding wizard.




2. Ad Networks Index

If you've previously set up your app and placements, you can simply create new Ad Sources from the Ad Networks Index page by clicking the "+ New Ad Source" button above or below the table.

Once you've filled in all required information, don't forget to bind this new ad source to whichever app or placement you desire.





Field Descriptions

Below are some details about the fields you will need to enter. 



The unique name you wish to give to this ad source. If you are going to have multiple instances of an ad source, it is suggested that you provide details for easier reference.


Publisher ABC sets up two ad sources for Admob using the following names:

  1. Admob Interstitial
  2. Admob Banner
Ad Source

The ad network or ad source you want to send traffic to.  

Ad Type

The ad type selection will be dependent on the options available for the ad source you selected.

Potential options include:

  • Interstitial HTML
  • Banner HTML
  • Video 
Ad Source Specific Fields

Each ad source will have specific variables that need to be defined for the connection to be set up properly to deliver ads. The number of fields, the values, and whether they are required will vary per ad source.


  • Admob Pub ID: ca-app-pub-xxxxxxxxxxxxxxxx/nnnnnnnnnnm
  • Mopub Ad Unit ID: bff7bf1371f646ce8d0b2f5a7nd5iog6s
  • Tapit Zone ID: XXXXX

Allows the publisher to change the status of an ad source from Active to Paused or vice-versa. 


Publisher ABC leaves both ad sources active so they can serve ads from both sources.


The CPM you are paid by this Ad Source. 


Publisher ABC would enter the following -

  • For the ad source named "Admob Interstitial", they enter $3 as that is the NET CPM they are paid by Admob for interstitials.
  • For the ad source named "Admob Banner", they enter $0.25 as that is the NET CPM they are paid by Admob for banners.
Impression Cap

The total number of impressions this ad source is eligible to serve for a given day, across all apps and placements. A value of 0 indicates no cap.


An ad source has asked Publisher ABC not to deliver more than 100,000 interstitial impressions per day. Publisher ABC then enters 100,000 in the Impression Cap field for their ad source.  

Request Cap

The total number of ad requests this ad source is eligible to receive for a given day, across all apps and placements. A value of 0 indicates no cap.


An ad source may ask Publisher ABC for a specific number of ad impressions, but if the fill rate is low, it may end up wasting ad opportunities and harming the publisher's revenue and eCPM. A publisher can use the Daily Request Cap field to limit the number of ad requests for a particular ad source and mitigate this risk.

Frequency Cap

The total number of impressions an ad source can serve per user for a given day. A value of 0 indicates no cap. 

There are a few potential use cases for the frequency cap field. Some examples include:

  1. An ad source complains that your unique user count is too low. They ask you to implement a frequency cap to resolve the issue. 
  2. An ad source complains that your banner CTR is too low. They recommend you implement a frequency cap in an effort to increase CTR.
Start Date

Start date for when you want the ad source available to receive ad requests.

End Date

End date for when you no longer want the ad source available to receive ad requests.

Assign this Ad Source to Placements

Allows the publisher to assign the ad source to ad placements (PLCs). For your convenience, a checkbox is provided at the top of the section and for each app to easily select multiple PLCs.

*This is not a required field, but if you do not assign an ad source to any PLCs, no ad requests will be sent to the ad source.


Publisher ABC only wants to target his aerWall (interstitial) placements with his Admob Interstitial ad source.



AerServ provides the following targeting options to allow only certain types of traffic to get sent to each ad source. 


Allows a publisher to define the geographic area where the ad source is eligible to serve. Current options are:

  • Country
  • If United States is selected, you also have the option of serving to specific DMAs

Allows a publisher to restrict the ad source to only serve ads to specific devices. Current options are:

  • All Devices
  • Specific Device/OS
    • iPhone
    • iPad
    • Android
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request