Pages to watch, a formula for the weekly GB, and a request rate that keeps you on the right side of site rules.
Watching only the product page misses most of what changes in the week of 27 November (Black Friday) to 30 November (Cyber Monday). Decide the pages first, then the rhythm; the rhythm is what drives the traffic bill.
No source publishes a reliable "prices change every N hours" figure, so treat the rhythm below as a starting point and adjust it after two or three days of your own logs.
| Item | What it tells you | Starting rhythm |
|---|---|---|
| Product page | Displayed price, struck-through reference price, coupon text, stock | A few times a day for key products; once a day for the rest |
| Category or sale landing page | Which items are promoted, site-wide codes, free-shipping thresholds | Once or twice a day |
| Marketplace listing with several sellers | Which seller holds the buy button and at what price | More often for the few items you compete on directly |
| Cart or checkout | Whether the coupon applies and the delivered price | A small sample, once a day |
Rhythm column is a suggested starting point, not a measured price-change rate. Store the price exactly as displayed, with the currency, the seller and the time of the check.
A shop can show another price, currency or shipping offer depending on the visitor's country. To record what a buyer in Germany sees, send the check through an exit located in Germany. Rotating residential covers 195+ countries, and the Budget line picks the country only; city targeting is a Premium line option where the city is available.
Rotating datacenter IPs are easier for shops to recognise as datacenter addresses, so use residential for retail price checks. The country-by-country method is in the guide on checking prices in other countries.
Traffic is the size of one response times how many responses you make: GB = page size x products x countries x checks per day x days. Measure the real size of the response you download (browser developer tools, Network tab); a plain HTML or data response is much smaller than a page that loads images and scripts.
Example with assumed numbers: 200 products x 3 countries x 4 checks a day x 5 days = 12,000 responses; at 0.3 MB each that is 3,600 MB, about 3.6 GB. At US$1.50 per GB (Budget line) that is about US$5.40; in the 100 GB package the rate is US$1.35 per GB. Add a margin for retries, because a retry downloads the page again. The traffic-estimate guide has the long version.
Read the site's robots.txt and terms before you automate. Google describes robots.txt as a way to manage crawler traffic, and some shops forbid automated access in their terms; follow what the site states.
Keep the rate low and steady. If a site answers 429 Too Many Requests, it is asking you to slow down; wait for the number of seconds in the Retry-After header if there is one, then resume at a lower rate. Switching to another IP does not change what the site asked for.
Write down the exact product URLs, the seller you track and the countries you care about. Fewer, well-chosen pages cost less than a broad crawl.
Open a product page in browser developer tools, Network tab, and note the transferred size. Or download the HTML or data response your script will use and check its size.
Open the rotating residential page, buy the traffic from 1 GB, and generate a proxy for each country. Choose the exit mode "Choose region / new IP per connection" and HTTP or SOCKS5.
From My assets copy HOST, PORT, USERNAME and PASSWORD, and run curl -x with https://ipinfo.io/json to confirm the country before any real run.
Expected result The country in the answer matches the proxy you generated.
Begin a few days before 27 November so you see normal prices first, then compare. After day one, check bytes used against your estimate.
Check Check the country of the exit, the currency, and whether the page needs JavaScript to show the price.
Fix Test the same URL through a proxy in the same country and compare the HTML; fix the country before changing the parser.
Stop when If the shop shows different prices to logged-in and logged-out visitors, record which one you track.
Check Look at your rate per site and at the Retry-After header.
Fix Lower the rate, wait as the header says, and cut the number of checks for low-value items.
Stop when If the answers keep coming at a low rate, the site may not allow automated access; stop and read its terms.
Check Compare the real response size with your assumption, and count retries.
Fix Download only the HTML or data response, not images and scripts, and cap retries.
Use the formula: page size x products x countries x checks per day x days. With the assumed numbers in this guide it is about 3.6 GB; your own page size decides the real figure.
No named source gives a reliable figure, so this guide does not quote one. Start with a few checks a day for key products and adjust after reading your own logs.
Yes: send the check through a residential exit in that country. The Budget line selects the country only.
No. The smallest purchase is 1 GB of rotating residential traffic, and purchased traffic has no expiry.
It depends on the site. Read its robots.txt and terms, keep the rate low, and stop when the site tells you to slow down.
Guides and pages that continue from here.
Multiply response size by products, countries, daily checks and days; then price the GB.
A repeatable method to see the prices, currency, shipping and ads a visitor in another country sees: clean session, confirmed exit, recorded result.
Proxies for price monitoring: see competitor prices, promotions and shipping as shoppers in each country (and major city on the Premium line) see them. Rotating residential from US$1.50/GB.
View options and pricingProduct observation · Confirmed on:
Product facts file of the site, checked 12 November 2026: rotating residential Budget line US$1.50 per GB (US$1.35 per GB in the 100 GB package), traffic from 1 GB, no expiry on purchased traffic, 195+ countries, Budget line country-level only, no free trial.
Official documentation · Confirmed on:
Read 12 November 2026: a robots.txt file is used primarily to manage crawler traffic to a site, and it is not a mechanism for keeping a web page out of Google.
Official documentation · Confirmed on:
Read 12 November 2026: 429 means the client sent too many requests in a given amount of time; a Retry-After header may say how long to wait.
Official documentation · Confirmed on:
Read 12 November 2026: Retry-After is given as a number of seconds or an HTTP date, and is used with 429, 503 and redirect responses.
Local example · Confirmed on:
Arithmetic done on 12 November 2026 with assumed round numbers, not measurements: 200 products x 3 countries x 4 checks a day x 5 days x 0.3 MB.
The page size is an assumption. Measure your own pages before buying.
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.
