Google AdMob (ex. AdMob) mediation

You can connect to the Boost via Google AdMob (ex. AdMob) mediation. To add the Boost to Google AdMob (ex. AdMob) mediation, follow these steps:

1. Integrate Google AdMob (ex. AdMob) mediation.
2. Connect the adapter for the Yandex Mobile Ads SDK.
3. Create an AdUnitId for your selected ad type in the Boost interface.
4. Add the Boost in the Google AdMob (ex. AdMob) web interface.
5. Sync the ad unit settings between the two web interfaces.

Connecting an adapter for the Yandex Mobile Ads SDK

To integrate the Boost with Google AdMob (ex. AdMob) mediation, add the adapter dependency to the build.gradle file of your project's module:

dependencies {
    ...
    implementation 'com.yandex.ads.adapter:admob-mobileads:8.0.0.0'
}

To manually transmit GDPR (user consent) and COPPA (age-restricted user) values from the app code to the Yandex Mobile Ads SDK, make sure to also enable the Yandex Mobile Ads SDK. Add the following to the dependencies block:

implementation "com.yandex.android:mobileads:8.0.0.0"

Adding the Boost in the Google AdMob (ex. AdMob) mediation web interface

For each ad placement (AdMob AdUnitId) in Google AdMob (ex. AdMob) mediation, create a corresponding ad unit (Ad Unit ID) in the Boost interface.

Next, add the Boost in the Google AdMob (ex. AdMob) mediation web interface:

1. Create a Google AdMob (ex. AdMob) ad unit

1. Go to your app section.
2. Create an ad unit for the selected ad format and configure the ad placement parameters (for example, its name).
3. After creating the ad unit, save its ID.

Screenshots from the Google AdMob (ex. AdMob) interface

2. Create a Yandex ad unit

Guide for creating an ad unit in the Boost interface.

3. Set up Google AdMob (ex. AdMob) mediation

1. In the Google AdMob (ex. AdMob) web interface, go to Mediation → Mediation groups and click Create mediation group.

2. Select a platform.

3. Set the mediation group parameters, such as name and region, then proceed to adding the ad placement.

4. Select your app, select the ad unit you created, and add it. The ad unit you added should appear in the Ad Units section.

5. The Boost can be added to Google AdMob (ex. AdMob) mediation only as a custom event. Click Add Custom Event to add a custom event. Set up your custom event for each adUnitId created in the Boost interface.

6. Configure a custom event for accessing the Boost by setting the event name and eCPM floor.

   Warning

   The eCPM floor currency and value must match the floor you set for the ad placement in the Boost interface.

   If you selected the Maximum revenue strategy for the ad placement in the Boost interface without a set floor, enter the expected or historical eCPM in AdMob. AdMob uses this value to position the custom event in the waterfall.

7. Set up mapping of the custom event to the Boost adapter:

   • Set the mapping name.
   • Set an adapter class name that corresponds to your selected ad format.
   • Set the event parameters.

   Each ad format has a corresponding Boost adapter class:

   • com.admob.mobileads.YandexBanner for banner ads.
   • com.admob.mobileads.YandexInterstitial for interstitial ads.
   • com.admob.mobileads.YandexRewarded for rewarded ads.
   • com.admob.mobileads.YandexNative for native ads.

   In the Parameter field, configure the custom event settings in JSON format. Make sure to set the Ad Unit ID for your selected ad placement: {"adUnitId": "R-M-XXXXXX-X"}.

   Warning

   The Boost adapter class name and the adUnitId JSON key are case-sensitive. Make sure you spell them correctly, otherwise ads might not load from the custom event.

   For native ads, when connecting to the Boost via Google AdMob (ex. AdMob), you must provide the store/storeView, which is needed to pass the required domain asset. If the storeView isn't registered or displayed, the impression may not be counted. For compact layouts, you can use a separate, single-line TextView without a signature, registered as the storeView.

8. Save the changes.

Screenshots from the Google AdMob (ex. AdMob) interface

4. Test the integration

Before you publish your app, make sure you've set up the custom event correctly:

1. Check that you entered the adapter class name exactly as shown in Step 7.
2. Make sure your custom event parameter uses the correct JSON format: {"adUnitId": "R-M-XXXXXX-X"}.
3. Test the integration using demo ad units or test placements.
4. Check your app logs and the Debug Panel for any adapter initialization or ad loading errors.