Every November, the same picture unfolds: sellers on Wildberries and Ozon start monitoring prices for a thousand SKUs, arbitrage marketers scale their campaigns on Facebook Ads and TikTok Ads for Black Friday, and SMM agencies sharply increase the number of accounts for their holiday content plans. And everyone faces the same problem — proxy traffic either runs out on the peak day or is purchased "with a reserve," which then sits idle as dead weight. Let's figure out how to calculate the volume of GB in advance and avoid losing money due to shortages or overpayments.
Why Traffic "Burns" and How Seasonality Plays a Role
The phrase "traffic does not burn" in the article's title is not a marketing cliché but the essence of the problem faced by almost everyone who purchases proxies on a pay-per-gigabyte model. For most providers of residential and mobile proxies, traffic is billed only for data actually transmitted: page requests, image downloads, API JSON responses. If you bought a package for 50 GB but used 30 GB in a month, the remaining 20 GB do not just disappear unless the provider imposes a strict expiration date on the package.
The problem lies elsewhere: seasonal tasks involve sharp spikes in consumption. In a regular month, a seller on Wildberries monitors 500 product cards once a day and spends a hypothetical 5 GB. During the pre-New Year sale, they add competitor monitoring every 2 hours, expand the list to 3000 SKUs — and suddenly need not 5, but 60 GB per month. If the purchase of traffic is not planned in advance, either the limit runs out on the peak day, or traffic has to be purchased at less favorable conditions at the last minute.
The same happens with arbitrage marketers: during Black Friday and 11.11, the number of advertising accounts in operation increases 2-4 times, each account requires a separate IP, and the frequency of checks and warming up increases. SMM agencies in December manage not 20, but 60 client accounts due to holiday content. All these spikes are predictable on the calendar — which means the volume of traffic can and should be calculated in advance, rather than purchased in a panic.
What Seasonal Peaks to Include in Your Plan
Before calculating gigabytes, you need to understand which dates and events create real load on proxies in your niche. Here are the main seasonal points to include in your traffic purchasing calendar:
| Event | Who is Affected | Traffic Load Increase |
|---|---|---|
| 11.11, Black Friday, Cyber Monday | Sellers on Wildberries/Ozon, arbitrage marketers | 3-5 times |
| New Year and Pre-New Year Sales | Sellers, SMM agencies | 2-4 times |
| March 8, February 23 | Gift category sellers, arbitrage marketers | 2-3 times |
| Launch of New Product Lines / Vacation Season | Marketers, Google Ads arbitrage marketers | 1.5-2 times |
| Black Friday on Avito (Auto, Electronics) | Ad scrapers, resellers | 2-3 times |
The main mistake is planning the purchase of traffic only for an "average month," without considering that 2-3 weeks before a major sale, the load starts to increase in advance: sellers warm up accounts, arbitrage marketers test creatives, and SMM teams prepare content plans. The peak traffic consumption usually occurs not on the day of the sale itself but during the preparation period leading up to it.
How to Calculate Traffic Volume for Your Tasks
Traffic calculation always follows one logic: volume per action × number of actions × duration of the campaign. Let's break it down into three typical scenarios.
Scenario 1. Price Monitoring on Wildberries/Ozon. One product card load through a scraper weighs on average 150-300 KB (HTML + images in cache usually do not load if the scraper works with API or without rendering images). If you monitor 2000 SKUs four times a day for 30 days of preparation for the sale: 2000 × 4 × 30 = 240,000 requests. With an average request size of 200 KB, this is about 48 GB per month — compared to 5-8 GB in a regular period when monitoring once a day.
Scenario 2. Farming and Managing Facebook Ads Accounts. One account during active warming (feed, stories, ad clicks) consumes 150-400 MB of traffic per day through a residential IP. If you scale from 10 to 40 accounts for 20 days before Black Friday: 40 accounts × 300 MB × 20 days = 240,000 MB ≈ 235 GB. This calculation needs to be done separately for each platform — TikTok Ads usually consumes less traffic due to video in a lower bitrate during previews but is heavier during active scrolling of the feed.
Scenario 3. SMM Agency, 50 Client Instagram Accounts. Publishing one post with a video through an anti-detect browser weighs 20-50 MB considering loading, preview, and feed. With 3 posts per day per account and activity for 25 days a month for the holiday content plan: 50 × 3 × 35 MB × 25 = 131,250 MB ≈ 128 GB.
A Simple Formula for Any Task:
Traffic Volume (GB) = (weight of one action in MB × number of actions per day × number of accounts or SKUs × days of the campaign) / 1024
Always add a 15-20% buffer to the obtained number for retries, connection errors, and re-downloads — especially when scraping, as marketplace sites may return captchas or temporary blocks requiring a repeat request through another IP.
Residential, Mobile, or Data Center: What to Choose for the Season
The type of proxy directly affects not only the stability of operations but also the economics of traffic consumption during the season. Different tasks require different balances of price, speed, and resistance to blocks.
| Proxy Type | When to Choose for the Season | Risk of Blocking |
|---|---|---|
| Residential Proxies | Price monitoring, account farming, SMM automation | Low |
| Mobile Proxies | Facebook Ads, TikTok Ads during peak campaigns | Minimal |
| Data Center Proxies | Mass scraping without geo restrictions, backup channels | Medium |
For seasonal monitoring of Wildberries and Ozon, residential proxies are optimal: they trigger scraping protection less frequently, and the IPs appear as regular customers, which is critical during sales when marketplaces strengthen anti-bot filters due to abnormal traffic growth on the site. For Facebook Ads and TikTok Ads accounts during peak season, mobile proxies are more logical — operator IPs with rotation reduce the risk of chain bans, which are particularly painful when 30-40 accounts are simultaneously in operation.
Data center proxies should be kept as a backup channel: they are cheaper in terms of traffic, and if the main pool of residential IPs runs out during the height of a sale, they allow you to continue monitoring competitor prices for 1-2 days until the purchased package arrives.
How to Avoid Overpaying for Traffic
The main trap of seasonal planning is purchasing "with a huge reserve just in case." This leads to the company paying for 200 GB, using 90, while the remainder sits idle until the next package. Here are some working principles that help keep expenses under control.
Base Your Estimates on Last Season's Data. If last November monitoring 1500 SKUs on Wildberries took 35 GB, this year, when expanding to 2000 SKUs, it makes sense to budget around 47 GB, not 100 GB "just in case."
Separate Traffic by Tasks. Do not purchase one general package for everything: scraping, farming, and SMM consume traffic unevenly and at different times. Separate traffic pools allow for a clearer view of which task genuinely requires a budget increase during the season and which remains stable.
Set Limits in Your Anti-Detect Browser. In Dolphin Anty, AdsPower, and GoLogin, you can set profiles linked to specific proxies and track usage for each account separately. This helps quickly identify if one account suddenly starts consuming traffic abnormally — for example, due to a looping automation or a bug in the warming script.
Disable Unnecessary Content Loading When Scraping. If the task is to collect only the price and availability of a product, rather than visually check the card, there is no need to load images and videos. Configuring the scraper to block media content reduces traffic consumption by 40-60% without data loss.
Stagger Peak Load Over Time. If price monitoring is not mandatory every 2 hours around the clock, set more frequent checks only during competitors' working hours and less frequently at night. This saves up to 30% of traffic without losing data relevance at critical moments.
Step-by-Step Traffic Purchase Plan for the Season
To avoid calculating traffic at the last minute, the purchase should be planned according to the following scheme, which is suitable for sellers, arbitrage marketers, and SMM agencies.
Step 1. 6-8 Weeks Before the Peak — Analyze data from the previous season: how many GB were used in a similar period last year, how much the load increased compared to a regular month.
Step 2. 4-5 Weeks Before the Peak — Calculate the volume of traffic using the formula from the section above for each task separately: scraping, account farming, SMM automation.
Step 3. 3 Weeks Before the Peak — Purchase the main traffic package with a 15-20% buffer, distribute it by tasks, and connect it in your anti-detect browser or scraper.
Step 4. 1-2 Weeks Before the Peak — Test the load on real volumes: run monitoring or farming at full scale for 2-3 days and observe the actual traffic consumption to adjust your forecast.
Step 5. During the Peak — Keep a backup channel on data center proxies or an additional package of residential traffic that can be activated in minutes if the main pool runs low ahead of schedule.
Step 6. After the Peak — Record the actual traffic consumption for each task. These figures will serve as a basis for calculations for the next similar season — planning Black Friday 2025 will be easier based on accurate data from Black Friday 2024.
Checklist Before Launching a Seasonal Campaign
- Traffic volume calculated separately for scraping, farming, and SMM tasks
- Increased load during the preparation period accounted for, not just on the day of the sale
- Appropriate proxy type selected for each task — residential, mobile, or data center
- Profiles set up in the anti-detect browser linked to specific proxies for tracking consumption
- Unnecessary media content loading disabled where not needed for scraping
- Backup traffic package purchased in case the calculated volume is exceeded
- Actual consumption recorded after the campaign for planning the next season
Conclusion
Seasonal peaks are not unexpected but a predictable part of the calendar for sellers, arbitrage marketers, and SMM specialists. Traffic shortages during Black Friday or 11.11 usually arise not because proxies "burn out," but because purchases were planned based on the metrics of an ordinary month, without considering the load increase of 2-5 times. Clear calculations using the formula "action weight × number of actions × campaign days," separate traffic pools for different tasks, and a backup channel for overspending allow you to navigate any seasonal peak without downtime and without overpaying for unused gigabytes.
If your task is stable price monitoring on marketplaces or farming advertising accounts during peak load periods, consider residential proxies — they provide a low risk of blocks precisely when platform protections are heightened the most. For advertising campaigns on Facebook Ads and TikTok Ads during the sale season, mobile proxies are better suited, while data center proxies can be kept on hand as a backup channel in case of traffic overspending — they deploy faster and are cheaper at larger volumes.