Step 1
Enter the schemeUrl of the app. If you do not know, you can consult the client development of the corresponding app. After entering, click to generate the verification address. At this time, a two-dimensional code for verification will be generated. Note here that the format of schemeurl must be atm.appkey, where atm is a fixed prefix and appkey is the appkey of the app to be tested. 
Step 2
Scan this two-dimensional code through a mobile phone or a three-party app (such as uc browser). Note that the test target app cannot be used. After scanning, the browser will open the following page and click to start the embedded test. At this time, if the previous steps are correct, the app to be tested will be called up on the mobile phone.
Step 3
After entering the test app correctly, the tracking verification page should automatically jump to the log details page. If it fails to jump automatically, it may be caused by the mobile phone network and PC network not being in the same network environment. At this time, you can click on the right side of the two-dimensional code on the platform to jump to the log details page.
Step 4:
After you jump to the real-time log details page, perform any operation in the app at this time, and the corresponding collection log will be printed on the log details page in real time, as shown in the following figure:
