Some problems and ideas of data embedding point

This article is some ideas about the buried points of our company

1. Buried point event binding

First , Our company has page embedding points （ The only buried point on each page , For example, the home page ） And events （ Buried point of behavior , For example, click on ） Two kinds of

We are the event embedment point and will bind the page embedment point , That is, a behavior of each page has a unique buried point , But is this necessary , Or what is the cost of doing this

There are hundreds of buried sites in our company （ Tiktok wechat and so on are generally 100 about ）, A like will have multiple buried points on different pages , It causes great trouble for maintenance and data development , In fact, we want all orders / Like and so on are the burial points of the same event , You can use one field to distinguish pages , For example, cancel the page burying point binding , The buried point of behavior events remains unchanged , You can distinguish the source by embedding points on the page , In the future, we will try to promote the unbound and unified specification of buried point events

2. The source of the entrance

give an example ： Chat room entrance , I know that the user has entered the chat room , But I don't know its source , It can also be said that the embedding point does not contain the information of its previous page

I will promote such a thing later , You should be able to get the information of the previous page , That is, the entrance of behavior , Facilitate event correlation , But you need to avoid user fallback events