Residential proxies look like real users but rotation still matters. Send too many requests from one sticky session, or rotate too aggressively on login flows, and you'll trigger rate limits or bans.
This guide covers practical rotation patterns we see work across e-commerce, ad verification, and social scraping workloads.
Sticky vs rotating sessions
Sticky sessions keep the same exit IP for a defined TTL (often 1–30 minutes). Use them when:
- The target binds sessions to cookies or cart state
- You need consistent geo for a multi-step checkout
- APIs expect a stable client fingerprint for a short window
Rotating sessions assign a new IP per request or on a short interval. Use them when:
- You're crawling large public catalogues
- IP reputation decays quickly on the target
- Volume matters more than session continuity
Rule of thumb: default to sticky for authenticated flows, rotating for anonymous crawls.
Pick the right geo granularity
Country-level targeting is enough for many retailers. Strict platforms often need city-level alignment mismatched timezone, language headers, and IP geo is a common fingerprint signal.
When testing, log the resolved geo for a sample of requests before scaling traffic.
Rotation intervals that work
| Workload | Session type | Typical TTL |
|---|---|---|
| Price monitoring | Rotating | Per request |
| Account login | Sticky | 10–30 min |
| Ad verification | Sticky | 5–15 min |
| SERP scraping | Rotating | Per request |
Avoid hammering a single ASN or subnet. Spread concurrency across pools and back off on 429 / 403 responses.
Headers and TLS still matter
Proxies solve IP reputation not bad client impersonation. Pair residential IPs with:
- Realistic
User-Agentstrings - Accept-Language matching your target region
- Consistent HTTP/2 or HTTP/1.1 behaviour (don't mix randomly per request)
Measuring success rate
Track per-domain metrics:
- HTTP 2xx rate baseline health
- Challenge rate CAPTCHA or interstitial pages
- Empty parse rate pages that load but block content server-side
If challenges spike after a config change, widen rotation interval or tighten geo before adding more IPs.
Getting started with RedScrape
RedScrape residential pools support sticky and rotating modes with country, state, and city targeting. Start with a small concurrency cap, validate geo resolution, then scale threads once success rate stabilises.
