What point is buried?
Buried point is fixed, regular data collection, tracking user behavior, to the follow-up of product optimization and user data operations provide support.
A little more popular is that you deploy Buried is made to collect data, such as user clicks, the screen view, these need to do some pre-deployment, these deployments are usually realized, when triggered, when to send what data in order to collect these data, the deployment is buried point.
Buried in the classification
according to the position of deployment can be divided into client and server Buried Buried, and the client can be divided according Buried Buried tool, it can be divided into three types: Buried codes, and visualization Buried buried point tools on the market now has the three ways, did not say which method is capable of rolling several other, because both have their drawbacks. Classification and specific advantages and disadvantages of various methods below Buried
Code Buried
This is a type currently best known, and most widely used, including Google Analyitcs, Friends of the Union, including some third-party tools are using the program.
The principle is : the SDK have deployed the basis of data to be collected in local tracking code, APP will start when initializing SDK, you click or trigger data acquisition position when the SDK will call the corresponding data interface to send data out, for example, we want to do click on a point buried position, that is, the button is clicked, this button will call the corresponding data OnClick SDK provides an interface to send data. Generally speaking, in order to avoid consumption of user traffic, usually after transmitting a plurality of data compression, and not to send a time.
Advantages:
High accuracy: precise control can trigger the condition, when it is triggered, accurate statistics of an event;
strong self-definition: You can customize a lot of rich data transfer data to the server;
Disadvantages:
heavy workload: the place needs to be tracked are added corresponding tracking code, we need to bury point, so the workload will be relatively large;
It is said that with this program, an updated version of the code large, likely to cause confusion, I think this is not a problem, I use this program a few years, do not have the change version of the old version of Buried do redeployment, only say, to give up the old version of the framework, a complete rewrite of APP when the need to redeploy, of course, the new page or when demand will need to add new buried, the workload is not large, and if you have internal a good feedback mechanism, this fast.
Others said that a performance impact, use a third-party SDK, will certainly consume memory bandwidth, which is unavoidable, As for data transfer, and now most of the third party is not transmitted in real time, all the accumulated data after compression , and other network when it is better to send data; the last one, now the mobile phone, may have as much processing power of some old desktop computer, if the performance impact of APP that you have or how much you have available how complex architecture.
As for data transmission is not reliable, it comes to the network, the network may have a delay or packet loss occurs, is a common problem to come, there are many solutions, locking, retransmission, callback.
Visualization Buried :
that developers no longer need to track point code buried, but from the code, just the face of the application interface little circle to the additional event data point force at any time. The core code and the allocation of resources separately, when APP start an update from the server configuration and resources, APP reported data according to the new configuration and resources, the entire structure is somewhat similar to GTM, the configuration is the GTM, loaded into the user each time you open the GTM is the latest configuration, so GTM trigger conditions are likely to be deployed on the trigger, enabling data collection.
Principle: web and APP pages have a similar structure, after the completion of the deployment SDK, SDK will automatically get relations at all levels of the page, the web is dom structure, the APP is UIVIEws, when you set Buried with Visual Page time the server can automatically know the location of elements and save these configurations to the server, the user opens and they will load the configuration to the client, when the user triggers when the position of the element, it will send the data out.
Advantages:
easy to deploy, can greatly save on labor costs;
for products and operations different codes can be configured through a visual interface;
Disadvantages:
not flexible and can not get custom data attributes, part of the visual location may be incomplete coverage;
every time you start the server to load the latest allocation of resources, waste flow.
Buried points:
Also called non-point buried, literally like to talk about, do not need to bury point, the data have been collected all the controls as much as possible, first in 2013, proposed by the Heap.
Principle: SDK with CSS selectors technical controls and monitoring of event-triggered technology, embedded in the APP SDK, the SDK will be in as much of the APP acquisition operations are down, you can do the classification of the data collected by the visual interface, basically it is to collect, after screening the rhythm, the case of data noise may occur.
Pros:
Easy to deploy, simply deploy SDK, initialization few lines of code, it will automatically collect data;
automatically collect a lot of data, be able to go back;
Disadvantages:
not flexible custom data attributes;
data collection and more, to put pressure on network transmission, and power consumption of user traffic, some will involve privacy issues.
Visualization Buried and buried point is very similar, except that they collect and process flow of information is just not the same, visualize buried point is collected before treatment, without burying point is to collect all, only selective processing, buried no point collecting as much data as is, so there was no point burying able to do back to the data, but it also means that the waste flow, waste of electricity, pit user.
Buried server
will be sent directly to the back-end number of agreements in the form of a few to go, such as the MP agreement, logs, or logs of the most commonly used, such as log collection to do a lot of personalized custom implementations of data, the workload is big .
In front of the client pays the bill are using third-party tools, server Buried, can be understood as a similar tool to develop their own infrastructure up.
Buried in principle
is simple: Buried point is simple, fast on the line, if a tool Buried toss a few months, this does not pit father thing.
Free: most people are doing the selection tool when the tool will consider whether to focus on pay, all you want for free tools now on the market are paid buried visual point and non-point buried, if the budget allows, consider using a visual point and non-embedded products, the major manufacturers of select products.
Accurate : the data collected is accurate, only the reference value, if the collected data with other data other large errors, simply not credible, then buried fancy point function is useless, the current accuracy the high point was buried in code.
APP buried point difference with the web bury point?
APP and WEb are buried point needs to be done to deploy, behavior is tracked by events, has buried point tracking and visual tracking.
The difference is that :
Web js tracking code is deployed, the browser is the page
APP deployed SDK, browse the screen
What is Event Monitoring ?
Event is to record user behavior or process, such as the user clicks the drop-down, these are the user's behavior, you can go through an event record. Most of the buried will point to track the form of events.
In GA, the event has
Event Category: is the name of the event, such as video playback
events behavior: either the user's behavior, such as video playback can begin playback, fast forward, pause and other acts
Events tab: can that page, the corresponding understanding is that playing video
value of the event: you can play a long time
whether the type of interaction: interaction types of events will be included in the calculation of bounce rate, generally the type of events are set to a non-interacting.
More details of the event monitor to see on the site event tracking related articles.
How APP application event monitoring
as long as the behavior can be applied event monitoring , such as
the registration form: Build conversion funnel
button tracking: locate zombies button
full path tracking; conversion path
selection Tracking: User preferences
......
there are plenty to go tracked by the event .