All Products
Search
Document Center

Log tracking

Last Updated: Jul 07, 2021

This topic introduces the log tracking involved in Mobile Analysis Service (MAS).

Data collection

MAS functions rely on the tracking logs reported by the client. To provide more accurate analysis capabilities, tracking logs collect the following device information: public IP address, IMEI, IMSI, device model, operating system version, network type (such as Wi-Fi, 3G, or 4G), operating system language, number of CPU cores, CPU rotation speed, memory size, screen resolution, client channel ID, and client version number.

Tracking log model

The tracking log model varies with the log type. A log is a string of characters separated by commas. Each field in the string has a specific meaning and the server splits a log by field.

Common tracking types are as follows:

  • Android or iOS tracking
    • Custom event tracking: Records actions such as button clicks or link clicks. You can create tracking for any trigger time of an action in your App. Then, the tracking logs can be used in the functions such as custom event analysis and funnel analysis.
    • Behavior tracking
      • Active device/user tracking: Records a start of your App, either cold start or App switches to the foreground. The tracking logs can be used to analyze key metrics such as Startup count, New users, Active users, and Active accounts.
        • In Android client, by default, one active device/user is reported every time the App switches to foreground after staying at background for over 30 minutes.
        • In iOS client, by default, one active device/user is reported every time the App switches from background to foreground. If you want to adjust the reporting interval as 30 minutes, you can set the return value of [[DTFrameworkInterface sharedInstance] logReportActiveMinInterval]; as 1800.
      • Page automation tracking: Records information such as page views, page traffic, and dwell duration. The tracking logs can be used to analyze metrics such as PV, UV, and Page traffic.
      • Switch-to-background tracking: Records information about the switch between the foreground and background of your App. The tracking logs can be used to analyze metrics such as App usage time and Active duration.
    • Performance tracking
      • Startup time tracking: Records the startup speed of your App, including the first startup (start an App for the first time after the App is installed) and non-first startup (App startup other than the first startup after App installation).
      • Stuck tracking: Records App stuck and related error logs. The stuck includes:
        • Android startup stuck: The main thread does not finish executing a method within 5s when the App starts.
        • Android ANR stuck: The App does not respond. For more information, see the ANR description on the Android website.
        • iOS startup stuck: The main thread does not finish executing a method within 5s when the App starts.
        • iOS ANR stuck: The main thread does not finish executing a method within 5s when the App is running.
      • Lag tracking: Records App lags and related error logs. A lag occurs when the main thread does not finish executing a method within the specified period (2.25 seconds for Android and 2 seconds for iOS).
      • Crash tracking: Records App crashes and error stacks.
  • HTML5 and PC tracking
    • Page tracking: Automatically records information such as page views and traffic flow. The information is used to measure indicators such as PV, UV, and Traffic flow direction.
    • Tap tracking: Records the click on a specific button or link on a Web page.
    • Exposure tracking: Records exposure information about certain content on a Web page.