If you don't see data for some of your application’s users on the world map, it may be because those users have private IP addresses. You can map such internal IP addresses to real geographic locations at Settings > Web and mobile monitoring > Map IP addresses to locations and thereby make these users visible on the map. You can even override settings for real client IP addresses if necessary for mapping purposes. Click Set geographic region for IP to map individual private IP addresses to geographic locations.
If you have numerous custom IP addresses to import, go to Settings > Web and mobile monitoring > Geographic locations, and click Import geographic regions from a CSV file, then select the file containing the data to import. You can also use this to import or update multiple data center mappings from a CSV file. For a custom mapping on a city that you want to import via a CSV file, be aware that you need to provide coordinates and country/region information.
A sample CSV file is available on the settings page for download. The file includes complete instructions, CSV file formatting requirements, optional fields, and examples. Enter either one single IP address or a range, for example, from
188.8.131.52 for one location or you can also use the CIDR notation with an IP address and a
/ followed by the subnet mask, for example:
184.108.40.206/26. The subnet mask attribute value is the number of non-zero bits as used in the CIDR notation. Click more to expand the help text at the top of the page, then click the sample CSV file link to download the sample file.
Granularity of regional performance analysis increases as the number of detected user requests goes up in a specific region (continent, country, state, or city). You can even override auto-detected IP addresses if necessary to improve mapping accuracy.