This guide shows you how to use the Google Mobile Ads SDK to load and display ads from Mintegral using mediation, covering both waterfall and bidding integrations. It covers how to add Mintegral to an ad unit's mediation configuration, and how to integrate the Mintegral SDK and adapter into a Flutter app.
Supported integrations and ad formats
The AdMob mediation adapter for Mintegral has the following capabilities:
Integration | |
---|---|
Bidding | |
Waterfall | |
Formats | |
App Open | 1 |
Banner | |
Interstitial | |
Rewarded | |
Rewarded Interstitial | |
Native | 2 |
1 Bidding and waterfall integrations for app open ad format are in closed beta.
2 Bidding and waterfall integrations for native ad format are in open beta.
Requirements
- Latest Google Mobile Ads SDK
- Flutter 3.7.0 or higher
- To deploy on Android
- Android API level 21 or higher
- To deploy on iOS
- iOS deployment target of 12.0 or higher
- A working Flutter project configured with the Google Mobile Ads SDK. See Get Started for details.
- Complete the mediation Get started guide
Step 1: Set up configurations in Mintegral UI
Sign up or Log in to your Mintegral account.
Locate the App Key
Navigate to the APP Setting tab and take note of the APP Key.
Add a new application
From the APP Setting tab, click the Add APP button.
Select the Platform and fill out the rest of the form. Then, click Save.
Android
iOS
Take note of your application's APP ID.
Android
iOS
Create an ad placement
Once your application has been created, navigate to the Placements & Units tab and click on the Add Placement button as shown below to create your ad placement.
Android
iOS
Enter a Placement Name and AD Format.
Bidding
Select Header Bidding as the Bidding Type. Fill out the rest of the form and click Save.
Waterfall
Select Traditional as the Bidding Type. Fill out the rest of the form and click Save.
Once your ad placement is created, take note of the Placement ID.
Android
iOS
Click the 1 AD Units drop down and take note of the AD Unit ID.
Android
iOS
Locate your Mintegral Reporting API Key
Bidding
This step isn't required for bidding integrations.
Waterfall
You will need your Mintegral Reporting API Key for setting up your AdMob ad unit ID. Navigate to Account > API Tools. Take note of your Skey and Secret.
Step 2: Set up Mintegral demand in AdMob UI
Definir as configurações de mediação para seu bloco de anúncios
Android
Para conferir instruções, consulte a etapa 2 no guia para Android.
iOS
Para instruções, consulte a etapa 2 no guia para iOS.
Add Mintegral to GDPR and US state regulations ad partners list
Siga as etapas em Configurações do GDPR e Configurações das regulamentações estaduais dos EUA para adicionar Mintegral à lista de parceiros de anúncios do GDPR e das regulamentações estaduais dos EUA na AdMob IU.
Step 3: Import the Mintegral SDK and adapter
通过 pub.dev 进行集成
将以下依赖项与最新版本的
Mintegral 软件包的
pubspec.yaml
文件:
dependencies:
gma_mediation_mintegral: ^1.0.0
手动集成
下载针对以下指标的最新版 Google 移动广告中介插件:
Mintegral、
将下载的文件解压缩,然后添加提取的插件文件夹
(及其内容)添加到您的 Flutter 项目中。然后,在
pubspec.yaml
文件,通过添加以下依赖项:
dependencies:
gma_mediation_mintegral:
path: path/to/local/package
Step 4: Add required code
Android
No additional code is required for Mintegral integration.
iOS
SKAdNetwork integration
Follow Mintegral's documentation
to add the SKAdNetwork identifiers to your project's Info.plist
file.
Step 5: Test your implementation
Ativar anúncios de teste
Registre seu dispositivo de teste em AdMob
Para fazer o teste da Mintegral com anúncios de banner, intersticiais, premiados e nativos, a Mintegral recomenda o uso das chaves de app, dos IDs do app, da posição e do bloco de anúncios fornecidos na Página de ID do teste da Mintegral.
Verificar anúncios de teste
Para verificar se você está recebendo anúncios de teste do Mintegral, ative os testes de uma única origem no Ad Inspector usando as Mintegral (Bidding) and Mintegral (Waterfall) origens de anúncios.
Error codes
If the adapter fails to receive an ad from Mintegral, publishers can check the
underlying error from the ad response using
ResponseInfo
under the following classes:
Android
com.mbridge.msdk
com.google.ads.mediation.mintegral.MintegralMediationAdapter
iOS
GADMediationAdapterMintegral
Here are the codes and accompanying messages thrown by the Mintegral adapter when an ad fails to load:
Android
Error code | Domain | Reason |
---|---|---|
101 | com.google.ads.mediation.mintegral | Invalid server parameters (e.g. Missing app ID or placement ID). |
102 | com.google.ads.mediation.mintegral | The requested ad size does not match a Mintegral supported banner size. |
103 | com.google.ads.mediation.mintegral | Missing or invalid bid response. |
104 | com.google.ads.mediation.mintegral | Mintegral SDK returned a no fill error. |
iOS
Error code | Domain | Reason |
---|---|---|
101 | com.google.mediation.mintegral | Invalid server parameters (e.g. Missing app ID or placement ID). |
102 | com.google.mediation.mintegral | Mintegral SDK returned a no fill error. |
103 | com.google.mediation.mintegral | Mintegral SDK failed to show an ad. |
104 | com.google.mediation.mintegral | The requested ad size does not match a Mintegral supported banner size. |
Mintegral Flutter Mediation Adapter Changelog
1.1.0
- Verified compatibility with Mintegral Android adapter version 16.8.31.0.
- Verified compatibility with Mintegral iOS adapter version 7.7.1.0.
- Built and tested with the Google Mobile Ads Flutter Plugin version 5.1.0.
1.0.0
- Initial release.
- Verified compatibility with Mintegral Android adapter version 16.7.21.0.
- Verified compatibility with Mintegral iOS adapter version 7.6.3.0.
- Built and tested with the Google Mobile Ads Flutter Plugin version 5.1.0.