Menu

Testing tools

Notes:

  • Supports developers in performing detection after integrating the TopOn SDK.
  • The test tool is only used for checking SDK integration and cannot replace the APP's own ad logic testing.
  • After testing is complete and before going live, developers should remove the relevant code that calls the test tool.
  • Version requirements: Android (v6.2.78 and above), iOS (v6.2.78 and above).

I. Product Introduction

Use the test tool to improve the efficiency of developer integration testing:

  • Basic Information: Detect information related to the app, device, and SDK.
  • TopOn SDK Settings: Check whether privacy settings and permissions have been successfully configured.
  • Integration Check: Check the integration status of third-party platform SDKs and adapters and test suggestions, as well as test ad loading for third-party ad platforms.

Version Description

II. Integration Process

Note: Before integrating the test tool, you need to first integrate the TopOn SDK. For the SDK integration method, refer to the Unity Plugin Usage Guide.

Android Integration Process

  1. Import the test tool's dependency library by performing the following two steps:
    Step 1: First, create a folder named Editor under the Unity project's /Assets/AnyThinkAds/Plugins/Android directory.
    Step 2: Create a Dependencies.xml file and add the following content to it, then place it in the Editor directory created in step one.

    Copy
    <dependencies>
        <androidpackages>
            <repositories>
                <repository>https://jfrog.anythinktech.com/artifactory/debugger</repository>
            </repositories>
            <androidpackage spec="com.anythink.sdk:debugger-ui:1.1.0"></androidpackage>
        </androidpackages>
    </dependencies>

    Note: The folder name in step 1 must be Editor, and the file name in step 2 must be Dependencies.xml.

  2. After completing the import of the test tool dependency library, you can directly call the C# API in the Unity layer. First, initialize the SDK, then call the following method to navigate to the test tool page:

    Copy
    // If you do not need to use online advertising ID testing, you can use ATSDKAPI.showDebuggerUI()
    // ATSDKAPI.showDebuggerUI();
    
    // Debug Key: used for online ID testing. You can get it from Backstage -> Account Management -> Key. 
    // Requirements: 1. SDK version 6.3.68 and above  2. Debugger UI tool version 1.0.8 and above
    ATSDKAPI.showDebuggerUI("Your Debug Key");

    Note: You must initialize the SDK before navigating to the test tool page.

iOS Integration Process

  1. Import the test tool's dependency library by performing the following two steps:
    Step 1: First, create a folder named Editor under the Unity project's /Assets/AnyThinkAds/Plugins/iOS directory.
    Step 2: Create a Dependencies.xml file and add the following content to it, then place it in the Editor directory created in step one.

    Copy
    <?xml version="1.0" encoding="utf-8"?>
    <dependencies>
        <iospods>
            <iospod name="TPNDebugUISDK" version="1.0.3"></iospod>
        </iospods>
    </dependencies>

    Note: The folder name in step 1 must be Editor, and the file name in step 2 must be Dependencies.xml.

  2. After completing the import of the test tool dependency library, you can directly call the C# API in the Unity layer. First, initialize the SDK, then call the following method to navigate to the test tool page:

    Copy
    ATSDKAPI.showDebuggerUI("Your Debug Key");

    Note:
    a. You must initialize the SDK before navigating to the test tool page.
    b. The features in the test tool require the media side to first obtain the IDFA before they can be used. Currently, SDK initialization does not obtain the IDFA.

Note: Before going live, you need to remove the relevant code that calls the test tool.

III. Test Tool Usage

  1. Basic Information

Function: Supports long-press to copy information and share current page data.

Android Basic Information

  • GAID is the Google Advertising ID. If GAID is displayed as empty, please check the following factors:

    1. Whether the phone has Google services.
    2. Whether the following method was called before entering this page to restrict GAID retrieval.
    Copy
    string[] deniedInfos = new string[] { "gaid" };
    ATSDKAPI.deniedUploadDeviceInfo(deniedInfos);
  • Android ID is a unique device identifier. If AndroidId is displayed as empty, please check whether the following method was called to restrict AndroidId retrieval:

    Copy
    string[] deniedInfos = new string[] { "android_id" };
    ATSDKAPI.deniedUploadDeviceInfo(deniedInfos);
  • Note: If the integrated SDK is an overseas SDK, enabling the debug mode below requires GAID not to be empty. If it is a domestic SDK, AndroidId must not be empty.

iOS Basic Information

  • IDFA is a unique device identifier. If IDFA is displayed as empty, please check whether the tracking permission has been granted.
  • Note: If IDFA is empty, ad debugging cannot be successfully enabled. Please grant the tracking permission in Settings.
    Article Image
  1. TopOn SDK Settings

TopOn SDK settings include two parts: Privacy Settings and Permission Settings.

  • GDPR Setup: 1. Supports setting directly in Unity, click to view; 2. Export Android and iOS native projects to set. For details, see Android GDPR Setup and iOS GDPR Setup.
  • Permission Settings: The list of permissions that the app has requested.
  • Android Page
    Article Image Article Image
  • iOS Page
    Article Image Article Image
  1. Integration Check

  1. Check the integration status in the ad platform list: Integration Abnormal, Integration Complete, Not Integrated.
    Article Image Article Image
  2. Toggle the switch to enable debug mode.
    Article Image
  3. Select an ad platform that has completed integration to enter debug mode.
  4. Select the ad format of the ad platform for testing.
    Article Image Article Image Article Image
  5. Click the share button in the top right corner to share the ad platform debugging information for the current page.
Previous
Testing Guide
Next
Revenue Tracking(v2.1.8 and above)
Last modified: 2026-07-03Powered by