You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so, customers can store their internal user_ids (or whatever they might call it) in an event's properties. this is different from the event's distinct_id, which is a unique identifier for the Mixpanel account. One person can get associated with multiple distinct_ids in Mixpanel, perhaps by using a different device or triggering events while signed out.
wondering if we should offer the ability to perform event-deduping and/or sessionization at the REAL user level (not the distinct_id level). will check out our sample data to see if i can find any cases where doing so would make a significant impact
The text was updated successfully, but these errors were encountered:
so, customers can store their internal
user_id
s (or whatever they might call it) in an event's properties. this is different from the event'sdistinct_id
, which is a unique identifier for the Mixpanel account. One person can get associated with multipledistinct_id
s in Mixpanel, perhaps by using a different device or triggering events while signed out.wondering if we should offer the ability to perform event-deduping and/or sessionization at the REAL user level (not the
distinct_id
level). will check out our sample data to see if i can find any cases where doing so would make a significant impactThe text was updated successfully, but these errors were encountered: