Use event properties to describe an action when it happened. Use user properties to describe the person who performed it. In Mixpanel, choosing the wrong one can change how you interpret a report, even when the tracking code works.
Consider a customer who starts on a Free plan and upgrades to Pro. If you want to know which plan they had when they created a report last month, capture that plan on the event. If you want to find customers who are on Pro today, maintain their current plan on the user profile.
A practical example
| Question | Recommended property |
|---|---|
| Which plan was used when a report was created? | Event: plan_at_event |
| Which plan does this customer have now? | User: current_plan |
| Which export format was selected? | Event: export_format |
| What role does the customer currently hold? | User: current_role |
These are suggested custom names, not reserved Mixpanel fields. Explicit names help your team distinguish historical context from current customer attributes.
How to send both types
This JavaScript example assumes that the Mixpanel SDK is initialized, tracking is permitted, and the application has authenticated the customer:
mixpanel.identify("customer_742");
mixpanel.people.set({ current_plan: "Pro" });
mixpanel.track("Report Created", {
plan_at_event: "Pro",
report_type: "Campaign Performance"
});
The profile update and the tracked action serve different purposes. Setting a user property does not add that property to the raw payload of every event. A report may join profile information to activity, but that is different from recording an event-time snapshot.
Why historical reports can surprise you
Suppose a customer created five reports while on Free, then upgraded. A breakdown using the ordinary current-plan profile property can describe those earlier actions using the customer’s current Pro status. That may be useful for analyzing today’s customer base, but it does not answer which plan they used at the time.
My recommendation is to write the business question next to the property definition in your tracking plan. “Current subscription tier” and “subscription tier at action time” should be separate definitions when you need both.
Where super properties fit
A super property is a convenient way for a client SDK to attach a value to subsequent events. It is still event context, rather than a user profile update. If you persist a plan value this way, update or clear it as the customer’s state changes.
How to verify your setup
- In a development project, create a report on Free.
- Upgrade the test account and update its profile to Pro.
- Create another report and inspect both raw events.
- Confirm that the first event still records Free and the second records Pro.
- Compare an event-property breakdown with a current-profile-property breakdown.
Ask a colleague to explain each report without reading your implementation notes. If the distinction is unclear, improve the property labels and descriptions before sharing the dashboard.
Need help with your Mixpanel setup?
Optizent helps teams plan, implement, and troubleshoot analytics. Contact Optizent to discuss your Mixpanel tracking or reporting needs.
References
GET EXPERT ANALYTICS HELP
Need help getting reliable answers from Mixpanel?
Tell us about your tracking, funnels, retention, or reporting challenge. Optizent can help you implement, audit, and use Mixpanel with confidence.
We will use these details to respond to your request. Please do not include passwords, account access, or customer data.
