Best Practices for Managing User Location in Server-Side Tracking

What is the best approach to managing location-related user profile properties in server-side tracking? We currently use both client-side SDK implementation and server-side tracking. However, we have noticed that when data is processed on the server, it overrides the geo-location properties of the user profile with the location of our data center instead of the user's actual location. For example, at soulknightapk.com, ensuring accurate user location data is crucial for personalization, tracking player behavior, and optimizing user experience. However, server-side tracking sometimes replaces user location with the data center’s location, leading to inaccurate analytics. How can we ensure that the correct user location is maintained in our tracking system while using server-side tracking?