Pick the pool for the job
A retail checkout scores the network a request comes from before it looks at anything else, so the pool you buy matters more than how many IPs you spread tasks across.
We do not sell static ISP proxies. A sticky session, which holds one residential IP for up to two hours, is the closest match.
- Residential: IPs from real home connections. Rotates per request by default or holds one IP for up to two hours. The default choice when every task gets its own address.
- Premium residential: a cleaner slice of the same network, and the only pool that bills city, ZIP and ASN targeting at 1× instead of 2×. Pick it when a release is limited to one city or carrier, or when standard residential IPs get flagged on a particular retailer.
- Mobile: 4G/5G carrier IPs shared by many real subscribers, which is why sites are slow to block them. It costs more per GB than residential, so many setups keep it for the checkout step.
- Datacenter: the cheapest and fastest pool, and the easiest for retail anti-bot systems to recognise because the ranges are public. Fine for stock monitors and API calls on lenient pages; do not count on it for a protected checkout.
Rotate for monitors, hold one IP for checkout
By default every request leaves from a new IP, which suits product-page monitors and restock polling. A checkout is different: cart, shipping and payment should arrive from one address, or the retailer sees the visitor change networks mid-order.
Put a session id in the proxy username and the gateway keeps one exit IP for that id, for as long as you set, from 1 to 120 minutes. Give each bot task its own id.
PROXY_USER__cr.us rotating: a new US IP on every request
PROXY_USER__cr.us;sessid.task01;sessttl.30 task01 keeps one US IP for 30 minutes
Match the region of the drop
Many releases are limited to a country, and some retailers show a different catalogue or price by region. Add the country to the username to exit from there.
Narrowing to a state, city, ZIP or carrier works on every pool, but it meters at 2× on all of them except premium residential, which meters it at 1×: a request draws 2 GB from your pack for every 1 GB delivered. Country-only traffic and sticky sessions cost no extra.
Budget the bandwidth before the drop
You pay per GB and a pack never expires, so size it from a test. Run one complete task through the gateway, read that product's usage in your dashboard, and multiply by the number of tasks.
As an illustration only: a task that moves 3 MB across monitoring, cart and checkout means 500 tasks use about 1.5 GB. Your number depends on the retailer and on whether your bot loads images, and blocking images and fonts in the bot is the easiest saving.
Use it in your bot or antidetect browser
Anything that accepts a proxy works: one gateway endpoint over HTTP/HTTPS or SOCKS5, with the username and password from your dashboard. Each product allows up to 2,000 concurrent connections, so a long task list can run at once.
For antidetect browsers there is a setup guide per browser, with the exact fields to fill in.
What a proxy does not solve
The IP is one signal among several. Retailers also look at the browser and TLS fingerprint, request timing, cookies and account history, so a clean IP will not rescue a bot that gets those wrong, and no proxy can promise that a particular retailer or drop will work. Check your retailer against the list of sites the network refuses before you buy.
Use it within our acceptable use policy: ticket-buying bots, fraud and abuse are not allowed.