Test Checklist

Please refer to the following test points during testing to ensure that the functionality and experience of each link meet expectations.

1. Initialize Taku SDK at App Launch

• Clearly identify which ad platforms are integrated (e.g., GDT, Baidu, etc.), and pay attention to whether each ad platform SDK is correctly integrated

---

2. Preload Ads After SDK Initialization Completes

• Stagger the execution of ad loading logic to avoid simultaneous high-concurrency ad load requests
• Reuse the same Ad instance object globally for Rewarded, Interstitial, Splash, and Native ad formats

---

3. Rewarded Video & Interstitial Ads

• After Taku SDK Initialization completes or upon entering the app home screen scenario, make the first load request in advance
• Before displaying an ad, call isReady to check if there is a displayable ad. If true, display it; if false, request to load an ad
• Rewarded Video rewards must be distributed in the onReward callback. Test whether rewards can be successfully distributed
• After the ad is closed, call load in the close callback for ad preloading
• Prevent multiple clicks: When displaying Rewarded or Interstitial ads, prevent multiple clicks to avoid displaying duplicate ads

---

4. Splash Ad

• If there is a custom timeout logic, pass the same timeout value to the Taku SDK
• On load timeout, navigate to the app home screen; if not timed out, display the ad in the onAdLoaded callback
• Preload for hot-start splash in onAdDismiss
• When the app switches to the background or pages switch, call isReady to check for available cache. If false, preload
• When clicking skip, check whether the onAdDismiss callback is normal and whether the external browser/app redirect is normal

---

5. Banner Ad

• ATBannerView can be added to the BannerViewContainer in advance and set to visible; it can also be loaded first and added to the BannerViewContainer and set to visible when needed for display
• Auto Refresh must be uniformly configured via Taku Dashboard > Select App > Edit Banner Mediation Unit > Advanced Settings. The auto refresh feature must be disabled in each ad platform's dashboard.
• After enabling the auto refresh feature in the Taku dashboard, check whether auto refresh is working properly

---

6. Native Ad

• If the NativeAd obtained in the onNativeAdLoaded callback is not null, save the reference for subsequent ad display
• Self-Rendering: All materials in SelfRenderView must be bound and rendered. Pay attention to whether onAdImpressed is triggered normally
• Resource Release: When using a NativeAd instance globally, release resources when the app exits. When bound to an Activity, call NativeAd.destroy() in onDestroy()
• Different platforms have different rendering requirements. Ensure that all ad platforms can normally fill, display, and trigger the onAdImpressed callback

---

7. Taku SDK Debug Log

Suggestion: For the waterfall configuration of each ad placement, make sure that each third-party ad platform's Ad Source is tested to fill and display normally before taking the app live.

• Log TAG filter: anythink
• Through log checks, confirm that each Ad Source configured on each Mediation platform can be filled, and that its load, fill, impression, and click callbacks can all be triggered normally

---