Integrate Chartboost with Mediation

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from Chartboost using mediation, covering waterfall integrations. It covers how to add Chartboost to an ad unit's mediation configuration, and how to integrate the Chartboost SDK and adapter into an Android app.

Supported integrations and ad formats

The Ad Manager mediation adapter for Chartboost has the following capabilities:

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded
Native

Requirements

• Android API level 21 or higher

• Latest Google Mobile Ads SDK

  • Complete the mediation Get started guide

Step 1: Set up configurations in Chartboost UI

Sign up for a Chartboost account and log in once your account is verified. Click the + APP button on the left sidebar. Fill out the form and click Save to add your app to Chartboost.

Then, in your Chartboost dashboard for your app, navigate to App Settings > Basic Settings to locate your App ID and App Signature.

Ad Manager requires the Chartboost User ID and User Signature for setting up your Ad Manager ad unit ID. You can find these parameters on your Chartboost dashboard by navigating to Tools > API Explorer. Your User ID and User Signature are located under the Authentication section.

Turn on test mode

Test ads can be enabled for your app from Chartboost's dashboard under the App Settings > Basic Settings as shown below.

Once test mode is enabled, you can request ads using the ad unit ID created earlier and receive a Chartboost test ad.

Step 2: Set up Chartboost demand in Ad Manager UI

Configure mediation settings for your ad unit

Sign in to your Ad Manager account. Navigate to Delivery > Yield groups and click the New yield group button.

Enter a unique Name for your yield group, set the Status to Active, select your Ad Format, and set the Inventory type to Mobile App. Under the Targeting > Inventory section, select the Ad Unit ID to which you want to add mediation.

Next, click the Add yield partner button.

If you already have a Yield partner for Chartboost, you can simply select it. Otherwise, select Create a new yield partner.

Select Chartboost as the Ad network and enter a unique Name. Enable Mediation and turn on Automatic data collection, and enter the User ID and User Signature obtained in the previous section. You don't need to enter a Username and Password. Click Save when done.

Once the Yield partner is selected, choose Mobile SDK mediation as the Integration type, Android as the Platform, and Active as the Status. Enter the App ID and the App Signature obtained in the previous section. Also, enter an Ad Location (e.g. "Game Over Screen") that uniquely identifies this placement in your app and a Default CPM value.

Chartboost Ad Locations (Named Locations) are simple names representing a place in your app where you want to show an ad. Ad Manager sends requests to the location specified in the settings. Once requests are sent, Chartboost will add the location to its dashboard for reporting purposes.

Note: Ad Manager is able to estimate CPMs for the top three Ad Locations in your Chartboost app. All other locations will be represented with a blended CPM.

In the Chartboost dashboard, your Ad Locations can be revealed in the Basic Settings page by clicking on Advanced Settings. Please see the Chartboost's Named Locations guide for more details.

Click Save at the bottom of the page when done.

Note: Automatic data collection takes a few days to gather data before it can accurately calculate a Dynamic CPM value for a mediation network. Once the eCPM can be calculated, it will be automatically updated on your behalf

Add Chartboost 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, CPRA, and User Messaging Platform. See Manage user access to your account for details.

Follow the steps in GDPR settings and US state regulations settings to add Chartboost to the GDPR and US state regulations ad partners list in the Ad Manager UI.

Step 3: Import the Chartboost SDK and adapter

Note: Failure to integrate the compatible Chartboost and Google Mobile Ads SDK versions might lead to build issues.

Android Studio integration (recommended)

Add the following Maven repository and the implementation dependencies with the latest versions of the Chartboost SDK and adapter to your app-level build.gradle file:

repositories {
    google()
    mavenCentral()
}

...
dependencies {
    implementation 'com.google.android.gms:play-services-ads:22.5.0'
    implementation 'com.google.ads.mediation:chartboost:9.5.0.0'
}
...

Manual integration

1. Download the .aar file of the latest version of the Chartboost SDK from Maven Central, and add it to your project.

2. Navigate to the Chartboost adapter artifacts on Google's Maven Repository. Select the latest version, download the Chartboost adapter's .aar file, and add it to your project.

Step 4: Implement privacy settings on Chartboost SDK

EU consent and GDPR

Under the Google EU User Consent Policy, you must ensure that certain disclosures are given to, and consents obtained from, users in the European Economic Area (EEA) regarding the use of device identifiers and personal data. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). When seeking consent, you must identify each ad network in your mediation chain that may collect, receive, or use personal data and provide information about each network's use. Google currently is unable to pass the user's consent choice to such networks automatically.

In SDK version 8.1.0, Chartboost added the addDataUseConsent() method. The following sample code sets data use consent to NON_BEHAVIORAL. If you choose to call this method, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

Java

DataUseConsent dataUseConsent = new GDPR(GDPR.GDPR_CONSENT.NON_BEHAVIORAL);
Chartboost.addDataUseConsent(context, dataUseConsent);

Kotlin

val dataUseConsent = GDPR(GDPR.GDPR_CONSENT.NON_BEHAVIORAL)
Chartboost.addDataUseConsent(context, dataUseConsent)

See Chartboost's GDPR article and their Android Privacy Methods for more details and the values that can be provided in each method.

US states privacy laws

U.S. states privacy laws 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 via a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The U.S. states privacy laws compliance guide offers the ability to enable restricted data processing 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.

In SDK version 8.1.0, Chartboost added the addDataUseConsent() method. The following sample code sets data use consent to OPT_IN_SALE. If you choose to call this method, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

Java

DataUseConsent dataUseConsent = new CCPA(CCPA.CCPA_CONSENT.OPT_IN_SALE);
Chartboost.addDataUseConsent(context, dataUseConsent);

Kotlin

val dataUseConsent = CCPA(CCPA.CCPA_CONSENT.OPT_IN_SALE)
Chartboost.addDataUseConsent(context, dataUseConsent)

See Chartboost's CCPA article and their Android Privacy Methods for more details and the values that can be provided in each method.

Step 5: Add required code

Modify AndroidManifest

Other elements

Add the following attribute to each activity in the AndroidManifest.xml file that will be showing Chartboost ads and supports different orientations:

android:configChanges="keyboardHidden|orientation|screenSize"

Lifecycle events

Per Chartboost's recommendation, Add the following code to all of your activity's lifecycle events that will be showing Chartboost ads.

Java

import com.chartboost.sdk.Chartboost;
// ...

@Override
public void onBackPressed() {
    // If an interstitial is on screen, close it.
    if (Chartboost.onBackPressed()) {
        return;
    } else {
        super.onBackPressed();
    }
}

Kotlin

import com.chartboost.sdk.Chartboost
// ...

@Override
fun onBackPressed() {
    // If an interstitial is on screen, close it.
    if (Chartboost.onBackPressed())
        return
    else
        super.onBackPressed()
}

Step 6: Test your implementation

Enable test ads

Make sure you register your test device for Ad Manager and enable test mode in Chartboost UI.

Important: Disable test mode for Ad Manager and Chartboost before releasing your app.

Verify test ads

To verify that you are receiving test ads from Chartboost, enable single ad source testing in ad inspector using the Chartboost (Waterfall) ad source(s).

Step 7: Prepare app for production

After you are able to receive Chartboost test ads, your app will be placed on Chartboost's Publisher App Review. Once your app is approved, you can then create your Publishing Campaign to configure your app for live Chartboost ads.

Navigate to Monetization > Publishing Campaigns from the left-side menu and click Add a Campaign (or + Add Campaign at the top right corner of your dashboard if you already have other campaigns) and choose Network Publishing when prompted.

Enter a Name for your publishing campaign, select the Placement Type, and select Google Play as the Platform. If your app has been approved by Chartboost, you'll be able to select your app and apply it to this campaign. Fill out the rest of the form and click Save to finish adding the campaign.

Optional steps

Permissions

For optimal performance, Chartboost recommends adding the following optional permissions to your app's AndroidManifest.xml file:

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />

Error codes

If the adapter fails to receive an ad from Chartboost, you can check the underlying error from the ad response using ResponseInfo.getAdapterResponse() under the following classes:

com.google.ads.mediation.chartboost.ChartboostAdapter
com.google.ads.mediation.chartboost.ChartboostMediationAdapter

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

Error code	Reason
0-99	Chartboost SDK returned an error. See Chartboost's documentation for more details.
101	The requested ad size does not match a Chartboost supported banner size.
102	Chartboost can only load 1 ad per location at a time.
103	Chartboost server parameters configured in the Ad Manager UI are missing/invalid.
104	The Chartboost interstitial or rewarded ad is not ready to be shown.

Additional resources

Start a Publishing Campaign provides additional details on how to set up Chartboost publishing campaigns.

Chartboost Android Mediation Adapter Changelog

Version 9.5.0.0

• Updated the minimum required Google Mobile Ads SDK version to 22.3.0.
• Verified compatibility with Chartboost SDK version 9.5.0.

Built and tested with:

• Google Mobile Ads SDK version 22.3.0.
• Chartboost SDK version 9.5.0.

Version 9.4.1.0

• Verified compatibility with Chartboost SDK version 9.4.1.

Built and tested with:

• Google Mobile Ads SDK version 22.2.0.
• Chartboost SDK version 9.4.1.

Version 9.4.0.0

• Verified compatibility with Chartboost SDK version 9.4.0.

Built and tested with:

• Google Mobile Ads SDK version 22.1.0.
• Chartboost SDK version 9.4.0.

Version 9.3.1.0

• Verified compatibility with Chartboost SDK version 9.3.1.

Built and tested with:

• Google Mobile Ads SDK version 22.1.0.
• Chartboost SDK version 9.3.1.

Version 9.3.0.0

• Verified compatibility with Chartboost SDK version 9.3.0.

Built and tested with:

• Google Mobile Ads SDK version 22.0.0.
• Chartboost SDK version 9.3.0.

Version 9.2.1.1

• Updated adapter to use new VersionInfo class.
• Updated the minimum required Google Mobile Ads SDK version to 22.0.0.

Built and tested with:

• Google Mobile Ads SDK version 22.0.0.
• Chartboost SDK version 9.2.1.

Version 9.2.1.0

• Verified compatibility with Chartboost SDK 9.2.1.

Built and tested with:

• Google Mobile Ads SDK version 21.5.0.
• Chartboost SDK version 9.2.1.

Version 9.2.0.0

• Verified compatibility with Chartboost SDK 9.2.0.
• Updated the minimum required Google Mobile Ads SDK version to 21.5.0.

Built and tested with:

• Google Mobile Ads SDK version 21.5.0.
• Chartboost SDK version 9.2.0.

Version 9.1.1.0

• Added the ChartboostMediationAdapter.setAppParams(String, String) method as an optional way to hardcode which app ID and app signature to use to initialize the Chartboost SDK.
• Verified compatibility with Chartboost SDK 9.1.1.
• Updated the minimum required Google Mobile Ads SDK version to 21.3.0.

Built and tested with:

• Google Mobile Ads SDK version 21.3.0.
• Chartboost SDK version 9.1.1.

Version 8.4.3.1

• Updated the minimum required Google Mobile Ads SDK version to 21.0.0.
• Updated the minimum required Android API level to 19.

Built and tested with:

• Google Mobile Ads SDK version 21.0.0.
• Chartboost SDK version 8.4.3.

Version 8.4.3.0

• Verified compatibility with Chartboost SDK 8.4.3.

Built and tested with:

• Google Mobile Ads SDK version 20.6.0.
• Chartboost SDK version 8.4.3.

Version 8.4.2.0

• Verified compatibility with Chartboost SDK 8.4.2.
• Updated compileSdkVersion and targetSdkVersion to API 31.
• Updated the minimum required Google Mobile Ads SDK version to 20.6.0.

Built and tested with:

• Google Mobile Ads SDK version 20.6.0.
• Chartboost SDK version 8.4.2.

Version 8.4.1.0

• Verified compatibility with Chartboost SDK 8.4.1.
• Updated the minimum required Google Mobile Ads SDK version to 20.6.0.

Built and tested with:

• Google Mobile Ads SDK version 20.6.0.
• Chartboost SDK version 8.4.1.

Version 8.3.1.0

• Verified compatibility with Chartboost SDK 8.3.1.
• Updated the adapter to use new AdError API.

Built and tested with:

• Google Mobile Ads SDK version 20.5.0.
• Chartboost SDK version 8.3.1.

Version 8.3.0.0

• Verified compatibility with Chartboost SDK 8.3.0.
• Updated the minimum required Google Mobile Ads SDK version to 20.5.0.

Built and tested with:

• Google Mobile Ads SDK version 20.5.0.
• Chartboost SDK version 8.3.0.

Version 8.2.1.0

• Verified compatibility with Chartboost SDK 8.2.1.
• Updated the minimum required Google Mobile Ads SDK version to 20.1.0.

Built and tested with:

• Google Mobile Ads SDK version 20.1.0.
• Chartboost SDK version 8.2.1.

Version 8.2.0.1

• Updated the minimum required Google Mobile Ads SDK version to 20.0.0.

Built and tested with:

• Google Mobile Ads SDK version 20.0.0.
• Chartboost SDK version 8.2.0.

Version 8.2.0.0

• Verified compatibility with Chartboost SDK 8.2.0.
• Updated the minimum required Google Mobile Ads SDK version to 19.5.0.

Built and tested with:

• Google Mobile Ads SDK version 19.5.0.
• Chartboost SDK version 8.2.0.

Version 8.1.0.0

• Verified compatibility with Chartboost SDK 8.1.0.

Built and tested with:

• Google Mobile Ads SDK version 19.2.0.
• Chartboost SDK version 8.1.0.

Version 8.0.3.2

• Added descriptive error codes and reasons for adapter load/show failures.
• Updated the minimum required Google Mobile Ads SDK version to 19.2.0.

Built and tested with:

• Google Mobile Ads SDK version 19.2.0.
• Chartboost SDK version 8.0.3.

Version 8.0.3.1

• Added support for Chartboost banner ads.

Built and tested with:

• Google Mobile Ads SDK version 19.1.0.
• Chartboost SDK version 8.0.3.

Version 8.0.3.0

• Verified compatibility with Chartboost SDK 8.0.3.
• Updated the minimum required Google Mobile Ads SDK version to 19.1.0.

Built and tested with:

• Google Mobile Ads SDK version 19.1.0.
• Chartboost SDK version 8.0.3.

Version 8.0.2.0

• Verified compatibility with Chartboost SDK 8.0.2.
• Updated the minimum required Google Mobile Ads SDK version to 19.0.1.

Built and tested with:

• Google Mobile Ads SDK version 19.0.1.
• Chartboost SDK version 8.0.2.

Version 8.0.1.0

• Verified compatibility with Chartboost SDK 8.0.1.
• Requires Chartboost SDK 8.0.1 or higher.
• Activity context is no longer required to load ads.

Built and tested with:

• Google Mobile Ads SDK version 18.3.0.
• Chartboost SDK version 8.0.1.

Version 7.5.0.1

• Fixed a bug where Chartboost adapter failed to invoke ad events.
• Updated the minimum required Google Mobile Ads SDK version to 18.3.0.

Built and tested with:

• Google Mobile Ads SDK version 18.3.0.
• Chartboost SDK version 7.5.0.

Version 7.5.0.0

• Verified compatibility with Chartboost SDK 7.5.0.
• Migrated the adapter to use AndroidX dependencies.
• Updated the minimum required Google Mobile Ads SDK version to 18.1.1.

Version 7.3.1.1

• Updated adapter to support new open-beta Rewarded API.
• Updated the minimum required Google Mobile Ads SDK version to 17.2.0.

Version 7.3.1.0

• Verified compatibility with Chartboost SDK 7.3.1.

Version 7.3.0.0

• Verified compatibility with Chartboost SDK 7.3.0.

Version 7.2.1.0

• Verified compatibility with Chartboost SDK 7.2.1.

Version 7.2.0.1

• Updated the adapter to invoke the onRewardedVideoComplete() ad event.

Version 7.2.0.0

• Verified compatibility with Chartboost SDK 7.2.0.

Version 7.1.0.0

• Verified compatibility with Chartboost SDK 7.1.0.

Version 7.0.1.0

• Verified compatibility with Chartboost SDK 7.0.1.
• Added support for new Chartboost error codes.
• Updated the Adapter project for Android Studio 3.0

Version 7.0.0.0

• Updated the adapter to make it compatible with Chartboost SDK 7.0.0.

Version 6.6.3.0

• Verified compatibility with Chartboost SDK 6.6.3.

Version 6.6.2.0

• Verified compatibility with Chartboost SDK 6.6.2.

Version 6.6.1.0

• Verified compatibility with Chartboost SDK 6.6.1.

Version 6.6.0.0

• Changed the version naming system to [Chartboost SDK version].[adapter patch version].
• The adapters can now be added as a compile dependency by adding the following to the build.gradle file's dependencies tag: compile 'com.google.ads.mediation:chartboost:6.6.0.0'
• Moved to distributing the adapter as an aar instead of a jar file (see README for additional instructions).

Version 1.1.0

• Removed Chartboost Ad Location from Chartboost extras. Ad Location is now specified in the AdMob console when configuring Chartboost for mediation.

Version 1.0.0

• Initial release. Supports reward-based video ads and interstitial ads.