Solutions

IP Geolocation for Ad Tech & Marketing

Target, localise, and protect campaigns with a privacy-first location signal — no cookies, no consent wall, resolved on the first impression.

Cookies are fading and consent walls block the rest. IP geolocation is the privacy-first location signal that still works — on the first impression, with no prompt. Target, localise, and measure campaigns by where the visitor actually is.


What ad tech and marketing teams do with it

Ordered from everyday targeting to advanced traffic protection.

Target campaigns by location

Read country, region, and city on request and serve the right campaign to the right geography — no cookies, no consent wall, works on the very first impression.

Example

Visitor → 203.0.113.x

city: Manchester · region: England → serves the UK-North creative set

Localise creative and landing pages

Match ad copy, currency, and landing-page language to the visitor's locale so the click-through experience feels native instead of generic.

Example

Visitor from Montréal → 24.200.x.x

country: Canada · currency: CAD → FR-CA creative + CAD pricing on the LP

Segment audiences and attribute by geo

Tag every event with country, region, and ASN so reporting, pacing, and attribution can slice performance by location and network without extra tracking.

Example

Click event → 85.90.x.x

country: Spain · asn_org: Telefónica → bucketed into ES / mobile-carrier segment

Enforce campaign eligibility and geo-fencing

Honour contractual, licensing, and regulatory boundaries by checking country and EU-status before a bid or placement fires — keep out-of-area spend from leaking.

Example

Bid request → 1.2.3.x

country: India · campaign is US/CA-only → suppress bid, no wasted spend

Filter invalid and fraudulent traffic

Datacentre ASNs and a country that contradicts the declared geo are classic bot and click-fraud signals. Use them to score traffic quality before it burns budget.

Example

Click → ASN: known hosting provider

datacentre origin + geo mismatch → flag as likely invalid traffic

The fields that do the work

Every one of these ships in the standard response — no add-ons, no tiers.

country / region / city Geo-targeting granularity down to the city
latitude / longitude Radius targeting and proximity campaigns
currency Localised pricing in creative and landing pages
connection (ASN / org) Carrier/network segmentation and IVT filtering
is_in_eu Consent and regional compliance gating

Common questions

Why use IP geolocation instead of cookies for targeting?

IP geolocation is a privacy-first signal that works on the first impression, needs no consent banner, and survives cookie deprecation. It gives country-to-city granularity from the request itself, making it one of the few scalable, non-intrusive location signals left in ad tech.

Is it accurate enough for city-level targeting?

Country and region are highly reliable; city is accurate for most consumer connections but can be coarser on mobile carriers and some infrastructure networks. For radius or proximity work, combine city with latitude/longitude and an accuracy_radius-aware fallback.

Can it help with ad fraud?

Yes, as one signal among several. A datacentre/hosting ASN or a location that contradicts the declared geo is a common indicator of bot or invalid traffic. It should feed a broader quality score rather than make a block decision alone.

Add location targeting in one request

Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. One call per impression, under 50ms median response.