Aug 03, 2022
In Interior Design Forum
When you need to query the APP product buried point data, you have to often ask the data product manager to confirm whether there are buried points, which fields are buried, whether there is already reported data, etc. Often the meta-information of these tracking events is scattered in the hands of multiple product managers, the information is scattered, and the communication costs are extremely high before analysts use the tracking data, which affects the efficiency of data use... Not only that, if there is an abnormality in mobile number list the buried point data, the process of tracing the historical problem of the buried point is also very long. The data product manager needs to confirm the version of the buried point requirement with the business product manager, and then the data product manager confirms the batch of the buried point design requirement. , and then give it to the development, and the development colleagues will find the problem... The management of buried point requirements and buried point design documents is scattered, and the efficiency of collaborative communication between products, development, and testing is low, which seriously affects work efficiency. Meta-information management of buried events is scattered and often distributed in the hands of multiple product managers. When analysts use buried data, they need to query buried requirements and meta information of buried events. This process involves a long process link, and communication costs are very high. It is extremely inconvenient to use point meta information to query.