Ogury SDK 5

Banner Ad

This article will go through all the steps required to display banner ads in your application through AdMob mediation.

Banner Ads are small or medium rectangle ads that have specific dimensions and occupy a certain position of the screen width and they can be freely integrated within the content of the app.

The banner comes with two predefined dimensions:

  • small banner (320x50)

  • MPU (300x250)

Requirements

You have registered an application on your Ogury Dashboard. If not, please refer to the Getting started section before the next steps.

Step 1: Create an Banner Ad ad unit

In all the following code samples, we will refer to this Ad unit id by using the string YOUR_OGURY_AD_UNIT_ID.

Ogury Banner Ad ad units are designed to display only the size that they have been created with.

When loading your AdMob Banner Ad, please make sure to load using an AdSize matching the size of your Ogury ad unit:

  • For a small banner, use AdSize.BANNER.

  • For a MPU, use AdSize.MEDIUM_RECTANGLE.

Step 2: Create Mediation Group

Follow the AdMob guide to create a mediation group for your Banner ad unit.

Step 3: Add Ogury in your Mediation Group

In order to display Ogury Banner Ad through AdMob mediation, you need to configure a Custom Event for Ogury in your mediation group.

  • Go on the Mediation Group page, and click on the mediation group you want.

  • Click on ADD CUSTOM EVENT, in the Waterfall section

  • Enter Ogury as Label, set an eCPM and click on CONTINUE.

For eCPM, you need to set the value that you agreed with your Ogury Account Manager.

  • Next to the name of your Banner ad unit, enter the following configuration and click on DONE:

Class Name:

com.ogury.mobileads.OguryBannerAdCustomEvent

In case you are already using the old custom event class(com.admob.mobileads.PresageBannerCustomEvent),do not update your existing ad unit mapping to use the new custom event class (com.ogury.mobileads.OguryBannerAdCustomEvent).A new ad unit and a new mapping should be created in order to not impact the users already using an older library. Ads will be served with the new SDK even if the custom event class is not updated.

Parameter:

{"assetKey":"OGY-XXXXXXXXXXXX","adUnitId":"YOUR_OGURY_AD_UNIT_ID"}

  • Click on SAVE.

If you wish to set up multi-placements for Ogury, you can add Ogury multiple times as an ad source / custom event inside your mediation group. Each time, you should make sure to use the corresponding Ad unit ids from Ogury dashboard, with the agreed eCPM value.

Step 4: Test your integration

As our algorithm works with personified targeting, you may not receive any ad while testing your application.

You can test your integration by adding the suffix _test to your interstitial ad unit id, for more details go to Test your implementation page.

Note that if you have just registered your application in the Ogury Dashboard, it will take around 15 minutes until you can successfully load an ad.

Additionally, you can follow the integration logs to get useful information on your integration status and any issue that might occur when displaying ads. Connect your device to Android Studio. Then filter the logs after the OGURY keyword to separate them from everything else.

Last updated