1. What is visual full buried point
1.1. The whole point
Before introducing visual full buried points, let’s take a look at full buried points.
Full burial point, also known as no burial point, no code burial point, no trace burial point, automatic burial point. Full buried point means that all or most of the behavioral data of users can be automatically collected in advance without the application development engineer writing code or only writing a small amount of code, and then the required behavioral data can be screened out and analyzed according to the actual business analysis requirements [1].
Shence analysis of iOS SDK currently support full buried events: App start, App exit, element click, page browsing. All it takes is for the guest developer to integrate correctly, initialize the SDK and enable the configuration to automatically collect events and related properties when the corresponding event fires.
1.2. Visualization of full buried points
1.2.1. Visualization of full buried point events
Visualization of fully buried events means that some fully buried events are created into a renamed virtual event [2] through visualization, so that we can quickly screen out the events we care about from the huge amount of fully buried events that have been collected.
Taking into account the actual application scenario, the current strategic analysis of the visualization of full buried points, support element click and page browsing events. For example, the add shopping cart button of the App will trigger a full buried event named “AppClick” when clicked, and collect relevant information about the button element and the current page. Although the “Add Shopping cart” button click triggers the full buried event of “AppClick” and collects information about the button element and the current page. Although the “Add Shopping cart” button click triggers the full buried event of “AppClick” and collects information about the button element and the current page. Although the “Add Cart” button click triggers the “AppClick” event, this event actually contains all the click-triggered events for the elements in the current App. Therefore, it is difficult to analyze information such as the number of hits or geographical distribution of the “Add cart” button over a given period of time.
1.2.2. Custom attributes
To visualize the custom attributes of a full buried point is to visually add the attributes related to the current event. For example, when clicking “Add shopping cart” button triggers “$AppClick” full buried event, the current product name, price, configuration information, etc., will be collected as event attributes.
Considering real commercial projects, products details information such as the request to the data from the network, then the asynchronous rendering, so at the time of trigger events page views, may have not rendered page data and information or display default values, that is not to collect page final display information, event page views so if support custom attributes, The collection may be inaccurate in many scenarios. Therefore, the current visualization of fully buried custom attributes only supports element click events.
In addition, the current custom attributes, while collecting element content, also support rule processing. For example, the content can be rounded, the first few characters, and only values. Regular expressions can also be written to meet more practical application scenarios.
1.2.3. Overall process
Figure 1-1 shows the overall process of visualizing full buried points:
Figure 1-1 Flowchart for visualizing the whole buried point
2. Why is it necessary to visualize all buried points
The last section briefly introduced the meaning and the overall process of visualization of full buried point, you may still have a question: since there is a full buried point, why also need to visualize full buried point?
2.1. Improve buried point efficiency
In fact, the essence of visualizing full buried points is to create virtual events based on a series of filters.
If we do not use the visual full buried point to analyze specific full buried point events, we need to create virtual events or combine filtering conditions for query according to the full buried point event name and the characteristics of related attributes. It can be imagined that the process is very time-consuming, and for the analysts who want to see the results, this kind of tedious work seriously affects the work efficiency.
The ability to analyze specific events or attributes using visual full buried points, which are simply selected and named on the front page in a visual manner, greatly improves burying efficiency. So that analysts do not have to spend too much time in the buried point, can focus more on product analysis and later decision.
2.2. Lower the threshold of embedding
With visual full burial points, it is possible to analyze specific user behavior and related attribute information without the involvement of the developer. The analysis personnel who are not familiar with the technical implementation can also bury the site quickly and efficiently, thus greatly reducing the threshold of burying the site.
2.3. Convenient iteration
When designing buried event, it is inevitable to omit some important scene event collection. Under the traditional acquisition scheme, we can only re-bury the concurrent version in App. After being online for a while, we get the data we need to analyze.
Visual full buried points are virtual events created based on full buried points, so we do not need these complex processes to define events in the Shenze analysis platform and support backtracking analysis. This enables analysts to analyze data of all online fully buried events without relying on some specific versions, and to collect complete data before and after versions in the process of version iteration, so as to meet analysis requirements.
Because a visual full buried point is a “buried event” created from a virtual event, we can create the “buried event” again if we accidentally delete it. In addition, historical data is not deleted. This greatly reduces the time cost and “lost event” impact of design omissions.
2.4. Application Scenarios
In terms of the quality of buried point itself, code buried point is far better than visual full buried point, but visual full buried point has incomparable advantages in cost of buried point and backtracking history. Visualization of full buried points is a better way to achieve data-driven early on for customers who meet the following scenarios:
- No or few R&D resources;
- The project was relatively early, with interaction analysis as the main and business analysis as the auxiliary;
- Most of the pages that need to be analyzed are activity pages, and the analysis appeals are mainly mobile terminals.
Code burial point and visual full burial point are the two burial point methods provided to customers at different stages of Strategic analysis. From the point of view of building a more solid data foundation, the code burying point is the first choice, but for some short and quick analysis needs, you can consider using visual full burying point.
3. How to use visual full buried point
3.1. Enter the visualization full buried point
3.1.1. Integrate the SDK
Before starting the visualization of full buried points, it is necessary to correctly integrate and initialize the iOS SDK of Zizu analysis, and then enable the visualization of full buried points, as described in the documentation: Enable visualization of full buried points [3].
3.1.2. The buried point page is displayed
Log in to the background environment of strategic analysis, enter the metadata management module, and start to visualize full buried points. As shown in Figure 3-1:
Figure 3-1 Visualizing the entrance of a fully buried site
3.1.3. Scan connection
- Select scan code link on the Shence analysis page to enter the page for scanning two-dimensional code. If you use the iPhone, you are advised to use the qr code scanning function provided by the system, and then jump to the Safari page. Android phones can use the browser scan function or wechat scan function to scan code, according to the browser pop-up prompt operation to open the corresponding H5 page;
- After scanning the code, click the button “Open the full buried point of App visualization” on the H5 page, and then click the button “Open” to successfully open the App to be analyzed.
- After connecting App successfully, visualization of full buried points can be carried out.
Figure 3-2 shows the process of scanning code connections.
Figure 3-2 Scan code connection diagram
3.2. Define events
3.2.1. Define element click events
After entering the visual full burial point, you can define the element click event. After a clickable element is selected, as shown in Figure 3-3:
Figure 3-3 Selecting a clickable element
You can see the following qualifiers:
- Unrestricted content (text);
- The qualifying order is the “3” bit.
The above two conditions mean that the “3” element click event occurs under “current page” within the same element in the list. If the content (text) of the element changes, the buried point is still valid.
Accordingly, element click events that qualify specific content are shown in Figure 3-4:
Figure 3-4 Element click events that qualify specific content
If we change the conditions, we can see that the qualification conditions are as follows:
- Restrict content (text);
- There is no limit to the order position.
The above two conditions mean that the click event of an element with the content (text) of “life trip” occurs under “current page” within the same element. The order of the elements changes, and the burial point remains valid. Element content (text) changes, burying point invalid.
In addition, composition depends on whether element content and element location are qualified or not. The following scenarios can also be met:
- An element that defines a particular content at a particular location;
- Define the entire list button (unlimited content, unlimited position).
It is important to note that only list elements, or nested child elements within a list, are supported by the positional constraint function.
3.2.2. Define page browsing events
Click “Create page browsing event” button, in the popup page, confirm the event name and click save. See Figure 3-5.
Figure 3-5 Create page browsing event
3.3. Customize attributes
In addition to defining the event, you can also select the element content in the page to define the attribute information for the event as follows:
- On the Create Element click event page, click the “Add Attribute” button, as shown in Figure 3-6: \
Figure 3-6 Add Properties button
2. Click the element on the page and save the attribute information, as shown in Figure 3-7
Figure 3-7 Saving the property information
3. Save the Settings and confirm the event, as shown in Figure 3-8.
Figure 3-8 Create event
After adding attributes, the “product_price” attribute will also be collected according to the content processing rules when clicking the “Buy now” button triggers the “$AppClick” full buried event.
4. Limitations of visualization of full buried points
Although visualization full buried point has many advantages, it is not a panacea, and it also has its own limitations.
4.1. Some events and attributes are not supported
Some specific element click events, because the current full buried point does not support collection, so the visual full buried point is not supported. For example: system keyboard switch input method and other key click.
In addition, some business-related information may not be displayed on the page, and custom attributes are not currently supported. For example: commodity inventory information, commodity ID, historical price, etc.
4.2. Custom attributes do not support backtracking
While the visual full burrow events for element clicks and page views support backtracking, the visual full burrow custom attributes do not. This is because the collection starts after the property is created, that is, the visual full buried event before the custom property is created does not contain the property.
5. To summarize
This article is the first of a series of articles on visualization full buried point. It mainly introduces the related concepts and usage of visualization full buried point, aiming to help you have an overall understanding of the visualization full buried point. The concrete realization of visualization full buried point will be introduced step by step.
Finally, welcome to join the open source community for discussion.
6. References
[1] WANG Zhuozhou. IOS Full buried Point Solution [M]. Beijing: China Machine Press,2020:162-197.
[2] manual. Sensorsdata. Cn/sa/latest/virtual…
[3] manual. Sensorsdata. Cn/sa/latest/e…
The article is from the public account – Shence Technology community