Identifying Event Properties Limited to Segment Source Name Only?
For my identify event I’m only getting the property segment_source_name and no other property associated to the event, for example token, email, roles, etc... Why is this?
For my identify event I’m only getting the property segment_source_name and no other property associated to the event, for example token, email, roles, etc... Why is this?
Hi Juan C., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
If your identify event in Mixpanel is only showing the property segment_source_name and not other expected properties like token, email, or roles, there are a few likely reasons based on the knowledge sources: 1. Segment Mapping and Preset Actions:
Segment’s Actions framework allows you to configure how data is sent to Mixpanel. For identify calls, Segment should map user traits (like email, roles, etc.) to Mixpanel user properties. If these mappings are not configured correctly in the Segment destination settings, only default or minimal properties (like segment_source_name) may be sent. Check your Segment destination “Mappings” tab to ensure all desired properties are mapped to Mixpanel fields. The token property is required for Mixpanel ingestion, but it is not visible in the UI—it is used internally by Mixpanel and not shown as an event property in reports [Segment Data Mapping].2. Segment Identify Call Content:
The properties that appear in Mixpanel depend on what is included in the Segment analytics.identify() call. If only segment_source_name is being sent from Segment, then only that property will appear in Mixpanel. Make sure your Segment identify calls include all the desired user traits (e.g., email, roles) as part of the payload [Segment Data Mapping].3. Mixpanel People/Profile Settings (Classic Destination):
If you are using the Classic Segment destination, note that Segment does not track Mixpanel People (user profiles) by default. You must enable this in your Segment settings. If not enabled, user properties like email or roles may not be set in Mixpanel [Segment FAQ].4. Hidden Properties in Lexicon:
It’s also possible that some properties are hidden in Mixpanel’s Lexicon, which would prevent them from appearing in the UI, even if they are being sent [Check for Hidden Events and Properties].Summary:
Check your Segment identify call payload, ensure your Segment-to-Mixpanel mappings are correct, and verify that Mixpanel People is enabled if using the Classic destination. Also, review Mixpanel Lexicon to ensure properties are not hidden. If these are all set up correctly, you should see all expected properties in your identify events.If you need more specific troubleshooting, please provide the exact Segment identify call payload and your Segment destination mapping configuration.
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.
Let me check the knowledge base for you again. One moment! 📚
To verify that Mixpanel People is enabled when using the Classic Segment destination, you need to check your Segment settings: - Go to your Segment workspace and open the settings for your Mixpanel destination. - Look for the setting called “Use Mixpanel People.” - Make sure this setting is enabled. If it is not enabled, Segment will not send user profile data (Mixpanel People) to Mixpanel by default.This is explicitly mentioned in the knowledge source: > No user profile data in Mixpanel (Classic destination only): Segment does not track Mixpanel People by default. This is a setting you need to enable in your Segment settings. To enable Mixpanel People, change the “Use Mixpanel People” setting in your Segment Settings UI Segment FAQ.If you do not see this option, you may be using the Actions destination, which always sends user profile data with identify calls.
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.
Let me check the knowledge base for you again. One moment! 📚
If you are using the Segment Actions destination, user traits sent in the identify call (such as email, roles, etc.) should be mapped to Mixpanel user profile properties. However, these properties will not appear as properties on the "identify" event itself in Mixpanel—they are set on the user profile, not as event properties.Here’s how it works according to the knowledge sources: - The Actions destination maps Segment’s identify calls to Mixpanel’s "Identify User" and "Set Profile Properties" actions. The user traits (like email, roles, etc.) are applied to the user’s profile in Mixpanel, not as properties of the identify event (Data Mapping).
- In Mixpanel, you can view these properties by looking at the User Profile for the user (using the distinct_id), not by inspecting the identify event in the Events view (User Profiles FAQ).What to do:
- Go to the User Profiles section in Mixpanel.
- Search for the user by their distinct_id (which should match the userId from Segment).
- You should see the properties (like email, roles, etc.) set on the user profile.If you want to see these properties as part of an event, you need to include them in a track call’s properties, not just in the identify call.Summary:
With the Actions destination, user traits from identify are stored on the user profile, not as event properties. This is expected behavior and aligns with how the integration is designed (Data Mapping; User Profiles FAQ).
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.
Let me check the knowledge base for you again. One moment! 📚
If you are using the Segment Actions destination and you see that user properties (such as email, roles, etc.) are not set on the user profile in Mixpanel, there are a few possible reasons based on the knowledge sources: 1. Check the Segment Identify Call Payload:
Ensure that your analytics.identify() call in Segment actually includes the user traits you expect (e.g., email, roles). If these are not present in the payload, they will not be sent to Mixpanel (Data Mapping).2. Review Segment Destination Mappings:
In the Segment UI, go to your Mixpanel Actions destination and check the “Mappings” tab. Make sure that the traits you want (like email, roles) are mapped to the correct Mixpanel user profile properties. If the mapping is missing or incorrect, the properties will not be set in Mixpanel (Data Mapping).3. Reserved Properties and Mapping Issues:
The property id in Segment is reserved and mapped to distinct_id in Mixpanel. Avoid using id for other purposes, as it may cause mapping issues (Data Mapping).4. Timing and Propagation:
Sometimes, there may be a short delay before properties appear on the user profile in Mixpanel. However, this is usually minimal with the Actions destination.If you have confirmed that your identify call includes the correct traits and your mappings are set up properly, but the properties are still not appearing, the knowledge sources do not provide further troubleshooting steps for this specific scenario. In that case, you may need to reach out to Segment or Mixpanel support for more detailed investigation.Summary:
Double-check your Segment identify call payload and the property mappings in the Segment Actions destination. If everything appears correct and the issue persists, the knowledge sources do not provide additional guidance for this situation.
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.
Let me check the knowledge base for you again. One moment! 📚
Based on the knowledge sources, it is not necessary to send the user_id again in the traits object of a Segment identify call. The userId parameter in the Segment identify call is mapped to Mixpanel’s distinct_id and is used as the unique identifier for the user. The user traits (such as email, roles, etc.) are sent as part of the traits object and are mapped to Mixpanel user profile properties.The mapping is described as follows: > 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 (Segment Integration Overview).Therefore, you only need to provide the user’s unique ID in the userId field of the identify call, and not again in the traits object.
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 does this seems correct? Destination field Value IP Address 125.22.210.82 User ID bc5cad93-1635-4ae6-9dc0-0bf5ac124651 Anonymous ID 62c89a28-0a86-45f6-9905-c17617922a63 User Properties { “token”: “Sp9s2f7ZIbLEkQVqAT84V”, “email”: “pallavi.kumari@ext.diffuse.ly”, “roles”: “internal”, “user_name”: “Pallavi Kumari”, “company_public_id”: “d3441dff-2cbb-4e61-8097-24f7828b40c7", “company_name”: “CarCutter” }