This topic describes the client-side and server-side log models for custom event tracking.
A hyphen (-) in the field description indicates that the field is not used.
Client log model
Ordinal number | Example | Field meaning |
00 | D-VM | Log header. The value is fixed to D-VM. |
01 | 2018-12-19 10:35:47.196 | Client log time. |
02 | A111111****11_IOS-default | Format: Application ID created in the console_Application platform-workspaceId |
03 | 1.0.1 | Client version, which is the application version. |
04 | 2 | Log tracking SDK version. The value is fixed to 2. |
05 | 411111111****11|811111****11111 | Format: IMSI|IMEI. |
06 | d5557b75-ff80-4aab-86a6-9b1a522b**** | Session ID. |
07 | user**** | The ID generated after a client-side user registers. This is the user ID. |
08 | event | The value is fixed to event. |
09 | - | - |
10 | first | Format: Previous page ID|Previous page position ID. If the current page is the home page, this field is "-" or "first". |
11 | - | - |
12 | - | - |
13 | - | - |
14 | - | - |
15 | PayResults | Custom event ID. |
16 | - | - |
17 | Pay | Custom business code. It is used to control the log upload policy. |
18 | - | - |
19 | - | - |
20 | - | - |
21 | - | - |
22 | time=2018-07-27^amount=10.05 | Used to store custom properties and their values. Format: key=value^key=value... |
23 | - | - |
24 | - | - |
25 | Wn111111111111111111**** | UTDID, which is the device ID. |
26 | - | - |
27 | - | - |
28 | - | - |
29 | - | - |
30 | - | - |
31 | - | - |
32 | - | - |
33 | vivo Xplay3S | Device model. |
34 | 4.4.2 | Operating system version. |
35 | WIFI | Network type, such as Wi-Fi, 2G, 3G, or 4G. |
36 | - | - |
37 | alipay | Channel ID. |
38 | zh-CN | Operating system language. |
39 | 0 | Hotpatching package version number. |
40 | 4 | Number of CPU cores. |
41 | 2265 | Maximum CPU frequency. Unit: MHz. |
42 | 2853 | Memory size. Unit: MB. |
43 | - | - |
44 | - | - |
45 | 2560x1440 | Screen resolution. |
46 | - | - |
47 | - | - |
Server-side log model
Ordinal number | Example | Field meaning |
01 | 2018-12-19 10:35:47.996 | Server-side log time. |
02 | ip=182.11.xx.xx^country=China^province=Beijing^city=Beijing^district=Chaoyang District | Contains information such as the server-side request IP address, country, province, and city. |
03 | 2018-12-19 10:35:47.196 | Client log time. |
04 | A11111111****_IOS-default | Format: Application ID created in the console_Application platform-workspaceId. |
05 | 1.0.1 | Client version, which is the application version. |
06 | 2 | Log tracking SDK version. The value is fixed to 2. |
07 | 41111111111****|81111111111**** | Format: IMSI|IMEI. |
08 | d5557b75-ff80-4aab-86a6-9b1a522b**** | Session ID. |
09 | user**** | The ID generated after a client-side user registers. This is the user ID. |
10 | event | The value is fixed to event. |
11 | - | - |
12 | first | Format: Previous page ID|Previous page position ID. If the current page is the home page, this field is "-" or "first". |
13 | - | - |
14 | - | - |
15 | - | - |
16 | - | - |
17 | PayResults | Custom event ID. |
18 | - | - |
19 | Pay | Custom business code. It is used to control the log upload policy. |
20 | - | - |
21 | - | - |
22 | - | - |
23 | - | - |
24 | time=2018-07-27^amount=10.05 | Used to store custom properties and their values. Format: key=value^key=value... |
25 | - | - |
26 | - | - |
27 | Wn11111111111111**** | UTDID, which is the device ID. |
28 | - | - |
29 | - | - |
30 | - | - |
31 | - | - |
32 | - | - |
33 | - | - |
34 | - | - |
35 | vivo Xplay3S | Device model. |
36 | 4.4.2 | Operating system version. |
37 | WIFI | Network type, such as Wi-Fi, 2G, 3G, or 4G. |
38 | - | - |
39 | alipay | Channel ID. |
40 | zh-CN | Operating system language. |
41 | 0 | Hotpatching package version number. |
42 | 4 | Number of CPU cores. |
43 | 2265 | Maximum CPU frequency. Unit: MHz. |
44 | 2853 | Memory size. Unit: MB. |
45 | - | - |
46 | - | - |
47 | 2560x1440 | Screen resolution. |
48 | - | - |
49 | - | - |