Manual buried point (code buried point) Visual buried point No buried point


Consider a few questions:

  1. What data to collect
  2. How does the business side invoke our collection script
  3. Manual embedding point: THE SDK needs to encapsulate a method for the business side to call, and the business side can control the parameter transmission mode
  4. No-buried point: Considering the pressure of the data volume on the server, we need to configure the no-buried point switch, which five elements can be configured for no-buried point collection
  5. User identification: How to distinguish and associate the collected data of tourist users and login users
  6. Device Id: When a user accesses web pages through a browser, the device Id must be stored in the browser. The device Id must be the same when the same user accesses different websites of 8 service parties
  7. Single page application: Is there any difference in data collection between popular single page application and ordinary Web page
  8. Hybrid application: Hybrid application of APP and H5 How do we communicate


General collection number of users open participation length of stay jump rate Quit rate…



  • Manual embedding (code embedding)

Manual code burying points are common, where the business party that needs to call a burying point invokes a burying point method where data needs to be collected

  1.  Command buried pointTo insert monitoring logic where monitoring is needed in the front-end code 

    $(document).ready(function() {/ /... There is some business logic sendRequest(Params); }); // Button click to send buried request $('button').click(function(){// There is some business logic here sendRequest(params); });Copy the code

Advantages: Control the sending of data time, event custom attribute detailed record

Page load upload parameter to background record, button click upload parameter to background record……..


2. Declarative buried point

Add buried information to the DOM element as follows

// key indicates the unique identifier of the buried point.

Act indicates the burying mode

< button data – stat = “{key: ‘111’, the act: ‘click’}” > buried point < / button >

Traverse the DOM tree, locate the node of the [data-stat] element, bind the click event,

Sends the information on [data-stat] to the server

Disadvantages: 1. Timing problem of traversing DOM tree. A simple example is that the row data of a table is asynchronously loaded, and the operation button in the table row needs to be buried, so traversing when the DOM is ready is obviously impossible to find 2. Bind the number of buried events, how to ensure that buried events will not be repeatedly bound to the element, an operation sent N buried requests repeated work, but also to deal with bubbling.


  • Visual burial point

The relationship between control operation and event operation can be configured through visual interface. Data is collected through background screenshots. However, the burying point is the burying point trend of this year, and many large factories’ own data burying point departments have also begun to do this. Through the buried configuration background, you can automatically generate buried code to be embedded in the page by associating elements with events to be collected.

Advantages: low cost, fast speed

Disadvantages: less behavior record information, less supported analysis methods, technical promotion and implementation is a little difficult (business front-end code specification is a major prerequisite)


  • No burial site

If there is no buried point, the front end automatically collects all events and reports buried point data, and the back end filters and calculates useful data

The advantage is that the front end only loads the buried script once. No need to bury point, convenient and quick

The disadvantage is that the traffic and the data collected are too large, the server performance pressure is huge, the behavior record information is little, the transmission pressure is big



You can determine the burying point scheme according to your own business content, such as 60% full burying point +40% manual burying point