Bind each antidetect or automation browser profile to one residential IP that matches timezone and language. Rotating mid-checkout is how sessions die.
Recommended: static residential, one IP per profile. Custom ports when you run a farm in one country. This is not the Social or E-commerce login policy page — it is the browser-identity page.
Reproduce a city UI without flying testers.
Click paths from the target country.
Stable egress while watching tags.
Profile, timezone, and IP must tell one story.
A proxy does not fix WebRTC leaks or a timezone mismatch. Pair a static IP with a hardened profile — then stop changing the IP.
Cookies invalidate at payment.
Cloudflare fails immediately.
Trust scores collapse.
Real IP still visible.
Nobody knows which profile owns which port.
Keep marketplace logins on the E-commerce mapping.
Recommended: residential static. Alternative: residential custom for many profiles in one country. Mobile only if the target is m.site.
| Product | Billing | Use it when… |
|---|---|---|
| Residential · Static Recommended | Per IP / period | Recommended — one static residential IP per warm browser profile. |
| Residential · Custom | Per port / period | Alternative — browser farm, many isolated ports, same country. |
Align timezone and Accept-Language.
Dozens of cold or warm profiles.
Both exist — match the browser tool.
Not on warm profiles.
Residential static helps; flags still matter.
That page is OS process routing. This page is the IP inside the browser.
Use mobile proxies, not this static desktop IP.
Static residential per warm profile. Custom ports for farms. Do not rotate checkouts.