Menu

Test Tool

Notes:

  • Support developers to detect and use after accessing TopOn SDK
  • Developers are testing After completion, the relevant code that calls the test tool will be deleted before going online
  • Version requirements: v6.2.70 and above

1. Product Introduction

Improve the efficiency of developer access testing by using testing tools:

  • Basic information: detect information about applications, devices, and sdk
  • TopOn SDK setting information: detect privacy settings , whether the permissions are successfully configured
  • Integration detection: detect the integration of the third-party platform SDK and adapter and test suggestions, and test the ad loading of the third-party advertising platform

Release Notes

TopOn SDK VersionTest Tool versionDescription
v6.2.70 and above(recommand)v1.1.11. Supports the latest version of the TaKu SDK
2. Fixed known issues
v6.2.70 and abovev1.0.81. Support Kwai platform debugging
2. Support sub-style debugging of native ads, banner ads, and interstitial ads on the Adx platform
v6.2.70-v6.3.68v1.0.5Support online advertising ID testing (for SDK 6.3.68 and above)
v6.2.70-v6.3.65v1.0.3Adapt to Vungle Version 7.0.0
v6.2.70-v6.3.65v1.0.1Compatible with org.jetbrains.kotlin:kotlin-stdlib:1.4.0 and Above version
v6.2.70-v6.3.65v1.0.0Adaptive aggregation version< li style="text-align: left;">The testing tool is only used to detect SDK integration and cannot replace the APP's own advertising logic testing

2. Access process

  • Refer to the TopOn SDK access document and integrate the SDK first.
  • Introduce testing tools and add references to Build.gradle:
repositories {
    maven {
        url "https://jfrog.anythinktech.com/artifactory/debugger"
    }
}
dependencies {
    // Debugger UI Tools
    implementation 'com.anythink.sdk:debugger-ui:1.1.1'
}
Copy
  • Calling up the test tool

Note: must be in After initializing the TopOn SDK, call the following method to call up the test tool.

ATDebuggerUITest.showDebuggerUI(context); 
//If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test 
//ATDebuggerUITest.showDebuggerUI(context, "Your Debug_Key");

3. Use of test tools

1. Basic information

Function: Support long press to copy information and Current page data sharing.

  • GAID is Google Advertising ID, if GAID shows empty, please check the following factors:
  1. Whether the phone has Google services.
  2. Before entering this page, whether to call The following method restrictionsGAID .
ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.GAID)
//If you need to use the online ID test function, call the following method. To obtain the Debug Key, refer to the following online ID test
//ATDebuggerUITest.showDebuggerUI(context, "Your Debug_Key"); 
  • Android ID is the unique identifier of the device. If AndroidId is displayed as empty , please check whether the following method is called to limit the acquisition of AndroidId:
ATSDK.deniedUploadDeviceInfo(DeviceDataInfo.ANDROID_ID)

2.TopOn SDK settings

TopOn SDK settings It includes two parts: privacy settings and permission settings.

  • Privacy settings

Limit reported data(Only for Domestic): There is a personalized recommendation advertising switch, Set the privacy information control switch. For details, please see Domestic privacy configuration.

GDPR(Only for Overseas): For details, please see Overseas Privacy Configuration.

  • Permission settings: List of permissions applied for by the application.

3. Integration detection

1. View the integration status of the advertising platform list: Integration exception, integration completed, Not integrated.

2. Check the switch to turn on debugging mode. If Gaid is empty, the debug mode function cannot be used.

3. Select the advertising platform to enter Debug Mode, and click on the upper right corner to share the advertising platform information of the current page.

4. Select the advertising style of the advertising platform for test operation.

4.Online ID Test

Online ID testing supports using online configured ad slots to test ads, and supports filtering ad sources under ad slots for testing.

Note: After running the online ID test, you need to restart the app to switch back to the developer app for testing to avoid caching problems caused by the in-app test ad slots and the test tool ad slots being consistent.

Prerequeisties

  • SDK version: v6.3.68 and above
  • Test tool version: v1.0.5 and above
  • Set SDK Debug Key: The steps to obtain it are Log in to background-> Account Manager -> Key
  • Debug mode is off

Start

  1. When initializing the SDK, pass in the application ID. When entering the online ID, the ad space configured in the application will be pulled.
  2. Enter the test tool by setting the Debug Key

The sample code is as follows:

//1. 初始化SDK
ATSDK.init(context, "Your App Id", "Your App Key");
//2.设置Debug Key进入测试工具
ATDebuggerUITest.showDebuggerUI(context, "Your Debug Key");

Online ID List

  • Support viewing application information: application name, App ID, application package name, SDK version
  • Support viewing the list of ad slots configured in the application
  • Support viewing ad slot information: name, ID
  • Supports clicking on an ad slot to jump to the ad slot test page for testing (video stream ads do not support testing for the time being)

Ad Placement Test

  • Support switching traffic groups
  • Supports bidding and waterfall advertising sources
  • Supports filtering advertising sources: unchecked advertising sources will be filtered when initiating lo



Last modified: 2025-07-31Powered by