Mediation

Integrate Network SDKs

Partner Adapter Integration πŸ”—

Mediation adapters are required to use other ad networks with Mediation.

Adapter Versioning Scheme πŸ”—

The partner adapter versions uses floating pegs and are formatted as follows:

<chartboost_mediation_sdk_major_version>.<partner_sdk_version>.<adapter_revision>
  • Chartboost Mediation SDK Major Version: The major version of the Chartboost Mediation SDK that the adapter is compatible with.
  • Partner SDK Version: The full partner SDK version that the adapter is compatible with. Note that this could be the traditional major.minor.patch version scheme, but there are some partners that have a major.minor.patch.revision version scheme.
  • Adapter Revision: The full partner SDK version that the adapter is compatible with. Note that this could be the traditional major.minor.patch version scheme, but there are some partners that have a major.minor.patch.revision version scheme.

Examples:

Partner Adapter Version Chartboost Mediation SDK Major Version Compatible Partner SDK Version Adapter Revision
AdMob 4.21.5.0.2 4 21.5.0 2
IronSource 5.7.2.5.1.0 5 7.2.5.1 0

Adapter Integration πŸ”—

Utilize our Chartboost Mediation Adapters below to compare which partners are ideal for you to integrate with. You can filter by ad format from the top right menu and compare selected partners. Click into the chosen partner for the latest supported partner adapter versions and integration guide or visit their adapter repository.

Be sure you are navigated to the Android specific adapters from the top right menu.

Adapter Repositories πŸ”—

Partner Network Android Repository
AdMob https://github.com/ChartBoost/chartboost-mediation-android-adapter-admob
Amazon Publisher Services https://github.com/ChartBoost/chartboost-mediation-android-adapter-amazon-publisher-services
AppLovin https://github.com/ChartBoost/chartboost-mediation-android-adapter-applovin
BidMachine https://github.com/ChartBoost/chartboost-mediation-android-adapter-bidmachine
Chartboost Monetization https://github.com/ChartBoost/chartboost-mediation-android-adapter-chartboost
Digital Turbine Exchange (Fyber) https://github.com/ChartBoost/chartboost-mediation-android-adapter-digital-turbine-exchange
Google Bidding https://github.com/ChartBoost/chartboost-mediation-android-adapter-google-bidding
HyprMX https://github.com/ChartBoost/chartboost-mediation-android-adapter-hyprmx
InMobi https://github.com/ChartBoost/chartboost-mediation-android-adapter-inmobi
ironSource https://github.com/ChartBoost/chartboost-mediation-android-adapter-ironsource
Liftoff Monetize (Vungle) https://github.com/ChartBoost/chartboost-mediation-android-adapter-vungle
Meta Audience Network https://github.com/ChartBoost/chartboost-mediation-android-adapter-meta-audience-network
Mintegral https://github.com/ChartBoost/chartboost-mediation-android-adapter-mintegral
MobileFuse https://github.com/ChartBoost/chartboost-mediation-android-adapter-mobilefuse
Pangle https://github.com/ChartBoost/chartboost-mediation-android-adapter-pangle
Unity Ads https://github.com/ChartBoost/chartboost-mediation-android-adapter-unity-ads

Partner SDK Integration πŸ”—

Partner SDK Integration Docs Additional Integration Notes
AdMob/Google Bidding The latest versions of AdMob require the usage of AndroidX support libraries.
Amazon Publisher Services
AppLovin
Bidmachine To integrate with Bidmachine SDK, contact your Bidmachine account manager.
Chartboost Monetization
Digital Turbine Exchange (Fyber)
HyprMX
  • HyprMX requires a unique generated identifier that needs to be static across sessions during its SDK initialization.
  • The ageRestrictedUser flag needs to be set before the Chartboost Mediation initializes to appropriately apply child-directed treatment to a user.
InMobi
ironSource ironSource provides their own Maven Repository, therefore does not use Maven Central to distribute their SDKs.
Liftoff Monetize (Vungle)
Meta Audience Network In addition, publishers may be needed to include the following in their network security config file (network_security_config.xml). 

  • <?xml version="1.0" encoding="utf-8"?>
<network-security-config>
  <domain-config cleartextTrafficPermitted="true">
    <domain includeSubdomains="true">127.0.0.1</domain>
  </domain-config>
</network-security-config>
And update AndroidManifest.xml 

  • <?xml version="1.0" encoding="utf-8"?>
<manifest ... >
<application android:networkSecurityConfig="@xml/network_security_config"
... >
...
</application>
</manifest>
For more information on Meta network security configuration check Network Security Config.
Mintegral Mintegral provides their own Maven Repository, therefore does not use Maven Central to distribute their SDKs.
Pangle
Unity Ads

Partner Consents πŸ”—

All privacy and consent information is configured via the Chartboost Core SDK’s Consent Management Platform.

The Mediation SDK will utilize the TCFv2 string as part of auction requests, and will forward consent changes to the partner adapters.

The following partners utilize complex non-IAB compliant privacy and consent signals that cannot be extrapolated from Core SDK consent signals. Last resort APIs will be exposed via that partner adapter’s AdapterConfiguration class and must be manually set.

HyprMX πŸ”— 

// Set consent status directly on the adapter configuration
HyprMXAdapterConfiguration.setConsentStatusOverride(context, CONSENT_GIVEN)

Pangle πŸ”— 

// Set consent status directly on the adapter configuration
PangleAdapterConfiguration.setGdprConsentOverride(consent) // this is an int
PangleAdapterConfiguration.setDoNotSellOverride(doNotSell) // this is an int

Unity Ads πŸ”— 

// Set consent status directly on the adapter configuration
UnityAdsAdapterConfiguration.setGdprConsentOverride(context, true)
UnityAdsAdapterConfiguration.setPrivacyConsentOverride(context, true)

Vungle πŸ”— 

// Set consent status directly on the adapter configuration
VungleAdapterConfiguration.setGdprStatusOverride(true)
VungleAdapterConfiguration.setCcpaStatusOverride(true)