You open a Mixpanel report to analyze where your users are coming from. Most events have location information, but some show (not set) for City, Region, or Country.
Why does this happen? And more importantly, how do you fix it?
This is a question that comes up in the Mixpanel community. Users sometimes notice that a significant percentage of their events are missing city or other geographic properties, even when the events themselves are being tracked successfully.
The good news is that missing location properties don’t necessarily mean your event tracking is broken. Mixpanel can receive an event successfully without being able to determine its geographic location.
Let’s look at why this happens and what you can do about it.
How Does Mixpanel Determine User Location?
Mixpanel can use IP-based geolocation to estimate where an event originated.
When an event is sent, Mixpanel may use the available IP address to derive geographic properties such as:
- City
- Region or state
- Country
For example, someone visiting your website from Seattle might generate an event with location properties indicating Seattle, Washington, United States.
However, Mixpanel does not automatically collect GPS coordinates. IP-based location is an estimate, and its accuracy depends on the IP address available and the geolocation service’s ability to map it.
This distinction is important when troubleshooting missing or inaccurate location data.
1. Mixpanel Cannot Determine a Location From the IP Address
One possible reason for missing location properties is that the IP address cannot be reliably mapped to a city or region.
This can happen with certain network configurations, VPNs, proxies, or IP addresses that lack sufficiently precise geographic information.
You may therefore see a country value but no city value, or an event without usable geographic properties.
What to check:
Open Mixpanel’s Events view and inspect several recent events with missing locations. Compare them with events where location is populated.
Check whether the missing values are concentrated among particular browsers, platforms, or traffic sources.
If the issue occurs only for certain users, network-related differences may be contributing to it.
2. Events Are Being Sent From Your Server Instead of the Browser
This is an important issue for companies using server-side tracking.
Suppose a user in Seattle performs an action on your website. Instead of sending the event directly to Mixpanel, your application sends it to your backend, which forwards the event.
If Mixpanel uses the backend server’s IP address, the location could reflect the server’s data center rather than the user’s location.
In some cases, location may be missing altogether.
What to check:
Determine how the affected events reach Mixpanel:
- Mixpanel’s browser SDK
- A backend SDK
- A customer data platform such as Segment
- A custom API integration
For server-side implementations, review how the original client IP address is handled and whether geolocation is intentionally disabled.
Do not assume that an IP address is being forwarded just because the original action occurred in a browser.
3. Geolocation Has Been Disabled
Some implementations intentionally disable IP-based geolocation for privacy reasons.
For example, an organization may configure its tracking pipeline to prevent IP addresses from being used to derive location.
This may be an appropriate decision based on the organization’s privacy requirements.
However, it can also explain why geographic properties are missing.
What to check:
Review the Mixpanel SDK configuration, server-side event payloads, and any intermediary tools.
Look for settings or values that explicitly suppress IP-based geolocation.
If geolocation is disabled intentionally, missing location properties are expected behavior rather than a tracking error.
Before changing these settings, confirm that collecting location information is consistent with your organization’s privacy policies and consent requirements.
4. Different Events Use Different Tracking Methods
You might be collecting some events using the Mixpanel browser SDK and others through a backend service.
For example:
| Event | Tracking method |
|---|---|
| Page Viewed | Browser SDK |
| Product Viewed | Browser SDK |
| Subscription Renewed | Backend |
| Payment Completed | Backend |
These events can have different location coverage because their tracking methods handle IP addresses differently.
If most of your browser events contain city information but backend events don’t, the difference may be explained by the implementation rather than the users themselves.
What to check:
Compare the percentage of events missing location properties for each event name.
Then group those events by their collection method.
This can help you determine whether the problem is specific to one SDK, integration, or tracking pipeline.
5. The User Is Behind a VPN or Proxy
IP-based geolocation is not always an accurate representation of a user’s physical location.
A user in Seattle might connect through a VPN server in California. Mixpanel may associate the event with California instead of Washington.
In other cases, the IP address may not provide sufficient information to determine a city.
This means location data can be present but inaccurate, or partially missing.
What to check:
Look for unusual concentrations of events in particular cities or regions.
If your data shows a large number of users in a location that doesn’t make sense for your business, investigate whether those events are coming through a proxy, VPN, or server-side integration.
Avoid treating IP-derived city data as a precise measurement of users’ physical locations.
6. You’re Looking at a Property That Was Never Collected
Another possibility is that the property you are analyzing isn’t present on the event.
For example, you might have a custom property named user_city that your application populates separately from Mixpanel’s automatic geolocation properties.
Even if Mixpanel determines the event’s location, that doesn’t necessarily mean your custom property will have a value.
Similarly, event properties and user profile properties serve different purposes. A location value on a user profile doesn’t automatically mean that the same value was included in every historical event.
What to check:
Inspect the raw event properties and confirm the exact property name you’re using in the report.
Determine whether it is an automatically derived geographic property, a custom event property, or a user profile property.
This simple check can prevent unnecessary changes to an otherwise working tracking implementation.
How to Troubleshoot Missing Location Properties in Mixpanel
If you’re seeing a large percentage of events without location data, I recommend following this process.
Step 1: Identify Which Location Properties Are Missing
Start by checking whether City, Region, and Country are all missing or whether the problem affects only one property.
Missing city information with a populated country value is a different situation from having no geographic information at all.
Step 2: Find the Affected Events
Use an Insights report to break down event activity by the relevant location property.
Look at which event types have the largest share of missing values.
For example, if 40% of Payment Completed events are missing a city but only 5% of Product Viewed events are missing it, investigate the payment tracking implementation first.
Step 3: Inspect Raw Event Data
Open the Events view and examine individual event payloads.
Check whether the expected geographic properties exist and whether they contain values.
Also look for differences between affected and unaffected events.
Step 4: Review the Tracking Implementation
Determine whether the affected events are sent from the browser, a mobile SDK, a backend, or an intermediary platform.
Review the relevant SDK configuration and IP-handling behavior.
For server-side events, verify whether Mixpanel receives the information needed for the intended geolocation behavior.
Step 5: Test With a New Event
Generate a test event using the affected tracking method.
Inspect the event in Mixpanel and verify whether location properties appear as expected.
If possible, compare the results with an event sent using a different collection method.
This can help isolate whether the issue is related to the event pipeline or the network environment.
Step 6: Validate the Results
After making any configuration changes, send fresh test events and compare location coverage.
Remember that fixing your implementation will not necessarily populate missing location properties on historical events.
Should Every Mixpanel Event Have Location Properties?
Not necessarily.
There are legitimate reasons why location data may be unavailable or intentionally excluded.
For example, an application might collect server-generated events that aren’t associated with a particular user location.
Or an organization might decide not to collect IP-derived geographic information for privacy reasons.
The important question isn’t whether every event has a city value.
It’s whether your implementation is collecting the information you actually need for analysis.
If geographic analysis is important to your business, you should understand how location properties are generated and monitor their completeness.
If geographic location isn’t important, missing city values may not require any action.
Final Thoughts
When Mixpanel events are missing location properties, don’t immediately assume that Mixpanel is failing to track events.
Start by checking how the events are collected, whether geolocation is enabled, and which properties are actually available.
In many cases, the differences come down to how the data is sent rather than a problem with the event itself.
A reliable analytics implementation isn’t just about collecting events. It’s about making sure the properties associated with those events are accurate, consistent, and useful for analysis.
Need Help Troubleshooting Your Mixpanel Implementation?
At Optizent, we help companies implement, audit, and troubleshoot Mixpanel and other analytics platforms.
Whether you’re dealing with missing event properties, inconsistent tracking, or data quality issues, we can help you identify the cause and improve the reliability of your analytics.
Contact Optizent to discuss your Mixpanel implementation.
GET EXPERT ANALYTICS HELP
Need help getting reliable answers from Mixpanel?
Tell us about your tracking, funnels, retention, or reporting challenge. Optizent can help you implement, audit, and use Mixpanel with confidence.
We will use these details to respond to your request. Please do not include passwords, account access, or customer data.
