Data burying point configuration method, storage medium and equipment

Abstract

The invention discloses a data burying point configuration method, a storage medium and equipment, and the method comprises the following steps: S1, setting a front end to record a behavior log of a user, comprehensively recording and reporting basic events such as page access and button click by adopting a comprehensive mode of full burying points and code burying points, and adding special burying points for functional events; s2, synchronizing various business data logs based on a back end, establishing a dimension information table, perfecting an EV event processing method, and ensuring the accuracy and comprehensiveness of data; and S3, carrying out buried point process management and data filtering management. According to the method, point burying process control and scheme compilation can be carried out based on point burying configuration, processing and a point burying system, the top design of a point burying technical scheme is perfected, understanding of event information and attribute information is increased through service mapping, the use condition is monitored, the problem that a triggering mechanism of point burying is not clear and unclear is solved, and the system reliability is improved. And the accuracy and comprehensiveness of burying point data are improved.

Description

technical field [0001] The invention relates to the technical field of data collection, in particular to a configuration method, system and equipment for data buried points. Background technique [0002] The so-called buried point is a term in the field of data collection. As a commonly used data collection method, its scientific name should be called event tracking. The corresponding English is Event Tracking, which refers to capturing, processing and sending specific user behaviors or events. Related technologies and their implementation process. [0003] Data embedding is to develop and embedding points for each event corresponding to user behavior based on business needs or product requirements, and report the data results of embedding points, record and summarize the data for analysis, promote product optimization and guide operations, or be used for Research user behavior habits and other aspects. [0004] For example, directly use third-party statistical tools such ...

AI Technical Summary

Problems solved by technology

[0007] ① Business compatibility issues

[0008] After the implementation of the previous specification, with the subsequent expansion of the business, the existing data fields cannot meet the analysis needs of the business;

[0009] ②Product compatibility issues

[0011] ③ The problem of inconsistency between the front and rear end buried points

[0014] Self-buried points generally define a unique id as a sign to distinguish users, but the third party lacks user attribute information, and generally uses the device number uuid / imei, or IP address segment, mac address segment as a distinguishing mark, resulting in statistics Data differentiation is not very compatible for scenarios where detailed data is required for retention analysis, conversion analysis, and churn analysis;

[0015] ⑤ Inadequate implementation of buried point development technology

[0016] In most cases, when we talk about buried points, we usually refer to front-end buried points. Front-end development engineers often do buried points artificially. During the development process, some information will be redundant, repeated, and records will be incomplete. the situation exists;

[0017] ⑥ Module differentiation among multiple products

[0019] ⑦The key pair design problem of custom buried point information

[0020] A json field (bdata) is often added to the burying point, and custom business information is written into the burying point for scene identification, such as activity id, business information, basic information of user snapshots, etc., written by different development Custom field formats may vary

Images