{"data":{"id":"68490","string_id":"cWhOQw","status":"1","parent_id":"68373","slug":"3MffkL","order":"5","name":"Testing Networks","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"1707211467","add_time":"1707205728","update_time":"1767611145","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"parent_name":"SDK Integration Guides","parent_type":"1","parent_slug":"cUkkAX","child":[{"id":"68491","string_id":"zRbmbL","status":"1","parent_id":"68490","slug":"How-to-test-ads-pzHY","order":"6","name":"How to test ads","type":"2","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1707211467","add_time":"1707205728","update_time":"1753781475","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"68491","content":"## 1. SDK Integration Verification\n\n**Note: Custom ad platforms do not support integration verification functionality.**\n\n### 1.1 Use Logs + Integration Verification API to Verify All Ad Platform Integrations\n\nCall the following code to enable logging and integration detection:\n\n```objc\n#import \n\n- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {\n [ATAPI setLogEnabled:YES];\/\/Turn on debug logs\n [ATAPI integrationChecking];\n ....\n return YES;\n}\n```\n\nBased on the output logs, check whether the SDK integration of each ad platform is normal.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/eX0YMBvs\/6887586558645.png)\n\nThe following table explains the meaning of each field:\n\n| Field | Note |\n|-------|------|\n| Status | Status of integrated ad platform SDK |\n| Reason | Reason for integration issues |\n| Recommended Versions | Recommended third-party SDK versions to import |\n| Use Versions | Third-party SDK versions imported by users |\n\n### 1.2 Use DebugUI Debugging Tool to Verify Integration\n\nPlease go to the [DebugUI](\/cn\/docs\/ce-shi-gong-ju-Beta-DLyz) debugging tool section.\n\n## 2. Debug Ads\n\nTopOn dashboard ad placement configuration takes effect in about **5-15 minutes**. After you modify related ad placement settings (such as adding or modifying ad sources), you may need to wait before they take effect.\n\nTopOn SDK provides sandbox caching for dashboard configurations for **30 minutes**. After you modify configurations, you need to wait for the cache time to end before requesting the latest dashboard configuration (expired cache will still use old configuration for that request).\n\nYou can choose one of the following three processes for testing based on your current development stage.\n\n### 2.1 Use DebugUI Debugging Tool to Verify Your Online Ad Source Configuration (Suitable for verifying ad source configuration)\n\nAfter you complete configuration in TopOn dashboard and other ad platform dashboards, use the online ID testing function of DebugUI debugging tool to quickly verify whether these configurations are correct.\n\n### 2.2 Use Debug Mode for Limited Ad Process Testing\n\n- When debugging overseas ad platforms, you may need to use proxy networks. InMobi is recommended to proxy to Southeast Asia, with India being optimal. Pangle should proxy to non-US regions. Other overseas platforms can try proxying to the platform's country\/region to improve ad fill rates\n- Ad sources in debug mode are not 100% filled. For example, Meta ad platform requires Facebook app installed on test devices, using quality devices and proxy networks to get lower fill probability, because debug mode uses TopOn's pre-configured ad sources\n- Only one ad platform can be debugged at a time. Please note to **turn off this function** after testing\n- After obtaining IDFA authorization, call the following API to configure test device IDFA, target ad platform and ad type\n- Debug mode parameter list can be [found here](\/docs\/Debug-Mode-Parameter-List)\n\n**Note: Custom ad platforms are not supported.**\n\n```objc\n#import \n \/\/ Set test IDFA, such as Meta ad test devices\n [ATAPI setHeaderBiddingTestModeWithDeviceID:@\"you device idfa\"];\n \/\/ Note: Calling this code will use server-delivered ad configuration for ad requests. If testing is complete and you need to use your own ad configuration, remove this code.\n [ATAPI setDebuggerConfig:^(ATDebuggerConfig *debuggerConfig) {\n \/\/ Device idfa\n debuggerConfig.deviceIdfaStr = @\"you device idfa\";\n \/\/ Specify test ad platform, see header file for other platform types\n debuggerConfig.netWorkType = ATAdNetWorkCSJType;\n \/\/ Specify Pangle specific ad type\n debuggerConfig.csj_nativeAdType = ATCSJNativeAdFeedSelfRenderType;\n }];\n```\n\n### 2.3 Use Your Own Ad Placement and Ad Source Configuration for Testing (Suitable for production environment testing)\n\nRemove DebugUI SDK, turn off debug mode, and fully use your app's ad display logic and TopOn dashboard configuration for testing.\n\n#### 2.3.1 How to Test Ad Sources One by One (Custom Rules)\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wa7y4l\/article\/OKPtwxZA\/688892e1678e9.png)\n \nThis can be achieved by configuring traffic groups and adding custom rules. First, refer to creating traffic groups with custom key-value rules. Put the ad sources to be tested in each traffic group (for example, traffic group A only contains Kuaishou, traffic group B only contains Tencent, here we demonstrate simulating Baidu), then test through the following code. (After adding the code, wait a few minutes for the dashboard traffic group configuration to take effect, then delete and reinstall the app for verification). For example:\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wa7y4l\/article\/OKPtwxZA\/6888931b9837f.png)\n\n\n> \u26a0\ufe0fNote\n>- Remember to delete the test setCustomData code after debugging.\n>- The following code is only for custom rules or custom rules (new).\n>- You may need to add your test devices in each ad platform dashboard (if supported by the ad platform).\n\n**After dashboard modification, it takes about 5 minutes to take effect; local policy cache sandbox is 30 minutes. It is recommended to delete the app to clear sandbox cache after it takes effect, then request again.**\n\n```objc\n\/\/Set before calling various types of ad loading (load) APIs. Remember to delete the test setCustomData code after debugging\n[[ATSDKGlobalSetting sharedManager] setCustomData:@{@\"istest\":@\"yes\"} forPlacementID:xxxx];\n\n\/\/Note: xxx is the actual parameter in the code\n[[ATAdManager sharedManager] loadADWithPlacementID:xxx extra:xxx delegate:xxx];\n```\n\n#### 2.3.2 How to Test a Batch of Ad Sources (Device IDFA Rules)\n\nYou can create test traffic groups and add your test device's IDFA. Then copy or create one or several ad sources you want to debug, wait for configuration to take effect, clear local cache, allow SDK to get IDFA (you can see SDK printing IDFA in initialization logs for success), then initiate ad loading to attach device IDFA information for ad requests. If your ad loading request is made after getting IDFA, you need to adjust system time 30 minutes later, return to the app and request again, and repeat this operation once to update sandbox policy cache.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/eX0YMBvs\/688856fbcb260.png)\n\n### 2.4 Request Ads Using Your Own Configured Ad Sources\n\n**Test Ads**: Please go to ad platform dashboard to add test devices (if supported by ad platform).\n\n**Production Ads**: Cannot control fill rate, affected by multiple factors. Tips to increase production non-bidding ad fill rate: 1. Lower fixed price configuration; 2. Try more node devices for overseas ad platforms; For overseas projects, please check if app-ads.txt is correctly configured before testing production bidding ads (both TopOn and third-party platforms need to be checked. For third-party ad platforms, please refer to their documentation for app-ads.txt configuration tutorials).\n\n## 3. View Ad Loading Failure Reasons\n\n### 3.1 Add Printing for Ad Placement and Ad Source Delegates\n \n> Ad source delegate methods can output original information from third-party ad platform SDKs, which is very useful for troubleshooting ad loading failure reasons.\n\n- One ad placement can configure multiple ad sources. To receive loading events for a specific ad source, you need to use ad source level delegate callback methods. If all ad sources fail to request, or the ad placement overall request times out, use ad placement level failure callback to receive events.\n\n- After enabling SDK log switch, SDK will print ad source loading failure information by default. If you want to collect and print this information yourself, please implement these delegate methods.\n\n- If your ad sources include bidding ads, you need to implement the following BiddingADSource delegate methods to get ad source bidding related information.\n\n- Print the description field in error object to view detailed error information. You can go to [Error Code Description](\/docs\/Error-code) document to view error code meanings.\n\n```objc\n#pragma mark - Ad Source Level Callbacks\n- (void)didStartLoadingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--AD--Start--didStartLoadingADSourceWithPlacementID:%@---extra:%@\", placementID,extra);\n}\n\n- (void)didFinishLoadingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--AD--Finish--didFinishLoadingADSourceWithPlacementID:%@---extra:%@\", placementID,extra);\n}\n\n- (void)didFailToLoadADSourceWithPlacementID:(NSString*)placementID extra:(NSDictionary*)extra error:(NSError*)error {\n NSLog(@\"Ad Source--AD--Fail--didFailToLoadADSourceWithPlacementID:%@---error:%@\", placementID,error);\n}\n\n\/*\nIf your ad sources include bidding ads, you need to implement the following delegate methods to get ad source bidding process information. If bidding fails, you can provide related failure information and give us feedback, or directly check third-party platform error code descriptions.\n*\/\n#pragma mark - Ad Source Level Callbacks - Bidding\n- (void)didStartBiddingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--bid--Start--didStartBiddingADSourceWithPlacementID:%@---extra:%@\", placementID,extra);\n}\n\n- (void)didFinishBiddingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--bid--Finish--didFinishBiddingADSourceWithPlacementID:%@--extra:%@\", placementID,extra);\n}\n\n- (void)didFailBiddingADSourceWithPlacementID:(NSString*)placementID extra:(NSDictionary*)extra error:(NSError*)error {\n NSLog(@\"Ad Source--bid--Fail--didFailBiddingADSourceWithPlacementID:%@--extra:%@--error:%@\", placementID, extra, error);\n}\n\n#pragma mark - Ad Placement Level Callbacks - All Ad Sources Loading Complete\n\/\/Success - Some ad source loaded successfully\n- (void)didFinishLoadingADWithPlacementID:(NSString *)placementID {\n NSLog(@\"didFinishLoadingADWithPlacementID:%@\", placementID);\n}\n\n\/\/Failure - No ad source loaded successfully\n- (void)didFailToLoadADWithPlacementID:(NSString *)placementID error:(NSError *)error {\n NSLog(@\"didFailToLoadADWithPlacementID:%@ error:%@\", placementID, error);\n}\n```\n\nHere is an actual printing case. Usually you need to pay attention to the following points when troubleshooting:\n- **Error Domain=com.anythink.PubNativeSDK** : Describes which package the error comes from\n- **Code=1** : TopOn or third-party SDK error code\n- **NSLocalizedDescription=HyBid - No fill** : Specific meaning of the error, where No fill usually means no ads returned\n- **adsource_id = \"2560962\"** : TopOn ad source ID where the error occurred\n- **ATAdLogger(UA_6.4.87)** : SDK version\n```objc\nATAdLogger(UA_6.4.87) Message:didFailBiddingADSourceWithPlacementID:b5bacaccb61c29extra:{\n\tadunit_id = \"b5bacaccb61c29\";\n\tcurrency = \"USD\";\n\tadsource_price = 0;\n\treq_id = \"cee21cc4b7ae08706a1a3ef3fc9060ba\";\n\tabtest_id = 609;\n\ts_id = 100172;\n\tusd_to_rmb_rate = \"1\";\n\trmb_to_usd_rate = \"0.1393\";\n\tnetwork_firm_id = 58;\n\tadsource_id = \"2560962\";\n\tnetwork_placement_id = \"9\";\n\tadsource_bid_type = 2;\n}error:Error Domain=com.anythink.PubNativeSDK Code=1 \"AnythinkSDK has failed to load native ad.\" UserInfo={NSLocalizedDescription=AnythinkSDK has failed to load native ad., NSLocalizedFailureReason=Error Domain=net.pubnative.PubnativeLite Code=1 \"HyBid - No fill\" UserInfo={NSLocalizedDescription=HyBid - No fill}}\n```\n\n### 3.2 Console Log Analysis\n\nYou can quickly get the following debugging information through console printed log information.\n\n- From Xcode logs, you can see tracking of various ad actions.\n- Locate the ad placement to be verified based on placement_id.\n- The action field in logs is the action corresponding to the log after initiating ad loading, including lrequest (ad request), request_result (ad return result), impression (ad display), click (ad click), close (ad close).\n\n**Log Example:**\n\n```json\n{\n action = \"request_result\"; \/\/Action after initiating ad loading: request (ad request), request_result (ad return result), impression (ad display), click (ad click), close (ad close)\n \"ad_type\" = reward; \/\/Ad placement type for loading: Native\/inter\/RewardVideo\/Banner\/Splash\n \"adsource_id\" = 12300; \/\/Ad source id\n auto = NO; \/\/Whether it's automatic request\n \"daily_frequency\" = 0; \/\/Number of displays the day before\n \"hourly_frequency\" = 0; \/\/Number of displays in current hour\n defaultAdSourceType = 0; \/\/Whether it's fallback ad source\n isheaderbidding = 0; \/\/Whether it's bidding ad source\n msg = \"Error Domain=Wind Code=600008 \\\"\\U8bf7\\U6c42\\U8d85\\U65f6\\U3002\\\" UserInfo={NSLocalizedDescription=\\U8bf7\\U6c42\\U8d85\\U65f6\\U3002}\"; \/\/If loading fails, complete error information will be output here\n network = Sigmob; \/\/Represents third-party platform\n \"network_firm_id\" = 29; \/\/Represents third-party platform's network_firm_id\n \"network_list\" = (\n Sigmob\n );\/\/Current third-party ad request list id, separated by \",\"\n \"network_unit_info\" = {\n \"app_id\" = 19761;\n \"app_key\" = 7064a19c108082ef;\n \"placement_id\" = ea1f8f7b662;\n }; \/\/Corresponding third-party ad platform app and placement information\n \"placement_id\" = b5d771f5a3458f; \/\/Ad placement id that initiated loading\n position = 0; \/\/Current ad source sort position\n refresh = 0; \/\/Whether it's auto refresh\n \"request_network_num\" = 1; \/\/How many third-party ad platform loadings are initiated simultaneously\n result = fail; \/\/Result parameter: success, fail\n \"sdk_version\" = \"4.2.1\"; \/\/Third-party platform SDK version\n \"segment_id\" = 0; \/\/Traffic group id\n}\n```\n\n### 3.3 Log Analysis Examples\n\nTopOn ads are divided into waterfall ads and bidding ads. The loading process of these two types of ads is slightly different. Bidding ads will first get bidding tokens without initiating loading yet, while waterfall ads directly initiate ad requests to ad platforms.\n\n**Initiate Ad Source Ad Request**, search for \"AD Request offer with network info:\" in console, result as shown:\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/eX0YMBvs\/6887597e67513.png)\n\nAnnotations in the figure:\n\n\u2460 Ad source layer in ad placement initiates request\n\n\u2461 Which ad platform the ad source layer in ad placement is, locate which ad platform\n\n\u2462 Related information of ad source platform in ad placement, ad platform information configured in TopOn.\n\n**Ad Source Ad Request Success**, search for \"handler success Request offer with network info:\" in console, result as shown:\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/eX0YMBvs\/68875a46a66f3.png)\n\nAnnotations in the figure:\n\n\u2460 Ad source layer in ad placement request successful\n\n\u2461 Which ad platform the ad source layer in ad placement is\n\n\u2462 SDK version of ad source platform in ad placement, can know the imported third-party platform SDK version\n\n\u2463 Traffic group id for ad placement loading, can know which traffic group is loaded, 0 represents default group\n\n**Ad Source Ad Request Failure**, search for \"handler fail Request offer with network info:\" in console, result as shown:\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/eX0YMBvs\/68875c17e9699.png)\n\nAnnotations in the figure:\n\n\u2460 Ad source layer in ad placement request failed.\n\n\u2461 Ad source layer loading failure information in ad placement. Based on which platform's ad, use error information to check corresponding platform's error codes.\n\n\u2462 Which ad platform the ad source layer in ad placement is.\n\n### 3.4 Common Search Keywords\n\n- **Impression with ad info:** Ad display information. If display is abnormal, you can search this print to see which ad source's ad.\n- **Close with ad info:** Ad close information.\n- **ATADLogger(UA_6.4.87)** Parentheses indicate integrated TopOn SDK version, ATADLogger is SDK log keyword.","pure_content":"1. SDK Integration Verification\nNote: Custom ad platforms do not support integration verification functionality.\n1.1 Use Logs + Integration Verification API to Verify All Ad Platform Integrations\nCall the following code to enable logging and integration detection:\n#import \n\n- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {\n [ATAPI setLogEnabled:YES];\/\/Turn on debug logs\n [ATAPI integrationChecking];\n ....\n return YES;\n}\n\nBased on the output logs, check whether the SDK integration of each ad platform is normal.\n\nThe following table explains the meaning of each field:\n\n\n\n Field\n Note\n\n\n\n\n Status\n Status of integrated ad platform SDK\n\n\n Reason\n Reason for integration issues\n\n\n Recommended Versions\n Recommended third-party SDK versions to import\n\n\n Use Versions\n Third-party SDK versions imported by users\n\n\n\n1.2 Use DebugUI Debugging Tool to Verify Integration\nPlease go to the DebugUI debugging tool section.\n2. Debug Ads\nTopOn dashboard ad placement configuration takes effect in about 5-15 minutes. After you modify related ad placement settings (such as adding or modifying ad sources), you may need to wait before they take effect.\nTopOn SDK provides sandbox caching for dashboard configurations for 30 minutes. After you modify configurations, you need to wait for the cache time to end before requesting the latest dashboard configuration (expired cache will still use old configuration for that request).\nYou can choose one of the following three processes for testing based on your current development stage.\n2.1 Use DebugUI Debugging Tool to Verify Your Online Ad Source Configuration (Suitable for verifying ad source configuration)\nAfter you complete configuration in TopOn dashboard and other ad platform dashboards, use the online ID testing function of DebugUI debugging tool to quickly verify whether these configurations are correct.\n2.2 Use Debug Mode for Limited Ad Process Testing\n\nWhen debugging overseas ad platforms, you may need to use proxy networks. InMobi is recommended to proxy to Southeast Asia, with India being optimal. Pangle should proxy to non-US regions. Other overseas platforms can try proxying to the platform's country\/region to improve ad fill rates\nAd sources in debug mode are not 100% filled. For example, Meta ad platform requires Facebook app installed on test devices, using quality devices and proxy networks to get lower fill probability, because debug mode uses TopOn's pre-configured ad sources\nOnly one ad platform can be debugged at a time. Please note to turn off this function after testing\nAfter obtaining IDFA authorization, call the following API to configure test device IDFA, target ad platform and ad type\nDebug mode parameter list can be found here\n\n\nNote: Custom ad platforms are not supported.\n#import \n \/\/ Set test IDFA, such as Meta ad test devices\n [ATAPI setHeaderBiddingTestModeWithDeviceID:@\"you device idfa\"];\n \/\/ Note: Calling this code will use server-delivered ad configuration for ad requests. If testing is complete and you need to use your own ad configuration, remove this code.\n [ATAPI setDebuggerConfig:^(ATDebuggerConfig *debuggerConfig) {\n \/\/ Device idfa\n debuggerConfig.deviceIdfaStr = @\"you device idfa\";\n \/\/ Specify test ad platform, see header file for other platform types\n debuggerConfig.netWorkType = ATAdNetWorkCSJType;\n \/\/ Specify Pangle specific ad type\n debuggerConfig.csj_nativeAdType = ATCSJNativeAdFeedSelfRenderType;\n }];\n\n2.3 Use Your Own Ad Placement and Ad Source Configuration for Testing (Suitable for production environment testing)\nRemove DebugUI SDK, turn off debug mode, and fully use your app's ad display logic and TopOn dashboard configuration for testing.\n2.3.1 How to Test Ad Sources One by One (Custom Rules)\n\nThis can be achieved by configuring traffic groups and adding custom rules. First, refer to creating traffic groups with custom key-value rules. Put the ad sources to be tested in each traffic group (for example, traffic group A only contains Kuaishou, traffic group B only contains Tencent, here we demonstrate simulating Baidu), then test through the following code. (After adding the code, wait a few minutes for the dashboard traffic group configuration to take effect, then delete and reinstall the app for verification). For example:\n\n\n\u26a0\ufe0fNote\n\nRemember to delete the test setCustomData code after debugging.\nThe following code is only for custom rules or custom rules (new).\nYou may need to add your test devices in each ad platform dashboard (if supported by the ad platform).\n\n\nAfter dashboard modification, it takes about 5 minutes to take effect; local policy cache sandbox is 30 minutes. It is recommended to delete the app to clear sandbox cache after it takes effect, then request again.\n\/\/Set before calling various types of ad loading (load) APIs. Remember to delete the test setCustomData code after debugging\n[[ATSDKGlobalSetting sharedManager] setCustomData:@{@\"istest\":@\"yes\"} forPlacementID:xxxx];\n\n\/\/Note: xxx is the actual parameter in the code\n[[ATAdManager sharedManager] loadADWithPlacementID:xxx extra:xxx delegate:xxx];\n\n2.3.2 How to Test a Batch of Ad Sources (Device IDFA Rules)\nYou can create test traffic groups and add your test device's IDFA. Then copy or create one or several ad sources you want to debug, wait for configuration to take effect, clear local cache, allow SDK to get IDFA (you can see SDK printing IDFA in initialization logs for success), then initiate ad loading to attach device IDFA information for ad requests. If your ad loading request is made after getting IDFA, you need to adjust system time 30 minutes later, return to the app and request again, and repeat this operation once to update sandbox policy cache.\n\n2.4 Request Ads Using Your Own Configured Ad Sources\nTest Ads: Please go to ad platform dashboard to add test devices (if supported by ad platform).\nProduction Ads: Cannot control fill rate, affected by multiple factors. Tips to increase production non-bidding ad fill rate: 1. Lower fixed price configuration; 2. Try more node devices for overseas ad platforms; For overseas projects, please check if app-ads.txt is correctly configured before testing production bidding ads (both TopOn and third-party platforms need to be checked. For third-party ad platforms, please refer to their documentation for app-ads.txt configuration tutorials).\n3. View Ad Loading Failure Reasons\n3.1 Add Printing for Ad Placement and Ad Source Delegates\n\nAd source delegate methods can output original information from third-party ad platform SDKs, which is very useful for troubleshooting ad loading failure reasons.\n\n\n\nOne ad placement can configure multiple ad sources. To receive loading events for a specific ad source, you need to use ad source level delegate callback methods. If all ad sources fail to request, or the ad placement overall request times out, use ad placement level failure callback to receive events.\n\n\nAfter enabling SDK log switch, SDK will print ad source loading failure information by default. If you want to collect and print this information yourself, please implement these delegate methods.\n\n\nIf your ad sources include bidding ads, you need to implement the following BiddingADSource delegate methods to get ad source bidding related information.\n\n\nPrint the description field in error object to view detailed error information. You can go to Error Code Description document to view error code meanings.\n\n\n#pragma mark - Ad Source Level Callbacks\n- (void)didStartLoadingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--AD--Start--didStartLoadingADSourceWithPlacementID:%@---extra:%@\", placementID,extra);\n}\n\n- (void)didFinishLoadingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--AD--Finish--didFinishLoadingADSourceWithPlacementID:%@---extra:%@\", placementID,extra);\n}\n\n- (void)didFailToLoadADSourceWithPlacementID:(NSString*)placementID extra:(NSDictionary*)extra error:(NSError*)error {\n NSLog(@\"Ad Source--AD--Fail--didFailToLoadADSourceWithPlacementID:%@---error:%@\", placementID,error);\n}\n\n\/*\nIf your ad sources include bidding ads, you need to implement the following delegate methods to get ad source bidding process information. If bidding fails, you can provide related failure information and give us feedback, or directly check third-party platform error code descriptions.\n*\/\n#pragma mark - Ad Source Level Callbacks - Bidding\n- (void)didStartBiddingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--bid--Start--didStartBiddingADSourceWithPlacementID:%@---extra:%@\", placementID,extra);\n}\n\n- (void)didFinishBiddingADSourceWithPlacementID:(NSString *)placementID extra:(NSDictionary*)extra {\n NSLog(@\"Ad Source--bid--Finish--didFinishBiddingADSourceWithPlacementID:%@--extra:%@\", placementID,extra);\n}\n\n- (void)didFailBiddingADSourceWithPlacementID:(NSString*)placementID extra:(NSDictionary*)extra error:(NSError*)error {\n NSLog(@\"Ad Source--bid--Fail--didFailBiddingADSourceWithPlacementID:%@--extra:%@--error:%@\", placementID, extra, error);\n}\n\n#pragma mark - Ad Placement Level Callbacks - All Ad Sources Loading Complete\n\/\/Success - Some ad source loaded successfully\n- (void)didFinishLoadingADWithPlacementID:(NSString *)placementID {\n NSLog(@\"didFinishLoadingADWithPlacementID:%@\", placementID);\n}\n\n\/\/Failure - No ad source loaded successfully\n- (void)didFailToLoadADWithPlacementID:(NSString *)placementID error:(NSError *)error {\n NSLog(@\"didFailToLoadADWithPlacementID:%@ error:%@\", placementID, error);\n}\n\nHere is an actual printing case. Usually you need to pay attention to the following points when troubleshooting:\n\n\nError Domain=com.anythink.PubNativeSDK : Describes which package the error comes from\n\nCode=1 : TopOn or third-party SDK error code\n\nNSLocalizedDescription=HyBid - No fill : Specific meaning of the error, where No fill usually means no ads returned\n\nadsource_id = \"2560962\" : TopOn ad source ID where the error occurred\n\nATAdLogger(UA_6.4.87) : SDK version\n\nATAdLogger(UA_6.4.87) Message:didFailBiddingADSourceWithPlacementID:b5bacaccb61c29extra:{\n\tadunit_id = \"b5bacaccb61c29\";\n\tcurrency = \"USD\";\n\tadsource_price = 0;\n\treq_id = \"cee21cc4b7ae08706a1a3ef3fc9060ba\";\n\tabtest_id = 609;\n\ts_id = 100172;\n\tusd_to_rmb_rate = \"1\";\n\trmb_to_usd_rate = \"0.1393\";\n\tnetwork_firm_id = 58;\n\tadsource_id = \"2560962\";\n\tnetwork_placement_id = \"9\";\n\tadsource_bid_type = 2;\n}error:Error Domain=com.anythink.PubNativeSDK Code=1 \"AnythinkSDK has failed to load native ad.\" UserInfo={NSLocalizedDescription=AnythinkSDK has failed to load native ad., NSLocalizedFailureReason=Error Domain=net.pubnative.PubnativeLite Code=1 \"HyBid - No fill\" UserInfo={NSLocalizedDescription=HyBid - No fill}}\n\n3.2 Console Log Analysis\nYou can quickly get the following debugging information through console printed log information.\n\nFrom Xcode logs, you can see tracking of various ad actions.\nLocate the ad placement to be verified based on placement_id.\nThe action field in logs is the action corresponding to the log after initiating ad loading, including lrequest (ad request), request_result (ad return result), impression (ad display), click (ad click), close (ad close).\n\nLog Example:\n{\n action = \"request_result\"; \/\/Action after initiating ad loading: request (ad request), request_result (ad return result), impression (ad display), click (ad click), close (ad close)\n \"ad_type\" = reward; \/\/Ad placement type for loading: Native\/inter\/RewardVideo\/Banner\/Splash\n \"adsource_id\" = 12300; \/\/Ad source id\n auto = NO; \/\/Whether it's automatic request\n \"daily_frequency\" = 0; \/\/Number of displays the day before\n \"hourly_frequency\" = 0; \/\/Number of displays in current hour\n defaultAdSourceType = 0; \/\/Whether it's fallback ad source\n isheaderbidding = 0; \/\/Whether it's bidding ad source\n msg = \"Error Domain=Wind Code=600008 \\\"\\U8bf7\\U6c42\\U8d85\\U65f6\\U3002\\\" UserInfo={NSLocalizedDescription=\\U8bf7\\U6c42\\U8d85\\U65f6\\U3002}\"; \/\/If loading fails, complete error information will be output here\n network = Sigmob; \/\/Represents third-party platform\n \"network_firm_id\" = 29; \/\/Represents third-party platform's network_firm_id\n \"network_list\" = (\n Sigmob\n );\/\/Current third-party ad request list id, separated by \",\"\n \"network_unit_info\" = {\n \"app_id\" = 19761;\n \"app_key\" = 7064a19c108082ef;\n \"placement_id\" = ea1f8f7b662;\n }; \/\/Corresponding third-party ad platform app and placement information\n \"placement_id\" = b5d771f5a3458f; \/\/Ad placement id that initiated loading\n position = 0; \/\/Current ad source sort position\n refresh = 0; \/\/Whether it's auto refresh\n \"request_network_num\" = 1; \/\/How many third-party ad platform loadings are initiated simultaneously\n result = fail; \/\/Result parameter: success, fail\n \"sdk_version\" = \"4.2.1\"; \/\/Third-party platform SDK version\n \"segment_id\" = 0; \/\/Traffic group id\n}\n\n3.3 Log Analysis Examples\nTopOn ads are divided into waterfall ads and bidding ads. The loading process of these two types of ads is slightly different. Bidding ads will first get bidding tokens without initiating loading yet, while waterfall ads directly initiate ad requests to ad platforms.\nInitiate Ad Source Ad Request, search for \"AD Request offer with network info:\" in console, result as shown:\n\nAnnotations in the figure:\n\u2460 Ad source layer in ad placement initiates request\n\u2461 Which ad platform the ad source layer in ad placement is, locate which ad platform\n\u2462 Related information of ad source platform in ad placement, ad platform information configured in TopOn.\nAd Source Ad Request Success, search for \"handler success Request offer with network info:\" in console, result as shown:\n\nAnnotations in the figure:\n\u2460 Ad source layer in ad placement request successful\n\u2461 Which ad platform the ad source layer in ad placement is\n\u2462 SDK version of ad source platform in ad placement, can know the imported third-party platform SDK version\n\u2463 Traffic group id for ad placement loading, can know which traffic group is loaded, 0 represents default group\nAd Source Ad Request Failure, search for \"handler fail Request offer with network info:\" in console, result as shown:\n\nAnnotations in the figure:\n\u2460 Ad source layer in ad placement request failed.\n\u2461 Ad source layer loading failure information in ad placement. Based on which platform's ad, use error information to check corresponding platform's error codes.\n\u2462 Which ad platform the ad source layer in ad placement is.\n3.4 Common Search Keywords\n\n\nImpression with ad info: Ad display information. If display is abnormal, you can search this print to see which ad source's ad.\n\nClose with ad info: Ad close information.\n\nATADLogger(UA_6.4.87) Parentheses indicate integrated TopOn SDK version, ATADLogger is SDK log keyword.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1707205731","update_time":"1753781475"},"pure_content":"1. SDK Integration Verification\nNote: Custom ad platforms do not support integration verification functionality.\n1.1 Use Logs + Integration Verification API to Verify All Ad Platform Integrations\nCall"},{"id":"68493","string_id":"849dP1","status":"1","parent_id":"68490","slug":"Testing-tools-Beta","order":"5","name":"DebugUI Debug Tool","type":"2","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1707211468","add_time":"1707205733","update_time":"1768463194","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"68493","content":"> You can use DebugUI to verify the integration of TopOn iOS SDK and test various ad platform functions in your project, but DebugUI cannot test your App's own ad logic.\n>\n> **Note: Custom ad platforms** only support online ad placement testing functionality, other features are not supported.\n\n# Debug UI Version\n\n| SDK version| DebugUI version |\n| - | - |\n| v6.4.93\u3001v6.5.34 | 1.0.6 |\n| >=v6.5.40 | 1.0.7 |\n\n## 1. Prerequisites\n\n- TopOn iOS SDK has been imported and successfully activated in your project\n- Cocoapods is installed\n\n## 2. Import TopOn iOS DebugUI\n\nPlease add different information to your podfile based on the integrated TopOn iOS SDK version:\n\n```ruby\npod 'TPNDebugUISDK','x.x.x'\n```\n\nAfter adding, please execute `pod install --repo-update`\n\n## 3. Enable TopOn iOS DebugUI in Your Project\n\n### 3.1 Get Debug Key from TopOn Dashboard\n\nThe steps to get it are: `Login to TopOn Dashboard` -> `Account Management` -> `Key` -> `SDK Debug Key`\n\n### 3.2 Get IDFA\n\nPlease select \"Allow\" for the IDFA popup. DebugUI needs to obtain IDFA information through code to work properly. If you're not sure how to get IDFA, please [refer here](\/docs\/integrated#4._Request_app_tracking_permission_from_users_to_obtain_IDFA).\n\n#### 3.2.1 How to Verify SDK Can Successfully Get IDFA\n\nEnable SDK log switch, search for IDFA in logs. After SDK initialization, if ATAdLog prints out IDFA, it's considered successful.\n\n![IDFA Verification](https:\/\/resource-wangsu.helplook.net\/docker_production\/7u2g9n\/article\/eX0YMBvs\/688856fbcb260.png)\n\n### 3.3 Display DebugUI\n\n> Before calling the DebugUI display API, you need to ensure:\n>\n> - iOS SDK has been successfully [initialized](\/docs\/integrated#7._Initialize_SDK)\n> - Will not trigger ad loading logic\n> - ATAdLog has printed out IDFA\n> - Turn off [debug mode](\/docs\/How-to-test-ads-pzHY#2.2%20Use%20Debug%20Mode%20for%20Limited%20Ad%20Process%20Testing)\n\n> Before your App goes live, please **delete** DebugUI related code.\n\nIn your **AppDelegate** or **main view controller**, fill in the DebugKey and use the following API to display DebugUI:\n\n```objc\n\/\/Import header file\n#import \n\n \/\/Call, note that push method requires a navigation controller, controller object parameter should not inherit and override some methods, if parameters are correct and IDFA is normally obtained by SDK but still not displayed, you can use GCD to delay 2 seconds to call the following API\n [[ATDebuggerAPI sharedInstance] showDebuggerInViewController:self showType:ATShowDebugUIPush debugkey:@\"Your Debug Key\"];\n\nor\n\n \/\/Example of displaying with 2-second delay\n dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(2 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{\n [[ATDebuggerAPI sharedInstance] showDebuggerInViewController:self showType:ATShowDebugUIPush debugkey:@\"Your Debug Key\"];\n });\n```\n\n## 4. DebugUI Feature Introduction\n\n> DebugUI supports long press to copy information and share current page data.\n\n### 4.1 View Basic Information\n\n![Basic Information](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58ba5df83e.png)\n\n### 4.2 View TopOn SDK Settings\n\n![SDK Settings1](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58c4b0f767.png)![SDK Settings2](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58c5c3c5af.png)\n\n\n### 4.3 Integration Detection\n\n![Integration Detection 1](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58c93d2e14.png) ![Integration Detection 2](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58c824c34e.png)\n\n### 4.4 Debug Mode Testing\n\n> - **When debugging overseas ad platforms, you may need to use proxy networks. For InMobi, it's recommended to proxy to Southeast Asia, with India being optimal. For Pangle, proxy to non-US regions. For other overseas platforms, you can try proxying to the platform's country\/region to improve ad fill rates.**\n> - **Ad sources in debug mode are not 100% filled. For example, Meta ad platform requires Facebook app to be installed on the test device, and requires quality devices and proxy networks to achieve lower fill probability.**\n> - **Debug mode works by using TopOn's pre-configured ad sources, which are not 100% guaranteed to fill ads successfully.**\n\n\u2460 You can check the switch on the following page to enable debug mode.\n\n![Debug Mode Switch](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58ccd2ebb5.png)\n\n\u2461 Select a completed integrated ad platform to enter **debug mode**.\n\n![Select Ad Platform](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58ccd2ebb5.png)\n\n\u2462 Select ad platform's ad format for testing operations\n\n![Ad Format Testing 1](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58d2b9838c.png) ![Ad Format Testing 2](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58d44250a0.png) ![Ad Format Testing 3](https:\/\/resource-wangsu.helplook.net\/docker_production\/h6wabu\/article\/DyeBOA\/67b58f7087c99.png)\n\n### 4.5 Online ID Testing\n\n> Online ID testing feature is only available in iOS DebugUI version 1.0.3 and above.\n\n#### 4.5.1 Display App Information and Ad Placement Configuration\n\n![App Information and Ad Placement Configuration](https:\/\/resource-wangsu.helplook.net\/docker_production\/wa7y4l\/article\/849dP1\/68889860bf427.png)\n\n#### 4.5.2 Online Ad Placement Testing\n\n\u2460 Click on an ad placement to enter the ad placement testing page\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wa7y4l\/article\/849dP1\/68889860bf427.png)\n\n\n\u2461 Perform online ad placement testing\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wa7y4l\/article\/849dP1\/6888984e188e1.png)","pure_content":"You can use DebugUI to verify the integration of TopOn iOS SDK and test various ad platform functions in your project, but DebugUI cannot test your App's own ad logic.\nNote: Custom ad platforms only support online ad placement testing functionality, other features are not supported.\n\nDebug UI Version\n\n\n\n SDK version\n DebugUI version\n\n\n\n\n v6.4.93\u3001v6.5.34\n 1.0.6\n\n\n >=v6.5.40\n 1.0.7\n\n\n\n1. Prerequisites\n\nTopOn iOS SDK has been imported and successfully activated in your project\nCocoapods is installed\n\n2. Import TopOn iOS DebugUI\nPlease add different information to your podfile based on the integrated TopOn iOS SDK version:\npod 'TPNDebugUISDK','x.x.x'\n\nAfter adding, please execute pod install --repo-update\n3. Enable TopOn iOS DebugUI in Your Project\n3.1 Get Debug Key from TopOn Dashboard\nThe steps to get it are: Login to TopOn Dashboard -> Account Management -> Key -> SDK Debug Key\n3.2 Get IDFA\nPlease select \"Allow\" for the IDFA popup. DebugUI needs to obtain IDFA information through code to work properly. If you're not sure how to get IDFA, please refer here.\n3.2.1 How to Verify SDK Can Successfully Get IDFA\nEnable SDK log switch, search for IDFA in logs. After SDK initialization, if ATAdLog prints out IDFA, it's considered successful.\n\n3.3 Display DebugUI\n\nBefore calling the DebugUI display API, you need to ensure:\n\niOS SDK has been successfully initialized\n\nWill not trigger ad loading logic\nATAdLog has printed out IDFA\nTurn off debug mode\n\n\n\n\nBefore your App goes live, please delete DebugUI related code.\n\nIn your AppDelegate or main view controller, fill in the DebugKey and use the following API to display DebugUI:\n\/\/Import header file\n#import \n\n \/\/Call, note that push method requires a navigation controller, controller object parameter should not inherit and override some methods, if parameters are correct and IDFA is normally obtained by SDK but still not displayed, you can use GCD to delay 2 seconds to call the following API\n [[ATDebuggerAPI sharedInstance] showDebuggerInViewController:self showType:ATShowDebugUIPush debugkey:@\"Your Debug Key\"];\n\nor\n\n \/\/Example of displaying with 2-second delay\n dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(2 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{\n [[ATDebuggerAPI sharedInstance] showDebuggerInViewController:self showType:ATShowDebugUIPush debugkey:@\"Your Debug Key\"];\n });\n\n4. DebugUI Feature Introduction\n\nDebugUI supports long press to copy information and share current page data.\n\n4.1 View Basic Information\n\n4.2 View TopOn SDK Settings\n\n4.3 Integration Detection\n \n4.4 Debug Mode Testing\n\n\n\nWhen debugging overseas ad platforms, you may need to use proxy networks. For InMobi, it's recommended to proxy to Southeast Asia, with India being optimal. For Pangle, proxy to non-US regions. For other overseas platforms, you can try proxying to the platform's country\/region to improve ad fill rates.\n\n\nAd sources in debug mode are not 100% filled. For example, Meta ad platform requires Facebook app to be installed on the test device, and requires quality devices and proxy networks to achieve lower fill probability.\n\n\nDebug mode works by using TopOn's pre-configured ad sources, which are not 100% guaranteed to fill ads successfully.\n\n\n\n\u2460 You can check the switch on the following page to enable debug mode.\n\n\u2461 Select a completed integrated ad platform to enter debug mode.\n\n\u2462 Select ad platform's ad format for testing operations\n \n4.5 Online ID Testing\n\nOnline ID testing feature is only available in iOS DebugUI version 1.0.3 and above.\n\n4.5.1 Display App Information and Ad Placement Configuration\n\n4.5.2 Online Ad Placement Testing\n\u2460 Click on an ad placement to enter the ad placement testing page\n\n\u2461 Perform online ad placement testing","is_draft":"0","editor_type":"2","file_path":"","add_time":"1707205737","update_time":"1768463194"},"pure_content":"You can use DebugUI to verify the integration of TopOn iOS SDK and test various ad platform functions in your project, but DebugUI cannot test your App's own ad logic.\nNote: Custom ad platforms only"},{"id":"68471","string_id":"DC5lgQ","status":"1","parent_id":"68490","slug":"Error-code","order":"2","name":"Error code","type":"2","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1707211461","add_time":"1707205693","update_time":"1753783165","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"68471","content":"

1. TopOn error code information description<\/h2>
The following is a summary of the error code:<\/p>
Error code<\/th> Note<\/th><\/tr>
2001<\/td> (GDPR is not set) GDPR consent not set
Suggestion:<\/strong>
Due to the data protection area (EU, etc.), please set the data before initialization To collect opinions, please refer to GDPR<\/a> document<\/td><\/tr>
1001<\/td> (Invalid strategy) Placement strategy invalid
Suggestion:<\/strong>
Check TopOn Do the appid, appkey and placement id passed in during initialization match?<\/td><\/tr>
1003<\/td> Ad loading fails, there will be two situations:
Suggestion:<\/strong>
1. Waterfall ad configuration - details Please check the background log analysis. If it is in the development stage, please check log output<\/a>
2. error msg contains Bid request have failed <\/strong>\u2014\u2014The bidding failed. For details, please implement the bidding agent to view didFailBiddingADSourceWithPlacementID<\/strong><\/td><\/tr>
1005<\/td> (No ad display) No ad found when trying to show ad
Suggestion:
Before calling the display ad, please first determine whether the ad slot has been prepared. You can check the judgment API of the corresponding ad type to judge<\/strong><\/td><\/tr>
1006<\/td> (show too frequently) Ad show too frequent
Suggestion: <\/strong>
Please try to display again later. You can set a display interval of a little time to avoid this problem. You can also use the aggregation management in the TopOn background to set the display interval. <\/td><\/tr>
1007<\/td> (display within hours Maximum number of impressions) Ad show too many time within the same hour
Suggestion:<\/strong>
In the case of testing, you can increase the number of impressions per hour. If it has been published, the code is considered normal. Case. <\/td><\/tr>
1008<\/td> (Show more than the maximum number of impressions in a day) Ad show too many time within the same day
Suggestion:<\/strong>
In the case of testing, you can increase the number of impressions per hour, if you have If released, this code is considered normal. <\/td><\/tr>
1009<\/td> (The corresponding Adapter is not imported) The adapter not found
Suggestion:<\/strong>
Please integrate the adapter of the corresponding advertising platform according to the information printed in the log<\/td><\/tr>
10010<\/td> (Ad loading timeout) Ad loading timeout
Suggestion:<\/strong>
Please change the network of the test device and try loading ads again<\/td><\/tr>
1013<\/td> (The SDK of the third-party platform is not imported or the wrong version is imported. Please correspond to AnythinkiOS and sub-package versions) Third party SDK not imported or wrong version's being used
Suggestion:<\/strong>
Please refer to our background download interface to select the corresponding adapter version for integration<\/td><\/tr>
1014<\/td> (Invalid App ID, App Key Or Placement ID) Invalid parameters encountered (App ID, App Key or Placement ID being nil)
Suggestion:<\/strong>
Please check whether the above information is correct and accurately fill in the initialization and ad loading<\/td><\/tr>
1015<\/td> (Ad delivery not turned on for the placement) Ad delivery not turned on for the placement
Suggestion:<\/strong>
Please open the corresponding advertising slot in the TopOn backend management system<\/td><\/tr>
1017<\/td> (advertising position strategy The placement strategy does not contain any ad sources, please check the mediation configuration in TopOn.
Suggestion:<\/strong>
Please add the media to be loaded in the corresponding ad slot Ad source, create an ad in the background of the advertising platform, and fill in the ad id into the ad slot<\/td><\/tr>
1018 <\/td> (Ad sources have been filtered)Ad sources are filtered, no ad source is currently available
Suggestion: <\/strong>
The advertising source has been filtered. It may be filled in the filtering API during initialization. Check whether it is filled in<\/td><\/tr>
1019<\/td> (The placementID load too frequently within the specified times period after the previous load failure
Suggestion:<\/strong>
Please wait at least 10s after the previous request failed before making a new request<\/td><\/tr>
1020<\/td> (During the specified time period, ads The placement load too many times within the specified time period
Suggestion:<\/strong>
Please adjust the number of times the ad slot is loaded to avoid excessive loading within a period of time <\/td><\/tr>
1029<\/td> (Debug mode, the placement strategy does not contain any ad sources, please check the debugger configuration) The placement strategy does not contain any ad sources, please check the debugger configuration in [ATAPI setDebuggerConfig]
Suggestion: <\/strong>
You can check whether the incoming ifa is the idfa of the device, and secondly check whether the debugging mode platform used is wrong. If there is no problem above, you can give us feedback and we will investigate. <\/td><\/tr>
1030<\/td> (Ad source is filtered and not filled) Ad source not filled, cause by customize fillter.
Suggestion:<\/strong>
The ad source ad is set to be filtered by the custom filter configuration, resulting in no padding being loaded. You can check the settings of the initialized custom filter<\/td><\/tr><\/tbody><\/table>
2. Network platform error code<\/h2>
Third-party advertising platform error codes&FAQ (frequently asked questions)<\/h2>
Meta(Facebook)<\/h3>
Common mistakes<\/th> Solution<\/th><\/tr>
1001 - No Fill<\/td> No padding. The most common reasons are that the user is not logged into the Facebook app when testing your mobile app, or the user is not logged into the Facebook mobile website when testing your mobile website<\/td><\/tr>
1000 - Network Error<\/td> Network problem, check whether to circumvent the firewall<\/td><\/tr><\/tbody><\/table>
For more Facebook error messages, please see: Facebook error codes<\/a><\/p>
Admob<\/h3>
Common errors<\/th> Solutions<\/th><\/tr>
0<\/td> 1. Use TopOn background advertising space and use Debug mode<\/strong> for testing 2. Check whether the wall is bypassed<\/td><\/tr>
1<\/td> Invalid ad request; check ad source Parameter configuration<\/td><\/tr>
2<\/td> The ad request failed due to network connectivity. Check whether to circumvent the wall<\/td><\/tr>
3<\/td> The ad request was successful, but no ads were returned due to lack of inventory. Use TopOn background advertising slots and use Debug mode<\/strong> for testing<\/td><\/tr><\/tbody><\/table>
For more Admob error messages, please see: Admob error code<\/a><\/p>
CSJ(TT)<\/h3>
Common Errors<\/th> Solutions<\/th><\/tr>
40029<\/td> Check the rendering type of the Pangolin code bit. The configuration of the TopOn background pangolin advertising source needs to be consistent with the Pangolin background The configuration remains consistent<\/td><\/tr>
40025<\/td> Go to the pangolin backend to download the SDK and replace the pangolin SDK provided by TopOn<\/td><\/tr>
40019 - The media configuration adtype is inconsistent with the request<\/td> TopOn background pangolin advertising source configuration problem<\/td><\/tr>
40018 - The media package name is inconsistent with the entry<\/td> The package name configured in the code<\/strong> is inconsistent with the Pangolin backend<\/td><\/tr>
40016 - The corresponding relationship between slot_id and app_id is illegal<\/td> TopOn background pangolin advertising source configuration Problem<\/td><\/tr>
40006 - The advertising slot ID is illegal<\/td> TopOn background pangolin advertising source configuration problem<\/td><\/tr>
102 - not matched Main template: The main template is not downloaded locally. It is normal to occasionally request ads for the first time<\/td> You can try to request ads a few more times<\/td><\/tr>
103 - Subtemplate not matched: Occasionally, in the early stage of access, the template is not matched. It will not appear after the SDK downloads the template successfully. <\/td> You can request a few more ads to try<\/td><\/tr>
107 - Template rendering times out without callback. Possible reasons are 1. Network reasons or 2. Hardware reasons. Therefore, the rendering fails. You can change the mobile phone or test the network environment. <\/td> You can request a few more ads to try<\/td><\/tr><\/tbody><\/table>
For more pangolin error information, please see: (login required) TT(CSJ) error code<\/a><\/p>
Pangle<\/h3>
For Pangle error information, please check: Pangle error code<\/a><\/p>
Mintegral <\/h3>
Error code<\/th> msg<\/th> Description<\/th> Solution<\/th><\/tr>
-1<\/td> EXCEPTION_RETURN_EMPTY<\/td> No ad filling, which may cause Reasons: 1. The advertisements you obtain during the test period are all official advertisements of Mintegral, so they will be affected by the intelligent optimization of the algorithm. If a large number of advertisements are loaded and displayed for a period of time, there may be no advertisements filled after a period of time. <\/td> Domestic version: 1. Make sure Mintegral background-application settings is turned on Whether to accept apk advertising<\/strong> Overseas version: 1. Check whether to bypass the wall or VPN to the United States Above If there is still a problem after checking, use TopOn background advertising slot and use Debug mode<\/strong> to test<\/td><\/tr>
-1201<\/td> EXCEPTION_UNIT_NOT_FOUND<\/td> The unitID does not exist\/entered incorrectly<\/td> TopOn background Mintegral advertising source configuration problem<\/td><\/tr>
-1203<\/td> EXCEPTION_UNIT_NOT_FOUND_IN_APP<\/td> The appID and unitID do not match<\/td> TopOn background Mintegral advertising source configuration problem<\/td><\/tr>
-1205<\/td> EXCEPTION_UNIT_ADTYPE_ERROR<\/td> Incoming The unitID advertising type does not match<\/td> TopOn background Mintegral advertising source configuration problem<\/td><\/tr><\/tbody><\/table>
For more Sigmob error information, please see: Mintegral error code<\/p>
Tencent(GDT)<\/h3>
Error code<\/th> Description<\/th><\/tr>
4013<\/td> The system does not support it. Native video template ads only support iOS 9 and above systems<\/td><\/tr>
4020<\/td> window is empty, you need to add the window attribute in AppDelegate<\/td><\/tr>
5006<\/td> Illegal package name verification The package name configured in the codeis inconsistent with the backend of Guangdiantong<\/td><\/tr>
6000<\/td> Unknown error, contact Tencent Advertising Business colleagues for assistance in troubleshooting. <\/td><\/tr><\/tbody><\/table>
For more Tencent advertising error information, please see: Tencent Ad error code<\/a><\/p>
AppLovin<\/h3>
Common mistakes<\/th> Solution<\/th><\/tr>
204<\/td> No padding, you can open the test mode through the Applovin background for testing<\/td><\/tr><\/tbody><\/table>
For more AppLovin error information, please see: AppLovin error codes<\/a><\/p>
Vungle<\/h3>
Common mistakes<\/th> Solution<\/th><\/tr>
Cannot get ads<\/td> Enable test mode through Vungle background for testing<\/td><\/tr>
After preloading Vungle's rewarded videos and interstitial ads successfully, one of the Vungle ads was played, and the isAdReady() of the other ad returned false<\/td> Vungle's rewarded videos and interstitial ads share the same advertising source resources<\/td><\/tr><\/tbody><\/table>
For more Vungle error messages, please see: Vungle error code<\/a><\/p>
Kuaishou<\/h3>
Common mistakes<\/th> Solutions<\/th><\/tr>
40003 - Advertising data is empty<\/td> If necessary, please contact us Kuaishou related personnel<\/td><\/tr>
310002 - appId is invalid<\/td> TopOn background Kuaishou advertising source configuration problem<\/td><\/tr>
310004 - packageName and registration Inconsistent packageName<\/td> Package configured in code Name<\/strong>Inconsistency with Kuaishou backend<\/td><\/tr>
330002 - posId is invalid<\/td> TopOn background Kuaishou advertising source configuration problem<\/td><\/tr>
330004 - posId is inconsistent with the registered appId information<\/td> TopOn background Kuaishou advertising source configuration issue<\/td><\/tr><\/tbody><\/table>
For more Kuaishou error messages, please check: (requires login to download) Kuaishou error code<\/a><\/p>
Sigmob<\/h3>
Common mistakes<\/th> Solutions<\/th><\/tr>
200000 - no ad filling<\/td> Add test device through Sigmob backend for testing<\/td><\/tr>
500420 - The requested app has turned off advertising services<\/td> Add test device for testing through Sigmob background<\/td><\/tr>
500473 - Requested app Does not exist<\/td> TopOn background Sigmob advertising source configuration problem<\/td><\/tr>
500701 - app has not opened any advertising channels<\/td> Check Sigmob background application status<\/td><\/tr><\/tbody><\/table>
For more Sigmob error information, please see: Sigmob error code<\/a><\/p>
Baidu<\/h3>
More Baidu Please check the error message: (Requires login to download) Baidu error code<\/a><\/p>
Bigo_Ads<\/h3>
For more Bigo_Ads error information, please see: Bigo_Ads error code<\/a><\/p>
UnityAds<\/h3>
For more UnityAds error messages, please see: UnityAds error code<\/a><\/p>
Chartboost<\/h3>
More Chartboost errors For information, please see: Chartboost error codes<\/a><\/p>
Ironsource<\/h3>
More For more Ironsource error messages, please see: Ironsource error codes <\/a><\/p>
Oneway<\/h3>
For more Oneway error messages, please see: Oneway error code<\/a><\/p>
StartApp<\/h3>
More For StartApp error messages please view: StartApp error code<\/a><\/p>
Ogury <\/h3>
For more Ogury error messages, please see: Ogury error codes<\/a><\/p>
Klevin<\/h3>
For more You Keying error messages, please see: Klevin error code<\/a><\/p>","pure_content":"1. TopOn error code information descriptionThe following is a summary of the error code: Error code Note 2001 (GDPR is not set) GDPR consent not setSuggestion:Due to the data protection area (EU, etc.), please set the data before initialization To collect opinions, please refer to GDPR document 1001 (Invalid strategy) Placement strategy invalidSuggestion: Check TopOn Do the appid, appkey and placement id passed in during initialization match? 1003 Ad loading fails, there will be two situations:Suggestion:1. Waterfall ad configuration - details Please check the background log analysis. If it is in the development stage, please check log output 2. error msg contains Bid request have failed \u2014\u2014The bidding failed. For details, please implement the bidding agent to view didFailBiddingADSourceWithPlacementID 1005 (No ad display) No ad found when trying to show adSuggestion:Before calling the display ad, please first determine whether the ad slot has been prepared. You can check the judgment API of the corresponding ad type to judge 1006 (show too frequently) Ad show too frequentSuggestion: Please try to display again later. You can set a display interval of a little time to avoid this problem. You can also use the aggregation management in the TopOn background to set the display interval. 1007 (display within hours Maximum number of impressions) Ad show too many time within the same hourSuggestion:In the case of testing, you can increase the number of impressions per hour. If it has been published, the code is considered normal. Case. 1008 (Show more than the maximum number of impressions in a day) Ad show too many time within the same daySuggestion:In the case of testing, you can increase the number of impressions per hour, if you have If released, this code is considered normal. 1009 (The corresponding Adapter is not imported) The adapter not foundSuggestion:Please integrate the adapter of the corresponding advertising platform according to the information printed in the log 10010 (Ad loading timeout) Ad loading timeoutSuggestion:Please change the network of the test device and try loading ads again 1013 (The SDK of the third-party platform is not imported or the wrong version is imported. Please correspond to AnythinkiOS and sub-package versions) Third party SDK not imported or wrong version's being usedSuggestion:Please refer to our background download interface to select the corresponding adapter version for integration 1014 (Invalid App ID, App Key Or Placement ID) Invalid parameters encountered (App ID, App Key or Placement ID being nil)Suggestion:Please check whether the above information is correct and accurately fill in the initialization and ad loading 1015 (Ad delivery not turned on for the placement) Ad delivery not turned on for the placementSuggestion:Please open the corresponding advertising slot in the TopOn backend management system 1017 (advertising position strategy The placement strategy does not contain any ad sources, please check the mediation configuration in TopOn.Suggestion:Please add the media to be loaded in the corresponding ad slot Ad source, create an ad in the background of the advertising platform, and fill in the ad id into the ad slot 1018 (Ad sources have been filtered)Ad sources are filtered, no ad source is currently availableSuggestion: The advertising source has been filtered. It may be filled in the filtering API during initialization. Check whether it is filled in 1019 (The placementID load too frequently within the specified times period after the previous load failureSuggestion: Please wait at least 10s after the previous request failed before making a new request 1020 (During the specified time period, ads The placement load too many times within the specified time periodSuggestion:Please adjust the number of times the ad slot is loaded to avoid excessive loading within a period of time 1029 (Debug mode, the placement strategy does not contain any ad sources, please check the debugger configuration) The placement strategy does not contain any ad sources, please check the debugger configuration in [ATAPI setDebuggerConfig]Suggestion: You can check whether the incoming ifa is the idfa of the device, and secondly check whether the debugging mode platform used is wrong. If there is no problem above, you can give us feedback and we will investigate. 1030 (Ad source is filtered and not filled) Ad source not filled, cause by customize fillter.Suggestion:The ad source ad is set to be filtered by the custom filter configuration, resulting in no padding being loaded. You can check the settings of the initialized custom filter2. Network platform error codeThird-party advertising platform error codes&FAQ (frequently asked questions)Meta(Facebook) Common mistakes Solution 1001 - No Fill No padding. The most common reasons are that the user is not logged into the Facebook app when testing your mobile app, or the user is not logged into the Facebook mobile website when testing your mobile website 1000 - Network Error Network problem, check whether to circumvent the firewallFor more Facebook error messages, please see: Facebook error codesAdmob Common errors Solutions 0 1. Use TopOn background advertising space and use Debug mode for testing 2. Check whether the wall is bypassed 1 Invalid ad request; check ad source Parameter configuration 2 The ad request failed due to network connectivity. Check whether to circumvent the wall 3 The ad request was successful, but no ads were returned due to lack of inventory. Use TopOn background advertising slots and use Debug mode for testingFor more Admob error messages, please see: Admob error codeCSJ(TT) Common Errors Solutions 40029 Check the rendering type of the Pangolin code bit. The configuration of the TopOn background pangolin advertising source needs to be consistent with the Pangolin background The configuration remains consistent 40025 Go to the pangolin backend to download the SDK and replace the pangolin SDK provided by TopOn 40019 - The media configuration adtype is inconsistent with the request TopOn background pangolin advertising source configuration problem 40018 - The media package name is inconsistent with the entry The package name configured in the code is inconsistent with the Pangolin backend 40016 - The corresponding relationship between slot_id and app_id is illegal TopOn background pangolin advertising source configuration Problem 40006 - The advertising slot ID is illegal TopOn background pangolin advertising source configuration problem 102 - not matched Main template: The main template is not downloaded locally. It is normal to occasionally request ads for the first time You can try to request ads a few more times 103 - Subtemplate not matched: Occasionally, in the early stage of access, the template is not matched. It will not appear after the SDK downloads the template successfully. You can request a few more ads to try 107 - Template rendering times out without callback. Possible reasons are 1. Network reasons or 2. Hardware reasons. Therefore, the rendering fails. You can change the mobile phone or test the network environment. You can request a few more ads to tryFor more pangolin error information, please see: (login required) TT(CSJ) error codePangleFor Pangle error information, please check: Pangle error codeMintegral Error code msg Description Solution -1 EXCEPTION_RETURN_EMPTY No ad filling, which may cause Reasons: 1. The advertisements you obtain during the test period are all official advertisements of Mintegral, so they will be affected by the intelligent optimization of the algorithm. If a large number of advertisements are loaded and displayed for a period of time, there may be no advertisements filled after a period of time. Domestic version: 1. Make sure Mintegral background-application settings is turned on Whether to accept apk advertising Overseas version: 1. Check whether to bypass the wall or VPN to the United States Above If there is still a problem after checking, use TopOn background advertising slot and use Debug mode to test -1201 EXCEPTION_UNIT_NOT_FOUND The unitID does not exist\/entered incorrectly TopOn background Mintegral advertising source configuration problem -1203 EXCEPTION_UNIT_NOT_FOUND_IN_APP The appID and unitID do not match TopOn background Mintegral advertising source configuration problem -1205 EXCEPTION_UNIT_ADTYPE_ERROR Incoming The unitID advertising type does not match TopOn background Mintegral advertising source configuration problemFor more Sigmob error information, please see: Mintegral error code Tencent(GDT) Error code Description 4013 The system does not support it. Native video template ads only support iOS 9 and above systems 4020 window is empty, you need to add the window attribute in AppDelegate 5006 Illegal package name verification The package name configured in the codeis inconsistent with the backend of Guangdiantong 6000 Unknown error, contact Tencent Advertising Business colleagues for assistance in troubleshooting.For more Tencent advertising error information, please see: Tencent Ad error codeAppLovin Common mistakes Solution 204 No padding, you can open the test mode through the Applovin background for testingFor more AppLovin error information, please see: AppLovin error codesVungle Common mistakes Solution Cannot get ads Enable test mode through Vungle background for testing After preloading Vungle's rewarded videos and interstitial ads successfully, one of the Vungle ads was played, and the isAdReady() of the other ad returned false Vungle's rewarded videos and interstitial ads share the same advertising source resourcesFor more Vungle error messages, please see: Vungle error codeKuaishou Common mistakes Solutions 40003 - Advertising data is empty If necessary, please contact us Kuaishou related personnel 310002 - appId is invalid TopOn background Kuaishou advertising source configuration problem 310004 - packageName and registration Inconsistent packageName Package configured in code NameInconsistency with Kuaishou backend 330002 - posId is invalid TopOn background Kuaishou advertising source configuration problem 330004 - posId is inconsistent with the registered appId information TopOn background Kuaishou advertising source configuration issueFor more Kuaishou error messages, please check: (requires login to download) Kuaishou error codeSigmob Common mistakes Solutions 200000 - no ad filling Add test device through Sigmob backend for testing 500420 - The requested app has turned off advertising services Add test device for testing through Sigmob background 500473 - Requested app Does not exist TopOn background Sigmob advertising source configuration problem 500701 - app has not opened any advertising channels Check Sigmob background application statusFor more Sigmob error information, please see: Sigmob error codeBaiduMore Baidu Please check the error message: (Requires login to download) Baidu error codeBigo_AdsFor more Bigo_Ads error information, please see: Bigo_Ads error codeUnityAdsFor more UnityAds error messages, please see: UnityAds error codeChartboostMore Chartboost errors For information, please see: Chartboost error codesIronsourceMore For more Ironsource error messages, please see: Ironsource error codes OnewayFor more Oneway error messages, please see: Oneway error codeStartAppMore For StartApp error messages please view: StartApp error codeOgury For more Ogury error messages, please see: Ogury error codesKlevinFor more You Keying error messages, please see: Klevin error code","is_draft":"0","editor_type":"1","file_path":"","add_time":"1707205695","update_time":"1753783165"},"pure_content":"1. TopOn error code information descriptionThe following is a summary of the error code: Error code Note 2001 (GDPR is not set) GDPR consent not setSuggestion:Due to the data protection area (EU, etc."}],"content":{"icon":"","desc":"","content_id":"68490","add_time":"1707205728","update_time":"1753691149","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}