Track competitor and marketplace prices from any market.
Localized residential IPs return the exact prices a shopper in that country sees, so your feeds stay accurate for repricing and MAP enforcement. Schedule checks across cities and carriers to catch geo-specific promotions.
Why this needs proxies
Sites vary what they return based on where the request appears to come from, and they rate-limit or block addresses that ask too often. Both problems have the same fix: exit from real consumer IPs in the right places, and spread the load so no single address looks unusual. That is the whole job a proxy does here.
The reason residential IPs succeed where datacenter ones fail is classification by ASN. Hosting networks can be challenged wholesale with a single rule; consumer ISP networks cannot, because doing so would block real customers.
Recommended products
| Product | Price |
|---|---|
| Budget Residential | $1.75/GB |
| Rotating Datacenter | $1.00/GB |
| Premium Residential | $2.75/GB |
Start with the cheapest option your target tolerates and move up only when it blocks you. Concurrent sessions are unlimited on every plan and country targeting is included in the price. Full tiers are on our pricing page.
How this works in practice
- Pick the cheapest product that works. Test the target on rotating datacenter first; move to residential only when you are actually refused.
- Choose the exit country deliberately. The data you get back is the data that country sees, so record which exit produced every record.
- Decide rotation vs sticky. Per-request rotation suits stateless collection; anything with a login or a multi-step flow needs one IP held for the whole session.
- Pace against the target, not your budget. Back off on 429 responses instead of rotating past them, and randomise intervals rather than hitting on the hour.
Common mistakes
- Rotating inside a session. The single most common cause of empty results and flagged accounts.
- Mismatched signals. An exit in one country with an Accept-Language header for another creates a visitor that does not exist, and some sites respond to the contradiction.
- Paying for residential too early. Plenty of targets never check, and the gap between $1.00/GB and $2.75/GB is substantial at volume.
- Not recording the exit. Data without its point of observation cannot be compared across markets.
Sizing your bandwidth
Work from page weight rather than guesswork. A page averaging 250 KB across 100,000 requests is roughly 25 GB. JSON APIs are far lighter, often a few kilobytes per call, while anything rendered in a headless browser pulls images and scripts too and can be several times heavier. Start at 1 GB, measure your actual average, then buy the package that matches.
Getting set up
Every product speaks HTTP(S) and SOCKS5, so this is a one-line change in most stacks. Credentials are assembled from a variable below rather than pasted inline, because a literal user:pass@host string in page copy can be rewritten by email-obfuscation filters.
import requests
endpoint = "geo.spyderproxy.com:12321"
creds = "USERNAME:PASSWORD"
proxy = f"http://{creds}@{endpoint}"
r = requests.get(
"https://example.com",
proxies={"http": proxy, "https": proxy},
timeout=30,
)
print(r.status_code)Confirm your exit is landing where you expect with the IP lookup tool before starting a long run. Bandwidth products begin at 1 GB, so you can validate for under $2.
Frequently Asked Questions
Why do I need proxies to monitor prices?
Retailers serve different prices by geography and personalise by visitor history. Requesting from one datacenter IP gets you one distorted view, and gets that IP blocked within a few hundred requests. Residential IPs in each target market return the price a real local shopper sees.
Which proxy type suits price monitoring?
Budget Residential at $1.75/GB handles most retail targets. Move to Premium Residential at $2.75/GB when you need city-level targeting or 8-hour sticky sessions to hold a cart or a logged-in state.
How often can I check prices without getting blocked?
With rotating residential IPs the practical limit is your bandwidth, not the target's patience, because no single IP accumulates a suspicious request history. Most teams run hourly checks on fast-moving SKUs and daily on the long tail. Randomise intervals rather than hitting exactly on the hour.
Can I monitor prices in specific cities?
Yes. Premium Residential supports country, state and city targeting, which matters for grocery, fuel and marketplace pricing where the delta between two metros in the same country can be significant.
Does this work for MAP enforcement?
Yes, and it is one of the most common uses. Localized IPs give you defensible evidence of what an unauthorised seller displayed in a given market at a given time. See our guide to MAP monitoring for how to structure the audit trail.