Recommended Settings for Ad Placements

Use these recommended settings for each type of ad placement to maximize your revenue. Each placement can have its own set of ad sources, business rules and reports.


We recommend a single banner placement that stays on the viewer's screen as a user navigates through your application. The best way to drive user engagement is to maximize the amount of time the ad is on the screen.

Recommended Settings

  • Always enable Rich Media on banner placements.
  • Banner size defaults to ‘dynamic’ ensuring correct display on all devices.


Mobile Video placements are an excellent way to generate higher revenue and value per ad because they deliver greater eCPMs and user interaction.

Recommended Settings

  • Interstitial placements are enabled on video ads as the Oath SDK supports both Landscape and Portrait video ads.
  • Interstitial placements allow both Video and static ad units, but can be configured to accept Video ad units only.
  • Our Video ad units have a configurable countdown timer informing users of when they can skip the ad. By default, the SDK presents a skip button after 7 seconds. Configure this setting at the application level. Longer skip button delay times increase completion rates and therefore give more value to your video inventory.
Please submit a request for configuration adjustments.


Static Interstitial

A static interstitial ad is a full screen ad unit that is typically presented at a logical break within an application. The best times to show an interstitial ad are: between levels of a game, after a user clicks on an article, or as a user navigates between sections of your application. Interstitial ad units tend to have better user engagement (higher CTRs) than banner ads, and typically deliver higher eCPMs.

Recommended Settings

Standard interstitial ad unit sizes are:

  • 320x480 (portrait) and 480x320 (landscape) on a phone
  • 768x1024 (portrait) and 1024x768 (landscape) on tablets.

Interstitial ad units tend to have better user engagement (higher CTRs) than banner ads, and typically deliver higher eCPMs.


Native is an inline ad format designed to seamlessly integrate and perform within mobile app experiences. The look and feel of the ad unit is controlled by the publisher, and typically is seamlessly integrated with an application to preserve the user experience. 

The Oath Ad Platforms SSP supports accessing and mediating native demand through our Marketplace, our direct ad network demand, and by integrating with third-parties partners (such as Facebook Ad Network or OpenX).

Recommended Settings

We recommend using a minimum of 4 basic elements per native ad unit to ensure high-level performance:

  • Title
  • Description
  • CTA Button
  • Image.
Have more questions? Submit a request