---
layout: page_v2
title: Prebid Mobile - Next-Gen SDK Bidding-Only Integration - Android
description: Integration of Prebid SDK Android with Google Next-Gen SDK using the 'Bidding-Only' integration
sidebarType: 2
---

# Prebid SDK Android with the Next-Gen SDK Bidding-Only Integration Method
{:.no_toc}

- TOC
{:toc}

{% include mobile/intro-nextgen-bidding-only.md platform='android' %}

## AdUnit-Specific instructions

This section describes the integration details for different ad formats. In each scenario, you'll be asked for a `configId` - this is a key established in conjunction with your Prebid Server provider. It's used at runtime to pull in the bidders and parameters specific to this adunit. Depending on your Prebid Server partner, it may be a UUID or constructed out of parts like an account number and adunit name.

### [Format: HTML Banner](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-html-banner.html)

### [Format: Interstitial Banner](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-interstitial-banner.html)

### [Format: Non-Instream Video](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-video-outstream.html)

### [Format: Interstitial Video](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-interstitial-video.html)

### [Format: Rewarded Video Ad](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-rewarded-video.html)

### [Format: Native In-App](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-native-in-app.html)

### [Format: Native In-Webview](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-native-in-webview.html)

### [Format: Multiformat (Banner+Video+InApp Native)](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-multiformat.html)

### [Format: Multiformat Interstitial (Banner+Video)](/prebid-mobile/recipes/subrecipes/android/nextgen-bidding-only-multiformat-interstitial.html)

## Additional Ad Unit Configuration

{% include mobile/adunit-config-android.md %}

### Impression tracking

In the Bidding-Only integration scenario, the Prebid SDK is responsible for tracking events for banner ads, like `burl`, `imp`, and `win`. The disadvantage of this approach is that the SDK doesn't have reliable information about the viewability of the WebView. As a result, impression tracking happens at the rendering stage of the ad. Or, if MRAID is supported, once the `viewableChange` event is fired. It leads to big discrepancies since the "1 pixel in view" requirement is not met.

To activate impression tracking for the banner ad unit - use the `activatePrebidImpressionTracker(adView)` method. The `adView` parameter should be an instance of the Next-Gen SDK `AdView`:

```kotlin
adUnit.activatePrebidImpressionTracker(adView)
adUnit.fetchDemand(adRequestBuilder) { ... }
```

For activation for the interstitial ad unit, you should call `activateInterstitialPrebidImpressionTracker()`:

```kotlin
adUnit = InterstitialAdUnit(CONFIG_ID, WIDTH, HEIGHT)
adUnit.activateInterstitialPrebidImpressionTracker()
```

After the invocation of `activateInterstitialPrebidImpressionTracker()`, the Prebid SDK will start analyzing the View Hierarchy and track the viewability of the ad view. Once the ad view is viewable for the user for at least 1 pixel for 1 second, the SDK will track an impression event for the presented ad. The SDK will stop analyzing the View Hierarchy once the caller object is destroyed.

## Further Reading

- [Prebid Mobile Overview](/prebid-mobile/prebid-mobile.html)
- [Prebid SDK Android Integration](/prebid-mobile/pbm-api/android/code-integration-android.html)
- [Prebid SDK Android Global Parameters](/prebid-mobile/pbm-api/android/pbm-targeting-android.html)