Black FridaySpecial - USA & Europe - 100 MBPS: $999.00 instead of $2,000.00. Coupon: BLACKFRIDAY, until November 27.See the plan
WeProxy

Guide

Black Friday Price Tracking: How to Use a Proxy for E-commerce Price Monitoring

9 min read

E-commerce price tracking means reading product prices, stock and promotions from store pages at regular intervals and keeping a dated record. A proxy spreads requests out and opens the page from the customer’s country. Choosing a proxy type, a Python example with JSON-LD, checking Black Friday discounts with the 10-day rule, common errors and legal limits.

Key takeaways

  • E-commerce price tracking means reading the price, stock and promotion details of specific products from store pages at regular intervals and storing them in a timestamped record.
  • In price tracking, a proxy spreads requests out instead of sending them from one IP and opens the page from the customer’s country or city; it does not change account-based prices such as member discounts or app prices.
  • Rotating datacenter suits stores that accept datacenter IPs, rotating residential suits large marketplaces that block datacenter IPs, and sticky sessions suit multi-step flows such as cart and shipping.
  • Reading the price from the page’s schema.org Product and Offer (JSON-LD) data instead of HTML selectors makes it less likely your parser breaks when the Black Friday theme goes live.
  • In Türkiye, from 1 August 2026 the pre-discount price is the lowest price in the last 10 days before the discount; in the EU the period is at least 30 days, so tracking has to start before the campaign.

E-commerce price tracking means reading the price, stock status and promotion details of specific products from store pages at regular intervals and storing them in a dated record. A proxy solves two problems here: it spreads requests out instead of sending them all from one office IP, and it lets you open the page from the country or city where your customers see it. During Black Friday week, prices change more often and sites tighten their bot protection, so the right proxy type and a reasonable request frequency decide whether your data arrives complete.

Three groups run price tracking: sellers watching how their own store compares with competitors, teams checking on behalf of a brand whether authorized resellers follow its pricing policy, and researchers who want to answer “Is this Black Friday discount real?” with data. All three groups need the same thing: to measure the same product under the same conditions at regular intervals.

Why do you need a proxy for price tracking?

If you check a few products once a day, you don’t need a proxy; looking in a browser is enough. The need starts when the number of tracked products and the request frequency go up. Opening hundreds of product pages every hour from the same IP runs into the store’s rate limit. The site first returns 429 Too Many Requests, then sends the IP to a CAPTCHA page or blocks it for a while. From that point on, your data shows the hours you were blocked, and the real price changes get lost.

The second reason is location. Many stores show the price, shipping cost, delivery time and stock based on the visitor’s country, and sometimes their city. A script that opens a Turkish store from a server abroad may get a different page from the one a customer in Türkiye sees: another currency, a “we don’t ship to this region” notice, or a redirect. A proxy with an exit IP in the target market lets you measure from the customer’s point of view.

The third is continuity. A price series is only valuable if the same product is measured the same way every day. When your office connection’s IP changes, the VPN drops or an IP gets blocked, the series gets gaps. A proxy setup separates the measurement from your personal connection. The general picture of this kind of work is described on the proxy for market research page.

Why is price tracking harder on Black Friday?

Black Friday falls on 27 November in 2026, and many stores start their campaigns days or even weeks earlier. In Türkiye the same event runs as “Efsane Cuma”. Several changes happen at once in this period, and each one makes price tracking harder:

  • Prices change several times a day. Hourly deals, limited-stock products and coupons applied in the cart mean that a once-a-day check misses most of the campaign.
  • Stores tighten bot protection. To protect their infrastructure under heavy traffic, they lower rate limits and the CAPTCHA threshold. A script that runs fine on normal days starts getting 403 and 429 this week.
  • Page layouts change. Campaign banners, countdown timers and new price boxes appear. A parser that reads the price from the HTML with a CSS selector can return empty values on the day the campaign theme goes live.
  • Prices differ from person to person. Conditional prices such as app-only prices, member discounts and cart coupons differ from what a visitor who isn’t logged in sees.

That last point also shows where a proxy stops helping. A proxy changes only the IP, and with it network-based signals such as country and city. Member discounts, app prices and personal coupons depend on the account, and a proxy can’t measure them. State clearly in your report which price you measured, for example: “price shown on the desktop page, not logged in, from a Turkish IP”.

Which proxy type is best for price tracking?

The right type depends on how the target site treats datacenter IPs, on your request volume and on how long the same session has to be kept.

JobRecommended productWhy
High-volume catalog crawling on stores that accept datacenter IPsRotating Datacenter IPv4Paid per GB, the IP changes on every request, 1–5 minute sticky sessions when needed
Price and stock tracking on large marketplaces that block datacenter IPsRotating Residential IPv4Home connection IPs, country and city targeting, sticky or per-request rotation
Flows that need a long sticky session (such as adding to cart to see the shipping cost)Premium Rotating ResidentialSticky time adjustable from 1 to 1440 minutes, no extra quota multiplier for city targeting
Uninterrupted, very high-volume crawling throughout campaign weekUnlimited Rotating Residential IPv4Paid monthly per port, GB not counted, 1–120 minute sticky and unlimited concurrent connections
Measuring a small number of products from the same address every time, a fixed checkpoint in TürkiyeStatic Residential IPv4The IP doesn’t change for the length of the plan, 11 countries including Türkiye, unlimited traffic on each IP

If you would rather get ready-made data from large marketplaces such as Amazon than build the proxy and parsing setup yourself, EveryInfra returns public data from Amazon and 100+ other platforms as structured JSON with a single API key.

Whether you pick rotating or sticky depends on whether the measurement takes one request or a flow of several steps. If you read the product page in a single request, an IP that changes on every request spreads the load. If you have to add the product to the cart to see the shipping cost, the steps must come from the same IP, or the site may drop the session. The sticky vs rotating proxy post covers this in detail. To see why target sites treat residential and datacenter IPs differently, read the residential vs datacenter comparison.

On plans sold per GB, the traffic you buy has no expiry; it stays in your balance until used and does not reset monthly. For tracking work that peaks a few times a year, like Black Friday, this means you don’t pay for unused traffic in the months between campaigns. If you want to test on your own target store before buying, Premium Rotating Residential comes with a 1 GB free trial.

How to set up e-commerce price tracking step by step?

A solid price tracking setup starts with five decisions: which products, which source, how often, from where, and how the data will be stored.

  1. Fix the product list. For each product, save the direct product page URL and, if possible, the store’s product code (SKU). Search result pages change every time because of sorting and ads, and they break the series.
  2. Read the price from structured data. Most e-commerce sites put schema.org Product and Offer markup on product pages for search engines. The price, priceCurrency and availability fields usually stay in place even when the page design changes. That makes it less likely your parser breaks when the campaign theme goes live.
  3. Set the frequency by product priority. During campaign week, measuring priority products hourly and the rest once or twice a day is enough for most jobs. Every request puts load on the target site; checking more often than you need raises both the chance of being blocked and your traffic use.
  4. Fix the location. Measure Turkish stores from a Turkish exit IP and foreign markets from an IP in that country, and save in every record which country and city you measured from. The Türkiye proxy locations page lists which products are offered for Türkiye and with which connection method. The difference between country, city and ASN targeting is explained in the proxy geo-targeting post.
  5. Store every measurement with a timestamp. Next to the price, also save the currency, stock, HTTP status code and an error note. “Price not found” and “site returned 403” are different kinds of gaps; if you don’t separate them, you can’t interpret the series.

The Python example below puts these steps into a single file. It opens the product page through the proxy, reads the Product offer from the JSON-LD and appends the result to a CSV file. The store addresses are placeholders; replace USER and PASSWORD with the proxy credentials from your dashboard.

import csv
import json
import re
import time
from datetime import datetime, timezone

import requests

PROXY = "http://USER:[email protected]:8989"
PROXIES = {"http": PROXY, "https": PROXY}
HEADERS = {
    "User-Agent": "PriceWatch/1.0 (+https://example.com/bot)",
    "Accept-Language": "tr-TR,tr;q=0.9",
}
PRODUCTS = [
    "https://shop.example/product/headphones-x1",
    "https://shop.example/product/vacuum-s5",
]
LD_JSON = re.compile(r'<script[^>]*application/ld\+json[^>]*>(.*?)</script>', re.S | re.I)


def offer_from_html(html):
    for block in LD_JSON.findall(html):
        try:
            data = json.loads(block)
        except json.JSONDecodeError:
            continue
        items = data if isinstance(data, list) else data.get("@graph", [data])
        for item in items:
            types = item.get("@type") if isinstance(item, dict) else None
            if types == "Product" or (isinstance(types, list) and "Product" in types):
                offer = item.get("offers") or {}
                if isinstance(offer, list):
                    offer = offer[0] if offer else {}
                price = offer.get("price") or offer.get("lowPrice")
                return price, offer.get("priceCurrency"), offer.get("availability")
    return None, None, None


with open("prices.csv", "a", newline="", encoding="utf-8") as f:
    writer = csv.writer(f)
    for url in PRODUCTS:
        ts = datetime.now(timezone.utc).isoformat(timespec="seconds")
        try:
            r = requests.get(url, proxies=PROXIES, headers=HEADERS, timeout=30)
        except requests.RequestException as exc:
            writer.writerow([ts, url, "", "", "", type(exc).__name__])
            continue
        if r.status_code != 200:
            writer.writerow([ts, url, "", "", "", f"HTTP {r.status_code}"])
        else:
            price, currency, stock = offer_from_html(r.text)
            writer.writerow([ts, url, price, currency, stock, "ok" if price else "no-price"])
        time.sleep(5)

Run the script on a scheduler (cron on Linux, Task Scheduler on Windows) and prices.csv turns into a dated price series for each product. The time.sleep(5) between requests is a deliberate slowdown: measuring without loading the target site is both the ethical choice and what keeps you from getting blocked. If the page loads the price only with JavaScript, the JSON-LD may come back empty; in that case you need browser automation. How to set a proxy in requests, httpx and aiohttp, and how to use SOCKS5, is covered in the using a proxy in Python guide.

Before the first run, check with the My IP tool that the proxy exits from the right country. If you use several proxy lines, you can test them all at once with the proxy checker.

Is the Black Friday discount real? How to read price history

The result people look for most often in price tracking is whether the “price before discount” shown in a campaign was ever actually charged. To answer that, you need to have started measuring before the campaign began; tracking set up after Black Friday week has started has no history to compare against, so it can’t answer the question.

In Türkiye, the Ministry of Trade amended the Commercial Advertising and Unfair Commercial Practices Regulation (Ticari Reklam ve Haksız Ticari Uygulamalar Yönetmeliği; Official Gazette, 1 July 2026, no. 33297). From 1 August 2026, discount advertising must use as the pre-discount price the lowest price applied in the last 10 days before the discount start date (Ministry of Trade announcement). In the European Union, Article 6a of Directive 98/6/EC takes as the reference the lowest price in a period of not less than 30 days before the discount.

MarketReference priceWhen to start tracking
TürkiyeLowest price in the last 10 days before the discountAt least 10 days before the campaign starts
EU countriesLowest price in at least 30 days before the discountAt least 30 days before the campaign starts

Find the lowest value in your series for the period before the discount started and compare it with the struck-through price; that shows whether the claim holds up. Two points need care here. First, the rule concerns the store’s own price, so don’t mix up the prices of different sellers on a marketplace. Second, gaps in measurement distort the result: if the series has a three-day stretch where you were blocked, you may have missed a low price on those days. This kind of analysis is for information only and is not legal advice; if you plan to file a complaint or report, rely on the official channels and the current text of the regulation.

Common price tracking errors and how to fix them

During campaign week, tracking scripts usually break for the same reasons. Read the table from symptom to cause:

SymptomLikely causeFix
429 Too Many RequestsToo many requests from the same IP or sessionLower the frequency, switch to per-request rotation, add delays between requests
403 Forbidden or a CAPTCHA pageDatacenter IP blocked or low IP reputationSwitch to a residential pool, keep request headers consistent with a real browser
407 Proxy Authentication RequiredProxy username/password wrong or missingCheck the details in your dashboard, percent-encode special characters in the URL
Price comes back in a different currencyExit IP is in another countryCheck country targeting, set the Accept-Language header for the market
Price field empty, page returns 200Campaign theme changed or the price loads with JavaScriptSwitch to JSON-LD; if there is none, use browser automation
Session drops at the cart or shipping stepIP changed during the flowUse a sticky session and keep the sticky time longer than the flow

Knowing whether an error code comes from the proxy or the target site tells you where to look for the fix. The proxy error codes guide explains, code by code, at which layer errors such as 407 and 502 occur.

Another common mistake is treating a CAPTCHA as an obstacle to solve. A CAPTCHA is the site’s signal that it wants you to slow down. Lowering the frequency, prioritizing which products you measure and spreading the load over the hours usually gives a more lasting result. The special cases of price and restock tracking for sneakers and limited-stock products are covered on the sneaker proxy page.

Reading the price on a public product page is the basis of price tracking; how you read it sets the limits. In practice, these are the limits to respect:

  • Read the target site’s terms of use. Some stores restrict automated access in their terms or offer an official API or partner feed for price data. If there is an official channel, use it.
  • Follow robots.txt rules. Standardized in RFC 9309, this file tells you which paths the site doesn’t want accessed automatically.
  • Don’t collect personal data. The subject of price tracking is the product. Data such as reviewers’ names or sellers’ personal contact details falls under KVKK and GDPR and should not be part of this work.
  • Don’t access login-only areas automatically. Opening fake accounts to measure member-only prices breaks the terms and also makes the measurement less reliable.
  • Limit the load. Delays between requests, a reasonable frequency and skipping resources you don’t need (images, video) reduce the load on the target site’s infrastructure.

Use of WeProxy services is subject to the acceptable use policy. The policy prohibits unlawful activity, unauthorized account access and attack traffic such as DDoS. Start your Black Friday tracking at least ten days before the campaign at a low frequency, and raise the frequency during campaign week only for priority products. That keeps your data comparable and your relationship with the target site trouble-free.

Frequently asked questions

Which proxy type should I choose for price tracking?

Look at how the target store treats datacenter IPs. On sites that accept them, a rotating datacenter proxy paid per GB is enough for high-volume crawling. Large marketplaces often block datacenter IPs, so rotating residential gives more stable results there. For multi-step flows such as adding to cart to see the shipping cost, use a sticky session; to measure a few products from the same address every time, use a static residential IP.

How can I tell if a Black Friday discount is real?

Start measuring the product’s price regularly before the campaign begins. In Türkiye, from 1 August 2026 the pre-discount price is the lowest price applied in the last 10 days before the discount start. Compare the lowest price in your records for that period with the struck-through price. In EU countries the reference period is at least 30 days. This comparison is for information only and is not legal advice.

How often should a price tracker send requests?

Set the frequency by how important the product is and how often its price changes. During campaign week, measuring priority products hourly and the rest once or twice a day is enough for most jobs. Checking more often puts load on the target site and raises the chance of 429 errors and CAPTCHAs. Add delays between requests and always measure the same product from the same country.

Why does my price tracking script get 403 or 429 errors?

A 429 means you are sending too many requests from the same IP or session; lower the frequency, add delays between requests and use per-request IP rotation. A 403 or a CAPTCHA page usually means the datacenter IP is blocked or has a low reputation; switching to a residential pool and using headers consistent with a browser usually fixes it. A 407 means the proxy credentials are wrong.

Is it legal to track competitor prices with a proxy?

Reading prices on public product pages is the basis of price tracking, but you have to follow the target site’s terms of use and robots.txt rules. If there is an official API or data feed, use it. Don’t collect personal data, don’t access login-only areas automatically and don’t overload the site. WeProxy services are subject to the acceptable use policy. This information is not legal advice.

Get Started

Test Your Proxy Setup Today

Check connectivity with free tools or talk to sales to pick the right package.