Chartboost Mediation Unity SDK

Summary

Chartboost Mediation Unity SDK provides support for Unity based games to easily integrate the Chartboost Mediation for Android & iOS platforms. This guide will contain step by step instructions on how to integrate the SDK, as well as recommended practices to make best use of all the features offered by the Chartboost Mediation SDK.

Minimum Requirements

| Plugin | Version | | ------ | ------ | | Cocoapods | 1.11.3+ | | iOS | 11.0+ | | Xcode | 14.1+ | | Android API | 21+ | | Unity | 2022.3.+ |

Integration

Using the public npm registry

In order to add the Chartboost Core Unity SDK to your project using the npm package, add the following to your Unity Project's manifest.json file. The scoped registry section is required in order to fetch packages from the NpmJS registry.

"dependencies": {
    "com.chartboost.mediation": "5.2.0",
    ...
},
"scopedRegistries": [
{
    "name": "NpmJS",
    "url": "https://registry.npmjs.org",
    "scopes": [
    "com.chartboost"
    ]
}
]

Using the public NuGet package

To add the Chartboost Mediation Unity SDK to your project using the NuGet package, you will first need to add the NugetForUnity package into your Unity Project.

This can be done by adding the following to your Unity Project's manifest.json

  "dependencies": {
    "com.github-glitchenzo.nugetforunity": "https://github.com/GlitchEnzo/NuGetForUnity.git?path=/src/NuGetForUnity",
    ...
  },

Once NugetForUnity is installed, search for Chartboost.CSharp.Mediation.Unity in the search bar of Nuget Explorer window(Nuget -> Manage Nuget Packages). You should be able to see the Chartboost.CSharp.Mediation.Unity package. Choose the appropriate version and install.

Setup

1. Ad Network Adapters
2. Android Manifest
3. Google External Dependency Manager (EDM)
4. Multidex

Integration

1. Initialization
2. Configure
3. Fullscreen Ad
4. Fullscreen Ad Queue
5. Banner Ad
6. Unity Banner Ad
7. Banner Visual Element
8. Error Codes
9. Unit Testing
10. FAQ

Migration Guides

1. Migration from v4 to v5
2. Migration from v3 to v4