Base Flow

For a detailed example of implementing a custom Adapter, refer to: Taku Demo

1. Class Descriptions for Implementing Each Ad Format

Developers need to inherit the class corresponding to the required ad format (see the table below) and override all abstract methods. In the corresponding methods, call the ad platform's API, callback the load result through the class member variable mLoadListener, and callback ad impression, click, close, and other event results through the class member variable mImpressionListener.

See how to create a Custom Adapter in the Taku dashboard

If you need to implement Bidding functionality using a custom Adapter, please check: Custom Advanced Configuration

2. Implementation of Common Abstract Methods and Ad Loading Event Callbacks

2.1 Implementation of Common Abstract Methods

2.2 Callbacks for Common Ad Loading Events

Use the member variable ATCustomLoadListener in the Adapter to implement callbacks for ad loading results.

Note: When using the member variable ATCustomLoadListener, null-check handling is required, because the Mediation SDK may internally reclaim this Listener object.

3. Usage and Notes for Custom Ad Platform Adapters

3.1 Usage Flow

• Developers only need to inherit the relevant classes and override the relevant methods. All methods in the custom Adapter do not need to be called by the developer. When the Ad Source for the custom ad platform is configured under the Ad Placement in the Taku dashboard, the SDK will internally call the relevant methods in the custom Adapter at the appropriate time.

• The developer calls the Taku SDK's load API to load an ad. The Taku SDK will create an instance of the custom Adapter class through reflection based on the class name configured in the dashboard, and call loadCustomNetworkAd() to request the ad. The loading result of the custom ad platform's ad needs to notify the Taku SDK by calling the methods of ATCustomLoadListener (onAdCacheLoaded, onAdLoadError). Eventually, the Taku SDK will notify the developer through the Taku callback methods.

• The parameters needed for loading ads on the custom ad platform (AppID, AppKey, PlacementID, etc.) should be configured in JSON string format in the Ad Source of that ad platform in the Taku dashboard. For example:

{
    "app_id":"2004533529842888",
    "unit_id":"VID_HD_16_9_15S_APP_INSTALL#2004533529842888_2110107055952201"
}

When the Taku SDK retrieves the backend strategy, it will convert this JSON string into a Map and pass it to loadCustomNetworkAd(Context context, Map).

• When the developer calls the Taku SDK's isAdReady API, it will call the custom Adapter's isAdReady() method.

• When the developer calls the Taku SDK's show API, it will call the custom Adapter's isAdReady() and show(Activity activity) methods.

3.2 Notes

• When adding a custom ad platform in the Taku dashboard, the Adapter class name must be configured with the full path class name (package name + class name), otherwise the Adapter class will not be created correctly when loading ads.

• Since the SDK internally creates the Adapter class through reflection, when building a release package, you must ensure that the Adapter class is not obfuscated. An example of the obfuscation rule is as follows:

# Replace  with the developer's own Adapter class name. 
-keep class  { *;} 
-keepclassmembers public class  { 
    public *; 
}

• For any issues encountered, refer to How to Test Ads for solutions.