According to their documentation, DAP is built on-top of Google Analytics, and also IP Anonymization is enabled by default. As a Google Analytics power-user, I happen to know two relevants facts: 1) Geography is inferred from IP Address 2) IP Anonymization happens before geo look-ups.

So, what's probably happening is that some IP address in Graceville happens to end in the octect 0. And a bunch of other high-volume addresses, when you drop their last octect because of IP Anonymization, look like the IP address from Graceville.

As a more general note, the accuracy of geography reports in GA are suspect to begin with (Amazon and Google only agree at the state level about 75% of the time), and with IP Anonymization enabled it takes a substantial nosedive.

I was wondering the same thing. The town has a total population of like 2200. I can’t find any data centers near there. Maybe it’s just a flaw in their metrics.

I’ve worked on systems in the past that had different levels of ip geolocation data precision. When the precision was low, they would pick the midpoint of the known area (maybe a whole state) to “fill in” more precise data (ex: the city). Since even “nowhere” is typically part of some town limits, we’d see otherwise tiny towns show up way too frequently.

My guess is that’s what’s happening here.

Case in point: https://theweek.com/articles/624040/how-internet-mapping-gli...

Graceville isn't really the midpoint of anywhere so I'd still be curious how it ended up being picked as the location.