Black Friday 2026 price monitoring with residential proxies
Baseline, sessions, local checks and pacing for the busiest week of the year, with a ready-made price checker.
By DINPROXY Team · · 6 min read
On this page
Black Friday falls on Friday, November 27, 2026, and Cyber Monday on November 30. For anyone who tracks prices, stock or deals, those five days from Thanksgiving to Cyber Monday are the busiest of the year: prices change by the hour, flash deals come and go, and retailers are at their strictest with automated traffic. This guide shows how to plan Black Friday price monitoring with residential proxies, from the baseline you collect now to the checks you run on the day.
Why Black Friday is the hardest week to monitor
Price monitoring that runs smoothly in October often stumbles in late November. Four things change at once:
- Prices move faster. Retailers reprice many times a day, and lightning deals can last a few hours. A daily check misses most of them.
- Bot defences get stricter. Under peak load, many shops turn on waiting rooms, CAPTCHAs and tighter rate limits, and the same scraper sees far more blocks.
- Deals depend on where you are. Prices, shipping costs and stock differ by country, and in the US often by state or city.
- Your own volume jumps. More products, more checks per day and more retries all land in the same week.
The answer is to plan ahead: collect a baseline before the sales start, check each page the way a local shopper would see it, and pace your checks so they keep working through the peak.
Collect a baseline before the sales start
A discount only means something next to the price before it. Many "was" prices on Black Friday are higher than anything the product actually sold for, and your own history is the only reliable comparison. Start collecting at least a week before Black Friday, and record the same fields every time:
| Field | Why it matters |
|---|---|
| Product ID and URL | Matches the same product across checks and sites |
| Current price and currency | The number you are tracking |
| "Was" or list price | Shows the discount the shop claims |
| Stock or availability | A great price on an item that is sold out is no deal |
| Shipping cost | Often changes during sales and changes the real price |
| Location of the check | Country, state or city the request came from |
| Time (UTC) | Lets you line up checks and spot the moment a deal starts |
With a week or two of history, you can tell a real price cut from a relabelled one, and you know each product's normal price before the rush begins.
Choose the right session for each page
Most of a price monitor is independent page loads, but some pages only show a price after a few steps. Match the session type to the page, as explained in our guide to rotating vs sticky residential proxies:
| Page | Session | Why |
|---|---|---|
| Category, search and deal listing pages | Rotating | Each page stands on its own; a new IP per request spreads the load |
| Product pages | Rotating | One request per product, so no session is needed |
| Price after choosing a size, colour or store | Sticky, a few minutes | The site remembers your choices between requests |
| Cart or checkout price (with shipping) | Sticky, 10 to 30 minutes | Several linked steps must come from one visitor |
On DINPROXY residential proxies, a username without a session option rotates, and adding @session= with @time= keeps the same IP for up to 120 minutes.
Check deals the way local shoppers see them
A deal in New York may not exist in London, and a store's stock in Chicago is not its stock in Dallas. Add the location to the proxy username so each check comes from a residential IP in the market you care about:
| You want prices from | Username |
|---|---|
| The United States | 1024~myuser@country=us |
| California | 1024~myuser@country=us@state=california |
| London | 1024~myuser@country=gb@state=england@city=london |
| Germany | 1024~myuser@country=de |
Run one set of checks per market and store the location with each result. For deals that appear only in a shop's app or mobile site, mobile proxies send the same checks through mobile carrier IPs, chosen by country.
Pace your checks through the peak
More checks are not always better. Hitting a shop too often during its busiest hours is the fastest way to get blocked, and it adds load the shop does not need. A schedule like this keeps the data fresh where it matters:
| Period | Suggested pace |
|---|---|
| Now to Wednesday, November 25 | Every 6 to 12 hours, to build the baseline |
| Thanksgiving to Cyber Monday (November 26 to 30) | Every 30 to 60 minutes for key products, every few hours for the rest |
| From December 1 | Back to daily, to see which prices stay down |
A few habits keep the checks running:
- Back off on errors. On
403,429or503, wait a little longer before each retry, then try again through a new IP. - Spread requests out. Add a random pause of a second or two between requests rather than sending them in bursts.
- Send realistic headers. A current browser
User-Agentand anAccept-Languagethat matches the market look like an ordinary visitor. - Stay within your connection limit. Each DINPROXY account can keep up to 100 connections open at once, residential and mobile together, so size your workers to fit.
For more on pacing and headers, read how to scrape a website without getting blocked.
A small price checker you can run
Many shops describe each product with schema.org data in the page, including the price in offers. This checker fetches each product page through a residential IP in the US, reads that price, retries through a new IP when a request fails, and adds a line to prices.csv for each product. Run it on a schedule, such as with cron, at the pace above.
import { fetch, ProxyAgent } from "undici";import { appendFileSync } from "node:fs";
const username = "USERNAME@country=us";const token = `Basic ${Buffer.from(`${username}:PASSWORD`).toString("base64")}`;const headers = { "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36", "accept-language": "en-US,en;q=0.9",};const urls = ["https://shop.example.com/product/123", "https://shop.example.com/product/456"];const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms));
// The price from the page's schema.org Product data, if it has any.function findPrice(html) { for (const [, text] of html.matchAll(/<script[^>]*application\/ld\+json[^>]*>([\s\S]*?)<\/script>/g)) { let data; try { data = JSON.parse(text); } catch { continue; } const items = [data].flat().flatMap((item) => item?.["@graph"] ?? [item]); for (const item of items) { const offer = [item?.offers].flat()[0]; if (offer?.price != null) return [offer.price, offer.priceCurrency ?? ""]; } } return [null, null];}
async function fetchPage(url, tries = 4) { for (let attempt = 0; attempt < tries; attempt++) { // A new connection for each attempt, so a retry leaves through a new IP. const dispatcher = new ProxyAgent({ uri: "http://proxy.dinproxy.com:7777", token }); try { const response = await fetch(url, { dispatcher, headers, signal: AbortSignal.timeout(30000) }); if (response.ok) return await response.text(); if (![403, 429, 503].includes(response.status)) return null; } catch { // timeout or network error: retry } finally { await dispatcher.close(); } await sleep(2 ** attempt * 1000 + Math.random() * 1000); } return null;}
for (const url of urls) { const html = await fetchPage(url); const [price, currency] = html ? findPrice(html) : [null, null]; appendFileSync("prices.csv", `${new Date().toISOString()},${url},${price ?? ""},${currency ?? ""}\n`); await sleep(1000 + Math.random() * 2000);}Replace USERNAME with your connection username from Tools → Users and PASSWORD with the proxy user's password, and put your product pages in the list. To check another market, change country=us to the location you need. If a shop has no schema.org price, read the price from the page's HTML instead, using the element the shop shows it in.
When a shop blocks you: send those pages to the Web Unlocker
Some shops put their Black Friday pages behind a waiting room or a CAPTCHA that no amount of pacing gets past. For those pages, use the Web Unlocker: it renders JavaScript, retries and works around anti-bot checks for you, and only successful requests use a result. Keep residential proxies for the pages that load normally and send only the hard ones to the Web Unlocker. Our comparison of the Web Unlocker and residential proxies explains how the two work together.
Plan your traffic before the rush
Residential proxies are billed per GB, so estimate your traffic before the week starts:
pages per check × checks per day × days × average page size
Measure the average page size yourself by fetching 20 or so of your product pages and adding up the bytes. A plain HTTP client like the checker above downloads only the HTML, which is much lighter than loading the full page with images and scripts in a browser. For example, 500 products checked every hour for the five days from Thanksgiving to Cyber Monday is 60,000 page loads; at 300 KB of HTML each, that is about 18 GB.
Buy the traffic before the sales start rather than in the middle of them. DINPROXY traffic never expires, so whatever is left over carries on to the holiday sales in December.
Your Black Friday checklist
- Start the baseline at least a week before November 27.
- Record price, list price, stock, shipping, location and time for every check.
- Rotate for listing and product pages; use sticky sessions for options, carts and checkout.
- Run one set of checks per market, with the location in the username.
- Check key products every 30 to 60 minutes from Thanksgiving to Cyber Monday.
- Back off on errors and add random pauses between requests.
- Send pages that stay blocked to the Web Unlocker.
- Estimate your traffic and buy it before the rush.
Frequently asked questions
Black Friday is on Friday, November 27, 2026, the day after Thanksgiving in the US. Cyber Monday follows on Monday, November 30.
Every 30 to 60 minutes for key products from Thanksgiving to Cyber Monday, and every few hours for the rest. Before the sales, every 6 to 12 hours is enough to build a baseline.
Rotating for listing and product pages, where each page stands on its own. Use a sticky session when a price appears only after choosing options or adding the item to a cart.