Skip to content

Proxies for Price Monitoring: Competitor Prices by Country and City

Collect competitor prices from real household IPs in every market you sell to.

Why price monitoring needs proxies

The price you see depends on where you look from. Retailers can set prices and stock per region — Google Merchant Center, for one, lets merchants override price and availability by state or postal code for shoppers there — so a check from your office shows one region's numbers.

Retail sites cap requests per IP, answering HTTP 429 when you go over, and they can block or challenge whole countries or hosting networks. A tracker on one server IP ends up collecting rate-limit pages, challenge pages or another country's store.

Rotating residential traffic is billed per GB, not per IP. Adding a market costs nothing until you download its pages, so the cost follows page weight — fetch product JSON or bare HTML instead of full pages with images.

Recommended price monitoring setup

Scroll horizontally with the arrow keys to read all content.

Recommended price monitoring setup
CriterionChooseWhy
ProductRotating residential proxyHousehold IPs in the market you monitor, billed per GB
LineBudget, US$1.50/GB (US$1.35/GB at 100 GB)Lowest per-GB price; Premium (US$5.00/GB) lets you choose the home ISP
Exit modeChoose region / sticky IP, one proxy per marketGlobal rotation has no fixed country, so prices from different markets would mix
Country and cityThe shopper's country; add State or City where prices differ inside itRegional prices exist below country level
ProtocolHTTPWorks in requests, httpx, Scrapy and browsers
Fresh IPRotate in My assets, or generate another proxyA sticky session holds its exit until you change it

The button below opens Rotating Residential Proxies with the AI and automation use case. Switch Line to Budget for US$1.50/GB, then generate one proxy per market.

Which Proxy302 proxy to buy

Scroll horizontally with the arrow keys to read all content.

Which Proxy302 proxy to buy
CriterionStatic ISPRotating residentialDatacenter
What you getA dedicated home-broadband IP that stays yours for the whole termReal household IPs: rotating exits, or a sticky session in a chosen country or cityFast fixed server IPs, HTTP and SOCKS5
PricePer IP and term — live price at checkoutBudget US$1.50/GB (US$1.35/GB at 100 GB); Premium US$5.00/GBPer IP and term — the cheapest per IP
Best for price monitoringSupplier portals and logged-in B2B price listsDaily price, promo and shipping checks per marketYour own stores and sites that accept server IPs

Prices in US dollars. Top up your wallet once and pay any line from it. Nothing renews automatically — renew in My assets to keep an IP.

Set up price monitoring proxies in 5 steps

  1. Open the setup and choose Budget

    The button below opens Rotating Residential Proxies with the AI and automation use case. Under Line choose Budget (US$1.50/GB).

  2. Buy traffic

    Open Add traffic, pick a package or enter a Custom GB (from 1 GB) and click Buy selected package.

  3. Generate one proxy per market

    Under Connection settings set Exit mode to Choose region / sticky IP, pick the Region — and State and City where prices differ — keep Protocol on HTTP and click Review cost and generate. Repeat for each market.

  4. Copy the lines

    In My assets, Copy each proxy and turn it into a URL such as http://USER:[email protected]:2222. Store them as PROXY_US, PROXY_DE and so on.

  5. Run the checks

    Use the code below to read the same product in each market and save price, currency, market and time.

    Expected result One line per market with a price and currency, or 'unknown' when the page couldn't be read.

Read one product's price in several markets (Python)

Scroll horizontally with the arrow keys to read all content.

# pip install httpx beautifulsoup4
import os
import httpx
from bs4 import BeautifulSoup

# One rotating residential proxy per market: Exit mode "Choose region / sticky IP" + that country
MARKETS = {"US": os.environ["PROXY_US"], "DE": os.environ["PROXY_DE"]}
PRODUCT_URL = "https://shop.example.com/products/sku-123"


def read_price(html):
    soup = BeautifulSoup(html, "html.parser")
    price = soup.select_one('[itemprop="price"]')
    currency = soup.select_one('[itemprop="priceCurrency"]')
    if price is None or currency is None:
        return None  # layout change, captcha or error page: unknown, never 0
    return price.get("content") or price.get_text(strip=True), currency.get("content") or currency.get_text(strip=True)


for market, proxy in MARKETS.items():
    try:
        with httpx.Client(proxy=proxy, timeout=30, follow_redirects=True) as client:
            r = client.get(PRODUCT_URL)
    except httpx.HTTPError as exc:  # proxy refused (407), timeout or connection error
        print(market, "unknown:", type(exc).__name__)
        continue
    result = read_price(r.text) if r.status_code == 200 else None
    print(market, r.status_code, result or "unknown")

Checked on 2026-10-18 (httpx 0.28.1, Beautiful Soup 4.14.3) through a local password-protected proxy, against HTTP and HTTPS product pages with schema.org price markup: both markets read 19.99 USD; with a wrong password each market printed 'unknown' instead of a price.

Quick fixes

Every market shows the same price

Check Are the proxies on Global rotation, or all set to one country?

Fix Generate one proxy per market with Choose region / sticky IP and that market's country.

The price comes back empty

Check Did you get a challenge, consent or error page? Did the page markup change?

Fix Record unknown, keep the last good price, and look at the HTML you saved before changing the parser.

Wrong currency

Check Does the site choose currency from the IP, a cookie or the URL path?

Fix Use a fresh client per market, open the market's own URL, and check the currency matches the market before saving.

429s or blocks

Check How many requests per site per minute? Are checks bunched together?

Fix Spread checks over the day, slow down per site and prefer lightweight JSON endpoints.

Price monitoring proxy FAQ

Why do I need proxies for price monitoring?

Without them your checks come from one IP that retailers throttle, and you only see your own region's prices. With one proxy per market you see what local shoppers see.

How much traffic will price monitoring use?

It depends on page weight: a product JSON is far smaller than a full page with images. Measure one product page, multiply by products, markets and checks per day, and you have your GB.

Can I monitor prices city by city?

Yes. Choose region / sticky IP lets you pick State and City as well as the country.

Is it billed per IP or per GB?

Rotating residential is per GB. Proxies for more markets draw from the same traffic, so you pay for the pages you download.

Can I monitor marketplaces such as Amazon?

Yes, on public product pages. Follow each site's terms and keep a steady pace; marketplace pages with seller accounts are covered on the platform pages.

Sources and verification

7
  1. Google Merchant Center Help — Regional availability and pricing

    Official documentation · Checked:

  2. MDN — 429 Too Many Requests

    Official documentation · Checked:

  3. Cloudflare docs — IP Access rules (by IP, ASN or country)

    Official documentation · Checked:

  4. Google Merchant Center Help — Set up regions (postal codes or states)

    Official documentation · Checked:

  5. Proxy302 pricing

    Product observation · Checked:

    Rotating residential per-GB prices as published on the pricing page and used by the console (Budget US$1.50/GB, US$1.35/GB in the 100 GB package; Premium US$5.00/GB; 1 PTC = US$1). Static ISP and datacenter IPs are quoted live per IP and term.

  6. Proxy302 console — Rotating Residential Proxies

    Product observation · Checked:

    Option names, billing modes and limits as shown in the live console on 2026-10-18: Line (Premium/Budget), Exit mode, Region, State, City, Protocol (HTTP/SOCKS5), Quantity (1–500), Term, Auto-renew IP (not yet available), My assets → Copy / Rotate / Renew / Copy for AI. Rotating residential connects through proxy.proxy302.com:2222 (HTTP) and :3333 (SOCKS5).

  7. Local proxy fixture run

    Local example · Checked:

    The code block was executed on 2026-10-18 against a local password-protected HTTP proxy that answers 407 without valid credentials; httpx 0.28.1 and Beautiful Soup 4.14.3 against a local product page with schema.org price markup, over plain HTTP and over HTTPS through a CONNECT tunnel: both markets read 19.99 USD; with a wrong password the proxy answered 407 and each market printed 'unknown' instead of a price.

    A local check proves the configuration syntax and authentication path, not access to any specific website, country or platform.

Ready to connect?

Create an account, top up once and pick rotating residential, static ISP or datacenter. Rotating residential exits cover 195+ countries and regions.