Based on the knowledge sources available, Mixpanel's case-sensitivity means student and Student are genuinely two separate values — so if your filter for user_type IS student is returning events with Student, that would actually be unexpected behavior.
However, there is one exception worth noting: the == comparison operator in Custom Properties is case-insensitive for strings. [Custom Properties] This means if you're using a Custom Property formula with ==, it would match both student and Student.
For your situation, here's what I'd recommend:
- 1.
Verify the actual values in your data — Go to Live View or a report and check the exact casing of user_type values being sent. It's possible both student and Student exist in your data.
- 2.
If you truly only want lowercase student, the filter should work correctly given Mixpanel's case-sensitivity. If it's still returning Student events, this may be a data quality issue where both casings are being tracked simultaneously.
- 3.
Long-term fix: Standardize your property values at the source (in your implementation) to always send lowercase student. [Tracking Strategy]
The knowledge sources don't contain enough information to explain why a standard report filter would incorrectly return Student when filtering for student — if this persists after verifying your data, I'd recommend reaching out to Mixpanel support directly.
