Use case

IP Geolocation API for Ad Targeting & Segmentation

Serve the right creative to the right region — and keep spend off bot traffic — from a single lookup.

Good targeting starts with location. One IP lookup gives you country, region, and city for geo-targeted creative and segmentation — plus the network and anonymiser signals that keep paid delivery focused on real people, not datacentre bots.


Who uses it

The teams that lean on this most, in rough order of how often we see it.

The signals it uses

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

country / region / city Geo-target campaigns and segment audiences
connection (ASN / org / type) Filter invalid traffic from hosting / bot networks
security (isVpn / isTor) Exclude anonymised traffic from paid delivery
timezone Dayparting and send-time optimisation
is_in_eu EU consent and privacy-aware targeting

How different teams put it to work

The same lookup, applied to how each team targets and monetises.

Ad Tech

Geo-target creative and filter invalid traffic

Example

Impression → 3.120.x.x · type: hosting

datacentre origin → mark as IVT, don't bill the advertiser

See more Ad Tech use cases →
Media

Segment audiences for regional monetisation

Example

Pageview → 151.101.x.x

country: US · region: CA → West-Coast ad pod + local sponsor

See more Media use cases →

Common questions

How does IP geolocation improve ad targeting?

It lets you serve the right creative, language, and offer by country, region, and city — and schedule by local timezone — without any cookie or login. Combined with the connection and anonymiser signals, it also keeps spend focused on real audiences rather than bots.

How does it help with invalid-traffic (IVT) filtering?

A large share of invalid traffic originates from hosting and datacentre networks rather than residential ISPs. The connection block flags that origin, and the VPN/Tor flags catch common anonymisers, so you can exclude the obvious invalid impressions before they're billed.

Is IP-based targeting privacy-friendly?

IP geolocation infers coarse location (country, region, city) from the network address without a permission prompt, cookie, or device identifier. Use the is_in_eu flag to apply consent and privacy rules where they're required, and keep targeting at the aggregate geographic level.

Target by location in one request

Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. Bulk endpoint available for enriching event streams.