Proxies for price monitoring and tracking

Portproof supplies the proxy connection for your own price tracker: buy proxy traffic by the GB, then choose the pool, country and rotation in the proxy username. Payments are accepted in cryptocurrency. Your collector handles the schedule, product matching, price history and alerts. Use it for public pages you are permitted to collect; use an official feed or API when it already supplies the data you need.

A useful observation identifies the product and variant, seller, pack size, quantity, currency, displayed price, promotion conditions, stock, shipping destination, delivery charge and tax treatment. Save the source URL and capture time with those fields. An HTTP success response alone does not show that the intended offer loaded.

Hold the storefront, delivery destination, language preference, account state and browser settings consistent between checks. A country-targeted proxy supplies a network route; it does not choose the shop location, currency, tax treatment or delivery postcode for you. Record the country requested separately from anything you have verified about the result.

Start with an ordinary HTTP request when the permitted response already contains the selected product and price. Use a browser when your task needs rendered content or a supported selection step. Verify the chosen variant and price fields before saving a row. A consent overlay, empty template or error message is not a new price.

In a browser, keep the same locale, viewport and session policy across comparable runs. Remove a resource only after checking that the fields under test still load correctly. Blocking an image may suit a text-price check; blocking the script that selects a variant can make that check wrong. Save the extraction version with the result so a parser change is distinguishable from a price change.

Choose residential when the job calls for a peer-network connection. The pool includes home broadband and mobile peer connections; it does not guarantee a particular access network. Check the live locations list for the country you need before scheduling a run. Device availability changes, and both pools are shared.

Choose mobile 4G/5G when the test specifically needs a carrier-network exit. A mobile address does not turn a desktop browser into a phone or make an app-only offer available. Set the browser or device separately. Mobile and residential traffic draw from the same GB balance, so a controlled comparison can keep the rest of the job unchanged.

Measure a representative sample with the same browser resources, redirects and retry policy as the planned job. Record the number of complete checks and the bytes transferred, rather than assuming each product page is one network request. A browser can request additional documents, scripts, images and other resources.

Use the price monitoring traffic planner to turn a measured sample into a schedule. For planning, multiply measured bytes per complete check by checks per run and runs in the period. Count only usable observations as completed checks: keep failed attempts and their transferred bytes in the sample. If the sample already includes retries, do not add the same retries again. Use a separate allowance for uncertainty, then compare the estimate with dashboard usage after an isolated test run. Client counters and the account meter do not necessarily measure the same bytes.

Collect public prices only where you are permitted to do so. Respect the site’s terms, robots.txt and request limits. Back off on a 429 or another request to slow down, and stop rather than escalating when access is refused. This offer does not cover account creation to reach restricted prices or interfering with another shop’s service.