Proxy pool sizing
How Many Proxies Do I Need for Ad Verification?
Plan proxy coverage for checking ads, redirects, landing pages and geographic delivery.
Practical estimate
For ad verification, proxy count depends on countries, campaigns, landing-page paths, check frequency and how much reserve you need when a route fails.
Workload
Pool
Reserve
BuyProxies guide
A good proxy count is not the biggest count. It is the smallest pool that keeps sessions stable, avoids repeated failures and leaves enough reserve for retries.
Simple formula
Starting pool = active sessions ÷ safe sessions per proxy × location multiplier × 1.25 reserve.
Build the pool around locations first. One campaign checked in five countries needs a different setup than many campaigns checked in one city.
Example pool sizes
| Workload | Starting point | Why |
|---|---|---|
| One campaign, few countries | 5-20 proxies | Enough for validation and repeat checks. |
| Many campaigns | 25-100 proxies | Segment by country, network and schedule. |
| Fraud or redirect investigation | Dedicated stable proxies per scenario | Repeatability matters more than rotating randomly. |
When to add more proxies
Add more proxies only when the current pool is healthy but capacity is the bottleneck. If many requests fail because credentials are wrong, the country is wrong or the target is blocking the workflow, a bigger pool just spreads the same mistake over more IPs. First fix connection quality, request pacing and session rules, then increase capacity.
A useful rule is to scale in visible steps. Increase the pool, run the same workload, compare error rate and keep the change only if useful results increase without a matching increase in blocks, timeouts or support work. For location-sensitive workflows, treat every country as its own pool instead of averaging all proxies together.
How to size the pool
- List countries, regions and devices you need to verify.
- Assign proxies to each location group.
- Test landing page, redirect and final URL separately.
- Save screenshots or logs for repeat checks.
- Keep reserve proxies for failed routes and re-checks.
A simple calculation example
Suppose the workload needs 30 active sessions and you are comfortable with 2 active sessions per proxy. The base pool is 15 proxies. If the job runs in two countries, split that into two location pools instead of one mixed pool. Then add reserve capacity for retries, maintenance and unexpected target friction. With a 25% reserve, that 15-proxy base becomes about 19 proxies before you round up for location coverage.
This calculation is not meant to be perfect. It gives you a safe starting number that can be measured. After the first run, compare successful results, retries, timeouts and manual fixes. If success rate is high but the queue is too slow, add proxies. If error rate is high, fix the workflow before buying more capacity.
Sizing mistakes
- Using proxies from the wrong country.
- Rotating so often you cannot reproduce the ad path.
- Mixing ad verification with unrelated scraping traffic.
- Ignoring DNS, browser language and geolocation differences.
FAQ
Why do ad checks need proxies?
Ads and landing pages can vary by location, network and user context.
Should ad verification proxies rotate?
Use controlled rotation. For investigations, stable repeatable checks are often better.
How many countries should I cover?
Cover the markets where the campaign actually runs, plus any suspected problem locations.
Order clarity
What you receive
- What you receive
Proxy connection details for the package processed through the live order form.
- Protocols
HTTP or SOCKS5 options are shown during configuration for supported packages.
- Authentication
Set the requested proxy credentials during configuration before checkout.
- Locations
Current location availability is shown in the selector and can change with inventory.
- Support and checking
Support can help verify connection details and review replacement requests under the service policy.