There are a few Mixpanel-specific checks you can do to narrow this down:
- 1.
Confirm events are arriving at all (for anyone).
Since you see other users’ data, your project is receiving events, but it’s still worth checking the Events view (formerly Live View) to confirm events are flowing in real time and that your implementation is generally healthy.[Debugging guide]
- 2.
Search by technical IDs, not just email.
In the Events view, manually trigger activity as that user (if you can) and then:
Search/filter by distinct_id, $user_id, $device_id, or any other property you know should be on their events (e.g. internal user ID), not just email.
If you’re using the JS SDK and can reproduce as that user in a browser, use mixpanel.get_distinct_id() in the console to get the distinct_id, then search for that in Events.[Debugging guide]
- 3.
Check if the user ever had a profile created.
From any event you do find for them in Events, click the user icon to open the User Profile. This lets you see:
Whether a profile exists at all
Whether $email was ever set on that profile (maybe it’s missing or spelled differently)
User properties on profiles show the latest value only, so if $email was never set, searching Users by email won’t find them.[User profiles debug]
- 4.
Rule out identity / merge issues.
If multiple people share a device and reset() is not called on logout, events from different users can be merged into one profile, so the user’s activity might be “hidden” under another identity cluster.[Identity FAQ]
Also, if different systems send events for the same person with different distinct_ids, you can end up with multiple profiles that share the same email or none with the email you expect.[Identity FAQ]
- 5.
Check for hidden events/properties.
If you know the event names they should be firing, confirm those events or properties aren’t hidden in Lexicon or marked inactive (which would hide them from dropdowns, though not from raw data). You can still search by exact event name in Events.[Hidden events]
- 6.
Validate implementation for that user path.
If you can reproduce their journey:
Use Events to confirm each expected event fires with the right properties and distinct_id.
Make sure identify() is called with a stable user ID and that people.set (or equivalent) is setting $email after identify, so the profile can be found by email.[Identify users]
If, after searching by distinct_id/$user_id and checking Events, you truly see no events for that user, the knowledge sources only suggest generic next steps: enable SDK debug logging, inspect network calls, and verify the correct project token and API host, to confirm their events are actually being sent to this Mixpanel project.[Missing events]
