Treat variables as attributes that describe events, [consumption of different products and content], [product name] are variables. For example: in our financial management project, I want to know which type of fund product the user likes, then "successful purchase" is a buried event, and "product executive list type" and "product ID" are variables. If you want to executive list see how much the user used for coupons when purchasing funds, you can also use "purchase success" as a buried event, and "coupon type" and "coupon ID" as variables for "purchase success".
Summary: There is a one-to-many relationship executive list between tracking events and event-level variables, and event-level variables can only be used with corresponding tracking variables. 2. Edit public properties and buried point locations Buried point executive list requirements: reasonable buried point design + clear event trigger timing + standardized naming + continuous maintenance of the data dictionary. Most of the data inaccuracy is caused by the different definitions of events between our business department and product department, so we must confirm it in the meeting and review.
Edit the PR attributes (that is, the user information required for each tracking point), such as user ID, registration channel, operating system, App executive list version, location information, etc. 2) Design the tracking points according to the core business in the early stage, and refuse to manage the chaos of massive tracking points (for example, in our project, we executive list mainly want to understand the user's product preferences and user content preferences). 3) If you use a third party (such as Umeng code buried points), it will actually be a little simpler and can meet about 70% of our needs.