Mixpanel Geolocation Troubleshoot #7246
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current: If an ip property is passed to Mixpanel, the value will be interpreted as the IP address of the request and therefore automatically parsed into Mixpanel geolocation properties (City, Country, Region).
Add the following sentence afterward: Segment sends data to Mixpanel as it receives it. If location traits are not included in an identify call, Segment doesn't add or infer them, it simply forwards the data as is to Mixpanel. Therefore, the resetting of location data to Dublin, Ireland is likely happening on Mixpanel's side.
To maintain the accuracy of location data in Mixpanel, you should include the $city, $country_code, and $region traits in all identify calls, not just the initial one. This is in line with Mixpanel's server-side best practices, which recommend sending geolocation data with server-side events to ensure accurate location tracking.
Merge timing
Related issues (optional)