Select platform: [Android (beta)
![New](https://developers.google.com/static/admob/images/new.svg)](https://developers.google.com/admob/android/next-gen/mediation/verve "View this page for the Android (beta) platform docs.") [Android](https://developers.google.com/admob/android/mediation/verve "View this page for the Android platform docs.") [iOS](https://developers.google.com/admob/ios/mediation/verve "View this page for the iOS platform docs.")

<br />

This guide shows you how to use Google Mobile Ads SDK to load and display ads from
Verve HyBid SDK using [AdMob Mediation](https://developers.google.com/admob/android/mediation) covering bidding
integrations. It covers how to add Verve HyBid SDK to an ad unit's mediation
configuration, and how to integrate the Verve HyBid SDK and adapter into an
Android app.

## Supported integrations and ad formats

The mediation adapter for Verve HyBid SDK has the following capabilities:

| Integration ||
|---|---|
| Bidding | [^1^](https://developers.google.com/admob/android/mediation/verve#bidding-footnote) |
| Waterfall |   |
| Banner |   |
| Interstitial |   |
| Rewarded Interstitial |   |
| Rewarded |   |
| Native |   |

^1^
Bidding integration is in alpha. Reach out to your your account manager to
request access.

## Requirements

- Android API level 23 or higher

<!-- -->

- Latest Google Mobile Ads SDK

- Complete the mediation [Get started guide](https://developers.google.com/admob/android/mediation)

## Step 1: Set up configurations in Verve HyBid SDK UI

For configuration setup, publishers can reach out to their Verve account
manager.

## Step 2: Set up Verve HyBid SDK demand in AdMob UI

### Configure mediation settings for your ad unit

You need to add Verve HyBid SDK to the
mediation configuration for your ad unit.

First, sign in to your [AdMob account](https://apps.admob.com/). Next, navigate to the
**Mediation** tab. If you have an existing mediation group you'd like to modify,
click the name of that mediation group to edit it, and skip ahead to
[Add Verve HyBid SDK as an ad source](https://developers.google.com/admob/android/mediation/verve#add-ad-source).

To create a new mediation group, select **Create Mediation Group**.

![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-create.png)

Enter your ad format and platform, then click **Continue**.

![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-new-Android.png)

Give your mediation group a name, and select locations to target. Next, set the
mediation group status to **Enabled** , and then click **Add Ad Units**.

![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-details-Android.png)

Associate this mediation group with one or more of your existing
AdMob ad units. Then click **Done**.

![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-select-Android.png)

You should now see the ad units card populated with the ad units you selected:

![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-card-Android.png)

#### Add Verve HyBid SDK as an ad source

Under the **Bidding** card in the **Ad Sources** section, select **Add
ad source** . Then select **Verve HyBid SDK** .  

Click **How to sign a partnership agreement** and [set up a bidding partnership](https://support.google.com/admob/answer/9842838) with Verve HyBid SDK.   

![](https://developers.google.com/static/admob/images/mediation/verve/bidding-agreement-1.png)   

Click **Acknowledge \& agree** , then click **Continue** .   

![](https://developers.google.com/static/admob/images/mediation/verve/bidding-agreement-2.png)   

If you already have a mapping for Verve HyBid SDK, you can select it. Otherwise, click **Add mapping** .   

![](https://developers.google.com/static/admob/images/mediation/verve/bidding-add-mapping-1-Android.png)   

Next, enter the **Zone ID** and **AppToken** obtained in the previous section. Then click **Done** .   

![](https://developers.google.com/static/admob/images/mediation/verve/bidding-add-mapping-2-Android.png)

### Add Verve Group to GDPR and US state regulations ad partners list

| **Important:** Verify that you have **Account Management** permission to complete the configuration for EU Consent and GDPR, US State regulations, and User Messaging Platform. See [Manage user access to your
| account](https://support.google.com/admob/answer/2784628) for details.

Follow the steps in

[European regulations settings](https://support.google.com/admob/answer/10113004#adding_ad_partners_to_published_gdpr_messages)

and

[US state regulations settings](https://support.google.com/admob/answer/14125907)

to add **Verve Group** to the
European and US state regulations ad partners list in the AdMob UI.

## Step 3: Import the Verve HyBid SDK and adapter

| **Note:** Failure to integrate the compatible Verve HyBid SDK and Google Mobile Ads SDK versions might lead to build issues.

### Android Studio integration (recommended)

In your project-level `settings.gradle.kts` file, add the following
repositories:  

    dependencyResolutionManagement {
      repositories {
        google()
        mavenCentral()
        maven {
    url = uri("https://verve.jfrog.io/artifactory/verve-gradle-release")
    }
      }
    }

Then, in your app-level `build.gradle.kts` file, add the following
implementation dependencies and configurations. Use the latest versions of the
Verve HyBid SDK and adapter:  

    dependencies {
        implementation("com.google.android.gms:play-services-ads:24.9.0")
        implementation("com.google.ads.mediation:verve:3.7.1.0")
    }

## Step 4: Implement privacy settings on Verve SDK

### EU Consent and GDPR


To [comply with
Google EU User Consent Policy](https://www.google.com/about/company/consentstaging.html), you must make certain disclosures to your
users in the European Economic Area (EEA), the UK, and Switzerland, and obtain
their consent for the use of cookies or other local storage where legally
required, and for the collection, sharing, and use of personal data for ads
personalization. This policy reflects the requirements of the EU ePrivacy
Directive and the General Data Protection Regulation (GDPR). You are
responsible for verifying consent is propagated to each ad source in your
mediation chain.
Google is unable to pass the user's
consent choice to such networks automatically.

See Verve HyBid SDK's privacy [documentation](https://github.com/pubnative/pubnative-hybid-android-sdk/wiki/GDPR-TCF-Compliance) for more information.

### US states privacy laws


[US states privacy laws](https://support.google.com/admob/answer/9561022)
require giving users the right
to opt out of the "sale" of their "personal information" (as the law defines
those terms), with the opt-out offered through a prominent "Do Not Sell My Personal
Information" link on the "selling" party's homepage. The
[US states privacy
laws compliance guide](https://developers.google.com/admob/android/privacy/us-states) offers the ability to enable
[restricted data processing](https://privacy.google.com/businesses/rdp/)
for Google ad serving, but Google is unable to apply this setting to each ad
network in your mediation chain. Therefore, you must identify each ad network
in your mediation chain that may participate in the sale of personal
information and follow guidance from each of those networks to ensure
compliance.

See Verve HyBid SDK's privacy [documentation](https://github.com/pubnative/pubnative-hybid-android-sdk/wiki/CCPA-compliance) for more information.

## Step 5: Add required code

No additional code is required for Verve HyBid SDK integration.

## Step 6: Test your implementation

### Enable test ads

Make sure you
[register your test device](https://developers.google.com/admob/android/test-ads#enable_test_devices)
for

AdMob.


| **Important:** Disable test mode for AdMob and Verve HyBid SDK before releasing your app.

### Verify test ads

To verify that you are receiving test ads from
Verve HyBid SDK,
enable
[single ad source testing](https://developers.google.com/admob/android/ad-inspector#single_ad_source_testing)
in ad inspector using the
**Verve (Bidding)** ad source(s).

Follow [Verve HyBid SDK's documentation](https://github.com/pubnative/pubnative-hybid-android-sdk/wiki/HyBid-Configuration) for additional configuration.

## Error codes

If the adapter fails to receive an ad from Verve HyBid SDK, publishers can
check the underlying error from the ad response using


[`ResponseInfo.getAdapterResponses()`](https://developers.google.com/admob/android/reference/com/google/android/gms/ads/ResponseInfo#getAdapterResponses())

under the following classes:  

    net.pubnative.lite.sdk
    com.google.ads.mediation.verve

Here are the codes and accompanying messages thrown by the Verve HyBid SDK
adapter when an ad fails to load:

| Error code | Reason |
|---|---|
| 100 to 103 | Verve HyBid SDK returned an error. |
| 101 | The requested ad size does not match a Verve HyBid SDK supported banner size. |
| 102 | Missing or empty app token. |
| 103 | Context is null. |

## Verve Android Mediation Adapter Changelog

#### Version 3.7.1.0

- Initial release.
- Verified compatibility with Verve HyBid SDK version 3.7.1.

Built and tested with:

- Google Mobile Ads SDK version 24.8.0.
- Verve HyBid SDK version 3.7.1.