IPGeolocation

Your new players are quitting after a few matches, beaten by cheaters you already banned.

That is the problem with bans in online games: banning an account does not always stop the person behind it.

A cheater ruins ranked matches, gets banned, and creates a new account. A smurf beats beginners on another account. A bot farms in-game currency, gets blocked, and comes back again.

Most of them return using a new IP address. Many hide behind a VPN, proxy, or residential proxy, so they can look like normal players.

Your system sees a new account.
But your real players see the same problem again.

Fair matches get worse. The game economy fills with farmed currency. New players get frustrated. And the players you want to keep are often the first to leave.

The IP Security API adds a signal your account checks are missing: the connection itself.

For any IP, it gives you a risk score and tells you whether it is a VPN, proxy, residential proxy, Tor exit or a datacenter, with the provider name and a confidence level, and it flags residential proxies even when the address looks like an ordinary home.

With that, you can challenge high-risk signups and logins so bans actually stick, flag likely smurfs and ban evaders by the network they keep coming back on, and slow the bots before they can farm and sell.

How are you stopping banned players from returning today?

Take a look: https://ipgeolocation.io/ip-security-api.html

Leads land in your CRM with no location on them, so every one gets slower follow-up and a guess at who should own it, even though the IP address came in with the answer.

IPGeolocation.io is now integrated with viaSocket, so you can fix that with no code. Location, timezone and security signals become ready-made steps you drop into a workflow. You connect your API key once, pick a trigger like a new form entry or signup, add an IPGeolocation.io step, map the IP, and send the result on to your CRM, sheet or email tool.

A few things teams build with it:

- Turn form submissions into enriched CRM leads, with the IP filling in city, region and country and setting lead source, and no extra fields to ask
- Flag risky signups by screening the IP for VPN, proxy and bot activity before they reach your team
- Branch a workflow by region so each location gets the right follow-up or owner

How are you adding location to your workflows today?

Connect it here: https://ipgeolocation.io/documentation/viasocket-integration

Here is an easy way to get fooled by your own traffic. A bot shows up calling itself Googlebot, your rules see a trusted crawler, and you wave it straight through. The problem is that a user agent is just a piece of text, and anything can put a search engine's name in it.

So scrapers and bad bots wear a trusted name to skip your bot rules, crawl your content freely, and quietly skew your analytics. The one thing they cannot fake is where their IP actually resolves.

The IP Location API returns the hostname behind any IP, from a reverse DNS lookup. A real crawler resolves to the search engine's own domain. An impostor resolves to a datacenter, or to nothing at all. With that, you can verify good bots before you trust them, unmask traffic pretending to be a known crawler, and identify the host and provider behind the IPs in your logs.

How are you verifying the bots you let through today?

Take a look: https://ipgeolocation.io/ip-location-api.html

You buy US media by market, then measure it on the wrong map.

Your TV and streaming are planned and measured by market, but your digital targeting and your analytics work in cities and states. US media runs on Designated Market Areas, the 210 regions that reflect how the country actually watches, and those markets do not line up with state or city borders. A single metro can cross two states, and one state can hold several markets.

So matching your site data back to your media plan turns into manual lookups and guesswork.

The IP Geolocation API puts it all on one map. For a US IP, it returns the Designated Market Area your media is bought against, and it goes finer when you need it, down to city and postal code, plus the connection type so you can separate mobile from broadband.

That means you can target and suppress campaigns by the exact markets your TV is running in, drop to city and ZIP for hyper-local offers, report results by market right next to the buy, and treat mobile and broadband differently.

How are you matching web traffic to media markets today?

More on the IP Geolocation API: https://ipgeolocation.io/ip-location-api.html