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 amajor.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 amajor.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 iOS specific adapters from the top right menu.
For CocoaPods users, Mediation adapters can be downloaded, along with their dependent ad network SDKs, by adding the following to your Podfile:
# Chartboost Mediation Adapter for AdMob
pod 'ChartboostMediationAdapterAdMob'
# Chartboost Mediation Adapter for Amazon Publisher Services
pod 'ChartboostMediationAdapterAmazonPublisherServices'
# Chartboost Mediation Adapter for AppLovin
pod 'ChartboostMediationAdapterAppLovin'
# Chartboost Mediation Adapter for Chartboost
pod 'ChartboostMediationAdapterChartboost'
# Chartboost Mediation Adapter for Digital Turbine Exchange (Fyber)
pod 'ChartboostMediationAdapterDigitalTurbineExchange'
# Chartboost Mediation Adapter for Google Bidding
pod 'ChartboostMediationAdapterGoogleBidding'
# Chartboost Mediation Adapter for HyprMX
pod 'ChartboostMediationAdapterHyprMX'
# Chartboost Mediation Adapter for InMobi
pod 'ChartboostMediationAdapterInMobi'
# Chartboost Mediation Adapter for Liftoff Monetize (Vungle)
pod 'ChartboostMediationAdapterVungle'
# Chartboost Mediation Adapter for ironSource
pod 'ChartboostMediationAdapterIronSource'
# Chartboost Mediation Adapter for Meta Audience Network
pod 'ChartboostMediationAdapterMetaAudienceNetwork'
# Chartboost Mediation Adapter for Mintegral
pod 'ChartboostMediationAdapterMintegral'
# Chartboost Mediation Adapter for MobileFuse
pod 'ChartboostMediationAdapterMobileFuse'
# Chartboost Mediation Adapter for Pangle
pod 'ChartboostMediationAdapterPangle'
# Chartboost Mediation Adapter for UnityAds
pod 'ChartboostMediationAdapterUnityAds'
Adapter Repositories π
Partner SDK Integration π
Partner SDK Integration Docs | Additional Integration Notes |
---|---|
AdMob/Google Bidding |
|
Amazon Publisher Services | |
AppLovin | |
Bidmachine | To integrate with Bidmachine SDK, contact your Bidmachine account manager. |
Chartboost Monetization | |
Digital Turbine Exchange (Fyber) | |
HyprMX | |
InMobi | |
ironSource | |
Liftoff Monetize (Vungle) | |
Meta Audience Network | Starting with Meta Audience Network 5.4.x, there are additional frameworks that their SDKs require: FBBSDKCoreKit_Basics and the AudioToolbox framework.
|
Mintegral | |
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(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)