Market research
Gather localized content, reviews and trends in any market.
Use case · E-commerce & pricing
Track competitor prices, stock and promotions exactly as shoppers in each market see them. Collect from local residential IPs on protected marketplaces and from fast datacenter IPs everywhere else.
The challenge
The problems every team in e-commerce & pricing runs into sooner or later.
Retailers localize prices, currencies, taxes, shipping and promotions. Collect from a single location and you compare yourself against numbers that shoppers in your own market never see.
Large stores rate-limit and fingerprint visitors, then serve CAPTCHAs or decoy pages to suspicious traffic. A blocked request is a missing price point, and a wrong price is worse.
Prices in competitive categories move several times a day. Checking thousands of SKUs every few hours needs high concurrency and a predictable cost per check, not a pool that slows down at peak.
The solution
Settings you control from the username, with no extra tooling or separate endpoints.
Set the country with -country-de or narrow it to a city. Each request returns the localized price, currency and delivery promise that shoppers in that market actually get.
Spread catalog checks across 55M+ residential IPs. Every request can leave from a new address, so per-IP limits never pile up on one connection during a large run.
Some prices only appear after you choose a delivery location or open the cart. Hold one IP for up to 120 minutes so cookies and IP stay consistent through the whole check.
Run easy targets on shared datacenter IPs and protected ones on residential from $0.74/GB. Sub-users with their own traffic limits keep each client or category within budget.
Recommended
Start with the first one. Most teams add a second pool as their targets grow.
Get started
List product URLs or SKUs with the markets you compete in. Group them by retailer, because each target may need its own proxy pool and request rate.
Request each page with the country, and the city if needed, set in the username. Read the price from structured data where the page provides it, since it survives most redesigns.
Store every observation with a timestamp, compare it with the last run and alert on price drops, stock-outs or new sellers. Keep the raw response for disputed cases.
Best practices for e-commerce & pricing
# pip install requests beautifulsoup4
import csv
import json
from datetime import datetime, timezone
import requests
from bs4 import BeautifulSoup
# Replace with the product pages you track, mapped to the shopper's country
WATCHLIST = {
"https://shop.example.com/de/p/espresso-machine-x1": "de",
"https://shop.example.com/us/p/espresso-machine-x1": "us",
}
HEADERS = {"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) "
"AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0 Safari/537.36"}
def product_offer(html):
"""Return (name, price, currency) from the page's JSON-LD Product data."""
soup = BeautifulSoup(html, "html.parser")
for tag in soup.find_all("script", type="application/ld+json"):
try:
data = json.loads(tag.string or "")
except json.JSONDecodeError:
continue
items = data.get("@graph", [data]) if isinstance(data, dict) else data
for item in items:
if isinstance(item, dict) and "Product" in str(item.get("@type")):
offer = item.get("offers") or {}
if isinstance(offer, list):
offer = offer[0] if offer else {}
price = offer.get("price") or offer.get("lowPrice")
return item.get("name"), price, offer.get("priceCurrency")
return None, None, None
with open("prices.csv", "a", newline="", encoding="utf-8") as f:
writer = csv.writer(f)
for url, country in WATCHLIST.items():
proxy = f"http://USERNAME-country-{country}:PASSWORD@gw.proxonym.com:8000"
r = requests.get(url, headers=HEADERS, timeout=30,
proxies={"http": proxy, "https": proxy})
name, price, currency = product_offer(r.text)
writer.writerow([datetime.now(timezone.utc).isoformat(), country,
url, r.status_code, name, price, currency])
print(country, r.status_code, price, currency, name)FAQ
Still unsure? The help center answers billing, setup and account questions.
Open the help centerResidential proxies are the safe default for large marketplaces and retailers with bot protection. Shared datacenter proxies cost less per request and work well on smaller stores and brand sites. Many teams route each domain to the cheapest pool that still returns clean data and only escalate to residential where they have to.
Yes, where pricing depends on location. Add -city- or -state- to your username to exit from that area. Some retailers also price by a delivery ZIP code stored in cookies: set that location on the site inside a sticky session so the cookie and the IP stay together for the whole check.
As often as your plan and the target allow. We set no concurrency limit, and the burst limit is around 10,000 requests per second per account. In practice, set the frequency per category, hourly for fast movers and daily for the long tail, and keep request rates polite.
Fetch only the data you need: product APIs or JSON-LD instead of full renders, no images or fonts, compressed responses. Use datacenter IPs where they work and residential only where needed. Sub-users with traffic limits keep each client, category or environment inside a fixed GB budget.
Prices on public product pages are generally treated as public information, and price monitoring is common practice in retail. Respect each site's terms, stay out of logged-in areas you are not entitled to, avoid overloading servers and consult a lawyer if you operate in a regulated market. Our acceptable use policy applies to all traffic.
Platforms
Platform guides with targeting tips, ready-to-run code and the proxy types that work best on each site.
Related
Teams often combine these with e-commerce & pricing on the same account.
Gather localized content, reviews and trends in any market.
Find counterfeits and phishing hidden behind geo-blocks.
Collect public data at scale without bans, CAPTCHAs or rate limits.
Pick a plan, pay with crypto and send your first request through Proxonym in minutes.