kapa.ai The tracking is set up via Segment who then sends the data to Mixpanel. In Mixpanel the user_id as other properties are being overwritten every time there’s a new identify_call
Based on the information provided in the knowledge sources, I can address your concern about user properties being overwritten in Mixpanel when using Segment for tracking. When using Segment to send data to Mixpanel, the identify call in Segment maps to Mixpanel's user identification and profile property setting. According to the Segment integration documentation: "When you call Segment's identify API, Mixpanel will set the specified userId as the Mixpanel distinct_id. Any traits you provide in the call will be applied as profile properties for the targeted user in Mixpanel."The behavior you're experiencing, where user properties are being overwritten with each new identify call, is actually the expected behavior for Mixpanel. This is because Mixpanel's set operation for profile properties overwrites existing values. From the Mixpanel documentation on setting profile properties: "If a profile property already exist, if will be overwritten with the latest value provided in the method. If a profile property does not exist, it will be added to the profile."To avoid overwriting properties you want to preserve, you have a few options: 1. Use Segment's traits object carefully, only including properties you want to update or add.2. If you're using Mixpanel's JavaScript SDK directly alongside Segment, you can use the mixpanel.people.set_once() method for properties you want to set only if they don't already exist.3. You can also use Mixpanel's mixpanel.people.union() method to add values to a list property without overwriting the existing values.If you need more granular control over how properties are updated, you might need to adjust your implementation strategy or consider using Mixpanel's SDK directly for certain operations.For more detailed information on managing user profiles in Mixpanel, you can refer to the Mixpanel documentation on storing user profiles.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
kapa.ai The user_id as other properties are being overwritten every time there’s a new identify_call. This is not the expected behaviour. When checking the Users section it displays the last users with an identify call and in the Activity Feed all events are assigned to this user, regardless of whether this or any other user performed those events.
Let me check the knowledge base for you again. One moment! 📚
I apologize for the confusion in my previous response. You're right that this behavior is not expected, and it indicates a potential issue with your Segment to Mixpanel integration or ID management. Let's investigate this further based on the information provided in the knowledge sources.The behavior you're describing suggests a problem with user identification and event attribution. Here are a few potential causes and steps to investigate: 1. ID Management Issue:
There might be an issue with how user IDs are being managed. According to the Mixpanel documentation on ID management, it's crucial to properly identify users, especially when they transition from anonymous to authenticated states.2. Incorrect Implementation of identify call:
The problem you're experiencing could be due to an incorrect implementation of the identify function. As mentioned in the Mixpanel documentation on hot shard limits, there could be an issue where a static string is being passed instead of a unique user ID. For example: LBKSfunction authenticate_user(user_id){ mixpanel.identify('user_id'); mixpanel.track('user_authenticated'); }LBKSThis would cause all users to send events with the same ID value: 'user_id', which could explain why all events are being attributed to the last identified user.3. Segment Integration Configuration:
Check your Segment to Mixpanel integration settings. Make sure that the "Use Mixpanel People" setting is enabled in your Segment Settings UI, as mentioned in the Segment integration FAQ.To troubleshoot this issue: 1. Review your implementation of the identify call in Segment. Ensure you're passing a unique user ID for each user.2. Check the Mixpanel events in the Activity Feed. Look for the distinct_id property on the events. If they're all the same, it confirms the ID management issue.3. Verify that your Segment to Mixpanel integration is set up correctly, especially the settings related to user identification and profile creation.4. If possible, use Mixpanel's debugging tools or Segment's debugger to trace how user IDs are being sent and processed.If after checking these points you're still experiencing issues, it would be best to contact Mixpanel support with specific examples of the behavior you're seeing. They can provide more tailored assistance based on your exact implementation and data flow.Remember, proper user identification is crucial for accurate event attribution in Mixpanel. Always ensure that unique user IDs are being passed correctly from Segment to Mixpanel for each user.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
