How do I do data bury?

Buried point a good privatization deployment data collection method, of course, this article is mainly for the code buried in the way to explain.

1. Clarify the purpose of the burial point

In layman's terms, that is, what data we need to look at, such as whether an article is shared enough, or the proportion of successful payment slips, can generally be broadly divided into three categories: user basic data, functional usage data, comprehensive data.

2. Sort out business processes

Combing business processes, in fact, is not necessary, but for some of the more complex user operation processes, it is necessary to pay special attention, because there are some need to be calculated through multiple steps to get a percentage, such as the user's order process, roughly need to be registered - > login - > browsing list - > access details - > buy immediately - > confirm orders - > payments, which involves the loss of users at each link, This allows you to infer the final payment conversion.

And there are some buried point purposes relatively simple, is to compare the popularity of multiple entrances, then directly in each entrance buried point can be, because it does not involve any process, just need to count their clicks can be.

3. Define the buried point event

As a product, we need to define the id of the event, the name of the event, the event id is the English field that the development engineer writes to the code, the name of the event is to be able to understand what is buried, but also need a name corresponding to the English field, and for some platforms such as the Alliance also need to define the event type, it can be defined as a multi-parameter type event or calculate the event.

That in addition to the above in the buried point of the third-party platform must submit parameters, in order to enable the product itself after a long time, or other colleagues can know before a buried point is what it means, generally we will also go to organize a buried point corresponding to which functional module, as well as a simple description of a buried point of instructions, you can use Excel table to organize, probably as follows:

4. Data collection

After producing the above buried point demand table, the table to the development engineer on it, of course, before this, also need to enter the corresponding events into the data statistics platform, to ensure that we can normally see the data, such as the AIA platform is in the event management to add events, and then to fill in the event id event name and select the type of event, of course, can also be added in bulk, the specific template of different platforms slightly different, need to add time to the various platforms to view.

Another purpose is to monitor the user's entry source for the open member, so we added the corresponding buried point at the entrance location where the member is opened, named clickOpen and added the parameter to the event, which is the property of the image fromPage and specified that the source is Banner and one is Dialog that pops up on the home page.

5. Add a burial point

So after sorting out the above burial site requirements, we add the corresponding events to the background of the Alliance (you can choose to add multiple or manual individual to add, the following image is a single added screenshot), while the above requirements to the development engineer to carry out the burial point.