It’s important that every event tracked in Mixpanel is meaningful and aligned with your product or business goals. Tracking an event like "User quota analysis" only makes sense if it represents a specific, actionable user behavior or system action that you want to analyze.
Mixpanel best practices recommend that events should capture user actions or behaviors, not calculations or internal metrics unless those calculations represent something you want to analyze as a user event. For example, events like "Button Clicked" or "Purchase Completed" are clear user actions. If "User quota analysis" was just a calculation or a custom function and not an actual user action, it likely doesn’t fit the intended use of event tracking in Mixpanel. Tracking such events can clutter your data and make analysis harder for your team, especially if the event doesn’t provide actionable insight or is not queried in your reports. In fact, Mixpanel recommends dropping events that are not being queried or are not useful for analysis, to keep your data clean and relevant Docs: Data Clean-Up.
If your CTO says it was a calculation and can be removed, that aligns with Mixpanel’s guidance: only track events that are meaningful for your analysis, and remove those that are not. This helps avoid unnecessary complexity and keeps your analytics focused on what matters Blog: Engineering Buy-In.
In summary: It does not make sense to track events in Mixpanel that are just calculations or internal functions unless they represent a meaningful user or system action you want to analyze. Removing such events is a good practice.
