Optimizing Event Tracking in Mixpanel: Best Practices Explained
Hi team, I have seen a suggestion from mixpanel to Group similar actions into a single event and use properties for context. For example, instead of separate events for each page view, page_name to distinguish between them. Similarly, use a single Page Viewed event with a page_name property for different pages or use a Button Clicked event with properties like button_name Now I kind of understand the benefit of their suggestion to use 1 single event for page view and add all pages as properties, (e.g home_page, cart_page, checkout_page, etc.)
But how gathering all buttons and screens in one event, will be better if we can add properties for each screen or for each button? e won't be flexible to add more info about the button or the screen, ( e.g. entery point, and other context) won't be tracked.
In addition, I'm afraid of how the flow chart will deal with properties and not separate events? the flow insight might all be page_view event.
Source: https://docs.mixpanel.com/docs/data-structure/events-and-properties#best-practices Thanks
