This topic introduces the client-side and server-side log models for custom event tracking respectively.
If the description of a field is “-“, it means the field is not used and you don't have to care it.
Client-side log model
No. | Example | Field description |
|---|---|---|
00 | D-VM | The log header, which is fixed to D-VM. |
01 | 2018-12-19 10:35:47.196 | The client log time. |
02 | A1111111****1_IOS-default | Format: App ID created in the backend_Platform type-workspaceId |
03 | V1.0.1 | The client version, namely, the App version. |
04 | 2 | The version of the log tracking SDK, which is fixed to 2. |
05 | 41111111111****|81111111111**** | Format: IMSI|IMEI |
06 | d5557b75-ff80-4aab-86a6-9b1a522b**** | Session ID |
07 | user**** | The ID generated after a user gets registered with client C, namely, the user ID. |
08 | event | Fixed to event |
09 | - | - |
10 | first | Format: Upper-level page ID|Upper-level page location 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 | The custom business code that is used to manage log upload policies. |
18 | - | - |
19 | - | - |
20 | - | - |
21 | - | - |
22 | time=2018-07-27^amount=10.05 | Used to store custom attributes and attribute values in the key=value^key=value… format. |
23 | - | - |
24 | - | - |
25 | Wn111111111111111111**** | The UTDID, namely, the device ID. |
26 | - | - |
27 | - | - |
28 | - | - |
29 | - | - |
30 | - | - |
31 | - | - |
32 | - | - |
33 | vivo Xplay3S | Device model. |
34 | 4.4.2 | OS version. |
35 | WIFI | Network type, such as Wi-Fi, 2G, 3G, or 4G. |
36 | - | - |
37 | alipay | Channel number. |
38 | en-US | Operating system language. |
39 | 0 | Version number of the hotpatch package. |
40 | 4 | Number of CPU cores. |
41 | 2265 | The maximum CPU speed, unit: MHz. |
42 | 2853 | The memory size, unit: MB. |
43 | - | - |
44 | - | - |
45 | 2560 × 1440 | Screen resolution. |
46 | - | - |
47 | - | - |
Server-side log model
No. | Example | Field description |
|---|---|---|
01 | 2018-12-19 10:35:47.996 | The server log time. |
02 | ip=182.11.xx.xx^country=China^province=Beijing^city=Beijing^district=Chaoyang District | Includes server request IP address, country, province, and city. |
03 | 2018-12-19 10:35:47.196 | The client log time. |
04 | A11111111****_IOS-default | Format: App ID created in the backend_Platform type-workspaceId. |
05 | V1.0.1 | The client version, namely, the App version. |
06 | 2 | The version of the log tracking SDK, which 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 user gets registered with client C, namely, the user ID. |
10 | event | Fixed to event. |
11 | - | - |
12 | first | Format: Upper-level page ID|Upper-level page location 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 | The custom business code that is used to manage log upload policies. |
20 | - | - |
21 | - | - |
22 | - | - |
23 | - | - |
24 | time=2018-07-27^amount=10.05 | Used to store custom attributes and attribute values in the key=value^key=value… format. |
25 | - | - |
26 | - | - |
27 | Wn111111111111111111**** | The UTDID, namely, the device ID. |
28 | - | - |
29 | - | - |
30 | - | - |
31 | - | - |
32 | - | - |
33 | - | - |
34 | - | - |
35 | vivo Xplay3S | Device model. |
36 | 4.4.2 | OS version. |
37 | WIFI | Network type, such as Wi-Fi, 2G, 3G, or 4G. |
38 | - | - |
39 | alipay | Channel number. |
40 | en-US | Operating system language. |
41 | 0 | Version number of the hotpatch package. |
42 | 4 | Number of CPU cores. |
43 | 2265 | The maximum CPU speed, unit: MHz. |
44 | 2853 | The memory size, unit: MB. |
45 | - | - |
46 | - | - |
47 | 2560 × 1440 | Screen resolution. |
48 | - | - |
49 | - | - |