Mediation

Integrate Network SDKs

Dependency Resolution & Google External Dependency Manager (EDM) πŸ”—

The Chartboost Mediation Unity SDK does not embed Google’s EDM plugin.

If you want to integrate ad networks with other supported SDKs as well, you will need Google’s External Dependency Manager. For more information see our recommended setup in Google External Dependency Manager (EDM).

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 πŸ”—

Starting with Chartboost Mediation 5.X series, Unity adapters are now distributed individually in npm and NuGet.

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 Unity specific adapters from the top right menu.

Adapter Repositories πŸ”—

The following table lists all of the open source repositories for the Unity adapter wrappers.

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

Dependency.xml Files πŸ”—

All Dependency.xml files are now embedded in each package Editor directory. This means they can’t be direclty overwritten. However, this can bypassed as needed by creating a duplicate of such file under your Assets directory where modifications can be done as needed.

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 πŸ”—

// Given
HyprMXAdapter.SetConsentStatusOverride(HyprMXConsentStatus.ConsentGiven);

// Declined
HyprMXAdapter.SetConsentStatusOverride(HyprMXConsentStatus.ConsentDeclined);

// Unknown
HyprMXAdapter.SetConsentStatusOverride(HyprMXConsentStatus.ConsentDeclined);

Pangle πŸ”—

// Consent
PangleAdapter.SetGDPRConsentOverride(PangleGDPRConsentType.PangleGDPRConsentConsent);

// No Consent
PangleAdapter.SetGDPRConsentOverride(PangleGDPRConsentType.PangleGDPRConsentNoConsent);

// Default
PangleAdapter.SetGDPRConsentOverride(PangleGDPRConsentType.PangleGDPRConsentTypeDefault);

// Sell
PangleAdapter.SetDoNotSellOverride(PangleDoNotSellType.PangleGDoNotSellTypeSell);

// Not Sell
PangleAdapter.SetDoNotSellOverride(PangleDoNotSellType.PangleDoNotSellTypeNotSell);

// Default
PangleAdapter.SetDoNotSellOverride(PangleDoNotSellType.PangleDoNotSellTypeDefault);

UnityAds πŸ”—

// Consent
UnityAdsAdapter.SetGDPRConsentOverride(true);


// No Consent
UnityAdsAdapter.SetGDPRConsentOverride(false);

// Consent
UnityAdsAdapter.SetPrivacyConsentOverride(true);

// No Consent
UnityAdsAdapter.SetPrivacyConsentOverride(false);

Vungle πŸ”—

// Consent
VungleAdapter.SetGDPRStatusOverride(true);


// No Consent
VungleAdapter.SetGDPRStatusOverride(false);

// Consent
VungleAdapter.SetCCPAStatusOverride(true);

// No Consent
VungleAdapter.SetCCPAStatusOverride(false);