we send out events through Segment, and a lot of times that ends up with users' locations getting set to Boardman OR (which is where the Segment servers are located). I'm guessing this is a fallback behavior in Mixpanel when it doesn't have location data in the event payload, it looks at where the request itself came from. Does anyone know a quick way to avoid this behavior, every few months I have to explain to someone on my team that no, we don't have some kind of super-user hub in Boardman OR, it's just a data error
Hey Vlad! It's definitely not ideal to have your team think you have a ton of users in Boardman OR. To turn off the geolocation, you can pass context.ip as 0 for all track, alias, and identify calls.
The Segment Documentation has more information about this process. I've also copied the relevant text below: > To avoid having any IP address sent to Mixpanel and by doing so, turn off geo-location for server-side users, pass the context.ip as 0.
Hereβs a python example:
analytics.track(user_id=user.id,
event='Ignore My IP', context={
'ip': 0
})
```LBKSLBKS> Provide `context.ip` to all your [`identify`](https://segment.com/docs/connections/spec/identify/), [`track`](https://segment.com/docs/connections/spec/track/), and [`alias`](https://segment.com/docs/connections/spec/alias/) calls to make sure Mixpanel doesnβt geo-locate your users.
Β
Mind giving that a try?
