ProxyNomad / Use cases
What people route through us.
Five jobs, described the way they actually run: which proxy type, which session pattern, and the mistakes that show up as invoices. If your job is not here, it is probably still one of these wearing a different name.
01 · Web scraping
Collection that survives contact with the target.
The pattern that works is tiered: every URL hits the datacenter pool first, and only responses that come back blocked retry through residential. Most targets never trigger the second tier, so the blended rate lands near $0.60/GB while the success rate looks residential. One credential set covers both gateways; the tier switch is a port number in your retry logic.
The mistake that costs the most is concurrency without pacing: a thousand workers through one city pool reads as an event, and targets respond to events. Ramp up, spread targeting as wide as the job allows, and treat a rising block rate as a signal to slow down before it becomes a reason to move up a price tier.
- Type
- Datacenter first, residential on block
- Sessions
- Rotating, per request
- Targeting
- As broad as the data allows
- Watch for
- Block-rate creep; it compounds quietly
02 · Price intelligence
The price a real shopper sees.
Retailers price by geography, and increasingly by who seems to be asking. A datacenter exit gets the generic price or the block page; a residential exit in the right city gets what the local customer gets, which is the entire dataset. City targeting matters here more than anywhere: national averages hide exactly the spread you are being paid to find.
Use short sticky sessions per store visit: land, load the product, read the price as one identity, rotate. Carts and checkouts are where dynamic pricing concentrates; if your pipeline needs basket-level prices, hold the session for the whole basket and never reuse it across stores. And collect at retail-shaped hours in the target's timezone: a price snapshot taken when no human shops is a snapshot of the wrong regime.
- Type
- Residential, city-targeted
- Sessions
- Sticky per store visit, minutes not hours
- Targeting
country+city, one per market- Watch for
- Geo-default prices polluting the series
03 · SEO & SERP monitoring
Rankings from where the searcher stands.
Search results are localized to the query's origin, so rank tracking is only as honest as its exit. Residential exits pinned per city give you the results page your client's customer sees in Turin or Denver, not the datacenter-flavored one served to obvious automation. Rotate per query: search engines key personalization and rate logic to session continuity you do not want.
Volume math is friendly: a results page fetched as bare HTML is tens of kilobytes, so a serious keyword set across a dozen cities runs in single-digit gigabytes a month. This is the rare job where the good proxy type is also the cheap line on the invoice. Spend the savings on query depth, not on a bigger pool than the job needs.
- Type
- Residential
- Sessions
- Rotating, one query per exit
- Targeting
cityper tracked market- Watch for
- Consent walls and empty 200s parsed as data
04 · Ad verification
See the campaign the audience sees.
You cannot audit a geo-targeted campaign from an office IP: the ad server has already decided you are not the audience. Verification means arriving as the buyer's segment arrives, residential exits in the campaign's cities, or mobile exits on the right carrier when the buy is in-app or carrier-targeted. ASN targeting earns its keep here.
Fresh identity per check, always: sticky sessions accumulate frequency caps and retargeting state, and by the third impression you are measuring your own contamination. Screenshot and log what actually rendered, placement, creative, landing URL, because the disputes this work exists to settle are settled by evidence, not by a dashboard export.
- Type
- Residential; mobile for in-app
- Sessions
- Rotating, fresh identity per check
- Targeting
city+asnto match the media buy- Watch for
- Retargeting state polluting your sample
05 · Lead data enrichment
Firmographics at a sustainable pace.
Enrichment traffic is many small reads across many public sources: registries, directories, company sites, news. The economics favor the tiered pattern, datacenter for the long tail that does not resist, residential for the handful of sources that do, and the volumes are small enough that proxy spend stays a rounding error next to the value of a clean record.
What matters here is rate; the IP class is secondary. Public sources tolerate polite, spread-out collection for years and shut down floods in a week. Pace per source, cache aggressively so you never fetch a page twice, and keep provenance on every field: enriched data gets challenged, and the record that knows where it came from is the one that survives review. What may be collected at all is covered in our acceptable use policy; it draws real lines and we hold customers to them.
- Type
- Datacenter, residential for resistant sources
- Sessions
- Rotating, low and steady
- Targeting
countryof the registry or directory- Watch for
- Per-source pacing; floods burn sources for good
Your job is not exotic. Its tuning is.
Send the target and the shape of the job; we will suggest the setup we would run ourselves, at the price we would pay.