To quickly get started with Quick Tracking, we recommend that you learn the basic concepts of the tracking SDK and traffic analysis products. These basic concepts run through the entire process from data tracking to data analysis.
Behavior tracking
In behavior tracking, there are four basic concepts to understand:
System events
System events are the most basic metrics that are sent by the SDK to track statistics on applications. All system event codes (corresponding to the ID field in the SDK message) start with "$$_".
Event Name | APP | Mini Programs | Web |
Application startup ($$_app_start) | Supported | Allowed | Not allowed |
Application exit ($$_app_end) | Supported | Allowed | Not allowed |
Share ($$_share) | N/A | Provided | Not allowed |
The system event protocol demo is as follows:
Page Events
Page events are events used to track page browsing behavior. The logs of page events contain two elements, page event identification code and page code.
Page event identification code: used to identify the event as a page event, corresponding to the ID field in the SDK message. The value is specified by the system,$$_page_start and $$_page_end,$$_page_start indicates that the page event is triggered when the page enters, and $$_page_end indicates that the page event is triggered when the page leaves.
Page Code: the unique identifier of the page, which corresponds to the page_name field in the SDK message. For example, if you want to tag a product details page, you need a code to specify the page as the product details page, such as Page_Detail. There are no special requirements for page codes. To prevent garbled characters, we recommend that you use lowercase letters or lowercase letters plus an underscore(_) as a event code.
The page event message demo is as follows:
Custom events
Custom events are events other than page events. They are commonly used to track user actions such as exposures and clicks. Before event tracking, you must specify a code for the event, which corresponds to the ID field in the SDK message. The event code is not mandatory. To prevent garbled characters, we recommend that you use lowercase English or lowercase English plus underscores as the event code.
The custom event message demo is as follows:
Attriubutes
Regardless of the event types, attributes need to be uploaded for events to identify the occurrence scenarios of events. For example, after the basic data such as the number of times and number of persons on the product details page is tracked, you need to add the product category attribute to the event on the product details page if you want to further know the number of times for different event categories on the product details page.
The attributes of Quick Tracking are classified into the following two types:
Global attributes:
Each event carries attributes, such as geographic location information. The message protocol demos of global attributes is as follows:
Event attributes:
Only the attributes that the event carries, such as the price attribute added to the shopping cart. The message protocol demo for the event attribute is as follows:
User identifier
All our behavior analysis must focus on a subject, which is used to connect behaviors. Quick Tracking supports two types of analysis subjects:
Device: the unique identifier of the device, which corresponds to the umid field in the SDK packet. The device is generated by the tracking SDK based on the hardware device identifier and is used to identify a unique device.
User: the unique identifier of the user, which is directly connected to the account system of the product. When the user logs in and calls the SDK, the account is used to identify the unique user.