SDK Access

SDK Version	Update time	Updates
v.1.0.1	2024.3.19	Fixed network request failure bug Optimized log
v1.0.2	2024.3.29	Added gateway request parameters Fixed log printing switch Updated TradPlus Adapter v1.0.1
v1.0.3	2024.4.8	Ad API completed Added Admob Adapter v1.0.1 Added Applovin Adapter v1.0.1 Added Topon Adapter v1.0.1 Updated TradPlus Adapter v1.0.2
v1.0.4	2024.4.10	Initialization API adds App Id parameter Banner Ad API adds size parameter
v1.0.5	2024.4.15	Fix gateway request issue
v1.0.6	2024.4.18	Fix bugs caused by confusion Update Admob Adapter v1.0.2 Update Applovin Adapter v1.0.2 Update Topon Adapter v1.0.2 Update TradPlus Adapter v1.0.3
v1.1.0	2024.5.8	Optimize ad bidding logic Native ad BeesNativeAdListener listener adds onAdLoaded(@NonNull BeesNativeAd nativeAd) callback Update Admob Adapter v1.0.3 Update Applovin Adapter v1.0.4 Update Topon Adapter v1.0.3 Added support for interstitial module v1.0.0 Added privacy compliance API
v1.1.1	2024.5.28	Fix privacy compliance issues Update Admob Adapter v1.0.4 Update Applovin Adapter v1.0.4 Update Topon Adapter v1.0.4 Update Interstitial Module v1.0.1
v1.1.2	2024.06.25	Optimize known issues Update Admob Adapter v1.0.5 Update Applovin Adapter v1.0.5 Update Topon Adapter v1.0.5 Update Insert Module v1.0.2
v1.1.3	2024.06.28	The interstitial function adds friendly control registration and removal APIs, BeesMediaVideo adds registerFriendlyObstruction and unregisterAllFriendlyObstructions methods The interstitial function adds AD label control APIs, BeesMediaVideo.Builder adds setShowAdLabelUI method Update interstitial module v1.0.2
v2.0.0	2024.11.18	Updated Ad API Fixed known bugs Updated interstitial module v1.1.0 Updated Admob Adapter v1.1.0 Updated Applovin Adapter v1.1.0 Updated Topon Adapter v1.1.0
v2.0.1	2024.11.22	Optimize ad requests Update Topon aggregation adapter v1.1.1
v2.0.2	2024.11.27	Optimize banner ad callback Update Topon aggregation adapter v1.1.2 Update Applovin aggregation adapter v1.1.1 Update Admob aggregation adapter v1.1.1
v2.0.3	2024.12.02	Optimize ad loading logic Fix known issues

Functional description

The Bees Ads SDK development kit (SDK for short) is mainly used to provide advertising bidding services to third-party applications. This article mainly describes how to integrate the SDK into the aggregation platform for partner developers to access and use.

Pre-access preparation

The pre-access preparation includes creating an application in the Bees backend and creating our media intermediary on the aggregation platform. Merchants who have completed this can skip this step. The parameters that need to be obtained include:

Parameter name	Parameter Description
app_id	Application id created by Bees backend
application_id	The app ID of Google Admob or Google Ad Manager backend

Please obtain these parameters through different platforms

1.app_id is obtained through BeesAds background

2.application_id is obtained through Google background, for details, please see: Document address

Basic environment

This tutorial is applicable to AndroidStudio development tools. If you do not have the above development tools, you can download them from the official website

SDK import

Important tips: Be sure to modify targetSdkVersion≥33; minSdkVersion≥21;

1. Configure the repository address item in the project-level build.gradle file

buildscript {
    repositories {
        google()
        mavenCentral()
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

1. In the application-level build.gradle file (usually app/build.gradle), complete the SDK integration

dependencies {
    // bees sdk
    implementation 'io.github.beesads:sdk:2.0.3'
    // google ads 
    implementation 'com.google.android.gms:play-services-ads:23.5.0'
}

1. Google Ads parameter configuration

<manifest>
  <application>
    <!-- Sample AdMob app ID: ca-app-pub-3940256099942544~3347511713 -->
    <meta-data
        android:name="com.google.android.gms.ads.APPLICATION_ID"
        android:value="ca-app-pub-xxxxxxxxxxxxxxxx~yyyyyyyyyy"/>
  </application>
</manifest>

Access process FAQ

If you encounter problems when using the SDK, you can refer to the following content to try to solve it.

1.How to apply for platform parameters such as app ID

Once the application is successfully created on our platform, it can be obtained

2.What should the targetSDKVersion be when packaging?

It is recommended to use 33 and above

3.How to deal with SDK obfuscation rules

We have handled SDK-related obfuscation, and there is no need to configure our SDK obfuscation rules in the project

4.How to initialize the SDK

You only need to complete the access to the aggregation platform SDK and configure our media intermediary. Bees SDK will complete the initialization process through the aggregation platform SDK

5.How to determine the initialization status of Bees SDK?

When using ad requests, view the initialization-related logs according to tag: bees-sdk

• When initialization is successful, the log shown in the figure below will appear:

• When initialization fails, the following log will appear:

Technical feedback

If this access document cannot solve your doubts, or if you have other technical questions, please send an email to: [e-mail]