Follow

How to Set Up an Ad Source

Ad Source (Mediation) Overview

 

What is Ad Mediation?

Ad mediation allows publishers to optimize their advertising revenue by managing  inventory allocation among multiple ad networks, forcing them to compete for your inventory. A mediation platform allows you to easily add and manage the existing ad networks that you currently work with, change priorities, adjust daily caps, modify GEO targeting, and more.

AerServ’s Ad Mediation Platform is a fresh take on mediation:

  • We bring you the highest yielding IAB standard ad formats (Banner, Interstitial, & Video)
  • Ad network diversity: AerServ offers the largest selection of ad networks to work with across banner, interstitial, and video, and for all GEOs. Choose from iAds, Admob, Mopub, Millennial Media, Inmobi, and many more.
  • Innovative technology that ensures you minimize wasted impressions.

 

What is an Ad Source? 

Ad sources are partner ad networks that have been integrated into our mediation platform via Sever to Server (S2S) connections or SDK adapters. Some ad sources we've integrated with include iAds, Admob, Mopub, InMobi, Millennial Media, TapIt, and many more.  

Our mediation platform allows you to:

  1. Work with 35+ global ad sources without installing additional SDKs
  2. Get reporting on 1 dashboard
  3. Allocate your traffic through various targeting
  • By App
  • By Ad unit
  • By Placement 
  • By Pricing 
  • By Country
  • By DMA
  • By Platform 
  • By Device

 

How to Set Up a New Ad Source

 

 

Step 1: Adding a New Ad Source

Setting up a new ad source is easy! You only need to enter a few details about the ad source, bind the ad source to an APP or PLC, and click the 'Save' button.

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

 

FIELD
DESCRIPTION
REQUIRED/OPTIONAL
Name

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.

Example:

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

  1. Admob Interstitial
  2. Admob Banner
Required
Ad Source

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

Required
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 
Required
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.

Examples: 

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

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

Example:

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

 Required
CPM

The CPM you are paid by this Ad Source. 

Example: 

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.
Required
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.

Example: 

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.  

Optional
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.

Example:

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.

Optional
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.
Optional
Start Date

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

Optional
End Date

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

Optional
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.

Example:

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

Optional

 

 

 

 

Step 2: Custom Targeting (Optional)

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

 

FIELD
DESCRIPTION
REQUIRED/OPTIONAL
Geography

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
Required
Devices

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
Required
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk