Sultan A.

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.)

Source: https://docs.mixpanel.com/docs/data-structure/events-and-properties#best-practices Thanks

Hi team, I wanted to ask about a pattern I’ve noticed in some event implementations and get your thoughts on the best practices around it. In some products, instead of firing multiple events (e.g., screen views or button clicks), teams track just one event at the end of a flow — usually when the user clicks a "back" or "X" button, or completes the flow. That event includes multiple properties like:

This is typically done in feature activation flows with multiple steps/screens or single navigation screen. The reasoning I’ve heard is that this method reduces event volume (and cost), and keeps things simpler. However, I’ve found that this approach doesn’t work well when building funnels or flow analysis in Mixpanel, since intermediate steps aren’t explicitly captured as events — making it harder to see actual user drop-offs or behavioral insights. So my question is:

What’s the recommended practice here — should I fire events at each meaningful user action or screen view, or is it acceptable (and encouraged) to wait until the end and fire one event with all the behavior as properties?

Would love to hear your perspective on accuracy, scalability, and analytics usability. Thanks!

Tracking behavior clarification: In our current setup, the team sometimes tracks a single event only after the user finishes a flow (e.g., Deposit Completed), and they use event properties to indicate what happened during the steps (like which method was clicked, etc.). Is this a recommended approach? Or would you advise breaking it into multiple step-by-step events (like Deposit Button Click, Deposit View, Payment Method Selected)? note that the argument is that increasing the events will add complexity and increase cost

Hi, can I call .identify once only upon registration without the need to call it each users sign in? If yes would I loose the link of guest id and user id?